Connecting Kallithea and RhodeCode

[Sean Farley]

Dmitry Konchalenkov <dmitry at rhodecode.com> writes:

> Andrew,
>
> Thanks for looping in other members! I'm sorry if my email came across the
> wrong way. The tracking code has nothing to do with intentions: it’s being
> applied by a popular Gmail plugin. I’ve disabled the plug-in for this reply.
>
> I want to follow up on just two points: collaboration and RhodeCode’s CLA.
> My goal was to find out how best to invite any interested members of the
> Kallithea community to also join our community. RhodeCode uses the AGPLv3
> license <http://choosealicense.com/licenses/agpl-3.0/>. Like yours, our
> community is open. We respect the skills and creativity of the people on
> this thread. I’ll reiterate the invitation here.
>
> Second, RhodeCode’s CLA <https://rhodecode.com/rhodecode-cla> does not
> require *any* copyright assignment. It also does not impose restrictions on
> what the copyright holder (contributing developer) can do with their work.
> It’s on our web site <https://rhodecode.com/open-source> for any potential
> contributors to see up front.

I'll also chime in. Frankly, given the history of your company and the
bullying it did to community developers, I do not trust RhodeCode. For
me, it's as simple as that.