Want to help QA drupal.org running on D7?

The Deal

It's time to start testing, poking, and prodding at the bigger, better pasture that will become our new home! Yes, that's right, this is the call for curious QA testers for drupal.org's new D7 goodness!

Click that sign up button if your interested in helping, perusing, or pointing out flaws. Especially the last part. We're looking for people to A/B the new site against the current D6 production site and find all the spots we've missed.

How It Goes Down

This is the way our Drupal 7 quality assurance ideal is envisioned to work: First, we need QA Section Captains for each aspect of drupal.org. These go-to volunteers will spend 5-10 hours of their week helping other volunteers to get familiar with the method of testing one particular section of the site, reviewing the bug reports logged by their volunteers, and relaying questions to the drupal.org project manager whenever needed.

There are 13(?) parts of the site to account for:

01. User login & user profiles & member directory
02. The Community:
- Help forums (support)
- Mailing lists
- Getting involved
- Chat
03. Documentation pages
- Installation guide
- Administration guide
- Community documentation
04. The Marketplace
05. Support for the Drupal software
- IRC instructions
- Other languages
- Books
- Professional services
- Drupal training
* NOT the forums
* NOT the community documentation
06. Support for the drupal.org website
- Spam management
- Site content issues (part of the project_issues section)
- Site functionality issues (part of the project_issues section)
- Learn more about drupal.org
07. Download & Extend
08. Projects
09. Project Issue queues
10. Project Issues
11. Git repositories
12. Git sandboxes
13. Search
- Sitewide search
- Project Issue queue search

During Week One, the QA Section Captains will undergo training in order to familiarize them with way the new site functions, where stuff is, what's changed, and what's not been changed. We'll also cover the way new bug reports should be created, how those issues get triaged, and how the various Upgrade Teams will be accepting the bug reports, tracking & fixing them while integrating with our new Behavior Driven Development system (yay!), and closing them. Once each of the QA Captains have a handle on things, it'll be time to open the floodgates and get everybody testing things together!

During Week Two, we'll need a flock of excited, motivated volunteer QA testers! Oh, wait, we already have that! Each volunteer will need to choose a section of the site and align themselves with the respective QA Captain, and we'll all start testing the Drupal 7 site together, reporting bugs, and if desired, posting patches too. Once the entire site has been poked and prodded, and all the bug reports are filed, fixed, possibly BDD'ed, deployed, and closed, it'll be time to flip the switch on our new D7 home!