<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=ISO-8859-1">
</head>
<body text="#000000" bgcolor="#FFFFFF">
Hi all,<br>
<br>
I'm resending my response to the public and archived Oversight Board
list. I just realized my first e-mail didn't go there.<br>
<br>
Regards!<br>
Kathy<br>
<div class="moz-forward-container">
<br>
<br>
-------- Original Message --------
<table class="moz-email-headers-table" border="0" cellpadding="0"
cellspacing="0">
<tbody>
<tr>
<th nowrap="nowrap" valign="BASELINE" align="RIGHT">Subject:
</th>
<td>Re: [Eg-oversight-board] Release manager, Package
releases vs Software releases, Membership fees</td>
</tr>
<tr>
<th nowrap="nowrap" valign="BASELINE" align="RIGHT">Date: </th>
<td>Thu, 15 Aug 2013 12:17:19 -0400</td>
</tr>
<tr>
<th nowrap="nowrap" valign="BASELINE" align="RIGHT">From: </th>
<td>Kathy Lussier <a class="moz-txt-link-rfc2396E" href="mailto:klussier@masslnc.org"><klussier@masslnc.org></a></td>
</tr>
<tr>
<th nowrap="nowrap" valign="BASELINE" align="RIGHT">To: </th>
<td>Elfstrand, Stephen F <a class="moz-txt-link-rfc2396E" href="mailto:stephen.elfstrand@mnsu.edu"><stephen.elfstrand@mnsu.edu></a></td>
</tr>
<tr>
<th nowrap="nowrap" valign="BASELINE" align="RIGHT">CC: </th>
<td>Evergreen Oversight Board +SFC
(<a class="moz-txt-link-abbreviated" href="mailto:evergreen@sfconservancy.org">evergreen@sfconservancy.org</a>)
<a class="moz-txt-link-rfc2396E" href="mailto:evergreen@sfconservancy.org"><evergreen@sfconservancy.org></a>, Lazar, Alexey
Vladimirovich <a class="moz-txt-link-rfc2396E" href="mailto:alexey.lazar@mnsu.edu"><alexey.lazar@mnsu.edu></a>, Curie, Carrie
L <a class="moz-txt-link-rfc2396E" href="mailto:carrie.curie@mnsu.edu"><carrie.curie@mnsu.edu></a></td>
</tr>
</tbody>
</table>
<br>
<br>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
<div class="moz-cite-prefix">Hi Stephen,<br>
<br>
Just to be clear, I do agree with the need to build funds and
for the EOB to find ways to support strategic development
projects. You get no arguments from me on that front.<br>
<br>
<blockquote type="cite"><span style="color:#1F497D"><o:p></o:p></span>
<p class="MsoNormal"><span style="color:#1F497D">We talked
about the need for funds to for instance, to use to match
grants we might get. One idea is to sell advertising space
on the Evergreen web site to vendors.</span></p>
</blockquote>
<br>
You had mentioned this idea at the last EOB meeting. In a
subsequent conversation with Dan Scott after that EOB meeting, I
learned that there are other open source projects that have
successfully highlighted donors/sponsors on their pages. It
might be worthwhile to investigate this option after the
community web site's conversion to Wordpress is done. <br>
<br>
Based on my involvement in the process for getting conference
sponsorships, I'm guessing we would need to avoid to use the
work "advertising" and describe them as sponsorships where the
donor is acknowledged on the web page.<br>
<br>
<blockquote type="cite"><span style="color:#1F497D">Another idea
is to have a membership fee. </span><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Kathy
you’re right to say that we shouldn’t charge people to run
Evergreen. I’m not suggesting that. <o:p></o:p></span>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">As
a public entity I can pay a membership fee but I just
can’t donate money to worthy causes. So if there was a
membership fee, I would pay it. I guess to flesh out my
idea a little I think a membership fee should be tied to
voting. Organizations and individuals who wish to vote on
community business should be members, so should the EOB
members. Remember we pay 10% of our total billings to the
Software Freedom Conservancy, I don’t see a problem
recouping that money back through membership fees. I’m not
talking about large amounts but something would help. <o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Crediting
organizations for in-kind efforts does seem fair, but
unfortunately doesn’t help raise actual dollars to match
with grants or sponsor development and documentation.</span></p>
</blockquote>
<br>
Thank you for the further explanation on the membership fee. I
guess I had misinterpreted some of this idea. <br>
<br>
I still am a bit uncomfortable to tying a fee to voting. I could
see cases where an institution may not be able to put a
membership fee into its budget, but might have staff who has
consistently contributed documentation throughout the year. For
me, it's would be hard to say that the institution is not
allowed to vote when they are contributing to the community. <br>
<br>
But there might be other ways of setting up a membership fee
infrastructure, perhaps building it into sponsors highlighted on
the Evergreen web site. Perhaps acknowledgement of different
levels of membership. <br>
<br>
Kathy<br>
<br>
<br>
<br>
<pre class="moz-signature" cols="72">Kathy Lussier
Project Coordinator
Massachusetts Library Network Cooperative
(508) 343-0128
<a moz-do-not-send="true" class="moz-txt-link-abbreviated" href="mailto:klussier@masslnc.org">klussier@masslnc.org</a>
Twitter: <a moz-do-not-send="true" class="moz-txt-link-freetext" href="http://www.twitter.com/kmlussier">http://www.twitter.com/kmlussier</a>
</pre>
On 8/15/2013 11:33 AM, Elfstrand, Stephen F wrote:<br>
</div>
<blockquote
cite="mid:A6F80436F9D3C049880E258CDD233069BAEFF8DB@DB5.Campus.mnsu.edu"
type="cite">
<meta http-equiv="Content-Type" content="text/html;
charset=ISO-8859-1">
<meta name="Generator" content="Microsoft Word 14 (filtered
medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";
color:black;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{mso-style-priority:99;
mso-style-link:"Balloon Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:8.0pt;
font-family:"Tahoma","sans-serif";
color:black;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";
color:black;}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";
color:black;}
span.EmailStyle20
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle21
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
/* List Definitions */
@list l0
{mso-list-id:479082982;
mso-list-type:hybrid;
mso-list-template-ids:1686259894 67698705 67698713 67698715 67698703 67698713 67698715 67698703 67698713 67698715;}
@list l0:level1
{mso-level-text:"%1\)";
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level2
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level3
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l0:level4
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level5
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level6
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l0:level7
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level8
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level9
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
--></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]-->
<div class="WordSection1">
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Hi
Kathy, <o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Thanks
for your response to my suggestions. <o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">I
didn’t generate a lot of discussion with my suggestions.
Yours is the only response I’ve received. I guess I’m just
out of step with the thinking of the rest of the EOB and
the developer community. <o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">I
hope everyone takes my comments as constructive criticism.
I do appreciate all the hard work and professionalism that
the developers and the community at large have shown. I
realize that many great things are going on. My goal is to
take it to the next level.<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">As
an administrator, I would like to see <u>Package</u>
releases not just <u>software</u> releases. For example<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">_At
PALS we run only standard releases, and have had upgrade
scripts them fail. We try to exercise due diligence and
figure things out for ourselves before we burden the
Community with questions but have had to go to the
developer list and see if someone might know why it would
fail. We’ve had to find someone who knew why and apply an
undocumented fixes. This makes it difficult to treat
Evergreen upgrades in a routine manner and adds
unnecessary costs to us and service delay to our users.
It makes one wonder whether the upgrade scripts are
adequately tested. <o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">I’ve
suggested before that someone not involved in a recent
release should run the upgrade scripts to make sure the
instructions are complete and correct and that the scripts
work. PALS would be willing to be one of these testers..<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">-Acquisitions
was released before it was usable, it was much too slow
for large invoices.<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">-Authorities
was not working well yet was released. Batch downloads of
new authority records should change all the records linked
to it. I know for instance that we lost a highly
prestigious customer because, at least in part, the
authority control system was not working. They went to
OCLC WSM instead. <o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">_Technical
and end user documentation is way behind the code, yes it
is getting better thanks to the community. Still, being
forced to consult 2 or 3 versions of incomplete
documentation is just not good. If we held software
releases until the documentation was completed, it would
give the community motivation to get the documentation
done.<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Giving
the Board some money to use for critical development would
be helpful I think . The Board could supplement what is
being done voluntarily by the community and fill holes by
sponsoring development and documentation. <o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">“</span>only
one person submitted his name as a candidate for the
position” <span style="color:#1F497D">Yes, I imagine it’s a
lot of work to volunteer for. If the Board had some funds,
it could offer a stipend to the release managers and get
more candidates. <o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">We talked
about the need for funds to for instance, to use to match
grants we might get. One idea is to sell advertising space
on the Evergreen web site to vendors. Another idea is to
have a membership fee. </span><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Kathy
you’re right to say that we shouldn’t charge people to run
Evergreen. I’m not suggesting that. <o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">As
a public entity I can pay a membership fee but I just
can’t donate money to worthy causes. So if there was a
membership fee, I would pay it. I guess to flesh out my
idea a little I think a membership fee should be tied to
voting. Organizations and individuals who wish to vote on
community business should be members, so should the EOB
members. Remember we pay 10% of our total billings to the
Software Freedom Conservancy, I don’t see a problem
recouping that money back through membership fees. I’m not
talking about large amounts but something would help. <o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Crediting
organizations for in-kind efforts does seem fair, but
unfortunately doesn’t help raise actual dollars to match
with grants or sponsor development and documentation.<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">The
fact that Equinox is requiring documentation is its
contracts is great. I think every contract should include
it. Let’s set this as a policy or best practice
suggestion as a board. Let’s have a documentation
hack-a-thon.<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">We
are competing with the Next Gen LMSs as well as current
ones. The next gen systems are including knowledge bases
for serials, OpenURL linking, and ERM in an integrated
work flow, as part of library management. We need to move
in that direction. <o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">_I
think Evergreen needs to be able work with the OLE folks
to use Open Knowledge Base and incorporate these next gen
features.<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">_Academic
libraries<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">_
need a patron API to keep our patron database in sync with
campus registration systems before large will want to use
it en mass. <o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">__effective
Authority Control<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">_
interaction with Campus financial systems<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">_NCIP
interactivity is critical to all of our potential
customers in Minnesota, without it they just won’t
consider Evergreen. PALS has undertaken to help develop
this.<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">_
Large public library systems will not move to Evergreen
without <o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">__a
first class Acq system<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">__effective
Authority Control<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">On
the Discovery side we need to incorporate <o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">_fast
SOLR based retrieval <o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">_come
up with a framework for OPAC layout that will handle
mobile devices as a matter of course.<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">_The
OPAC should have the ability to use APIs from 3<sup>rd</sup>
parties like Summon for Web-scale discovery. <o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">VuFind
does all this already. Why not package VuFind with
Evergreen? Do we really need to create our own OPAC? <o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Or
if we do, why not use a CSS framework like Bootstrap,
which handles mobile devices and is easier to customize.<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">These
is not just a theoretical concern for the future, We’ve
already lost several prospects to OCLC Web Scale
Management. <o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">PALS
is willing to work on development, quality issues and
strategic priorities, It just frustrates me when we have
to spend time figuring out things like upgrades that
should be routine, or compiling documentation from
multiple sources, or features that are released before
they are ready for prime time.<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">So
the reason I want the EOB to have funds available to it,
is for it to sponsor <u>strategic</u> development that
may not be of immediate concern to existing users but will
position Evergreen to compete with the Next Gen Systems
being developed. This will help appeal to potential
customers not just current ones. Appointing the release
manager and paying a stipend will give the EOB more
influence on development directions and ensure that
releases are packaged more completely. Documentation and
bug fix bounties could be sponsored as well. <o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Maybe
what we need is <u>product</u> management in addition to
a release management. If the EOB had some funds and more
influence, it could play that role. We need to set
long-term development priorities to make Evergreen a force
in the market of the future and go beyond its’ reputation
as a very basic system for small libraries.<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">We’ve
talked about using some crowd-sourcing software to gather
support for specific development and that is a good idea.
The EOB could throw some money into the crowd-sourced pot
for specific projects, if it had some.<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">It
seems that the common opinion is that we really don’t need
to change much because things are going well as they are.
While a lot of great things are happening, I think we
could do better with a little more long-term strategic
management of the Evergreen product. That seems like the
natural role of the EOB. Of course the EOB would always
consult with the whole Evergreen community as it does
this work.<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#376092;mso-style-textfill-fill-color:#376092;mso-style-textfill-fill-alpha:100.0%"><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="color:#376092;mso-style-textfill-fill-color:#376092;mso-style-textfill-fill-alpha:100.0%"><span
style="color:windowtext">Stephen Elfstrand<o:p></o:p></span></span></p>
</div>
</blockquote>
<br>
<br>
</div>
<br>
</body>
</html>