dmitry-k

Agree. However, large enterprises usually have common compliance/access control policies, something not easily implemented across multiple VCS (unless there's a full-fledged internal development team dedicated to that).

Working in a big firm adds overhead, yet has certain benefits (resources, etc.). That's a whole different topic though.

At RhodeCode (https://rhodecode.com) we believe it's up to a team to decide, which version control better fits their needs and preferences.

Some companies even have Git, Mercurial, and SVN, working all together under centralized repository management.

@e12e Try RhodeCode (https://rhodecode.com), we have quite a few educational users (e.g. Carnegie Mellon University) using RhodeCode in the way you described. RhodeCode also has secure authorization, user permission management and a web interface. One can even edit/commit directly from within a built-in web editor.

Couldn't agree more. In RhodeCode (https://rhodecode.com) we use Pull Requests with a voting system. Interested reviewers are added automatically, depending on the repository and the changes being made.

Merge and rebase for pull requests might soon land in RhodeCode too.

Mozilla uses Mercurial too. Not to mention other companies from all the different industries using Mercurial with RhodeCode.

RhodeCode is self-hosted, but you can run it in Azure/Amazon cloud. For large companies, that setup might prove even more stable than relying on someone else's cloud [1]

[1] GitHub's down? https://news.ycombinator.com/item?id=9497821

@dvdgsng We're better than ever, thanks! I don't know if you heard, RhodeCode CE is now free and open source. Feel free to join our Slack: https://rhodecode.com/join

We'll be rolling out a major release next week, might be the right time to spread a word to colleagues ;)

>No more productivity drop when github is down

It could have been the motto of RhodeCode (https://rhodecode.com). Self-hosted repository management not only has a benefit of having one's uptime under control, but also is much more secure.

That's not true. Some parts (e.g. CSS and images) never were open source.

You can read more about why RhodeCode went back to open source (AGPL) here: https://rhodecode.com/blog/113/rhodecode-goes-open-source

@zardeh Totally agree in that adding friction is bad. At Rhodecode, we tried to eliminate it, by creating a dedicated page for contributors (https://rhodecode.com/open-source) and allowing to login via GitHub / BitBucket.

One more point: although the contributions are not made for the recognition alone, a bit of it never hurts. We ended up with a badge system for https://community.rhodecode.com , where code contributors get rights to moderate discussions (since they ARE the core users of RhodeCode).

RhodeCode is free and open source: https://rhodecode.com/open-source .

https://try.rhodecode.com:

#1 It plays nicely with existing trackers and CI tools.

#2 RhodeCode fully supports Git, Mercurial & SVN (hence no VCS lock-in).

@lackbeard https://try.rhodecode.com RhodeCode has a modern UI, with automated PR's, and configurable integrations(CI/issue trackers) across Git/Mercurial/SVN.

Since RhodeCode is open source, it can be tailored to one's own needs.

RhodeCode has a configurable diff limit. There's no problem in displaying 10K+ lines in a diff. https://rhodecode.com/features/productivity

In fact, it's a part of our code review/pull request functionality, therefore "it just works".

@ghettosoak, Dmitry from RhodeCode team is here! Have you considered https://rhodecode.com ?

RhodeCode CE is free, self-hosted & open-source, with code review tools, user management, and automations. It takes ~5mins to get your own instance up and running. Most of RhodeCode users have secure, behind-the-firewall repositories, where conventional tools are not enough. Seems like a good fit for your case.

I realize you are using Git, however if you collaborate with an external partner or customer, RhodeCode supports Git, Mercurial & SVN repos _simultaneously_ . See, should you decide to migrate from one VCS to another, we got you covered :)

Besides, we have a great engineering culture, hence performance has never been a problem (e.g., we use Elasticsearch for full-text code search). Ask our users on #Slack: https://rhodecode.com/join

Nice post on the SaaS offerings! That, however, is not an option for enterprises where source code is that critical, it should "never leave the perimeter".

Those firms need a behind-the-firewall kind of security, under a common software platform, preferably open source (like rhodecode.com).

In other words, it is a must to have source code management that is developer-focused (with code reviews, pull requests and automation), yet provides unified security across the code base, with access controls and common authentication.

Thanks! Added the license information (we're AGPL) and links to the source code.