[Koha] Community Feedback

[Joe Atzberger]

Brooke --

I don't even think we're talking about the same thing anymore.  Versions
will differ, and if you prefer an old version for its featureset or the
specific implementation of a given feature, then stick with that version or
please work to port the code over.  No substantive feature has been
deprecated capriciously.  Indeed, bugs are sometimes introduced with new
architectures and compromises between competing designs can alter
requirements, interfaces or functionality.  But this is normal to any
developing project.

The point was already settled in the other thread that aspects of the HLT
acquisitions implementation in question never made it to mainline Koha.  As
far as that goes, it was not "broken" or taken out: it was never there.  So
we're not talking about the same thing.  I don't blame Katipo or Chris or
HLT or anybody else, because managing customizations vs. mainline code can
get complicated, especially using the version control systems of that time,
with limited professional and community resources, etc, etc.

Similarly, I'm not going to argue LibLime's business practices to you in
this or any other thread.  In the end, for the Koha project, the best code
coming in wins.  I have yet to see a situation where code that was better
for *all* Koha users was rejected in favor of inferior code.  It doesn't
matter who wrote it, or whether they were paid, by whom, or how much.  This
includes situations where my own code was rejected as inferior!

--Joe Atzberger
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.katipo.co.nz/pipermail/koha/attachments/20081217/3fad6251/attachment.htm