SoC 2008

Proposed Abstract: This proposal aims to create a module that implements the GData protocol specification in Drupal. The Google data APIs provide a simple standard protocol, called "GData", for reading and writing data on the web using either of two standard XML-based syndication formats: Atom or RSS. This module will handle all the basic stuff a developer shouldn't have to worry about when developing modules that extend its functionality such as data transfer, protocol adherence, and authentication. It will expose its own API which will allow other developers to create modules that easily interact with information provided by Google's many service APIs. Using this module, module developers who need access to this information need only concern themselves with what's important: the data.

I like the idea that suggested a theme and module manager for Drupal. I am hoping for some suggestions here. I was thinking about basing my proposal on that, but adding a few things. Administators should not only be able to automatically install new themes and modules, but they should be able to update and remove them as well. I was even thinking that it might be nice to check dependencies, so that one installed module would install all required modules with it.

Suggestions? (Other than "Go home!") ;)

Hi,

I'm interested in taking a part as a student in GSoC 2008. So, here's my idea.

Drupal came with jQuery as its default javascript library. For some user, who uses another javascript library outside jQuery (such as mootools, prototype etc.), this thing often causes any trouble because their script always conflicting with jQuery.

So, i would like to develop a module which is allow user to:

<

ul>

A brief overview of Metalink: "Metalink solves the first problem -- how to find the most speedy way to download a file -- by grouping different download protocols into one protocol. This enables Metalink clients to automatically switch between different mirror servers without explicit user instructions. Not only multiple server information is described but also meta-data (e.g., the location of the server, document tags and license)." Geospatial Semantic Web

Some basic features the information in a metalink can be used for:

The drupal color module, if utilized, is one of the most powerful modules in a theme developer's arsenal for extending their design. I feel that this module deserves attention and has the potential to expand.

As a drupal themer who has experimented with color themes and the color.module internals I have bumped into things that would really improve the coloring experience and the module's power/usefulness.

Hi everyone!

My name is Markus Schanta, I'm a 21 year old Computer Science student from Vienna, Austria and I would love to participate in the 2008 SoC and do some work on the project* modules.

The project* modules provide project management for Drupal sites. Generally projects are assumed to represent software that has source code, releases, and so on. The project* collection of modules (Project, Project issue tracking, and CVS integration) is the largest set of code running on drupal.org besides Drupal core.

Current backup solutions for Drupal, like the backup module, tend to assume the site is kept inactive during backup, to avoid inconsistency problems; then export the DB and files, and archive them somehow, in order to restore the site in the event of a complete data loss.

While this is fine for smaller and less active sites, a better mechanism for bigger sites sould provide the ability to have:

As I have worked with different content management and middleware solutions, one problem I have encountered numerous times, and that I think needs a better solution in drupal, is import and export of data and provision of web services. I think it would be good for drupal to create an import/export framework that would allow drupal developers to make re-usable, sharable import and export modules by implementing PHP objects to a few commmon interfaces and then adding their new import/export type into a central, common import/export module.

This is especially relevant for modern corporate newspapers that need to integrate content from different legacy systems, produce that content, then send it off to a number of different web publishing systems, and then also face the prospect of their systems changing if they are bought or sold. The framework as outlined in the design below could also be a means of implementing REST services (SOAP or XML-RPC would probably require another layer on top of this, though you probably could do it in this framework).

Moved to official ideas list