Community Proposal

I'd like to make a suggestion for a new module, that makes it easier to create template/theme overrides, without having to manually create syntactically correct .tpl filenames and content.

The problem

Overview: Formbuilder which allows users to build forms by simply dragging and dropping fields. Is in need of a port to Drupal 7, plus quite some adjustments to make it work better.

Description:Formbuilder has long been seen as the interface that CCK UI should be. However given the complexity of this module and the interaction its trying to solve - few have worked on it. It originated out of the 2008 GSoC program, and I hope to spur it new live with this years program.

Drupal.org Formbuilder project

Overview:
There is so much content in the Internet that its availability becomes its own problem, we still need to manually extract information from each content. Sure there's a lot of ways this is being addressed like use of meta data, tags, web semantics, micro-format but it only yields data. As example, a news article has headline and title; its tagged and categorized. We used web semantic analysis and find Persons, places, events and etc. Still we dont know anything really about it, how does the mentioned persons related to the places and events. Where they on it or referring to it? How about answering "Is the article a good or bad news?" To whom is it good to and by what degree?

I think a central field management module would benefit many other modules. Currently CCK allows adding custom fields for a content type. It's not very easy to re-use these fields with a custom module.

For the same if a module could provide a central field manager, and other modules can utilise these fields by way of some API, that would be great.

Overview: Drupal Commerce is a fresh implementation of the Ubercart feature set on Drupal 7 using fieldable entities to the max and depending on Views and Rules. What a product is has been separated from how a product is displayed (see this thread for more details), and the attributes system has been completely redone to work through fields on product types and enforce unique SKUs for every variation of a product. While greatly improving the underlying data model, this adds to the complexity of listing products for sale, especially when closely related products need to be sold through the same display (i.e. multiple sizes of a particular t-shirt style). This project will take advantage of the field settings for fields on product types and Token patterns to create bulk product generation forms and enhancements to the Product Reference field and its Add to Cart form display formatters to present these products for sale.

Overview

the Drawing API is an API module that allows developers to define vector graphics in a structured array format (resembling the Forms API). It was aimed at bringing SVG display closer to developers, taking over the rendering part so that graphics can be created more easily.

Description

My idea is about having a unified payment api for Drupal. It useful for site which does not need e-commerce features but need some kind of payments from members like subscriptions based membership, paid nodes, donations,... etc.
Currently what we have is support for either specific gateway, or we need to install e-commerce modules get these functionality.

Here is project idea related to rules (for drupal 7) an interested student could pick up.

Currently rules follows a naive approach for evaluation rules, thus each rule and its conditions are check sequentially as specified. However when rule bases get big it would make much sense to optimize the evaluation of the rules. As something like the RETE algorithm doesn't apply to the module, I think the best thing to do would be reordering the rules in a decision tree, thus each condition is only checked once. A rules are already prepared and cached for evaluation, we could plug into this preprocessing step without hassle.

Something I always wanted to do but never found the time for is creating an install profile for Drupal that would install a ready-to-go forum that is similar to what you get if you install a forum software like PHPBB. I found that many webmasters use PHPBB just because it is easy to set up, even if they know that they want to integrate more functionality that is difficult/impossible to realize with a dedicated forum software.