Hi all,<br><br>My understanding is that we are talking about 3 different 'products' here: Koha : with a vibrant and productive community of users and developers, and 2 forks developed by LibLime/PTFS: LEK and Harley.<br>
<br>Its not about versions of Koha folks; LEK and Harley are forks. They are not Koha. The Harley fork has the potential to be incorporated back into Koha but LEK is a straight fork.<br><br>I'm not clear what the problem is that needs solving with regards to Koha. The Koha community is functioning effectively and development continues. The problem we used to have was solved with the Koha community moving to <a href="http://koha-community.org">koha-community.org</a><br>
<br>I think PTFS have to decide whether they want to join the community or not. It could happen quite easily if they have a mind to. Releasing the Harley code was a very definite and positive step in the right direction of bringing the PTFS Harley fork back into Koha. <br>
<br>Koha doesn't actually need PTFS or the <a href="http://koha.org">koha.org</a> domain name. If PTFS see no value in joining the Koha community then I see no problem at all in Koha and PTFS just going our separate ways: live and let live. Harley and LEK could exist as perfectly valid LMS products developed and supported by PTFS. But they are not Koha.<br>
<br>Cheers Jo. <br><br> <br><br><div class="gmail_quote">On Sun, Oct 17, 2010 at 2:32 AM, ed c <span dir="ltr"><<a href="mailto:terrapin44@yahoo.com">terrapin44@yahoo.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div class="im"><br>
--- On Sat, 10/16/10, Chris Cormack <<a href="mailto:chris@bigballofwax.co.nz">chris@bigballofwax.co.nz</a>> wrote:<br>
<br>
<br>
> I think you are confusing the issues ed. Complaining<br>
> about bad behaviour is not the same as caring enough<br>
> about a domain the project no longers uses, to allow<br>
> for a stacked foundation.<br>
<br>
</div>I am not the one that said "used to care about" the assets when it is clear that members of the community keep referring to it. It is not only the domain, recently there were complaints about a logo. The Koha logo is an asset registered to PTFS in the United States and other countries according to Horowhenua Library Trust Koha Subcommittee report dated April 29, 2010 [1]. Thus, if they want to change or make a different logo (asset), at least in the US, they have the right. It is their asset. So, no I am not confusing the issues.<br>
<div class="im"><br>
> As for the fork, you have it wrong too, there are<br>
> most definitely some forks, Koha is not one of them.<br>
<br>
</div>I probably wasn't clear what I meant about forks but it really isn't of importance. So, point taking, and accepted.<br>
<div class="im"><br>
<br>
> I don't see why we should have to rename, how about<br>
> we just keep using <a href="http://koha-community.org" target="_blank">koha-community.org</a> and working<br>
> on Koha.<br>
<br>
</div>As long as their are two (or more) versions of Koha that are different without different names, it is going to lead to confusion by people that might consider using the software (which was my scenario 1 below). I didn't say you had to rename it, I said that is the only way I see this confusion will not continue to exist and get worse - which incidentally was a concept someone else originally brought up on this list, not me.<br>
<div class="im"><br>
<br>
> Ill make you a deal, i won't mention <a href="http://koha.org" target="_blank">koha.org</a> again<br>
> if that will assuage your worry that I want it back<br>
> enough to rush in a foundation with special treatment<br>
> for one company.<br>
<br>
</div>I am not sure what you mean. You already said you don't want to rush this.<br>
<br>
> Chris<br>
<br>
Edward<br>
<br>
[1] <a href="http://koha-community.org/hlt-koha-committee-report-on-discussions-with-ptfs/" target="_blank">http://koha-community.org/hlt-koha-committee-report-on-discussions-with-ptfs/</a><br>
<div><div></div><div class="h5"><br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
_______________________________________________<br>
Koha mailing list <a href="http://koha-community.org" target="_blank">http://koha-community.org</a><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>
</div></div></blockquote></div><br><br clear="all"><br>-- <br>Joann Ransom RLIANZA<br>Head of Libraries,<br>Horowhenua Library Trust.<br><br><i>Q: Why is this email three sentences or less?<br>
A: <a href="http://three.sentenc.es" target="_blank">http://three.sentenc.es</a></i><br><br>
<div style="visibility: hidden; display: inline;" id="avg_ls_inline_popup"></div><style type="text/css">#avg_ls_inline_popup { position:absolute; z-index:9999; padding: 0px 0px; margin-left: 0px; margin-top: 0px; width: 240px; overflow: hidden; word-wrap: break-word; color: black; font-size: 10px; text-align: left; line-height: 13px;}</style>