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