QA & Testing Team
This team is responsible for finding and resolving bugs in our source code, improving the development process, and making sure that Haiku complies to our own standards and fulfills our users' high expectations.
Getting Involved
This team does not currently have any members. If you are interested in contributing to the QA & Testing Team, please start by sending an email to the Haiku mailing list expressing your desire to do so, and what specific skills you can offer to that end.
Documentation
There is no formal sign-up process. Volunteers just start with helping us and then they automatically become "official" contributors.
For example:
We need help with finding and fixing bugs (see our Trac instance). We would also be thankful for code cleanups and improvements. Just send your patches to the General Mailing List (or Trac) or the developer responsible for the component.
In what form do you want to contribute?
Waldemar,
Would gladly like to get involved... one thing holding me back is getting an actual haiku.image on one of my spare PCs without a little guidance. And though I could offer some of my coding skills to the project, I would prefer to do pure QA testing and maybe analyze some code and get up to speed on the Haiku APIs and the BeOS programming documentation before contributing any real code, though I would like to do that as well.
Hi Dennis,
Thanks for your interest in helping out. The devs don't frequent the forums as mush, so may I suggest that you subscribe and post a message to the Haiku mailing list? You are more likely to get guidance and faster there. :-)
Here is the URL where you can subscribe:
http://www.freelists.org/list/openbeos
Nice to see someone interested in this area of the project!
When and where can you sign up for the QA and Testing team?