I am strongly considering moving to gitlab.
They have CI within gitlab.com even for private repos :)
Introducing unlimited private repositories
131–140 of 662 posts
Re: Introducing unlimited private repositories
#132The per user pricing is pretty reasonable but only when you think of seeders (publishers/editors/pushers call them as you like).
For instance I would love to subscribe to a BI cloud suite that really fit my need, but I'm basically the sole query editor and I have potentially 200 private readers + some public OpenData. I simply just can't come to my boss and ask that we subscribe to this service on a 200 users basis while only one users will really have the use of the license...
Re: Introducing unlimited private repositories
#133Earlier quoted context omitted.
Bitbucket is terrible though, so what does it matter?
Can you clarify? Why is Bitbucket "terrible"?
Bitbucket's issue tracker is such a pain to work with. I remember being redirected to a new page whenever I had to create a new tag. Then I'd loose the content of the issue I had started to write, something like that.
Re: Introducing unlimited private repositories
#134Earlier quoted context omitted.
Bitbucket is terrible though, so what does it matter?
Can you clarify? Why is Bitbucket "terrible"?
https://bitbucket.org/site/master/issues/2874/ability-to-sea...
Integration with Jira is nice though.
Re: Introducing unlimited private repositories
#135A small comparison: Team | Cost Before | Cost Now 1 repo, 5 users | $25 | $25 1 repo, 10 users | $25 | $70 11 repos, 5 users | $50 | $25 11 repos, 10 users | $50 | $70 5 repos, 50 users | $25 | $430 50 repos, 5 users | $100 | $25 50 repos, 50 users | $100 | $430 I'm not sure how common are organizations with few users and large number of repose - I guess software houses that keep old projects (for maintenance and fut…
But to me this makes sense - one naturally will have more repos than developers, and as it is costly to add a developer to your team, but adding a repo is a command line, then making cost a function of developers seems to align most software teams with githubs incentives.
The real place where it hurts is users who aren't paid employees.
Re: Introducing unlimited private repositories
#136Earlier quoted context omitted.
Except that now GitHub is 9x more expensive than BitBucket (and for a team under 5 developers, GitHub is $25 vs. BitBucket's $0).
Well, 7x, but yes, GitHub is more expensive. $70 for 10 developers is still really cheap. Personally I prefer the GitHub interface and $60 is still within the range of even smaller companies.
Re: Introducing unlimited private repositories
#137Re: Introducing unlimited private repositories
#138Earlier quoted context omitted.
Why? BitBucket is superior in every respect, plus importantly they give free private repos for every user. No price gouging like we're seeing with GitHub.
Oh, come on. It's OK to dislike this change, but "BitBucket is superior in every respect" and "price gouging" are far from objectively obvious.
Re: Introducing unlimited private repositories
#139Do outside collaborators count as paid users?
Hi alanfranzoni, Outside collaborators on public repositories of an organization are free. Only the ones invited to collaborate on private repositories are counted as paid users. Hope this helps!
Re: Introducing unlimited private repositories
#140I'm sure a lot of people will be moving from Bitbucket to this, Bitbucket's plans were great for hundreds of repos, but Github's ecosystem is definitely preferable.