A field class to support dimensions. The following three modes are supported:
Area (width and height)
Volume (width, height and depth)
The module comes with two formatters where the dimension values either get displayed as a table with each value of the dimension in a new row or as a single line with the initial(s) of the dimension components as the label(s).
Opigno Audio App
Allows users to add audio files to Opigno.
Creates a new Opigno tool "Audio Files", a new field type opigno audio that extends the file field type, a new field formatter using audiojs as well as a new content type "Audio".
The content type is set as an Organic Group content and a display view is also created.
It is like the Infrastructure and Webmasters queues but is specific to groups.drupal.org. So, where people used to enter things into those queues with a Component of groups.drupal.org they can now enter them here.
This is also a place to report spam, account problems, or other issues with Association.drupal.org website, as well as suggest ideas and improvements. It is like Webmasters and Content projects, but specific to association.drupal.org.
You can also report spam or other problems with Drupalcon websites here.
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.
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 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.
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: