To be fair, staff at PTFS, who is now our Koha support vendor, have made contributions to community Koha (both new development and bug fixes). Let's remember that it is LibLime Enterprise Koha that was forking from community Koha, not PTFS. <br>
<br>PTFS now has responsibility for the 100+ Koha development projects sponsored by SCLS. It is our intent that 100% of these projects will be contributed to community Koha. Despite the unfortunately worded email yesterday, it is my belief that PTFS has no problem with doing so and must do so as stipulated in our contract. <br>
<br>Furthermore, we are working with the excellent migration staff at LibLime (and now PTFS) to migrate our data. It is a complex data migration and we are quite happy with the work done so far.<br><br>We chose Koha because we placed a high value on being part of an open source community. We are still very much committed to the Koha open source community and appreciate the work that has been done before us, the work that is being done and the work yet to come. <br>
<br><br><div class="gmail_quote">On Fri, Apr 30, 2010 at 1:26 PM, Lori Ayre <span dir="ltr"><<a href="mailto:loriayre@gmail.com">loriayre@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
If I were a LL/PTFS customer and valued being in an open source<br>
community, I would be talking to different service providers about<br>
what it would take to migrate my data to the current community<br>
supported version. Just sayin'.<br>
<font color="#888888"><br>
Lori Ayre<br>
</font><div class="im"><br>
On Fri, Apr 30, 2010 at 10:53 AM, Cab Vinton <<a href="mailto:bibliwho@gmail.com">bibliwho@gmail.com</a>> wrote:<br>
</div><div><div></div><div class="h5">>> It would be good to hear from more LL/PTFS customers on the specific points<br>
>> addressed in this post.<br>
><br>
> That would be us, among many others.<br>
><br>
> I suspect that most PTFS libraries are simply trying to process what<br>
> this means for them. And unfortunately, I also suspect that many may<br>
> feel there is relatively little to be gained by responding in public.<br>
><br>
> If they support PTFS's position, a public defense would put them in<br>
> the cross-hairs, a difficult position to be in considering they don't<br>
> know all the facts.<br>
><br>
> If they don't support it, they will most likely seek to open a dialog<br>
> with PTFS directly, or to simply bide their time until such time as<br>
> they're in a position to migrate to another vendor. No point in<br>
> annoying someone who may be in a position to make your life very<br>
> difficult.<br>
><br>
> Not saying which category we fall under :-)<br>
><br>
> Best,<br>
><br>
> Cab Vinton, Director<br>
> Sanbornton Public Library<br>
> Sanbornton, NH<br>
> _______________________________________________<br>
> Koha mailing list<br>
> <a href="mailto:Koha@lists.katipo.co.nz">Koha@lists.katipo.co.nz</a><br>
> <a href="http://lists.katipo.co.nz/mailman/listinfo/koha" target="_blank">http://lists.katipo.co.nz/mailman/listinfo/koha</a><br>
><br>
_______________________________________________<br>
Koha mailing list<br>
<a href="mailto:Koha@lists.katipo.co.nz">Koha@lists.katipo.co.nz</a><br>
<a href="http://lists.katipo.co.nz/mailman/listinfo/koha" target="_blank">http://lists.katipo.co.nz/mailman/listinfo/koha</a><br>
<br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br>Vicki Teal Lovely<br><br>Helping our 52 member libraries provide the best possible service to the public.<br><br>ILS Project Manager<br>South Central Library System<br>
Madison, WI<br><a href="mailto:vtl@scls.lib.wi.us">vtl@scls.lib.wi.us</a><br>(608)242-4713<br><br>