3 ms·
RhodeCode was already Open Source once and it then went "closed source"[1]. That event resulted in creating a truly Open Source fork called Kallithea[2] (GPLv3)
by adamkruszewski 10y ago
RhodeCode was already Open Source once and it then went "closed source"[1]. That event resulted in creating a truly Open Source fork called Kallithea[2] (GPLv3) held under Software Freedom Conservancy[3] umbrela.
I wonder if they tried to cooperate with SFC, as it seems they have choosen an Open Source license incompatible with Kallithea (AGPL vs GPL3)? Would those two projects try to work together?
There is not much choice if you need Mercurial self-hosting unfortunatelly, so this move is much appreciated.
[1] http://ebb.org/bkuhn/blog/2014/07/15/why-kallithea.html http://ebb.org/bkuhn/blog/2014/07/15/why-kallithea.html
[2] https://kallithea-scm.org/ https://kallithea-scm.org/
[3] https://sfconservancy.org/ https://sfconservancy.org/
- raiso-lo 10y agoAgree, Mercurial definitely lacks a self-hosting platform. Not quite sure about _truly Open Source_ though: AGPLv3 is also Open Source (http://www.gnu.org/licenses/agpl-3.0.en.html http://www.gnu.org/licenses/agpl-3.0.en.html). Regardless of the license compatibility, RhodeCode seems to be developed much more actively (looking at https://code.rhodecode.com/ https://code.rhodecode.com/).
- marcinkuzminski 10y agoHi Adam, We're in constant contact with SFC, we also talked to Bradley about OpenSource RhodeCode. We picked AGPL since this is what we believed would be the best option for us. RhodeCode 4.X is totally different project now, and as for Kallithea, we will see how this works out. We're of course open to cooperate with other projects.