This is an incomplete overview over the Pros and Cons of various code hosting providers and version control systems.

Code Hosting

GitHub

Pros

• Currently used
• Well-known
• Good UI
• Good CI

Cons

• Policies drive away contributors
• Problematic for FOSS

Launchpad

Pros

• Previously hosted there
• Good bugtracker and project page UI

Cons

• No CI
• Bad merge request UI

Codeberg

Pros

• FOSS-oriented
• Interface very similar to GitHub

Cons

• Unknown site
• Experimental CI

GitLab

Pros

• Interface similar to GitHub

Cons

• Unknown site
• Limited CI time (50000 minutes)

Table format

	GitHub	Launchpad	Codeberg	GitLab
familiarity	3	3	0(+)1	0
UI	3	2	3	2
CI	3	0	0(+)	1
user base	3(-)	1	0	2
stability	3(-)2	3(-)3	?	3
FOSS	-3	-1	3	0
policy	-3	0	1	0

CI Service Providers

Github Actions

Pros

• Provides a lot of Target OS

Cons

• See Github cons

CircleCI

Pros

Cons

Travis

Pros

Cons

Appveyor

Pros

Cons

VCS

Git

Pros

• Currently using it
• State of the art
• Performant and efficient
• Well-known for new contributors

Cons

• Hard to learn

Bazaar / Breezy

Pros

• Previously used
• Nice merge conflict resolving
• Easy to learn

Cons

• Outmoded
• Slow and inefficient
• Little-known for new contributors
• Moving would lose our commit history

Subversion

Pros

• Previously used
• Nice merge conflict resolving

Cons

• Very outmoded
• Slow and inefficient
• Little-known for new contributors
• Moving would lose our commit history