On Fri, Sep 12, 2008 at 2:13 PM, Frederic Demians <[EMAIL PROTECTED]> wrote:
> > > Would you be actively reviewing many or most patches that are > > submitted, and > > perhaps maintaining a QA Git tree? Or do you see your role more as > > organizing testing or advocating good software development practices? > > Let's set the records straight. I wouldn't be a QA manager in the strict > sense of the term. I neither got the time nor the resources to be so. QA > manager on a project like Koha could be a full-time job. This is clearly > not my proposal which is modestly to give 1-2 hours a day to this > activity. So if QA manager role is to review patches before pushing > them, I'm not the right person. I see him as the person who put an eye > on the project as a whole, at a high level, from a technical and > community perspective, having in mind quality and open sharing between > participants. I could also undertake and coordinate specific activities > like testing and performances improvement. > > So I'd say ingenuously that I'm available and open to give limited (but > valuable :-) time to a QA manager role which has to be defined by the > developers community. Hi all, I feel strongly that a QA Manager should be responsible for facilitating the following tasks: 1. review of every line of code submitted to the project, making sure it conforms to our coding guidelines 2. manually testing the new function, bug fix, etc. 3. doing a reasonable amount of regression testing to ensure that the code doesn't negitively affect other functions within Koha. 4. communicating with patch submitters to ensure open flow of information, letting them know when code doesn't conform to requirements, or when the bug that was claimed to be fixed wasn't, or it creates another bug. Now ... how this is accomplished is up for review, I said 'facilitating' because perhaps a QA Manager can and should assign one or more deputies to do the actual heavy lifting, review, testing, etc., and the QA Manager should certainly also be responsible for overseeing an automated testing environment. However, that automated environment shouldn't substitute for the above listed important tasks that will ensure the quality of submissions and features. -- Joshua Ferraro SUPPORT FOR OPEN-SOURCE SOFTWARE CEO migration, training, maintenance, support LibLime Featuring Koha Open-Source ILS [EMAIL PROTECTED] |Full Demos at http://liblime.com/koha |1(888)KohaILS
_______________________________________________ Koha-devel mailing list Koha-devel@lists.koha.org http://lists.koha.org/mailman/listinfo/koha-devel
