Community Idea

Overview: Drupal Authenticated User Scalability

A module that will include capabilities to upload files (both images and documents via same interface), create/browse sub-directories, provide access to uploaded files by roles and integrate with new http://drupal.org/project/wysiwyg better than existing modules (IMCE, ImageAssist and others)

Overview:
Enhance the taxonomy system with node functionality like: Author, Timestamp, Status (Published, ...)

Description:
According to the old discussion that "Everything is a node (users too)" this will help in a lot of common (to be solved) problems.
Hav e alook at Everything is a node discussion, especially:
Why taxonomy:

* The taxonomy builder becomes a streamlined interface to both build a tree of terms (nodes) and select an item from that tree to classify a node
* Both the tree and each classification can be designated using relationships
* All the taxonomy storage and retrieval functions can be encapsulated by the relationship API

Mentors:

• narres - will help with defining todos

Difficulty: medium

Google Apps have an API for adding users, it would be very useful to be able to setup users directly from Drupal.
A similar thing has been done for moodle : http://code.google.com/p/moodle-google/, so Drupal shouldnt stay behind :-).
If it sounds too easy, we might add integration between spreadsheets and CCK contents (to be able to publish "structural data" on a drupal site just by entering them into a google spreadsheet of the same structure).
Maybe this other one could stand as a project itself ?

Overview: Make integration of version control systems with Drupal rock, and at the same time help out a module family that's going to be running on drupal.org soon.

Description:

drupal.org has great integration with CVS, including stuff like a commit messages page (which can also be viewed separately for each project), CVS account management, commit restrictions provided dynamically by the website, or automatic packaging of release tarballs just by specifying the CVS tag when creating the release node. All of that makes drupal.org an immensely powerful and easy to use platform for managing Drupal projects in CVS. As a downside though, all of that works only for CVS, and the fact that it doesn't cope with other version control systems is one major reason that drupal.org is still sticking with CVS all the way.

Version Control API was born as a Summer of Code project (the logs!) in 2007, and aims to provide version control integration for Drupal while not depending on any specific version control system (VCS), and being flexible enough for usage on sites other than drupal.org.

A number of solutions are springing up for deploying site configuration (spaces, patterns, etc). And solutions are starting to spring up around deployment of custom sites as well - the Aegir project and the Domains module both provide tools for pushing out multiple sites on a single infrastructure.

NOTE: This idea is strictly about displaying calendar data, not managing or storing such data.

Create a comprehensive calendar display module with the following features:

1. Allow for multiple calendar feeds of different types to create a merged calendar display output.

   a. auto sort and arrange multiple events within each day-cell. Include features to deal with conflicts in multiple calendar feeds. Include features to deal with event displays overflowing a given day-cell.

For more information, see http://drupal.org/project/image_overlay

Project page is http://drupal.org/node/236461

Official ideas list address is http://drupal.org/node/236135