When comparing GitPrep vs Gerrit, the Slant community recommends Gerrit for most people. In the question“What are the best self-hosted web-based Git repository managers?” Gerrit is ranked 6th while GitPrep is ranked 23rd. The most important reason people chose Gerrit is:
Gerrit supports group and user authorizations for various repositories. Only authorized users can push code to the master branch.
Specs
Ranked in these QuestionsQuestion Ranking
Pros
Pro Private and public repositories supported
GitPrep supports private and public repositories.
Pro Fast and lightweight
GitPrep is written in Perl and uses SQLite as a database, this makes of GitPrep one of the lighter and less resource-intensive alternatives out there.
Pro Easy Installation
GitPrep's setup and installation is very easy. It's only for linux/unix systems though, but it requires just some commands on the terminal to install.
Pro Authorizations for users and groups
Gerrit supports group and user authorizations for various repositories. Only authorized users can push code to the master branch.
Pro Integration with LDAP, bug-tracking tools, CI, etc.
Full integration with LDAP (users, groups), bug-tracking systems (Jira, Bugzilla), CI (Jenkins, Hudson) and other tools.
Pro Configurable project workflow, not always feature branches are the most suitable workflow
Pro Project policy customization can be done with hooks and plugins
Multiple hooks available on various events. Plugin API for more customization of project behavior.
Pro Self-contained installation of Java package, simple upgrades
Most upgrades require only download of new war file and running it in init mode. In some rare cases db reindex is required.
Pro Web UI extension with plugins
A number of plugins available for web UI extension. Plugin API for more customization.
Cons
Con The UI is very cluttered
Gerrit's user interface is very cluttered and messy, and quite ugly to look at. The navigations is also not very intuitive, which may hold some people off.
Con Difficult to customize
Fixing the UI/UX problems with CSS customization is nearly impossible. The markup doesn't include many classes, making it difficult to target CSS rules to specific elements of the interface.