News for hackers. Stuff that matters.
Re:GitLab 8.3 released with Auto-merge and GitLab Pages by x1024 on Tuesday December 22, 2015 @08:42PM (#10781538)
What's the "Network effect" for private repos?
Re:GitLab 8.3 released with Auto-merge and GitLab Pages by dajohnson89 on Tuesday December 22, 2015 @08:59PM (#10781587)
I'd imagine the network effect is non-existent for private repos, but for public repos it's huge. And then there's the issue of switching between Gitlab and Github for private/public projects.
Re:GitLab 8.3 released with Auto-merge and GitLab Pages by nalck on Wednesday December 23, 2015 @01:55AM (#10782307)
That's essentially it. GitHub has won its role as the (meta)repository of public record. I suspect many stick with it over its competitors for this very reason.
Re:GitLab 8.3 released with Auto-merge and GitLab Pages by bubalus on Tuesday December 22, 2015 @10:08PM (#10781744)
Just because a repo starts out private, it doesn't mean it has to be private forever.
Re:GitLab 8.3 released with Auto-merge and GitLab Pages by lewisl9029 on Tuesday December 22, 2015 @10:48PM (#10781832)
Exactly this. I generally begin my projects as private GitHub repos and then make them public once they have a MVP-quality demo of some sort.

I also make heavy use of GitHub's issues/milestones system, even on private repos, to keep myself organized. I'd probably use GitLab a lot more if I knew of an easy way to port issues and milestones over to GitHub when I decide to make a project public.

On a related note, can anyone recommend some good external issue tracking systems that integrates well with both GitLab and GitHub?