There's a long, convoluted history of issues between the Koha community and Liblime over community 'assets', some of which is summarised here:
http://lwn.net/Articles/386284/
LibLime acquired the Koha portions of Katipo Communications back in 2007, including the koha.org domain name and other assets. The Koha community subsequently had to move to koha-community.org.
"Had to" because Liblime stopped sharing access to the site, something which they had promised to do when taking over maintenance of it (get it in writing next time). Koha.org now exclusively promotes Liblime's non-open fork of Koha.
PTFS/LibLime's "non-open fork" of Koha is available on Github: https://github.com/liblime/LibLime-Koha. We gratefully accept pull requests and bug reports there, as well. We're pushing yet another release there next week.
Shortly after the acquisition of LibLime, PTFS offered up the koha.org domain for sale to several community members, including HLT and other vendors, as a means of hopefully rectifying the relationship with them. No one bit, so we've retained it.
obelos is correct; one of the products supported by LibLime, LibLime Koha (LK for short), is periodically published to the shared GitHub link. The code in that repository is an older version of what LibLime's LK customers are running (4.2 versus 4.6 or 4.8). LK is, to the best of my knowledge, the extension of Harley, a Koha fork put out by PTFS several years ago. obelos: is the new version you're releasing next week 4.4, or something later?
There is also the close-source product, LibLime Enterprise Koha (LLEK), which I believe may have been rebranded as "LibLime Academic Koha". This software is a separate fork from LK, one started by LibLime before it's purchase by PTFS. The announcement can be viewed here: http://liswire.com/content/liblime-announces-liblime-enterpr...
So, PTFS/LibLime has both a non-open fork (LLEK) and a partially open fork (LK). As time passes, these forks diverge further and further from Koha (for example, Koha has since switched templating systems, which makes applying interface layer code from one to the other very difficult).
I must admit, I like the idea of a themed bundle like this. Some of the other bundle deals can seem a bit ... random. It would be good to see software bundles that mirror (or support) particular workflows.
It's a shame they're not sharing more details about what these 'innovative new features' will be though before asking people to commit to a new company. The NY times article mentions browseable “stacks” but it would be nice if Avos could elaborate a bit more on their plans:
LibLime acquired the Koha portions of Katipo Communications back in 2007, including the koha.org domain name and other assets. The Koha community subsequently had to move to koha-community.org.