|
⇤ ← Revision 1 as of 2015-07-22 10:15:30
Size: 2281
Comment: New page, beta
|
Size: 3357
Comment: improving
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 28: | Line 28: |
| === Other solutions === * savannah.gnu.org * gna.org * gitlab |
=== Some other solutions === See [[https://en.wikipedia.org/wiki/Comparison_of_source_code_hosting_facilities|this WikiPedia article]] for an extensive list and comparison. Here thoughts on some of these platforms and some services which are not mentioned in the WikiPedia article: * [[http://savannah.gnu.org|savannah.gnu.org]] * Runs on Savane * 100% Free Software * [[https://takezoe.github.io/gitbucket/|GitBucket]] * Description: "GitBucket is a GitHub clone powered by Scala" * Free Software (Apache License) * Provides functionalities like issues, wikis, pull requests... * Similar to workflow of GitHub * [[http://gna.org/|gna.org]] * Runs on Savane * 100% Free Software * [[http://gitlab.com|GitLab]] |
| Line 33: | Line 45: |
| * open-core (proprietary extensions) * usable FS solution * experience similar to github * allura * phabricator * seems to be good, but complicated for many people * gitbucket * similar to workflow of GH * github-backup |
* Open-Core model * Community Edition (CE) is Free Software and quite usable * Enterprise Edition (EE) is under a proprietary license and contains features not available in CE * Experience is similar to GitHub * Phabricator * Seems to be good, but complicated for many people * [[https://github.com/joeyh/github-backup|github-backup]] * "github-backup is a simple tool you run in a git repository you cloned from GitHub. It backs up everything GitHub publishes about the repository, including branches, tags, other forks, issues, comments, wikis, milestones, pull requests, watchers, and stars." |
| Line 44: | Line 55: |
| - If a program belongs to a bigger community (KDE, Gnome, Apache, GNU), host it on their platforms to increase synergy effects - If it's something different, look at Free Software platforms (see above). If your project gets bigger, you'll need an own website, wiki or mailing list anyway. So why not an own git repository from the beginning? - If even that is no solution, look at GitHub.com or GitLab.com but be aware of the downsides! |
1. If a program belongs to a bigger community (KDE, Gnome, Apache, GNU), host it on their platforms to increase synergy effects 1. If it's something different, look at Free Software platforms (see above). If your project gets bigger, you'll need an own website, wiki or mailing list anyway. So why not an own git repository from the beginning? 1. If even that is no solution, look at GitHub.com or GitLab.com but be aware of the downsides! |
| Line 49: | Line 60: |
| - Creating a multiplexer: 1 client for many networks and platforms - More initiative of people to pay for (Free Software) services - More ways to connect decentral instances to increase visibility for a project |
* Creating a multiplexer: 1 client for many networks and platforms * More initiative of people to pay for (Free Software) services * More ways to connect decentral instances to increase visibility for a project |
Thoughts about different Version Control Systems
Version Control Systems became very popular in the last years. We as Free Software Advocates should be aware of the different platforms, projects and companies in this sector. Therefore, we collect some thoughts about popular services and their alternatives.
Single VCS solutions
GitHub
Why is GitHub so popular?
- New level of source code hosting: Git, Wiki, issue tracking, collaboration inside and outside a project
- One tool for all
- in contrary to GNU philosophy
- GH is big, makes projects visible and collaboration easier
Positive
- New and effective workflow of fork-edit-pull
- Could have had a positive effect on Free Software projects. Possible reasons:
- more FS projects
- easy collaboration
- probably quality boosts
- We have to think about: Is it better to have more FS projects overall on some non-free platforms, or less FS projects but only on free platforms?
Negative
- Lock-In effect
- Contra: Clients are free, APIs are public to move projects to other platforms
- No lock-in by technical restrictions but by habits?
Some other solutions
See this WikiPedia article for an extensive list and comparison. Here thoughts on some of these platforms and some services which are not mentioned in the WikiPedia article:
- Runs on Savane
- 100% Free Software
- Runs on Savane
- 100% Free Software
- can be self-hosted, but also used on gitlab.com
- Open-Core model
- Community Edition (CE) is Free Software and quite usable
- Enterprise Edition (EE) is under a proprietary license and contains features not available in CE
Experience is similar to GitHub
- Phabricator
- Seems to be good, but complicated for many people
Recommendations:
- If a program belongs to a bigger community (KDE, Gnome, Apache, GNU), host it on their platforms to increase synergy effects
- If it's something different, look at Free Software platforms (see above). If your project gets bigger, you'll need an own website, wiki or mailing list anyway. So why not an own git repository from the beginning?
If even that is no solution, look at GitHub.com or GitLab.com but be aware of the downsides!
Possible ways to improve situation:
- Creating a multiplexer: 1 client for many networks and platforms
- More initiative of people to pay for (Free Software) services
- More ways to connect decentral instances to increase visibility for a project