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.
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.
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.
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.
This project is like the Infrastructure and Webmasters queues but is specific to localize.drupal.org. So, where people used to enter things into those queues with a Component of localize.drupal.org they can now enter them here.
It might also serve as a repository for custom code on localize.drupal.org in the future.
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.