News for hackers. Stuff that matters.
Re:Dear open-source maintainers, a letter from GitLab by Vespasian on Monday January 18, 2016 @06:22AM (#10923754)
We are dealing with a lot of sensitive data and code which is legally not allowed to physically leave our group and GitLab is in my opinion the best open source choice for that.

I feel its community edition is up to par with github in most aspects and it a was a change towards the better from our previous svn based solution (Redmine)

Re:Dear open-source maintainers, a letter from GitLab by dev360 on Monday January 18, 2016 @06:30AM (#10923779)
A good friend of mine likes to run https://gogs.io/ .. I havent used it heavily but Ive been impressed so far.
Re:Dear open-source maintainers, a letter from GitLab by kzrdude on Monday January 18, 2016 @09:22AM (#10924504)
I wonder why they advertise the "platform"/implementation language so clearly (in this case Go). It shouldn't matter for the users? I get sceptical, as if the only reason they exist is to provide the same service but in a new implementation.
Re:Dear open-source maintainers, a letter from GitLab by rcarmo on Monday January 18, 2016 @02:30PM (#10926325)
Performance. That thing is _fast_ when compared to a Ruby-based stack.
Re:Dear open-source maintainers, a letter from GitLab by Ellahn on Wednesday January 20, 2016 @12:11AM (#10936192)
Does this really affect end users? In the end, this decision should mostly mean less servers, no...?
Re:Dear open-source maintainers, a letter from GitLab by rcarmo on Wednesday January 20, 2016 @05:23PM (#10941844)
Sysadmins are people too :)
Re:Dear open-source maintainers, a letter from GitLab by johnmaguire2013 on Monday January 18, 2016 @04:59PM (#10927315)
I've been using Gogs for personal use for a while. I love its speed and its simplicity.

That said, it's probably not a good fit for most businesses at this point. It's relatively new, and mostly maintained by a single developer, who spent the last summer on vacation.

He's very active when he's around, and almost always working on improving Gogs, but there's a lot of people with features requests (the issue that's always getting comments today is for opening pull requests across branches within a single repository -- i.e. not forking.)

Re:Dear open-source maintainers, a letter from GitLab by talideon on Monday January 18, 2016 @07:40AM (#10924044)
It's a bit of a pity that they don't self host, even if they also have a Github repo.
Re:Dear open-source maintainers, a letter from GitLab by bovermyer on Monday January 18, 2016 @07:16AM (#10923933)
I was unaware of this. Thanks for the link.

It seems just about everything is being re-written in Go these days...

Re:Dear open-source maintainers, a letter from GitLab by xena on Monday January 18, 2016 @08:22AM (#10924202)
Go is easier to deploy than Rubby on Fails.
Re:Dear open-source maintainers, a letter from GitLab by quesera on Monday January 18, 2016 @08:35AM (#10924265)
> Go is easier to deploy than Rubby on Fails.

You could have said that without cheapening the level of discourse.

Re:Dear open-source maintainers, a letter from GitLab by dham on Monday January 18, 2016 @08:53AM (#10924346)
Does that even matter in the world of Docker?
Re:Dear open-source maintainers, a letter from GitLab by bovermyer on Tuesday January 19, 2016 @04:48PM (#10934341)
Yes, because not everyone uses Docker yet. Some may never adopt it. So long as that remains a viable path, then the matter of deployment systems and complexity is relevant.
Re:Dear open-source maintainers, a letter from GitLab by Ellahn on Wednesday January 20, 2016 @12:15AM (#10936201)
Unless you are smart enough to be a Rubyist.

If you're not you just seem like someone who came to the NodeJS Party late and didn't understand Go is C for gigantic codebases using parallelism. :D

Re:Dear open-source maintainers, a letter from GitLab by niutech on Monday January 18, 2016 @02:10PM (#10926198)
You should also consider Apache Allura (https://allura.apache.org/), Fossil (http://www.fossil-scm.org/), Phabricator (http://phabricator.org/) and GitBucket (https://gitbucket.github.io/gitbucket-news/).
Re:Dear open-source maintainers, a letter from GitLab by rplnt on Monday January 18, 2016 @06:57AM (#10923875)
There's also Stash (now renamed to BitBucket Server (edit: fixed name, as pointed out in the reply)). It does not include some of the features (such as issue tracking), and I think rightly so. I haven't used GitLab for maybe 2 years now, so I can't compare the two.
Re:Dear open-source maintainers, a letter from GitLab by johnmaguire2013 on Monday January 18, 2016 @05:01PM (#10927322)
To be clear, it doesn't support issue tracking because it is an Atlassian project. Issue tracking is done through Jira, another product they offer.
Re:Dear open-source maintainers, a letter from GitLab by nate148 on Monday January 18, 2016 @07:00PM (#10927954)
Umm no, you are incorrect. Bitbucket does have its own issue tracker like GitHub.. (but it is not turned on by default) and what I am referring to is NOT JIRA Software.

https://confluence.atlassian.com/bitbucket/enable-an-issue-t...

Re:Dear open-source maintainers, a letter from GitLab by johnmaguire2013 on Tuesday January 19, 2016 @12:20AM (#10929010)
That looks to be for Bitbucket Cloud. We were discussing Bitbucket Server, the hosted solution.
Re:Dear open-source maintainers, a letter from GitLab by lmm on Monday January 18, 2016 @07:13AM (#10923919)
It's named bitbucket server or something like that - don't confuse it with bitbucket proper.