Drupal

When you think twice about the problems you're facing, then you'll realize, yes, you are a leader, too. You won't be able to do everything on your own. But you are able to inspire others to change things. They might only need a little feedback to approach it correctly.

This sort of inspiration is called "mentoring". And, I'd like to turn it into a campaign that everyone can and should participate in. Just (carefully) cherry-pick up to 5 people, who are following you, and ask them whether they'd like to learn a lot more.

The idea behind a content inventory is to determine what content you have and where it lives (the quantitative survey). The content audit is qualitative, where you assess whether it's any good or not, and what needs to change to improve it.

The install script configures the LAMP stack for drupal, installs APC, drush, drush make and sets up a database for our drupal. After this we launch the make file which downloads all needed code for our drupal. Now the script will configure the drupal file system, set up the permissions and copy the drupal install profile and resources.

(Wouldn't have linked, except they also linked to Drubuntu and others so they clearly did their research.)

Mobile application for DrupalCon conferences.

Currently the installer attempts to fake systems in core, like the cache, and actually duplicates a lot of code found elsewhere for module management and what not. Why not simply package a minimal database dump, similar to how the update tests used a Drupal 6 dump written in DBTNG, that can be installed to create an extremely minimal Drupal installation. At that point the installer can act like any other module and provide forms to complete the process.

Taking it old school, but +1.

My list is getting huge, but the following six ideas are always reliable.

Fast Permissions Administration with CTools and Collapsed Fieldsets
...