Haiku QA team: looking for volunteers!
This post is a followup to post: http://www.haiku-os.org/community/forum/dedicated_haiku_qa_testing_team
So I am currently trying to assemble a QA team for the Haiku project which will be tasked with attempting to implement a QA process that would hopefully drive quality standards within the Haiku project. Currently, there is no dedicated QA team to oversee the testing process that would include a formal QA process for Haiku development.
The misson is simple: to establish a formal QA process (and test cycle) which is complimentary to the Development process without impeding on the efficiency and effectiveness of the current and future development and release cycles.
Things to consider getting done (in no particular order)...
Most of the things listed above will take time to get done and mature. And some of the things listed are probably not the most fun to do as it can be a lot of digital paperwork (so-to-speak).
I can assume some folks interested in being a part of the Haiku QA team already have some QA/testing experience, do QA/testing for a living or just like to break things (with QA/testing) and so the best team in my mind is one that has folks with different talents and strengths that harmonize well. Now for me, I'm no QA lead for this endeavour, I plan to be in the trenches with everyone else and I'd like to bring together people who simply desire to push and advocate for quality in everything that is Haiku and we help each other manage the whole QA process that we have established and agreed on. We all want Haiku to be the best operating system on the planet and the Haiku Dev team can only do so much (when not coding); so for us folks who can't help out with coding can certainly drive the QA/testing aspect of the project and maybe be the loud and proud voice of the Haiku end-user when it comes to driving quality.
If anyone is interested, please give a shout out here and maybe this thread will be a starting point going forward.