41 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.


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


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



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

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

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:

Drupal.org content

A project with issue tracker for Drupal.org non-documentation content organization and moderation. This is a place for issues about marketplace listings (services, training and books), case studies, front page promotion requests, planet drupal feeds, etc.

"Content" vs "Webmasters"

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

"Content" vs "Documentation"

For issues with Documentation content please use the Documentation project instead.

What about subsites?

Subsites have own issue queues for problems with their content:

Helping content team

UX tasks

In which we track research, interaction, and visual design tasks for Drupal. Maintained by the UX Team.

The goal is to use the issue queue to maintain an up-to-date and actionable overview of what the UX folk are working on or would like to see happen in the near future.

* This queue does not contain any UI discussions, those are to be found under the Usability tag or in the Usability group.


Drupal Community Working Group

We work on community stuff!

From great community ideas to helping smooth ruffled feathers, the Community Working Group is tasked with stewardship over the Drupal Code of Conduct, and the non-technical, non-code, non-infrastructure sides of the Drupal project.

For more details, see


Drupal Technical Working Group

The TWG's job is to ensure that the necessary policies, procedures, and standards exist to address technical concerns affecting the Drupal community. This includes items that affect all projects, such as the Drupal coding standards, Git repository usage and licensing policies, and Drupal's full-project approval process. The TWG does not necessarily author and maintain these policies itself, but merely ensures that they exist, are well maintained, and that they are successful.


DrupalCI: Puppet Scripts (Modernizing Testbot Initiative)

This sub-project will host the puppet configuration scripts used to build out the various servers which make up the environment.

Visit the DrupalCI main project page for more info.


DrupalCI: Dispatcher (Modernizing Testbot Initiative)


This sub-project is responsible for the scripts and configuration files used on the jenkins master/slave servers which serve as the central job dispatcher for the environment. It is anticipated that this repository will contain xml files of the jenkins job definitions and related scripts for import on the Jenkins server.



Install the required gems with bundler (http://bundler.io/v1.6/bundle_install.html) via:


DrupalCI: Results (Modernizing Testbot Initiative)


This sub-project is responsible for the long-term archival, storage, and exposure of build artifacts and job/test results; similar to the (non-dispatch related) functions performed by qa.d.o today. It is anticipated that this project could end up being a full drupal site on it's own accord, and the repository will include any custom code related to that build.



We use Phing as a build tool for this project. Please install Phing via the following instructions:


[Archive] Drupal.org D7 upgrade QA

This project is archived. This was a place to track bug reports during community testing of Drupal.org D7 upgrade.

Please, do not open new issues in this queue, they won't be addressed.

If you want to report a bug about Drupal.org, search all Drupal.org-related issues first.

If you are absolutely sure there is no existing issue about a problem you want to report, you can create one of the following: