Launchpad vs RhodeCode

Launchpad makes it easy to translate free open source projects into virtually any language in the world. Users are allowed to start working on translating any project they want just by having a Launchpad account and a web browser. Most of the time they don't have to even join a team to start working and the editor is web based, so there is no need for any special software.

If you use launchpad, it gives you a build system (on their platform) as well as easier deployment - user merely adds your PPA to their sources.list file. Deployment (on Ubuntu, at least - other debians as well) doesn't get simpler than this.

Launchpad is built to be used for open source projects, as such it needs a powerful bug trackers to allow developers who want to contribute to jump right in. Launchpad displays bug statistics (total number of bugs, number of bugs fixed etc...) as well. Bugs can be searched and displayed from every project hosted on Launchpad or for single projects.

It's open source and it can be installed on your own machine, which gives high security and isolated environment for the codes. Whole application installation is super easy and independent from the Linux distribution.

RhodeCode supports Mercurial, Git and Subversion in a unified way that allows you to do code-reviews and other stuff on each of them.

User management is centralized around administrators which can give granular permissions to individual users or user groups/. These permissions can be related to allowing contributions, editing, or simply giving read-only access to users.

Code reviews can be done via Pull Requests, or simply commit-by-commit. There are voting rules, random reviewers pools, and smart comment invalidation logic. Pull requests are also versioned so it's easy to review partial changes after the author has updated his code.

When you create a Pull-request you can add set of reviewers. They all have to vote and approve the PR. There's some flexibility on how the voting is accepted, it can be majority wins, or all-agree. Good practice is to add BOT accounts like jenkins, that also will vote on the review, based on for example tests run, and can forbid a merge because of a negative vote. In addition users can leave special type of comments that will also prevent merges, aka TODO notes. Once TODOs are resolved a Pull Request can be merged.

RhodeCode CE (Community Edition ) is free and open source. Enterprise Edition (EE) adds premium support, corporate authentication. and tool integrations on top of the RhodeCode CE.

RhodeCode has auth plugins, now supported include: LDAP, LDAP with user groups, TOKEN, Container auth, PAM

Files can be added, modified and deleted from the web interface, including adding directories, and uploading files.

RhodeCode have the most advanced Permission system on the market, allowing things like permission inheritance, permission delegation. All comes in a format that doesn't get hard to manage at scale.

The builtin header auth can delegate authentication to other existing systems for further validation chain.