The future of this project

[Marcin Kuźmiński]

Hi Andrew,

There have been many efforts to create this project. However, because it's
a RhodeCode based project I'm following
it closely. I must say that for me this project looks quite dead. We have
more and more users moving from Kallithea to RhodeCode, strictly because
really no new relevant features are developed.
And I understand it, RhodeCode had so much legacy stuff cleaning things up
took us many many months...
No company will bet on Kallithea seeing such stale state. There are lots of
FOSS project now doing source code management and they are very active.

For me personally contributing to open source projects is something more
than helping the maintainers to move the project forward. We have the
capacity inside the company to produce regular releases, however
community driven contributions often improve things around the project. One
of the goals of a project such as RhodeCode is to help Mercurial be
relevant because of great tooling around that project.

No one can guarantee that OpenSource project will stay, because a lot of
things can happen.
Currently, there's AGPL version, one can fork it and move it forward if
you're unhappy about people behind it. Just look what happened with
Gogs/Gitea.

>From my perspecitve, there's close to 0% chance for RhodeCode beeing merged
with Kallithea, because of our Brand, and simply at this point those are
two VERY different projects
written in two incompatible web frameworks. We provide infrastructure and
installer for RhodeCode cannot imagine re-implementing it for another
project (just too much effort)

I'm absolutely open to discussing RhodeCode to join and help the community,
however the state of Kallithea as community project doesn't look promising.
And honestly, from my observation the main driver behind developing new
feature of it were from one very big commercial company :)

If someone has better alternative we're open for discussion, i think we
want to have the BEST possible project that support Mercurial.

Best,


On 13 June 2017 at 12:30, Andrew Shadura <andrew at shadura.me> wrote:

> On 13/06/17 10:04, Marcin Kuźmiński wrote:
> > Hi All,
> >
> > Given the opportunity of this email thread, i'd like to pitch in the
> > open-source version of RhodeCode CE again.
> >
> > - A fully functional, free AGPL v3.0 software
> > - based on a modern web framework - Pyramid
> > - we had almost 20 releases in last 12 months
> > - introduced major features like Git LFS, Mercurial Evolve
> > - per repo settings
> > - web mergeable pull requests
> > - integration framework
> > - and many more
> > - a quickly growing community use base we currently have over 170 people
> > on our community slack channel.
> >
> > As a part of Management team i must admit that close sourcing the
> > project was a big mistake, however, we learned our lesson, and bet on
> > the new business model that is based on OpenSource Core and RhodeCode
> > will have a CE free edition.
> >
> > We talked a bit about some co-operation, and i believe it's a good time
> > to re-think this. I'll be blunt, i think that it doesn't look like there
> > a sense of two such similar open-source projects to exist.
> >
> > I highly valued contribution from this community that was done into the
> > RhodeCode codebase, i invite everyone again to join and have an
> > influence on the tool you or your company is using regularly.
> >
> > Happy to chat about any options again, if someone is interested.
>
> This is very nice of you Marcin, but honestly I'm struggling to imagine
> how is going to work. Are you suggesting we abandon Kallithea and all
> hard work we’ve done and just go help develop RhodeCode? Yes, there
> seems to be a lot of development in RhodeCode, but is there really a big
> community around it? From the Mercurial log it looks more like a single
> person project (while certainly you do a lot of work!). What if
> something happens to the company again?
>
> I understand how you feel about the project you started, but I don't
> think it is the best idea to join to projects by abandoning one
> developed by the community. It would be much better if the company could
> become a member of the community instead.
>
> I'm not saying "no, we don't want to work with you", not at all. What
> I'm saying if we want to work together, we need a better plan.
>
> --
> Cheers,
>   Andrew
> _______________________________________________
> kallithea-general mailing list
> kallithea-general at sfconservancy.org
> https://lists.sfconservancy.org/mailman/listinfo/kallithea-general
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sfconservancy.org/pipermail/kallithea-general/attachments/20170614/7239953d/attachment.html>