<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=iso-8859-1"><meta name=Generator content="Microsoft Word 15 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;
mso-fareast-language:EN-US;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=EN-AU link="#0563C1" vlink="#954F72"><div class=WordSection1><p class=MsoNormal><a name="_MailEndCompose"><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;mso-fareast-language:EN-US'>I think this has the potential to create a lot of conflict. <o:p></o:p></span></a></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;mso-fareast-language:EN-US'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;mso-fareast-language:EN-US'>I know the guideline saying that one company shouldn’t sign off its own patches slows things down, but – like Owen – I think it’s an important guideline. While I’m sure no one would abuse the process maliciously, I think a lot of mistakes would probably go unnoticed out of a desire to speed along the process. Even if the tester hasn’t worked on the development, there is an (unspoken) incentive to pass the patch and be less critical than someone from another organization. I think stability is more important than more features. Of course, some recent patches have shown that even our current process isn’t always able to catch all the problems. <o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;mso-fareast-language:EN-US'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;mso-fareast-language:EN-US'>I think Brooke mentioned that we need more people. That’s probably true. If you think about it, more sign offs will mean even more of a burden on QA, which will mean more and more mistakes get through. Of course, I want to volunteer and do more, but I don’t have the time. Where do we stand regarding a patch coming from one company, a different company signing off, and QA coming from the original company? If Bywater and BibLibre add more people to the QA team, and test each other’s patches, that probably could compensate for higher volumes of patches both needing testing and having been tested. Mind you, I suppose the incentive then becomes to test the other company’s patches faster so they test yours faster and maybe the level of criticism lowers again anyway. Maybe we should trust people’s judgement and let more people add sign offs (so long as we’re also adding eyes to QA, I think). <o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;mso-fareast-language:EN-US'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;mso-fareast-language:EN-US'>In any case, I think the main point where conflict will come is in the pointing out of abuse. No one likes receiving criticism. I could easily see rifts forming where one or two companies think that they’re acting within the guidelines but other people think they’re abusing the system. I think it would be awkward to point out such abuses in some cases, and heated or tense in other cases. <o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;mso-fareast-language:EN-US'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;mso-fareast-language:EN-US'>I don’t know. Those are my two cents. I’m the only one at my company involved in the community, so I don’t really have a stake either way. I’m just concerned about stability and overworking key individuals. That said, I don’t have the time to volunteer at the moment. I’ve been too busy to test or contribute patches recently, so I wouldn’t put too much weight in my words.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;mso-fareast-language:EN-US'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;mso-fareast-language:EN-US'>I suppose I’d like to hear from the QA team and former/present/future Release Managers on the subject. If they think they can handle an influx of patches due to companies signing off their own patches (admittedly via different individuals) and potential interpersonal conflict, then I suppose I’m up for it. <o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;mso-fareast-language:EN-US'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif'>David Cook<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif'>Systems Librarian<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif'>Prosentient Systems<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif'>72/330 Wattle St, Ultimo, NSW 2007<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;mso-fareast-language:EN-US'><o:p> </o:p></span></p><div style='border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm 4.0pt'><div><div style='border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm'><p class=MsoNormal><b><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri",sans-serif'>From:</span></b><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri",sans-serif'> koha-devel-bounces@lists.koha-community.org [mailto:koha-devel-bounces@lists.koha-community.org] <b>On Behalf Of </b>Brendan Gallagher<br><b>Sent:</b> Saturday, 11 October 2014 2:10 AM<br><b>To:</b> Koha Devel<br><b>Subject:</b> [Koha-devel] Proposal for a change in guidelines for the sign-off process in the Koha-community<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><div><div><div><p class=MsoNormal>Hello All - <o:p></o:p></p></div><div><p class=MsoNormal style='margin-bottom:12.0pt'><br clear=all>During the hackfest, there was a discussion on the sign-off process for Koha. In attendance was, Nathan, Chris, Katrin, Paul_P, Jonathan, Arnaud, Joy, Brendan, Tomás, Brooke, Tom, and BobB. Here is what we all agreed upon to send a proposal to the next developers or general meeting<br><br>I’d like to put forward a motion for removal of the guideline that one company shouldn’t sign-off on the same company's patches within the community. I am suggesting additional checks be included in the sign-off process to prevent abuse of the proposed guideline, such as the committer and the person signing off must not have collaborated on the development of the patch. We shall review that idea/process every 6 months as an agenda item in the general meeting, to make sure that no abuse of the new privilege has occurred; also note here - that we do not have to wait 6 months to point out abuse of this new privilege. The QA team and Release Team still have the right to ask for more eyes to look at a certain bug at anytime and this should continue.<o:p></o:p></p></div><p class=MsoNormal>Thank you,<o:p></o:p></p></div><p class=MsoNormal>Brendan Gallagher<o:p></o:p></p></div></div></div></body></html>