Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Introducing unlimited private repositories

github.com

Post reply on HN
Print view View original

621–630 of 662 posts

Re: Introducing unlimited private repositories

#621

Post by Fomite »

ProblemFactory wrote: post #195
hunvreus wrote: post #130

1. Take a gazillion dollars in funding on an over-hyped valuation, 2. Go through significant organizational changes that end up with the departure of a co-founder (and more suits in the building). 3. Notice that a significant segment of your growth (VC-funded startups) are running out of money. 4. Switch to a user-based pricing to generate more revenue for investors, but spin it as a freebie "Hey! Look at the cool un…

> But I'd appreciate if their PR department didn't expect us to swallow this as a positive change. I don't have any numbers on how people structure their accounts on Github, but my feeling is that this is a positive change for the majority of Github users. Git encourages having many smaller repos for modules over massive single repos. $1/repo/month is fine for active projects, but gets expensive really fast if you wa…

This is a positive change for me as well.

Re: Introducing unlimited private repositories

#622

Post by etjossem »

sytse wrote: post #618
etjossem wrote: post #522

Earlier quoted context omitted.

Creating a Security page on the site to explain your infosec policies would go a long way. I like that we're able to view previous disclosures [1] and active security issues [2], but I had to dig a bit to find them. Surface those. [1] https://about.gitlab.com/vulnerability-acknowledgements/ [2] https://gitlab.com/gitlab-org/gitlab-ce/issues?label_name%5B...

Sorry for the late reply, we've been busy releasing https://about.gitlab.com/2016/05/11/git-repository-pricing/ Anyway, I've added most information to https://about.gitlab.com/disclosure/ with https://gitlab.com/gitlab-com/www-gitlab-com/commit/eab7e345... That page is linked from https://about.gitlab.com/contact/

Awesome, thanks for the quick response.

Re: Introducing unlimited private repositories

#623

Post by rpedela »

giovannibajo1 wrote: post #63
arnvald wrote: post #40

A 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…

Even for software houses, it's VERY problematic as we add customers to projects as external collaborators and we're going to get billed for that forever, even if most customers have very light usage, and even for non active projects. I was thrilled by this news but it's going to be completely unaffordable for us. We have 29 users and 51 external collaborators. We have recently upgraded to the Platinum plan ($2460/yr)…

Would billing your customers for Github access be a solution?

Re: Introducing unlimited private repositories

#624

Post by educar »

sytse wrote: post #423
educar wrote: post #160

Earlier quoted context omitted.

a) They are vc funded b) They give things free to drive up adoption. For example, I don't think it will be free anymore if it was as popular as GitHub. Since that would not be sustainable. IMO, it's a poor decision by gitlab to give things out for free. Instead of innovating on features, they try to keep it cheap.

Having a free GitLab.com doesn't mean we don't innovate on features. See https://gitlab.com/gitlab-org/gitlab-ce/blob/master/CHANGELO... and https://about.gitlab.com/2016/03/29/gitlab-runner-1-1-releas... for features we recently added.

Sorry, I didn't imply GitLab was not innovating. (Apologies for wording my comment poorly). In fact, quite the opposite. I want to see GitLab build a product that people willingly pay for.

(I say the same for all companies. Charge money for your product. If people see value, they will pay.)

Re: Introducing unlimited private repositories

#625

Post by Aldo_MX »

driverdan wrote: post #443
sandGorgon wrote: post #154

Earlier quoted context omitted.

Bitbucket is awesome. Their bug tracker is much better... plus Hipchat for free! Do you seriously spend money on Slack ;)

Slack hasn't had the downtime issues HipChat has had this year.

*yet

Re: Introducing unlimited private repositories

#626

Post by simoncion »

marssaxman wrote: post #600
ak4g wrote: post #583

Earlier quoted context omitted.

It's not necessary, it's a waste of development time and easily the biggest big-picture collective failure of our software engineering profession of the last decade. It easily beats out anything from the $foo.js world and the ongoing low-level security nightmare of web application development, because git, and more importantly, unnecessarily complex and error-prone git workflows have seen adoption across all kinds of…

I have been using git for years and I still find its interface completely inscrutable. I have given up trying to learn it in a way that makes it make sense, and simply use a handful of everyday commands I've memorized by rote and look everything else up when I need it. I can't think of any other piece of software I actually use which has such a messy, non-predictable interface. Even 'make' eventually succumbed to rat…

> I have given up trying to learn it in a way that makes it make sense, and simply use a handful of everyday commands I've memorized by rote and look everything else up when I need it.

? Here are the commands that I have used and make sense to me:

branch, tag, log, diff, push, pull, fetch, commit, rebase (with or without -i), reset, add, rm, mv, stash, status, remote, bisect, reflog, blame, and fsck.

Is this set of commands more or less the same as the set of commands that you've learned by rote memorization?

Re: Introducing unlimited private repositories

#627

Post by therealmarv »

WorldMaker wrote: post #391
therealmarv wrote: post #228

Earlier quoted context omitted.

you are doing it wrong. If you want issue management you will buy Jira from the same company which is superior to github. Bitbucket is one tool of many for Atlassian.

Isn't that the problem, though? GitHub has one Issue tracker that is "good enough" for most projects I've worked on, and gets better over time because GitHub dog foods it (even if they don't always see some of the large open projects issues with it). Bitbucket has two Issue trackers, a "sort of useful" minimalist one that is worse than GitHub's and an upsell to Jira which is maximalist overkill for any project I've w…

I've never said I'm a fan of Jira. I also think it is overkill for all the little projects I've been working on. As other mentioned before here: Maybe look into gitlab.com ... they dogfood their project and the bugtracker is pretty good. https://about.gitlab.com/2016/05/11/git-repository-pricing/

Re: Introducing unlimited private repositories

#628

Post by nikolay »

glusterfuck wrote: post #95
nikolay wrote: post #70

This is way too expensive! Self-hosted GitLab is cheaper and has better uptime! Not to mention, they should have made you pay only for users with commit rights!

Only if you assign no value to your own time, and assume you can do a better job with availability and durability than a dedicated Operations team and a multi-million dollar budget.

Only if you think GitHub is the only SaaS option... which it is not.

Re: Introducing unlimited private repositories

#629

Post by marssaxman »

simoncion wrote: post #626
marssaxman wrote: post #600

Earlier quoted context omitted.

I have been using git for years and I still find its interface completely inscrutable. I have given up trying to learn it in a way that makes it make sense, and simply use a handful of everyday commands I've memorized by rote and look everything else up when I need it. I can't think of any other piece of software I actually use which has such a messy, non-predictable interface. Even 'make' eventually succumbed to rat…

> I have given up trying to learn it in a way that makes it make sense, and simply use a handful of everyday commands I've memorized by rote and look everything else up when I need it. ? Here are the commands that I have used and make sense to me: branch, tag, log, diff, push, pull, fetch, commit, rebase (with or without -i), reset, add, rm, mv, stash, status, remote, bisect, reflog, blame, and fsck. Is this set of c…

Commonly: pull, push, commit -a, reset --hard HEAD, checkout $FILE, status, log, show $HASH.

Sometimes: commit --amend, rebase -i, add, rm, mv, stash [pop|apply].

Rarely: branch, revert.

Git's documentation uses such a wide and flagrantly inconsistent variety of terminology and maintains such a poor distinction between its interface and its implementation that trying to read it actually worsens my understanding and reduces my confidence. I get everything useful from stackoverflow and ignore the docs at this point, and have thus resigned myself to using git as a form of voodoo.

Subversion was so much clearer; I wish it had done a better job with merges and hadn't been so server-dependent. Mercurial seemed to actually care about its interface design, and the DVCS experience might suck less if it had won, but I've never had a chance to actually use it.

Re: Introducing unlimited private repositories

#630

Post by brianwawok »

morgante wrote: post #512
brianwawok wrote: post #433

Earlier quoted context omitted.

Why? If it is Encrypted in ansible vault or something it's not a terrible way to keep your creds.

If they're encrypted, you can put them in a public repo.

Call it overkill, but I would see no reason not to go both private repo + encrypted creds.

Is ansible vault encryption brute force proof? I have no idea. I could spend an hour and figure out. But why not just follow decent engineering principles and double lock my door?

Post reply on HN