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.
[UPDATE] Once you've read this entire post and clicked the signup button, put your name into the appropriate section of the Drupal.org D7 Upgrade - QA Testing organization chart.
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!
Comments
awesome! i would like to
awesome! i would like to help! (:
STRAIGHT EDGE // WEB DEVELOPER
Yes!!!
I would love to help. Signed Up
Signinig up!
Signinig up!
Singed Up!!
Excellent ! Signed up...
It would be fun!
Signed up :-)
http://www.MittalPatel.co.in
Tried to sign up and
Tried to sign up and got
"Validation error, please try again. If this error persists, please contact the site administrator."
edit -- worked after i posted this message ;-)
Sign me up too
looking forward to it
All in
Would love to help
Signed up
I would like to be a tester, ¡Signed up!.
Signed up ;)
Signed up ;)
signed up
And I have added my name to a section but I don't see anyone else's names. Is that correct?
i think so :S
i think so :S
STRAIGHT EDGE // WEB DEVELOPER
Still need help?
I just saw this today (signup is cut off) - but can help if you still need it.
also interested but had a
also interested but had a question too. Are there plans to opensource / release drupal.org as an installation profile on drupal.org (very trippy). I think this would be a unique opportunity to give people the guts that are powering drupal.org as this will be an architectural shift to begin with. Having the whole site be a learning opportunity could help improve people's understanding of how the site was able to be built and scaled to meet the demands of the community. Profiler / Profiler Builder could help reduce overhead in accomplishing this
Ex Uno Plures
http://elmsln.org/
http://btopro.com/
http://drupal.psu.edu/
This might give you some
This might give you some insight into Drupal.org -- I don't believe they will ever release a dist simply due to branding, but you never know.
http://drupal.org/node/27367
Even if it was just the make
Even if it was just the make file of public projects used. The more open the better in my mind as I'm building every website/system I make now as a distribution (minus content). It's been critical as a learning piece in meetings and local user groups to make a site that transparent.
Ex Uno Plures
http://elmsln.org/
http://btopro.com/
http://drupal.psu.edu/
I think people are in favor
I think people are in favor of opensourcing everything but the theme.
If you can write some queries to extract the data you need (e.g. system table and variables table to get the right configs) I'd be happy to run them to help you document them in that page laughnan mentioned.
knaddison blog | Morris Animal Foundation
Profiler Builder
http://drupal.org/project/profiler_builder will snag these settings in a format that http://drupal.org/project/profiler understands so that a "distro" could be made very painlessly (at least in terms of just having the pieces in from the export and what to use
Ex Uno Plures
http://elmsln.org/
http://btopro.com/
http://drupal.psu.edu/
What would be the testing procedure for this one?
Senpai et Captains,
Would you have suggestions as to how testers proceed with testing of D7 site? How has it been done in past?
Thanks
You can join a group (there
You can join a group (there are several) as marked in the Google Document and go from there in each specific category. As you find issues (in modules, core, drupal.org theme, etc.) then you can create an issue. If you have questions Senpai can clarifiy or you can contact the QA Captain for that specific subject.
Cheers!
Alex
Elaborate expectation please
I am willing to help the initiative and registered but need help in the form of what needs to be done and what the expectations, guidelines etc.
Hope I have not misunderstood anything.
_
Why did you close signup? I liked to participate on this event. And now there are 192 signed up members. It was good if you allowed 200 members :)
Doubt is the father of invention ... ZendegiyeSabz
I would like to help if you
I would like to help if you are still looking for some more person..
Thanks :)
Wonderful, count me in incase
Wonderful, count me in incase there is need for help
I can help if the you need it still.
I would like to help in testing, review, style all of the above.
If you still need people I'm there with bells on.
Regards,
Leo Jackson