The Koha community retains its Documentation Manager

It has been a week of big news in the koha world. Some bad, like Liblime’s fork of Koha finally becoming public knowledge and some good like Nicole staying on as Documentation Manager.

What makes this news even better, is the fact that two of the Koha support vendors teamed up to insure Nicole could stay in the community

In an environment when some people are actively trying to paint the community as a bad thing, it’s great to see that the people who understand Free Software are prepared to walk the walk, not just talk the talk

10 thoughts on “The Koha community retains its Documentation Manager”

  1. Pingback: Chris Cormack (ranginui) 's status on Saturday, 12-Sep-09 08:46:06 UTC -
  2. Yes, it’s a week of big news. And one is bound to have mixed feeling about it all, I guess.
    Thanks for the “walk the walk” thumbs up: we don’t want to forget that BibLibre wouldn’t exist without HLT, Katipo, yourself, Nelsonville PL and a few others. In an ecosystem, you just don’t burn the forest just to make room… for ruins.


  3. Please. Could we have a little less back-patting and a little more effort in decent code?

    Speaking as someone who is paying for your next release of Koha, I’d love to see more effort from the rest of the “ecosystem” to provide innovative, consumer-driven, and bug free software.

    That’s “walk the walk.”


  4. Wow, you are really paying for it? All by yourself? That’s excellent, so I can expect all your patches tomorrow can I?

    You helped back in 1999 as well did you? Funny, I don’t remember ever talking to you then, or indeed ever, in fact the only interaction you have had with me is this one now.

    Have you submitted some bugs on for enhancements, or bugs? Have you in anyway participated in the community, or are you just on the sidelines taking what others work on, and criticising?


  5. Ben, you’re not paying for the next release of Koha, you paying for the next release of Liblime’s new proprietary version of Koha. Good luck with your completely bug-free software, and leave our ecosystem alone.


  6. My apologies for all the fuss I created. I certainly don’t wish to denigrate the work of others. Or offend egos.

    Maybe a better question is this: What’s the beef with LibLime?


  7. Apology accepted, thank you very much for tendering it.
    The beef is with the decision to with hold code, it’s not a specific Liblime beef, the beef would be with whoever made this decision.
    If Liblime does not have the time to integrate the changes back upstream, that is totally fine. I would ask then that they set up a public git repo, so that others can do that integration for them.
    It will make it a lot easier for them to integrate features from upstream into their custom version also.


  8. (You have to scroll to the bottom for “Collaboration” but it’s there.) (This one is better — second paragraph, quoted here.)

    ‘A public software release of each version of LibLime Enterprise Koha will occur periodically, after the sponsoring library and LibLime’s customers have had adequate time to ensure that the codebase is of sufficient quality and stability to be contributed back to the KohaCommunity. LibLime Enterprise Koha software releases will be available from the download page of LibLime’s Website.’

    To Nicole and Owen (especially Nicole) my apologies again for the slur. I know first hand the quality of their work.


  9. Hi Ben
    Thanks for continuing the discussion. While on face value this doesn’t sound to bad. But the big drawback is that if the code is made public just in a big release. We lose all the history of code changes that you get with version control.
    It makes integrating the changes a large magnitude more difficult than if we could pull from a git repository. Hours becomes days. And the more divergent the code becomes (ie the bigger the gap between releases) the days easily become months, cleaning up the conflicting code, bugs that crept in etc.
    If the code was in a publicly available repository we could be merging and testing as we go, maybe even fixing bugs, or spotting them.

    I’m assuming you also extend your apology to the others who have worked on Koha, past and present, remembering of course that Koha was started by Horowhenua Library Trust, and that a huge raft of people, Liblime included, have benefited from that.


  10. When HLT developed Koha back in 2000 we gave it to the world in the spirit of community. We are very happy, delighted in fact, for any organisation or individual to take it, improve it and then give their improvements back.

    Recipricocity is the keystone which gives strength to the Koha Community.

    We do not begrudge vendors taking our gift and building a commercial enterprise out of it, as Liblime, Biblibre and any number of others have done, but the deal is that you give back. This has worked well for a decade and Liblime has been a strong, valued and much appreciated member of the Koha international community over that time.

    So it is incredibly sad and disappointing to me that Liblime has decided to breach the spirit of the Koha project and offer a ‘Liblime clients only’ version of Koha.


Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

%d bloggers like this: