Reminder: Koha project meeting on #koha, 12 September 2008 at 19:00 UTC
Hi, As a reminder, the Koha developers will be holding a meeting on the #koha IRC channel on 12 September 2008 at 19:00 UTC. The agenda is: 1. Confirm the release manager, translation manager, and documentation manager for Koha 3.2. Each of these positions has one candidate at present: Release Manager: Galen Charlton, LibLime Translation Manager: Chris Cormack, Catalyst Documentation Manager: Nicole Engard, LibLime, 2. Decide on the release maintainer for Koha 3.0 The two candidates are currently Joshua Ferraro (LibLime) and Henri-Damien Laurent (BibLibre). 3. Discuss whether the position of Kaitiaki should be filled. 4. Discuss options for filling the position of QA manager for 3.2. 5. Discuss the features planned for Koha 3.2. All Koha users, developers, and other interested parties are welcome to attend. The meeting will be logged, and I will also send a summary to the koha and koha-devel mailing lists. For information about the #koha IRC channel, please see http://www.koha.org/community/irc.html. Regards, Galen -- Galen Charlton VP, Research & Development, LibLime galen.charlton@liblime.com p: 1-888-564-2457 x709 skype: gmcharlt
4. Discuss options for filling the position of QA manager for 3.2.
I volunteer for this role. I am Frédéric Demians. I've been providing solutions and services to French specialized libraries for years with my own company: Tamil. I'm selling now SaaS based on Koha. I have a developer background, having designed and coded in the old good days a pre-ILS from scratch included a search engine with no more than a C compiler and a bitstring algorithm! I'm still conducting developments using different kind of plateforms, FLOSS & proprietary (.NET). I see the QA Manager role as an opportunity to give back to the Koha Community. I conceive Koha QA Manager as a dual position, managing both software and community quality, trying to improve good coding practices and horizontal cooperation between Koha developers/vendors. -- Frédéric DEMIANS http://www.tamil.fr/u/fdemians.html
Hi Frederic, On Fri, Sep 12, 2008 at 4:09 AM, Frederic Demians <frederic@tamil.fr> wrote:
4. Discuss options for filling the position of QA manager for 3.2.
I volunteer for this role.
Thanks for volunteering. I'm wondering if you could describe in a little more detail what you propose to do as QA manager? 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? Regards, Galen -- Galen Charlton VP, Research & Development, LibLime galen.charlton@liblime.com p: 1-888-564-2457 x709 skype: gmcharlt
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. -- Frédéric
Frederic Demians <frederic@tamil.fr> wrote:
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.
I'd like QA to be doing things like building automated brown-paper-bag-error-spotting tools, helping remind us all about the tasks that are falling through the cracks and similar things like that. For comparison, the description of debian's QA is http://qa.debian.org/ Hope that helps, -- MJ Ray (slef) Webmaster for hire, statistician and online shop builder for a small worker cooperative http://www.ttllp.co.uk/ http://mjr.towers.org.uk/ (Notice http://mjr.towers.org.uk/email.html) tel:+44-844-4437-237
On Fri, Sep 12, 2008 at 2:13 PM, Frederic Demians <frederic@tamil.fr> 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.
To me, that level of removal sounds more like a hypothetical Project Manager or historical Kaitiaki. Koha pointedly needs concrete Quality Assurance whether that comes from RM, QA Mgr, group feedback or some combination. The QA Mgr seems like the right place to situate most of that responsibility at the day-to-day level. I suppose we'll get a chance to chat about it here in a few minutes anyway... --joe
On Fri, Sep 12, 2008 at 2:13 PM, Frederic Demians <frederic@tamil.fr> 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 jmf@liblime.com |Full Demos at http://liblime.com/koha |1(888)KohaILS
participants (5)
-
Frederic Demians -
Galen Charlton -
Joe Atzberger -
Joshua Ferraro -
MJ Ray