Drupal.org

Groups.drupal.org

This project has two purposes.

1. It is like the drupal.org customizations project to hold site specific code.
2. 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.

Association.drupal.org

This project holds site specific code for association.drupal.org.

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.

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:
http://drupal.org/project/simpletest
http://drupal.org/project/simpletestauto

Robin's project demo: Drupaltestbed
Components:
freshen.php - Brings drupal source from CSV, runs install of the new drupal checkout.

action/install.php - Simpletest script for running the install script.

Bluecheese

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.

Contributing

See Contributing to Bluecheese theme for an introduction to getting involved.

Templates & function overrides

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:

• Look for duplicate issues before writing yours
• Include your Git access status
• Describe precisely what you were trying to do
• Include the exact text of any error messages
• Provide the steps to reproduce the problem
• Do provide screenshots where they're helpful

Localize.drupal.org

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.

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: Develop a conflict resolution process for community issues .

Drupal.org BDD

Doobie is the home of Drupal.org Behavior Driven Development.

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

• PHP 5.3: http://php.net/ (Make sure curl extensions are available)
• Git: http://git-scm.com/downloads/ (for Git tests)
• Expect: http://expect.sourceforge.net/ (for Git tests involving password auth)
• Java (for selenium)
• Selenium Server (formerly the Selenium RC Server): http://seleniumhq.org/download/

Set up instructions:

1. Clone this repository
2. In the repo root, install Composer, a PHP Dependency Manager:
   curl -s http://getcomposer.org/composer.phar > composer.phar
   OR
   wget -nc http://getcomposer.org/composer.phar
3. Run the composer install command:
   php composer.phar install
   Note: This takes a little while before you start seeing any output.
4. Copy behat.local.yml.example to behat.local.yml, making sure you're pointed at the base host you intend. You'll use this file to store settings that reflect your local environment, credentials, and other settings which don't belong in the repository.
   

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.org Library Packaging Whitelist

If you're an installation profile/distribution author who needs to include an external library in your project:

1. Check to see if your library is already included in the list of existing whitelist entries. If so, you're set; nothing to do here!
2. If not, please search the existing queue to see if someone's already requested it. Please note that until #1706506: Packaging whitelist URLs page - Search does not yield any results is resolved you will need to manually browse the list.
3. If not, verify that the license of the library is one of the following: GPL v2 and later, LGPL v2 and later, (any of these GPL V2 and later-compatible licenses).
4. If so, check to ensure the library meets the criteria for inclusion in the whitelist.
5. Once these criteria are met, please create an issue to request it. The issue should include the following:
   • A link to the library itself (the library's home page, or the project page on GitHub, etc.).

DSWG

Placeholder for the proposed Drupal.org software working group.

Drupal.org Testbots

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.

Frequently Asked Questions

• How do I enable automated testing for my project? On your project, Edit->Issues->Enable automated testing checkbox. (docs page) (issue)
• Why is my patch marked "postponed"? Most of the time this is because the branch you're testing against hasn't passed tests. Follow the "branch" link on the qa.drupal.org page explaining that your patch is postponed and you'll see the status of branch testing. Usually some work is required on the branch (and tests won't succeed without new commits).
• Why does my test fail on the testbot but works OK locally? There are probably three key differences between your local test environment and the testbot
  • The testbot is running php 5.3.10 (from dotdeb)
  • The testbot has clean URLs turned off by default (as does Drupal)
  • The testbot webroot is in a subdirectory (like http://drupaltestbot.osuosl.test/checkout/?q=admin)

Drupal Community Governance

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.

Overview

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:

Drupal.org Project applications

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

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

• The Drupal Project code of conduct
• Drupal CWG Governance
• Drupal-CWG Charter

We're using this Drupal project tracker to log and follow up on community issues.

Drupal.org site upgrade QA

Overview

This is the canonical place for reporting and tracking all Drupal.org bugs during a site upgrade from one core version to the next (e.g. D6 to D7).

This project will be used in the QA phase of the Drupal 7 upgrade.

Instructions for submitting a new bug report

Step One

SEARCH this issue queue. Please *do not* submit a new bug report until you're 99% sure there is not another issue in here that deals with the problem you've found.

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.

Since Phase 2 is now complete (we're on Git, buh-bye CVS!), this project is now purely historical. No new issues should be filed here - file them against Git on Drupal.org instead.

SupportDO

**A place for the Support Team to sync up our work on the initial support.drupal.org build while we sprint.**

Current roadmap:

Must-have features for initial launch:

• #1122202: The ability to post and answer questions
• #1122204: The ability to post short comments on answers and questions
• #1122208: Some sort of points tracking
• #1122212: The ability to vote questions and answers up or down. (What about comments?)
• #1122216: The ability to close or merge questions that are off-topic or duplicates
• #1122218: The ability to tag questions by topic and Drupal version so that people can follow exactly the content that interests them
• #1122222: UI feature that will suggest possible duplicates as the question is typed.
• #1122198: Filter to make linking to drupal.org nodes faster/easier
• #1122230: The ability to flag content for moderator review.

*Theming will be handled after major functionality has been added, but before any beta launch.

Wish list features for initial launch:

• #1122232: Solr integration for suggestions and search.
• #1122234: Suggest tags based on content
• #1126048: Add {username}.user support to dopl?
• #1129652: Find a way to link to api

Post-launch priorities:

• #1122238: Posti-launch UI improvements
• #1122240: Base privileges/moderator abilities on rep?

drupaltestbot

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

Related repositories: drupaltestbot-puppet, Project Issue File Review, Project Issue File Test

drupaltestbot-puppet

This contains the puppet scripts used to deploy testbots in the Drupal.org infrastructure.

To deploy new code:

1. Test and commit your code.
2. ssh root@drupaltesting.org (See DamZ for permissions. Eventually this will be on drupal.org infrastructure.)
3. cd /etc/puppet
4. git pull drupal master

Related repositories: drupaltestbot-puppet, Project Issue File Review, Project Issue File Test
Related documentation: Automated Testing Infrastructure and How to deploy a testbot

This was originally forked from http://github.com/damz/drupaltestbot-puppet

pifr_setup script: Set up QA testbots

This is the script which was formerly used to deploy testbots on http://qa.drupal.org. It's the pifr_setup script forked from http://github.com/scor/pifr_setup.

Current setup instructions instead: How to deploy a testbot

I don't think we'll end up using this again, but we might, so it's here for reference. But we may revamp this.

Currently we're manually doing a couple of the steps in this process:

1. apt-get update
2. apt-get install puppet
3. Set the hostname to some_descriptive_hostname-mysql.
4. In /etc/hosts, set that hostname to the primary interface IP address.
5. puppetd --test --server puppet.damz.org
6. gzip -dc /tmp/drupaltestbot.sql.gz | mysql drupaltestbot
7. Put your pubkey in ~/.ssh/authorized_keys
8. Connect to the website and configure at admin/pifr/configuration and connect it up to qa.drupal.org
9. Enable the testbot to confirm it.

DrupalCon Denver 2012 Website

That's right! The official issue queue of the DrupalCon Denver 2012 Website.

• Live site: http://denver2012.drupal.org
• Dev site: http://denver2012.staging.devdrupal.org/ (u:drupal/p:drupal)

Purpose

Our aim is to use a Drupal.org sandbox for this site in an effort to use the ticket tracking system and for maximum visibility to the community, the Association, and for future teams building out DrupalCon websites. We'll be using COD as our base installation and customizing from there. So the first thing to help out doing is upgrading COD to Drupal 7. Go help!

Documentation

We are coordinating our documentation within the Association's Open Atrium website. There you can find any official documentation, high level metta discussions, environment details and credentials. If you need access, please ask in #drupal-colorado

Participation

If you would like to help build out this website, here's how you can become part of our team:

1. Google volunteer signup http://tinyurl.com/4x8lqjk (if you haven't already)
2. Open up an issue requesting to be part of the team. Subject: Membership

Nagios Testing Project (new)

This is a dummy project used only for nagios monitoring. And yes, before long the commits will be ignored from the commitlog. See #1113660: Blackhole specific commits (by user or by project)

Interface improvements for groups.drupal.org

Student proposal for GSoC 2011:

Improvements to groups.drupal.org interface.