Live data from Hacker News

GitHub Enterprise 2.0

enterprise.github.com

51–60 of 68 posts

Re: GitHub Enterprise 2.0

#51

Earlier quoted context omitted.

Why Ubuntu over Debian, out of curiosity? I've seen Spotify switch from Debian to Ubuntu and regretting it already.

When I made the decision for my shop, we chose Ubuntu because of the guaranteed support cycle. Debian's support windows were too short, and we need to be able to plan years ahead of time for when we must spend the time to upgrade the OS. It takes a lot of testing and tweaking, and Debian didn't give us any certainty beyond a few months out. Ubuntu gives us a five year guarantee (and they've been sticking to that for…

> Debian didn't give us any certainty beyond a few months out.

Actually, now they do: https://wiki.debian.org/LTS

Re: GitHub Enterprise 2.0

#53

Earlier quoted context omitted.

Our experiences with GitLab have been really positive. GL may not be on par with GHE UX wise, but I don't really feel that this has been an issue for us. Coming from GH or GHE, GL is a little more difficult to navigate, but it's getting better with each release. The thing that probably bugs me the most is the home page for a repository being the activity stream. However, considering that we're saving $25k per year by…

Looks like we're still on 7.3.1. I don't see anything in the release notes for more recent versions about syntax highlighting, but they might have snuck something in, or it could be a dependent package change. 25k sure is a lot of money. Then again, can you put a price on the frustration of developers used to working with something better? Maybe.

25k is for 100 developers, and we actually have more users than that. GHE is really pricey. However, I don't hear complaints about GitLab, probably because everyone was coming from SVN, and they have little experience with GH.

Re: GitHub Enterprise 2.0

#54

Earlier quoted context omitted.

We're running 12.04 on github.com so made sense to sync them up.

Why Ubuntu over Debian, out of curiosity? I've seen Spotify switch from Debian to Ubuntu and regretting it already.

Because Debian doesn't provide enterprise support. Let say that you've got a critical bug somewhere, do you really think you can tell your boss 'Yeah I asked on IRC / forums / mailing list to get an ETA'

Re: GitHub Enterprise 2.0

#55
post #51

Earlier quoted context omitted.

When I made the decision for my shop, we chose Ubuntu because of the guaranteed support cycle. Debian's support windows were too short, and we need to be able to plan years ahead of time for when we must spend the time to upgrade the OS. It takes a lot of testing and tweaking, and Debian didn't give us any certainty beyond a few months out. Ubuntu gives us a five year guarantee (and they've been sticking to that for…

> Debian didn't give us any certainty beyond a few months out. Actually, now they do: https://wiki.debian.org/LTS

Not even close: "Debian-LTS will not be handled by the Debian security team, but by a separate group of volunteers and companies interested in making it a success (with some overlap in people involved)."

Re: GitHub Enterprise 2.0

#56
post #50

Over a year I started the process of convincing the people I needed to at my job (Federal, Non Defense/Law Enforcement) to get an instance of Github Enterprise installed. Though it took a lot of time and effort, I managed to get both the approval and funds needed for a small scale - 10 user - install (on my 3rd try, gov't is really against change). Our current "enterprise" VCS is PVCS (so old I had to look it up). Th…

Having previously used a single seat-pack deployment (the aforementioned $5k minimum order), and having sent a fairly substantial amount of questions/requests to GitHub's enterprise support folks, I'm not sure what you mean by "too small for them to care".

It's not like they're going to be exchanging tech stuff with your billing person, so not sure what issue you're referring to in your last sentences.

In order for GitHub to take away anything actionable from your example, they'd need more details on what issues actually occurred with the interaction.

Re: GitHub Enterprise 2.0

#57
post #50

Over a year I started the process of convincing the people I needed to at my job (Federal, Non Defense/Law Enforcement) to get an instance of Github Enterprise installed. Though it took a lot of time and effort, I managed to get both the approval and funds needed for a small scale - 10 user - install (on my 3rd try, gov't is really against change). Our current "enterprise" VCS is PVCS (so old I had to look it up). Th…

> A couple months ago, the entire thing collapsed on my face and we went with gitlab instead. Why? Because github's sales team f*ed it up. Apparently, the $5k minimum order was too small for them to care (at least that's what my side says). Too bad, I really wanted to get them in the door.

Ben Balter from GitHub's government team here. I'm sorry to hear we let you down. Please let us make it up to you. You (or anyone else) should feel free to reach out to me any time at government@github.com, and I'll personally help navigate the process.

For what it's worth, we care a lot about the experiences of all our users, whether you're a developer using the GitHub.com front end, a system administrator spinning up GitHub Enterprise, or a COTR procuring a license for your agency. I'm not part of the Sales team. In fact, my full-time job is to help empower those working to "fix/modernize gov't tech from the inside", and a big part of that over the past year or so has been seriously leveling up the user experience for government and other large enterprises.

To help here, we now have a dedicated government team (https://government.github.com) that makes sure our front-line sales reps and supportocats are conversant in "govspeak", a semi-private government peer group (https://github.com/government/welcome) to collaborate on best practices, and are streamlining the procurement process for government with invoicing and standardized contract vehicles (and now FedRAMP support as part of AWS). I'd love your input on how we can do better.

Re: GitHub Enterprise 2.0

#58
post #54

Earlier quoted context omitted.

Why Ubuntu over Debian, out of curiosity? I've seen Spotify switch from Debian to Ubuntu and regretting it already.

Because Debian doesn't provide enterprise support. Let say that you've got a critical bug somewhere, do you really think you can tell your boss 'Yeah I asked on IRC / forums / mailing list to get an ETA'

One problem with that is that Ubuntu is actually quite limited. As soon as you enable universe you're out of support.

Luckily there are many small consulting companies out there which can happily support both Debian and Ubuntu!

Re: GitHub Enterprise 2.0

#59

Can someone who has used both this and Gitlab provide an insight on how the experiences differ?

As someone who's used both Gitlab, Github Enterprise, and Stash in a corporate environment, I have to admit I prefer GHE, for the features it shares with core Github, if nothing else.

My only gripe w/ GHE is the lack of branch-based ACLs. If we want to implement a Github Flow (https://guides.github.com/introduction/flow/index.html) methodology, but also have automatic branch detection and testing in our CI (Jenkins/Bamboo/whatever), we end up having to assign all users the ability to create branches in the given repository (which, in turn, gives them the perms to push to master). I'm actually quite surprised that this hasn't been implemented yet in GHE; I can understand why GH wouldn't have it, but GHE (because of the nature of its user base) really should.

That issue aside, the UI in GHE is simply superior to GL and Stash.

Post reply on HN