<div>I think fractures have to be taken on a case by case basis. They can actually be healthy things in some cases and I can certainly mention some FLOSS projects where they were good things. Some come back and benefit the core project down the road. So, I'm not inclined to say "forking bad." There can be very good forks. Now, the question to me becomes do we want to do anything about KCLS's whatever they're doing, fork or otherwise. First, we would have to say we're singling them out but we seem to have passed that milestone already. I personally would like to see them share whatever they have discovered. I have repeatedly asked for that as an individual. I think there is a moral obligration to do so and maybe even an ethical one. If the board wanted to take a stance that projects forking code should redistribute their changes and share what they have learned I would support that but with the caveat that it wouldn't be a legal position. <br /><br /></div>
<div> </div>
<div> </div>
<div class="replyBody">on Mar 04, 2014, <b>McKinney, Elizabeth</b> <emckinney@georgialibraries.org> wrote:<br />
<blockquote class="email_quote" style="border-left: 2px solid #267fdb; margin: 0 0 0 1.8ex; padding-left: 1ex;">
<div style="font-family: times new roman,new york,times,serif; font-size: 12pt; color: #000000;">Rogan and all, <br /><br />More than code and licenses, I think the EOB needs to consider if it will take on a role addressing fractures in the community. And if so, how?<br /><br />Elizabeth<br /><br />
<div><span name="x"></span>Elizabeth McKinney <br />PINES Program Director <br />Georgia Public Library Service <br />A Unit of the University System of Georgia<br />1800 Century Place, Suite 150<br />Atlanta GA 30345<br />404.235.7141<br /><a class="parsedEmail" href="mailto:emckinney@georgialibraries.org" target="_blank">emckinney@georgialibraries.org</a><br /><a class="parsedLink" href="http://www.georgialibraries.org/" target="_blank">http://www.georgialibraries.org/</a><br /><br /><br /><br /><span name="x"></span></div>
<br /><hr id="zwchr" />
<div style="color: #000; font-weight: normal; font-style: normal; text-decoration: none; font-family: Helvetica,Arial,sans-serif; font-size: 12pt;"><b>From: </b>"Rogan Hamby" <<a class="parsedEmail" href="mailto:rogan.hamby@gmail.com" target="_blank">rogan.hamby@gmail.com</a>><br /><b>To: </b>"Elizabeth McKinney" <<a class="parsedEmail" href="mailto:emckinney@georgialibraries.org" target="_blank">emckinney@georgialibraries.org</a>><br /><b>Cc: </b>"Galen Charlton" <<a class="parsedEmail" href="mailto:gmc@esilibrary.com" target="_blank">gmc@esilibrary.com</a>>, "Oversight Board" <<a class="parsedEmail" href="mailto:eg-oversight-board@list.evergreen-ils.org" target="_blank">eg-oversight-board@list.evergreen-ils.org</a>><br /><b>Sent: </b>Tuesday, March 4, 2014 10:00:05 AM<br /><b>Subject: </b>Re: [Eg-oversight-board] EOB meeting at the conference<br /><br />
<div dir="ltr">Has the code they have produced been publicly released? I'll be honest, without a public release of their changes I don't feel confidant in any description of their efforts as a fork, spork or anything else. I've several times asked for them to share their work with the community and essentially been told that it's not the kind of thing that translates, it's a case by case optimization. That's pretty vague and not disputable from the outside.
<div> </div>
<div>Evergreen is released under the GPL which doesn't require that changes be distributed, only that if they are that they are distributed under certain terms. In fact, in a sense, the GPL is permission to fork.</div>
<div> </div>
<div> </div>
</div>
<div class="gmail_extra"><br /><br />
<div class="gmail_quote">On Tue, Mar 4, 2014 at 9:52 AM, McKinney, Elizabeth <span dir="ltr"><<a class="parsedEmail" href="mailto:emckinney@georgialibraries.org" target="_blank">emckinney@georgialibraries.org</a>></span> wrote:<br />
<blockquote class="gmail_quote" style="margin: 0 0 0 .8ex; border-left: 1px #ccc solid; padding-left: 1ex;">
<div>
<div style="font-size: 12pt; font-family: times new roman,new york,times,serif;">Galen and all, <br /><br />I would like to add an agenda item to the upcoming EOB meeting. While I know that we will need to develop our agenda for the community update, we as a group should consider how to handle forks in the Evergreen code. <br /> <br />From the KCLS Director's Report, February 2013 : <a href="https://www.kcls.org/about/board/2013/02262013/directorsreport.pdf" target="_blank">https://www.kcls.org/about/board/2013/02262013/directorsreport.pdf</a><br /> In light of what appears to be a fork in the code, that brings up a few questions for discussion: <br /><br />Does the EOB have a role in attempting to prevent forks in the code? <br />Should the EOB chair convene a group to contact and work with anyone intending to fork? <br /> If a fork occurs, should we monitor the situation for cases of copyright/trademark infringement? We would assume they would contribute their code back to the community or change the name of their product. <br />
<div style="font-size: 14.72px; font-family: sans-serif;" dir="ltr"> </div>
Elizabeth
<div><br /><br /><br />
<div><span></span>Elizabeth McKinney <br />PINES Program Director <br />Georgia Public Library Service <br />A Unit of the University System of Georgia<br />1800 Century Place, Suite 150<br /> Atlanta GA 30345<br /><a href="http://tel:404.235.7141" target="_blank">404.235.7141</a><br /><a class="parsedEmail" href="mailto:emckinney@georgialibraries.org" target="_blank">emckinney@georgialibraries.org</a><br /><a href="http://www.georgialibraries.org/" target="_blank">http://www.georgialibraries.org/</a><br /> <br /><br /><br /><span></span></div>
<br /><hr /></div>
<div style="font-size: 12pt; font-style: normal; font-family: Helvetica,Arial,sans-serif; text-decoration: none; font-weight: normal;"><b>From: </b>"Galen Charlton" <<a class="parsedEmail" href="mailto:gmc@esilibrary.com" target="_blank">gmc@esilibrary.com</a>><br /> <b>To: </b>"Kathy Lussier" <<a class="parsedEmail" href="mailto:klussier@masslnc.org" target="_blank">klussier@masslnc.org</a>><br /><b>Cc: </b><a class="parsedEmail" href="mailto:eg-oversight-board@list.evergreen-ils.org" target="_blank">eg-oversight-board@list.evergreen-ils.org</a><br /> <b>Sent: </b>Monday, March 3, 2014 4:56:17 PM<br /><b>Subject: </b>Re: [Eg-oversight-board] EOB meeting at the conference
<div>
<div class="h5"><br /><br />Hi,<br /><br />7:30 a.m. on Thursday is fine with me, as is doing it at lunch.<br /> <br />Regards,<br /><br />Galen<br /><br />On Mon, Mar 3, 2014 at 12:17 PM, Kathy Lussier <<a class="parsedEmail" href="mailto:klussier@masslnc.org" target="_blank">klussier@masslnc.org</a>> wrote:<br />> Sorry folks. I wasn't thinking clearly when I wrote this last e-mail (or the<br /> > first one for that matter).<br />><br />> Our conference meeting space is only available until 5 p.m. Wednesday. We<br />> would need to start at 4 p.m. to get in an hour-long meeting, and I do think<br />> that several Board members will be running late as they wrap up with their<br /> > the reports tutorials and the hackfests.<br />><br />> I had originally suggested 8 a.m. Thursday as an alternative. However, I now<br />> realize that this time isn't ideal for me. As we get closer to 9 a.m., I<br /> > will need to prepare to get things lined up for our morning programming.<br />> Dare I say 7:30 a.m. on Thursday?<br />><br />> The only other options I see are 1) lunchtime Thursday, which I'm guessing<br />> will be problematic for Yamil, who is coordinating the Lunch-Arounds and<br /> > 2)Thursday afternoon, which will conflict with the vendor reception.<br />><br />> My apologies in advance to those who are traveling from the West Coast and<br />> those who just aren't usually awake that early in the morning.<br /> ><br />><br />> Kathy<br />><br />> Kathy Lussier<br />> Project Coordinator<br />> Massachusetts Library Network Cooperative<br />> <a href="http://tel%28508%29%20343-0128" target="_blank">(508) 343-0128</a><br /> > <a class="parsedEmail" href="mailto:klussier@masslnc.org" target="_blank">klussier@masslnc.org</a><br />> Twitter: <a href="http://www.twitter.com/kmlussier" target="_blank">http://www.twitter.com/kmlussier</a><br />><br />> On 3/3/2014 2:27 PM, Kathy Lussier wrote:<br /> >><br />>> We also could probably push it back to 4:30 since others on the Board will<br />>> most likely be finishing up with their respective hackfests at 4 p.m., if<br />>> they aren't attending the reports tutorial.<br /> >><br />>> Kathy<br />>><br />>> Kathy Lussier<br />>> Project Coordinator<br />>> Massachusetts Library Network Cooperative<br />>> <a href="http://tel%28508%29%20343-0128" target="_blank">(508) 343-0128</a><br /> >> <a class="parsedEmail" href="mailto:klussier@masslnc.org" target="_blank">klussier@masslnc.org</a><br />>> Twitter: <a href="http://www.twitter.com/kmlussier" target="_blank">http://www.twitter.com/kmlussier</a><br />>><br />>> On 3/3/2014 2:16 PM, Chauncey Montgomery wrote:<br /> >>><br />>>> Kathy,<br />>>> I'll be doing a tutorial on reports until 4pm on Wednesday, but if the<br />>>> Wednesday time works for everyone else, I could just be a little late to the<br /> >>> meeting.<br />>>> CM<br />>>><br />>>> Chauncey G. Montgomery, MLIS<br />>>> Director/Fiscal Officer | Community Library<br />>>> 44 Burrer Drive | Sunbury, OH 43074<br />>>> <a href="http://tel:740-965-3901" target="_blank">740-965-3901</a> | <a href="http://community.lib.oh.us" target="_blank">http://community.lib.oh.us</a><br /> >>><br />>>> On 02/28/2014 05:10 PM, Kathy Lussier wrote:<br />>>>><br />>>>> Hi all,<br />>>>><br />>>>> Following up from our meeting yesterday, we do have space available at<br /> >>>> the conference for an EOB meeting. What time do people want to meet<br />>>>> during the conference? In prior years, we've tried not to meet at a time<br />>>>> when programming is happening. The EOB update will be on Friday morning<br /> >>>> this year, so we may want to meet before Friday.<br />>>>><br />>>>> Since I'm guessing most EOB members will be around for the resource<br />>>>> allocator summit, will a Wednesday afternoon meeting around 4 p.m. work<br /> >>>> for people? Another possibility is 8 a.m. on Thursday. The reception is<br />>>>> Thursday at 5p.m., so I don't think we want to meet then.<br />>>>><br />>>>> Kathy<br />>>>><br /> >>><br />>><br />>> _______________________________________________<br />>> eg-oversight-board mailing list<br />>> <a class="parsedEmail" href="mailto:eg-oversight-board@list.evergreen-ils.org" target="_blank">eg-oversight-board@list.evergreen-ils.org</a><br /> >> <a href="http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/eg-oversight-board" target="_blank">http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/eg-oversight-board</a><br />><br />><br />> _______________________________________________<br /> > eg-oversight-board mailing list<br />> <a class="parsedEmail" href="mailto:eg-oversight-board@list.evergreen-ils.org" target="_blank">eg-oversight-board@list.evergreen-ils.org</a><br />> <a href="http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/eg-oversight-board" target="_blank">http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/eg-oversight-board</a><br /> <br /><br /><br />-- <br />Galen Charlton<br />Manager of Implementation<br />Equinox Software, Inc. / The Open Source Experts<br />email: <a class="parsedEmail" href="mailto:gmc@esilibrary.com" target="_blank">gmc@esilibrary.com</a><br />direct: <a href="http://tel%2B1%20770-709-5581" target="_blank">+1 770-709-5581</a><br /> cell: <a href="http://tel%2B1%20404-984-4366" target="_blank">+1 404-984-4366</a><br />skype: gmcharlt<br />web: <a href="http://www.esilibrary.com/" target="_blank">http://www.esilibrary.com/</a><br />Supporting Koha and Evergreen: <a href="http://koha-community.org" target="_blank">http://koha-community.org</a> &<br /> <a href="http://evergreen-ils.org" target="_blank">http://evergreen-ils.org</a><br />_______________________________________________<br />eg-oversight-board mailing list<br /><a class="parsedEmail" href="mailto:eg-oversight-board@list.evergreen-ils.org" target="_blank">eg-oversight-board@list.evergreen-ils.org</a><br /> <a href="http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/eg-oversight-board" target="_blank">http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/eg-oversight-board</a></div>
</div>
</div>
</div>
</div>
<br />_______________________________________________<br /> eg-oversight-board mailing list<br /> <a class="parsedEmail" href="mailto:eg-oversight-board@list.evergreen-ils.org" target="_blank">eg-oversight-board@list.evergreen-ils.org</a><br /> <a href="http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/eg-oversight-board" target="_blank">http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/eg-oversight-board</a><br /> </blockquote>
</div>
</div>
</div>
</div>
<br /><hr size="1" /><br />_______________________________________________<br />eg-oversight-board mailing list<br /><a class="parsedEmail" href="mailto:eg-oversight-board@list.evergreen-ils.org" target="_blank">eg-oversight-board@list.evergreen-ils.org</a><br /><a class="parsedLink" href="http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/eg-oversight-board" target="_blank">http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/eg-oversight-board</a><br /><br /></blockquote>
</div>
<div> </div>