Difference between revisions of "GitHostingSoftware"

Some info to help with comparing git hosting software packages. See GitInfrastructureComparison

Git Server Software

GOGS

Github.com

Dev-Info: https://developer.github.com/v3/ https://developer.github.com/v3/#authentication https://developer.github.com/webhooks/

GitLab

“You will be running Sidekiq, Unicorn, Nginx, Ruby (plus all its gems) and then Gitlab itself.”

Kallithea

cgit

gitbucket - JVM

gitblit - JVM

http://gitblit.com/

Phabricator + Diffusion

gitolite

http://gitolite.com/gitolite/index.html

Apache Allura

Misc

Other Links

YA Feature Comparison Page

https://en.wikipedia.org/wiki/Comparison_of_source_code_hosting_facilities

FOSS dot-org Git Implementations

Apache Foundation Git

Please contact the infrastructure-dev@apache.org mailing list if you have comments or suggestions regarding this service.

Apache Software Foundation (ASF) infrastructure has evolved over more than a decade, with several major internal revisions, leading to the current implementations. ASF infrastructure design has concepts of mirrors (sites) and committers (people) built-in throughout. The ability of an ASF project to semi-autonomously create its own repositories and web presence, which then benefits from shared authentication, backup and other infrastructure services, is fundamental. Core servers were BSD and Solaris as well as Linux; small tools are often bash, perl, xslt and others; substantial backend engines are often implemented in java.

The 2013 U.S. Form 990 lists gross income for the ASF as $1.1 million, with $489k spent on infrastructure maintenance and development.

Guidelines for New Project Steering Committee Members: http://www.apache.org/dev/pmc.html#newcommitter http://www.apache.org/dev/pmc.html#SVNaccess

This tool is part of the committers-to-permissions chain: https://svn.apache.org/repos/asf/infrastructure/site/trunk/people/keys-fetch.py https://svn.apache.org/repos/asf/infrastructure/site/trunk/people/keys-README https://people.apache.org/keys/committer/

An example of an early 2000's era, xml process to auto-generate sites with permissions: https://svn.apache.org/repos/asf/infrastructure/site-tools/trunk/projects/HowItWorks

Misc ASF entrypoint: https://svn.apache.org/repos/infra/infrastructure/trunk/projects/whimsy/www/secretary/workbench/worklist.cgi

ref: https://mail-archives.apache.org/mod_mbox/whimsical-dev/201506.mbox/%3CCAFG6u8FoEb_KVwvtuiyYvo7JrwTqkWSbBsN4+Kf=dfP2wVcZcQ@mail.gmail.com%3E

A 2009 Infastructure Incident Report: https://blogs.apache.org/infra/entry/apache_org_downtime_initial_report

Debian Project Git

The Debian Project hosts extensive, custom-built project and package infrastructure including a comprehensive git interface using cgit, replacing an earlier gitweb system (when?).

cgit Browser: http://anonscm.debian.org/cgit/users/eric/gnupg2.git/

gitweb Repository Browser Example: Vcs-Browser: http://anonscm.debian.org/gitweb/?p=pkg-gnutls/libgcrypt.git;a=shortlog;h=refs/heads/branch1.6

Kernel dot org Git

05Mar2015 -- Linux Foundation System Administrator Konstanin Ryabitsev mentions gitolite and cgit LINK

https://git.kernel.org/cgit/

Wikimedia Foundation Git

twentyafterfour on #wikimedia-labs: phabricator might still be a decent way of managing your repositories; our phabricator accepts LDAP logins plus OAuth. It's essentially the same thing as gitolite but with a lot more automation around account management, key management and hooks. Phabricator integrates all of that into one package (which can still be somewhat automated / integrated with other tools) Gitolite likely doesn't support LDAP; certainly a lot lighter weight than Phab stack, if you are comfortable with perl and don't mind doing a bit of integration work; you have to deal with account management yourself.

mutante on #wikimedia-devtools says: we currently use gerrit for code review gerrit.wikimedia.org and gitblit for git.wikimedia.org. Things are being migrated to phabricator.wikimedia.org though diffusion. You are in the right channel. You can git clone all of our server configs btw. it's a puppet repo and all public. you might also be interested in wikitech.wikimedia.org, our labs environment where you can get free virtual machines to test things

General Attributes of Git Hosts

Implementation Language
License
Machine Resource Usage

Common Features

Dashboard & File Browser
Issue Tracking, Milestones & Commit keywords
Organizations support
Wiki
Code Review
GIST
Web Hooks

Feature Comparison

login via LDAP
private repositories
external issue tracker
internal issue tracker
tool to migrate from trac
external wiki
internal wiki
organization management
comment issues via mail
PostgreSQL backend
Multilanguage
Comments on diff lines
Pull requests
Webhooks
CL
tracking of forks

@@ Line 85: / Line 85: @@
 Apache Software Foundation (ASF) infrastructure  has [http://www.apache.org/history/timeline.html evolved] over more than a decade, with several major internal revisions, leading to the current implementations. ASF infrastructure design has concepts of '''mirrors''' (sites) and [http://people.apache.org/phonebook.html?unix=committers '''committers'''] (people) built-in throughout. The ability of an ASF project to semi-autonomously create its own repositories and web presence, which then benefits from shared authentication, backup and other infrastructure services, is fundamental.  Core servers were '''BSD''' and '''Solaris''' as well as '''Linux''';  small tools are often bash, perl, xslt and others; substantial backend engines are often implemented in java.
+The 2013 U.S. Form [https://www.apache.org/foundation/records/990-2013.pdf 990] lists gross income for the ASF as $1.1 million, with $489k spent on infrastructure maintenance and development.
 Guidelines for New Project Steering Committee Members: