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