Getting the QA Effort organised

After working over the threads, I have realized that we should probably start by defining the logistics of the team. As always, anything posted here is open to discussion, debate and disagreement. Please comment on as many points as possible. ============================================================ Here is what we already know ============================================================ Why We Exist: ------------ The primary goal for the QA team will be to support the PHP core developers by providing quality assurance. ============================================================ Here is what we must figure out! ============================================================ Who wants to be involved in the core team ------------------------------------------------------------ Could everyone who is prepared to be actively involved with the PHP QA Team please send a confirmation to the list. How to help the QA effort succeed ------------------------------------------------------------ For this to succeed, we have to have a dedicated group of people who make time to consistently work on the QA effort. I know that I personally have difficulty in making time to contribute to the QA effort. I have been thinking that a possible remedy for this is for me to set aside a fixed amount of time per day to work on QA issues. I am prepared to spend 1 hour per day, 5 days per week on the effort. Perhaps some of the experienced Open Source developers on the list could comment on what strategies they use to help themselves find time to work on their Open Source projects. ============================================================ Next Message: Suggested Goals for the PHP QA Team Zak Greant Creative Director Nucleus Information Service Inc. "Always do right- this will gratify some and astonish the rest." - Mark Twain