<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="Generator" content="Microsoft Word 12 (filtered medium)">
<style>
<!--
/* Font Definitions */
@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:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
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.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:11.0pt;
font-family:"Calibri","sans-serif";}
p.MsoListParagraphCxSpFirst, li.MsoListParagraphCxSpFirst, div.MsoListParagraphCxSpFirst
{mso-style-priority:34;
mso-style-type:export-only;
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
p.MsoListParagraphCxSpMiddle, li.MsoListParagraphCxSpMiddle, div.MsoListParagraphCxSpMiddle
{mso-style-priority:34;
mso-style-type:export-only;
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
p.MsoListParagraphCxSpLast, li.MsoListParagraphCxSpLast, div.MsoListParagraphCxSpLast
{mso-style-priority:34;
mso-style-type:export-only;
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri","sans-serif";
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;}
@page Section1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.Section1
{page:Section1;}
/* List Definitions */
@list l0
{mso-list-id:959339970;
mso-list-type:hybrid;
mso-list-template-ids:1076554584 67698689 67698691 67698693 67698689 67698691 67698693 67698689 67698691 67698693;}
@list l0:level1
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:.25in;
text-indent:-.25in;
font-family:Symbol;}
@list l0:level2
{mso-level-tab-stop:1.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level3
{mso-level-tab-stop:1.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level4
{mso-level-tab-stop:2.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level5
{mso-level-tab-stop:2.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level6
{mso-level-tab-stop:3.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level7
{mso-level-tab-stop:3.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level8
{mso-level-tab-stop:4.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level9
{mso-level-tab-stop:4.5in;
mso-level-number-position:left;
text-indent:-.25in;}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
-->
</style>
</head>
<body lang="EN-US" link="blue" vlink="purple">
<div class="Section1">
<p class="MsoNormal">There has been some concern expressed recently about
PTFS/LibLime owning the registry entries for several domain names with the word
Koha in them. I would like to address that and other issues.</p>
<p class="MsoNormal"> </p>
<p class="MsoListParagraphCxSpFirst" style="margin-left:.25in;text-indent:-.25in;
mso-list:l0 level1 lfo1"><span style="font-family:Symbol"><span style="mso-list:Ignore">·<span style="font:7.0pt "Times New Roman"">
</span></span></span>In mid-March, of this year, PTFS announced the
acquisition of LibLime from Metavore.</p>
<p class="MsoListParagraphCxSpMiddle" style="margin-left:.25in;text-indent:-.25in;
mso-list:l0 level1 lfo1"><span style="font-family:Symbol"><span style="mso-list:Ignore">·<span style="font:7.0pt "Times New Roman"">
</span></span></span>In April, LibLime attempted to communicate with
Horowhenua Library Trust Koha Committee about taking over support for <a href="http://koha.org">koha.org</a>,
but communications were not successful.</p>
<p class="MsoListParagraphCxSpMiddle" style="margin-left:.25in;text-indent:-.25in;
mso-list:l0 level1 lfo1"><span style="font-family:Symbol"><span style="mso-list:Ignore">·<span style="font:7.0pt "Times New Roman"">
</span></span></span>In May, LibLime released Harley as well as
approximately 70 individual feature commits from LIBLIME customer-sponsored
development and LIBLIME corporate-sponsored development. Harley was
3.0.x Koha with all of the 70 feature commits included. This gave
potential Koha users the opportunity to either download Harley with the
features, or select individual features for individual use. While 3.2 was
nearing official release at that time, our customers who sponsored the
development were pleased to see several of those features included in the 3.2
plans. </p>
<p class="MsoListParagraphCxSpLast" style="margin-left:.25in;text-indent:-.25in;
mso-list:l0 level1 lfo1"><span style="font-family:Symbol"><span style="mso-list:Ignore">·<span style="font:7.0pt "Times New Roman"">
</span></span></span>Throughout the remainder of the summer, LibLime
has continued to develop sponsored features for customers under contracts
acquired through the purchase of LibLime.</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">I am saddened at the criticism directed at PTFS/LibLime and
our employees on blog posts, listservs, and other electronic communication
forums. Since Q3 2008, PTFS has been participating in the Koha
community. This participation includes code submission, attendance and
sponsorship at KohaCon 2009, active use of Bugzilla for new feature development,
and IRC/Listserv contributions. We have expanded the worldwide use
of Koha by bringing many new customers to the project, and we continue to
promote the benefits of open source ILS solutions. We have released
customer-sponsored and PTFS/LibLime-sponsored code for worldwide use, and we
will continue to do so.</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">In regards to the domain names, it is part of our standard
operating procedures to purchase domain names in the business markets we are
involved with and LibLime has acquired multiple domain names related to Koha
and open source ILS. In addition, some of these names were also
transferred over as a part of the LibLime acquisition. PTFS owns many
domain names in all our lines of business. We did not try to hide this
action and could have made these transactions private. Nothing has been
done with the domain names at this point. They do not have web sites
built around them, nor do they re-direct anywhere. They are simply owned
by LibLime, thus preventing any non-Koha entity or competitor from acquiring
the domains and diverting potential future Koha users to other ILS
solutions. This is to the benefit of all Koha users and developers.</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">LibLime would like to help the Koha community build a better
Koha for the future. There is much to do to develop the application so
that it can compete head to head with commercial solutions in all library
markets. LibLime’s goal is to help make sure that Koha becomes the
dominant open source ILS solution and not just another alternative.
To ensure success, we believe that the Koha organization needs to grow into an
organization that will globally unite all those involved with Koha. The
project needs many companies, independent developers and Koha affiliated
intuitions and customers worldwide to participate and work harmoniously
together help build the world’s best open source ILS. </p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">The HLT Koha Committee was established as holding body for
the Koha project property. We believe that it is now time to move to the
next step and create a full-fledged governance structure capable of supporting
Koha as a rapidly expanding global open source endeavor. </p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">In this regards, LibLime will help organize and fund the
creation of a Koha Software Foundation as a 501(c)3 non-profit
corporation. Once the establishment of the Koha Software Foundation
is complete, PTFS/LibLime will transfer the assets we own related to Koha to
this corporation, including Koha related domain names as well as pending
trademark applications. </p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">LibLime officially requests that interested parties contact us
who are interested in helping to create and manage this foundation. We
would welcome and hope that multiple worldwide groups will all participate
together. Initially, LibLime will help to fund the development of
articles, bylaws and governance documents and help the foundation to become a
self supporting organization. LibLime does not aim to dominate or control
the foundation; we will expect to participate as any qualified organization and
as a voting member. We believe that the establishment of an independent
foundation will provide the structure for ongoing management and governance of
the Koha project and should provide the basis for a less divisive atmosphere
surrounding the efforts of all the stakeholders involved, including the
companies involved in development and support services as well as the libraries
and consortium that rely on Koha. </p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">Our decisions on how LibLime will continue to proceed in the
Koha project will continue to be based upon communications we receive,
proposals to support the Koha Foundation and acceptance of our organization as
a viable part of the community to help Koha become the world’s best ILS.</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">Best regards:</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">John Yokley</p>
<p class="MsoNormal">CEO</p>
<p class="MsoNormal">PTFS/LibLime</p>
</div>
</body>
</html>