I like GitLab more than Gitorious on a purely technical level, but GitLab unfortunately has a CLA and uses the MIT expat license, whereas Gitorious used the AGPL.
I guess I will just self-host my own GitLab CE instance now.
We have the CLA to ensure this we're on the right side of copyright law. But your article looks interesting and I'll read it.
Great to hear you plan to run GitLab CE, we hope you'll enjoy it.
I appreciate that. I think you have good intentions. The author of the article is Bradley Kuhn, who works at the Software Freedom Conservancy. He's an expert when it comes to the legal aspects surrounding free software projects, so perhaps having a conversation with him about the CLA would be a worthwhile experience.
The CLA is only a license, another license than MIT, but doing _almost_ the same things. IIRC, the difference is that it gives you okay to make proprietary distributions without respecting MIT conditions.
You do not need it to be "on the right side of copyright law".
Using MIT-licensed code is on the right side of copyright law just as well. (unless what you want is to disobey poor old MIT)
The install could use a bit of work, and setting up the repo hosting was somewhat tricky to understand the documents (various users and sudo lines to create). But overall it's pretty fantastic.
> I guess I will just self-host my own GitLab CE instance now.
I moved from Google Code to a forked version of indefero. I would be happy to post the link but I don't want to be a shameless post. Indefero itself actually has some problems that I fixed (such as a scale problem), but otherwise it's pretty stable. I have over 100 projects in my instance and it's working really well.
I used Rhodecode for awhile before they sold out - and while it was nice looking - it seemed like every new version introduced a new bug or issue. It was also a pain upgrading.
A lot of people dislike google code because it doesn't have the "social" aspects of pull requests - but the pull requests I've offered have not been pulled or the author of the project wanted to keep requesting modifications that it just wasn't worth my time. The later was actually an important fix because his project was just completely broken...
I like google code because it's just simple no frills. Uploads/wikis/source all right there.
 - http://projects.ceondo.com/p/indefero/
There is an opening for someone to provide gratis gitlab CE or other exclusively free software based git hosting.
That said I do hope you take steps to reassure people who want to be using an option which preserves their software freedom, for example that the CE will not be slowly deprecated, more features moving into EE.
I admit that making a fully credible commitment is challenging: options include multi-copyrightholder-copyleft which presumably you don't want at all as an MIT licensed project + some proprietary bits in EE, and a variation on the Fiduciary License Agreement used for Qt. But those two options are copyright-focused; there are probably other mechanisms to be thought of.
Recently Gitlab CE has undergone some quite significant UI updates along with very noticeable performance improvements. Excellent work guys!
Signed: a very happy Gitlab CE user.
But adding more features to the open source version every month is great. Hopefully that and a massive userbase sums to making it obvious that any substantial move towards deprecating the open source version will lead to a successful hostile fork, as there will be tons of people able and interested in doing that if necessary, resulting in you never making it necessary. :)
It is sad that enterprises are confused by freedom rather than demanding of it, but that's an issue for the software freedom movement to solve.
On another note, https://about.gitlab.com/better-than-github/ is a well done page. I wish you maximum success.
And yes, the huge community around GitLab will ensure a fork if we turn evil and start crippling the open source version.
Glad you like our comparison page with GitHub :)
It didn't quite fit into our workflow - I think we would like to use gitlab as a beautiful web client, but then push our code there back into our own vanilla git repo on https/ssh. Gitlab seems as it is a turnkey product, repo hosted internally. It was certainly very easy to import our existing projects into it.
May I ask what the reason is you don't want to host the repo's in GitLab itself?
I think your issue lies elsewhere, not on the packaging scheme.
Sometimes, in a lab, it's easier to ask for forgiveness than permission.
I resent the way things went down, such as removing people's repositories, and paying gitorious developers to shut down the project. Those are history now, and I can't say they prevents anyone (anyone paying attention, that is) from taking a different route - fortunately, both projects are freely licensed and data is in git repositories.
They raise questions about the future though: next time people's code would be also removed? Will there be at least three months then, or less?
Why exactly doesn't Gitlab move freely licensed projects?
Since it bought the gitorious.org site, it's like you have two hosting sites, and want to close one down. For freely-licensed projects, making a copy is easy (whether people use it or not) - if Gitlab wanted to.
We don't move projects because we don't want to move them to a new organization and url without explicit consent. We're working with archive.org to make sure nothing is lost.
Destroying what might be the only public repository of some projects, and breaking a ton of existing links, is not something that sounds good.
Edit: I updated the size, it was not 12TB but 4.5
It would be awesome if an other individual or organization is willing to sponsor the hosting costs so we could keep it open longer, if so please email me at email@example.com or comment here.
GitLab bought Gitorious so they could shut it down, not so they could give it to someone else. That is the purpose of acquisitions within the same field.
That's a pretty disingenuous thing to say when it seems like the only reason an "upgrade path" is needed in the first place is because of the acquisition and shutdown.
Edit: Even with Gitorious being "no longer sustainable" in its current form, there are other methods that could have been used (price adjustments, fundraising, etc) rather than an outright and very short-term shutdown.
For now you'll have to install from source https://gitlab.com/gitlab-org/gitlab-ce/blob/master/doc/inst...
More about the memory requirements can be found in https://gitlab.com/gitlab-org/gitlab-ce/blob/master/doc/inst...
Gogs works though.
Regarding "Hosted service?": Tuleap is both on premises (regular Tuleap install ) and/or in SaaS with http://mytuleap.com
Might want to list trac/apache bloodhound, possibly redmine and fossil as well. Otherwise a nice list :)
[edit: Oh, and Launchpad seems like a natural fit for this list as well? Looks like there's some (recent) progress adding support for git to Launchpad as well: https://bugs.launchpad.net/launchpad/+bug/1032731
Edit: I mean, what was the purpose of buying gitorious? The employees? Enticing the gitorious customers and users to use gitlab?
You can view all public projects on GitLab.com via https://gitlab.com/explore
An interesting project is F-Droid, an installable catalogue of FOSS https://gitlab.com/fdroid/fdroiddata
"In my point of view, as long as no deadlock..data race is unavoidable."
Why does GitLab have to kill the AGPL instance of Gitorious they aqquired? Most of the people I know who use Gitorious.org did so so we could use an AGPL service to host our repositories. GitLab simply does not do this as it uses a lax permissive license. In addition to this they impose CLAs on any contributors :/ sigh
It is really a shame that GitLab feels the need to remove the only AGPL service that fills this need. I do not know where I will be migrating my repositories, but it will not be GitLab unless they wish to offer the community an AGPL instance.
Plus, it's really cross platform, and you don't have to work on 5 different versions of the same app, while not excluding any mobile OS.
You guys are maybe celebrating a bit too much. Cut down on the drinks. ;)
Why no XMPP, or phone, or physical address?