<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">Hi all,<br>
<br>
I had a meeting with the event coordinator at the hotel yesterday,
and it turns out the Wednesday night event that forced us out of
the meeting rooms at 5 p.m. ultimately fell through. So let's go
back to planning for a Wednesday, 4:30 p.m. meeting in Salons 5-7
(the location of the DIG hackfest). It will ensure that everyone
is wide awake, will give us ample time for discussion, and won't
conflict with other conference activities.<br>
<br>
Kathy<br>
<pre class="moz-signature" cols="72">Kathy Lussier
Project Coordinator
Massachusetts Library Network Cooperative
(508) 343-0128
<a class="moz-txt-link-abbreviated" href="mailto:klussier@masslnc.org">klussier@masslnc.org</a>
Twitter: <a class="moz-txt-link-freetext" href="http://www.twitter.com/kmlussier">http://www.twitter.com/kmlussier</a>
</pre>
On 3/5/2014 11:28 AM, Rogan Hamby wrote:<br>
</div>
<blockquote
cite="mid:CAMwaE4KWDTO=YK6REpXvLFvcFL=10us+P6KBa8C8LdPvnrYsiQ@mail.gmail.com"
type="cite">
<div dir="ltr">I think it would be worth sitting down to review
the tools at our disposal but also discuss what our
responsibilities are and what we think they should be. And I
want to applaud you for starting to think to the future on this
Elizabeth. I think this might be worth a sit around the table
conversation for quicker back and forth but I'll give some
additional thoughts here. Not all are direct responses to what
you brought up Elizabeth but follow down a few corollary paths.
<div>
<br>
</div>
<div>We have the Evergreen trademark. That means that code
can't be forked and called Evergreen in any way shape or form.
</div>
<div><br>
</div>
<div>We have the GPL so we can force access to the code and
expand on it if it's re-distributed. </div>
<div><br>
</div>
<div>Both of those things protect Evergreen but don't prevent
someone from creating a new thing out of it. It would be
entirely within someone's rights to take Evergreen and build a
whole new incompatible ILS out of it, stripping what they
don't like and calling it Bonsai. I don't have a problem with
that, that's part of the intention of the GPL is to enable
such things.</div>
<div><br>
</div>
<div>Now, I do have a personal issue if a library were to do
that and use it for their library and not republish the code.
It's legal but I think it's wrong. But all I can do is as an
individual, express my personal opinion as to the wrongness of
the action.</div>
<div><br>
</div>
<div>Now, could we have stopped this? Let's imagine that the
Bonsai library was an Evergreen library first before they
forked the code. I'm not in favor of trying to extend our
legal rights to make additional requirements of Evergreen code
users. We start moving away from the GPL there and if we even
begin thinking about such things we need Tony here for every
step of that discussion. I'll probably oppose it pretty
strongly as well. With that said, unless we did that there's
nothing we could force. </div>
<div><br>
</div>
<div>Could we encourage, could we take a more active role, could
we try to set a standard, maybe make some voluntary to sign
community policies that foster the kind of community we want?
I think that's a discussion very much worth having. I think
this is more of what you were asking Elizabeth and how I took
your email but correct me if I'm wrong.</div>
</div>
<div class="gmail_extra"><br>
<br>
<div class="gmail_quote">On Wed, Mar 5, 2014 at 10:39 AM,
McKinney, Elizabeth <span dir="ltr"><<a
moz-do-not-send="true"
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">Hi Ben, <br>
<br>
I am not proposing anything at this point other than
discussion of the Board's role given that we are now
seeing what appears to be the first fork. Yes, we need
to consider the health of the community and protecting
our assets. <br>
<br>
Is/was there something we can/could have done as a board
to keep KCLS as a community member and partner in
development? Do we want to take an active role in these
types of community situations? Since the Board works
directly with the SFC to deal with
copyright/licensing/trademark, we also need to have that
discussion. If a fracture occurs, what do we need to do
as the board to protect the assets of the community? <br>
<div class=""><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>
<a moz-do-not-send="true" href="tel:404.235.7141"
value="+14042357141" target="_blank">404.235.7141</a><br>
<a moz-do-not-send="true"
href="mailto:emckinney@georgialibraries.org"
target="_blank">emckinney@georgialibraries.org</a><br>
<a moz-do-not-send="true"
href="http://www.georgialibraries.org/"
target="_blank">http://www.georgialibraries.org/</a><br>
<br>
<br>
<br>
<span name="x"></span><br>
</div>
<br>
</div>
<hr>
<div
style="font-size:12pt;font-style:normal;font-family:Helvetica,Arial,sans-serif;text-decoration:none;font-weight:normal"><b>From:
</b>"Ben Hyman" <<a moz-do-not-send="true"
href="mailto:ben.hyman@bc.libraries.coop"
target="_blank">ben.hyman@bc.libraries.coop</a>><br>
<b>To: </b>"Elizabeth McKinney" <<a
moz-do-not-send="true"
href="mailto:emckinney@georgialibraries.org"
target="_blank">emckinney@georgialibraries.org</a>><br>
<b>Cc: </b>"Rogan Hamby" <<a
moz-do-not-send="true"
href="mailto:rogan.hamby@gmail.com" target="_blank">rogan.hamby@gmail.com</a>>,
"Oversight Board" <<a moz-do-not-send="true"
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 11:24:18 AM
<div>
<div class="h5"><br>
<b>Subject: </b>Re: [Eg-oversight-board] EOB
meeting at the conference<br>
<br>
Hi Elizabeth,<br>
<br>
I'm interested to hear more about what are you
proposing. The health of the Evergreen community
is common cause - by celebrating shared successes
and creating an environment for more successes,
don't we all win? Seems to me the board's efforts
on the resource allocator summit, merchandising
initiatives and others came about with these
objectives in mind. Did you have other pragmatic
ideas? <br>
<br>
Cheers <br>
<br>
Ben Hyman <br>
Executive Director | BC Libraries Cooperative<br>
<a moz-do-not-send="true"
href="mailto:ben.hyman@bc.libraries.coop"
target="_blank">ben.hyman@bc.libraries.coop</a>
| <a moz-do-not-send="true"
href="tel:1.855.383.5761%20ext%201001"
value="+18553835761" target="_blank">1.855.383.5761
ext 1001</a> | cell: <a moz-do-not-send="true"
href="tel:250.889.2738" value="+12508892738"
target="_blank">250.889.2738</a><br>
<a moz-do-not-send="true"
href="http://bc.libraries.coop" target="_blank">bc.libraries.coop</a>
| Twitter: @BCLibrariesCoop<br>
<br>
On 2014-03-04, at 7:20 AM, McKinney, Elizabeth
wrote:<br>
<br>
> 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>
> 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 moz-do-not-send="true"
href="tel:404.235.7141" value="+14042357141"
target="_blank">404.235.7141</a><br>
> <a moz-do-not-send="true"
href="mailto:emckinney@georgialibraries.org"
target="_blank">emckinney@georgialibraries.org</a><br>
> <a moz-do-not-send="true"
href="http://www.georgialibraries.org/"
target="_blank">http://www.georgialibraries.org/</a><br>
> <br>
> <br>
> <br>
> <br>
> <br>
> From: "Rogan Hamby" <<a
moz-do-not-send="true"
href="mailto:rogan.hamby@gmail.com"
target="_blank">rogan.hamby@gmail.com</a>><br>
> To: "Elizabeth McKinney" <<a
moz-do-not-send="true"
href="mailto:emckinney@georgialibraries.org"
target="_blank">emckinney@georgialibraries.org</a>><br>
> Cc: "Galen Charlton" <<a
moz-do-not-send="true"
href="mailto:gmc@esilibrary.com" target="_blank">gmc@esilibrary.com</a>>,
"Oversight Board" <<a moz-do-not-send="true"
href="mailto:eg-oversight-board@list.evergreen-ils.org"
target="_blank">eg-oversight-board@list.evergreen-ils.org</a>><br>
> Sent: Tuesday, March 4, 2014 10:00:05 AM<br>
> Subject: Re: [Eg-oversight-board] EOB meeting
at the conference<br>
> <br>
> 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. <br>
> <br>
> 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.<br>
> <br>
> <br>
> <br>
> <br>
> On Tue, Mar 4, 2014 at 9:52 AM, McKinney,
Elizabeth <<a moz-do-not-send="true"
href="mailto:emckinney@georgialibraries.org"
target="_blank">emckinney@georgialibraries.org</a>>
wrote:<br>
> 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 moz-do-not-send="true"
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>
> <br>
> Elizabeth<br>
> <br>
> <br>
> <br>
> 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 moz-do-not-send="true"
href="tel:404.235.7141" value="+14042357141"
target="_blank">404.235.7141</a><br>
> <a moz-do-not-send="true"
href="mailto:emckinney@georgialibraries.org"
target="_blank">emckinney@georgialibraries.org</a><br>
> <a moz-do-not-send="true"
href="http://www.georgialibraries.org/"
target="_blank">http://www.georgialibraries.org/</a><br>
> <br>
> <br>
> <br>
> <br>
> <br>
> From: "Galen Charlton" <<a
moz-do-not-send="true"
href="mailto:gmc@esilibrary.com" target="_blank">gmc@esilibrary.com</a>><br>
> To: "Kathy Lussier" <<a
moz-do-not-send="true"
href="mailto:klussier@masslnc.org"
target="_blank">klussier@masslnc.org</a>><br>
> Cc: <a moz-do-not-send="true"
href="mailto:eg-oversight-board@list.evergreen-ils.org"
target="_blank">eg-oversight-board@list.evergreen-ils.org</a><br>
> Sent: Monday, March 3, 2014 4:56:17 PM<br>
> Subject: Re: [Eg-oversight-board] EOB meeting
at the conference<br>
> <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 moz-do-not-send="true"
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 moz-do-not-send="true"
href="tel:%28508%29%20343-0128"
value="+15083430128" target="_blank">(508)
343-0128</a><br>
> > <a moz-do-not-send="true"
href="mailto:klussier@masslnc.org"
target="_blank">klussier@masslnc.org</a><br>
> > Twitter: <a moz-do-not-send="true"
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 moz-do-not-send="true"
href="tel:%28508%29%20343-0128"
value="+15083430128" target="_blank">(508)
343-0128</a><br>
> >> <a moz-do-not-send="true"
href="mailto:klussier@masslnc.org"
target="_blank">klussier@masslnc.org</a><br>
> >> Twitter: <a moz-do-not-send="true"
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 moz-do-not-send="true"
href="tel:740-965-3901" value="+17409653901"
target="_blank">740-965-3901</a> | <a
moz-do-not-send="true"
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 moz-do-not-send="true"
href="mailto:eg-oversight-board@list.evergreen-ils.org"
target="_blank">eg-oversight-board@list.evergreen-ils.org</a><br>
> >> <a moz-do-not-send="true"
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 moz-do-not-send="true"
href="mailto:eg-oversight-board@list.evergreen-ils.org"
target="_blank">eg-oversight-board@list.evergreen-ils.org</a><br>
> > <a moz-do-not-send="true"
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 moz-do-not-send="true"
href="mailto:gmc@esilibrary.com" target="_blank">gmc@esilibrary.com</a><br>
> direct: <a moz-do-not-send="true"
href="tel:%2B1%20770-709-5581"
value="+17707095581" target="_blank">+1
770-709-5581</a><br>
> cell: <a moz-do-not-send="true"
href="tel:%2B1%20404-984-4366"
value="+14049844366" target="_blank">+1
404-984-4366</a><br>
> skype: gmcharlt<br>
> web: <a moz-do-not-send="true"
href="http://www.esilibrary.com/"
target="_blank">http://www.esilibrary.com/</a><br>
> Supporting Koha and Evergreen: <a
moz-do-not-send="true"
href="http://koha-community.org" target="_blank">http://koha-community.org</a>
&<br>
> <a moz-do-not-send="true"
href="http://evergreen-ils.org" target="_blank">http://evergreen-ils.org</a><br>
>
_______________________________________________<br>
> eg-oversight-board mailing list<br>
> <a moz-do-not-send="true"
href="mailto:eg-oversight-board@list.evergreen-ils.org"
target="_blank">eg-oversight-board@list.evergreen-ils.org</a><br>
> <a moz-do-not-send="true"
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 moz-do-not-send="true"
href="mailto:eg-oversight-board@list.evergreen-ils.org"
target="_blank">eg-oversight-board@list.evergreen-ils.org</a><br>
> <a moz-do-not-send="true"
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>
> eg-oversight-board mailing list<br>
> <a moz-do-not-send="true"
href="mailto:eg-oversight-board@list.evergreen-ils.org"
target="_blank">eg-oversight-board@list.evergreen-ils.org</a><br>
> <a moz-do-not-send="true"
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>
</div>
</div>
</div>
<br>
</div>
</div>
<br>
_______________________________________________<br>
eg-oversight-board mailing list<br>
<a moz-do-not-send="true"
href="mailto:eg-oversight-board@list.evergreen-ils.org">eg-oversight-board@list.evergreen-ils.org</a><br>
<a moz-do-not-send="true"
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>
<br>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
eg-oversight-board mailing list
<a class="moz-txt-link-abbreviated" href="mailto:eg-oversight-board@list.evergreen-ils.org">eg-oversight-board@list.evergreen-ils.org</a>
<a class="moz-txt-link-freetext" href="http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/eg-oversight-board">http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/eg-oversight-board</a>
</pre>
</blockquote>
<br>
</body>
</html>