42 Drupal.org projects match your search

Drupal.org is maintained by volunteers and the Drupal Association. These projects organize work on Drupal.org itself. For more about how Drupal.org works, see the FAQ.


Subfields is an implementation of core's Field UI that allows you to split a single field into as many sub-fields as you like. It is a lot like Composed Field, but each value is stored as a text string so it is searchable and available to Views.

You can configure each sub-field type as if it were literally a single field. This module only supports select list and textfield input boxes. But is also provides a regex validation handler to validate that appropriate data is provided.


jQuery Autosize

jQuery Autosize example


Allows text areas to automatically resize as rows of text are added.

Uses the jQuery Autosize library found here: http://www.jacklmoore.com/autosize/


jQuery 1.7+ in Chrome, Firefox 4+, Safari 5+, Internet Explorer 6+, Opera 11+.


Download from here: http://www.jacklmoore.com/autosize/


Watchdog JS Errors

A simple module to save Javascript errors in watchdog.

Configure user permissions in Administration » People » Permissions: Save js errors in Watchdog



Bluecheese is the redesigned Drupal.org theme. The theme must be implemented in accordance with the new Drupal.org style guide (also see the original style guide from the Mark Boulton redesign), Markup guide, and CSS guide.

This theme is only for use on official Drupal.org sites. Do not use this for businesses, local groups and other sites, which should have their own brand and identity. Questions and comments about use of this theme should go to the Drupal Association.

Access to this theme is restricted to redesign implementers team. Drupal community members who wish to work on improving the theme are able to get access to the private BZR repository so they can make patches for this issue queue.


See Contributing to Bluecheese theme for an introduction to getting involved.

Templates & function overrides


Drupal.org webmasters

A project with issue tracker that you can use to report spam, broken links, or user account problems on Drupal.org website.

"Webmasters" vs. "Content"

Issues related to non-documentation website content, such as case studies, marketplace listings, Planet Drupal feeds, front page posts etc. belong to the Drupal.org content project. There is a separate project for Documentation content.

"Webmasters" vs. "Infrastructure"

If you want to report a problem with the Apache and MySQL installation on drupal.org, the Mailman mailing lists, the Git repositories, and the various Drupal installations on the drupal.org domain, please use the Drupal.org infrastructure project instead.

What about subsites?

Most subsites have own issue queues:

If a sub-site is not in the list above, you can use the queue here to report problems.

Helping as a webmaster


This is the main project for all Drupal documentation. To learn more about helping with documentation efforts, start with the Contribute to documentation section of the handbook.

Drupal.org infrastructure

An issue tracker for everything related to the Drupal.org servers. This includes the Apache and MySQL installation, the Mailman mailing lists, the Git repositories, and the various Drupal installations on the drupal.org domain.

If you want to report spam, broken links, or user account problems, please use the Drupal.org webmaster's issue tracker instead.

Test driven development infrastructure

NOTE (May 20/2012): Testing infrastructure Issue queue is currently being monitored over at the "Testbot" project page.

A project to manage the infrastructure for test driven development of Drupal core and contributed modules. This project extends work supported by Boris Mann and implemented by Moshe Weitzman.

This project is now live and reporting on automated test results: http://testing.drupal.org/tests

It is based on work funded by the Google summer of code project for test automation. Mentored by Thomas Ilsche and Rok Zlender during 2006, and 2007 respectively. Implementation of automated testing has been led by Rok Zlender, with support from Kieran Lal, and Robin Monks. Robin's work is based on his work with the quality project for Mozilla.

Moshe and Rok's work:

Robin's project demo: Drupaltestbed
freshen.php - Brings drupal source from CSV, runs install of the new drupal checkout.

action/install.php - Simpletest script for running the install script.


Drupal.org CVS applications

This project is obsolete.

Create an issue for http://drupal.org/project/projectapplications instead following the full project application instructions.

The Great Git Migration

This project is purely a container for issues pertaining to Phase 2 of the Git Migration. Mostly, this is here so that issues that don't have a specific home in other modules can avoid squatting in the infrastructure queue.

Drupal.org Project applications

Drupal code review logo

This project is the place to post applications for ability to create full projects.

For more information, see Applying for permission to create full projects.

Maintainers can immediately add co-maintainers to a project without going through an application process by granting Write to VCS privileges on the Maintainers tab. The co-maintainer will need to agree to the Drupal contributions repository usage agreement before they will be able to write to the repository.

Review bonus


Git on Drupal.org

This issue queue began as Git Migration Community Testing to collect and triage issues uncovered during the 'git phase 2' community testing period. Now that the Git migration is live, we will continue to use this queue for support. Issues may be moved to the queue of one of the 12+ modules that comprise the Git system when necessary.

When you report an issue here:



This project builds the debian packages (drupaltestbot, drupaltestbot-mysql, drupaltestbot-pgsql, and drupaltestbot-sqlite) used to deploy a testbot in the Drupal.org testing infrastructure.

To deploy new code as a part of a package:

  1. Test and commit code
  2. Log into https://drupaltesting.org/jenkins/ (See DamZ for privileges; this will eventually be on Drupal.org infrastructure.)
  3. Build infrastructure-package-build

This does the following actions (so you can build the packages manually for testing):

rm *.deb || true

cd drupaltestbot
debuild -b -uc -us
cd ..

cd drupaltestbot-mysql
debuild -b -uc -us
cd ..

cd drupaltestbot-sqlite3
debuild -b -uc -us
cd ..

cd drupaltestbot-pgsql
debuild -b -uc -us
cd ..

# Only copy new .deb files, so that we don't override packages that haven't changed version.
rsync --ignore-existing *.deb /var/www/packages/pool/main

Related repositories: drupaltestbot-puppet, Project Issue File Review, Project Issue File Test


This contains the puppet scripts used to deploy testbots in the Drupal.org infrastructure.

To deploy new code:

Drupal.org Library Packaging Whitelist

If you're an installation profile/distribution author who needs to include an external library in your project:

  1. First, check to see if your library is already included in the list of existing whitelist entries. If so, you're set; nothing to do here! (Please note that until Drupal.org is upgraded to D7 you will need to manually browse the existing whitelist entries)
  2. If the library is not listed, please search the existing queue to see if someone has already requested that library.
  3. If the library has not been whitelisted or requested, ensure the library meets all criteria for inclusion in the whitelist and verify that the license of all files in the library are GPLv2 compatible.
  4. If all the criteria are met, create an issue to request it. The issue should include the following:
    • A link to the library itself (the library's home page, or the project page on GitHub, etc.).

Drupal.org Testbots

This project is a place for issues to be filed or questions to be asked about the Drupal.org testbots and all the projects related to them. Since there are so many d.o projects involved it seems that most people just need a one-stop shop for issues. They can be moved out from here.


Drupal Association

The Drupal Association is an educational non-profit organization that tasks itself with fostering and supporting the Drupal software project, the community and its growth.

This issue queue is deprecated.

For questions, discussions, policy changes, and other items please use Drupal Association Group

Drupal.org drush

User-facing drush commands that are specific to the Drupal.org site.

Currently, this includes the extensions to drush make that are used by the Drupal.org distribution packaging system. They live here as a separate project to make it easy for potential distribution maintainers to get this additional validation code so they can ensure that their distribution .make file is valid for the Drupal.org packaging system.


Drupal Community Governance

This project was formed to work together on the Drupal community's governance process and structure and policies. If you're interested in specific issues regarding governance, take a look in the issue queue and add more if you'd like.

The repository holds a collection of charters relating to Drupal community governance working groups, as well as a place to hold discussion about said policies. These charters are currently solely maintained by Dries Buytaert. Other governance policy documentation can be found at About Drupal: Governance.


For the Drupal project, we are working towards developing a number of working groups related to various aspects of the community (security, documentation, conflict resolution, Drupal core, etc.), with Dries Buytaert as the final decision-maker:

Drupal project governance consists of Community Working Group, Technical Working Group, Security Team, Documentation Team, and a Working Group per major Drupal core version.


Drupal.org BDD

Doobie is the home of Drupal.org Behavior-Driven Development. Tests are specific to D.O. See the Drupal Extension to Behat and Mink if you're looking for a tool to assist in testing Drupal sites in general.

Software requirements to run tests:

This project requires the following, installed on the system running the tests. If you don't set these up, see the error messages you'll get at http://drupal.org/node/1783000

Set up instructions:

  1. Clone this repository
  2. In the repo root, install Composer, a PHP Dependency Manager:
    curl -s http://getcomposer.org/composer.phar > composer.phar
    wget -nc http://getcomposer.org/composer.phar
  3. Run the composer install command:
    php composer.phar install
    Note: This takes a little while before you start seeing any output.


Conflict Resolution

This project is a place for resolving conflicts in our community. More information to follow.

A discussion of how we may use this project is in #1493430: [meta] Develop a conflict resolution process for community issues .


BAM Infrastructure

Project of the Branding and Marketing committee.

BAM infrastructure: organizing the Drupal Branding and Marketing Committee, tools and processes.

Other BAM projects:

BAM Research

Project of the Branding and Marketing committee.

BAM research: [TBD]


  1. Ongoing market research to verify target audiences or change them based on the outcome of the research.
  2. Competitive research
  3. Quick Review of D.o Marketing Message

Other BAM projects:

BAM Branding

Project of the Branding and Marketing committee.

BAM branding: [TBD]


  1. Audit on Drupal Marketing Material
  2. Improve DrupalCamp Visibility

Other BAM projects:

BAM Mission

Project of the Branding and Marketing committee.

BAM mission: helping the Board to achieve its mission of growing the Drupal community


  1. Promoting the activities of the Drupal Association
  2. Drive Attendance to Global Training Days
  3. Drive DA Memberships
  4. Selling DA Memberships at the Camps

Other BAM projects: