HNHacker News
TopNewBestAskShowJobs

connorshea

657 karma · joined August 30, 2014

Software Engineer primary working with Ruby
submissionscomments
connorshea··on Ask HN: Is S3 down?
GitLab Pages [0] is pretty good for static websites IMO, you can use GitLab CI to build more complex sites as well [1].

Disclosure: I work for GitLab

[0]: pages.gitlab.io [1]: https://about.gitlab.com/2016/12/07/building-a-new-gitlab-do...

connorshea··on GitLab’s Secret to Managing Employees in 160 Locations: Write Everything Down
She's referring to issues in the backup process specifically, not in the company culture (which IMO is pretty good).
connorshea··on GitLab’s Secret to Managing Employees in 160 Locations: Write Everything Down
I didn't know Zapier was a fully remote company, that's awesome :)

I pretty much agree with your thoughts about over-communicating, it's super important and we've run into exactly the same things, where people aren't always caught up on everything going on at the company. In my experience this happens in physical workplaces as well, just to a lesser extent.

connorshea··on Our long term plan to make GitLab as fast as possible with Vue and Webpack
It should be noted that Gogs was recently forked to Gitea due to disagreements about the management style of Gogs as an open source project.

See https://blog.gitea.io/2016/12/welcome-to-gitea/

connorshea··on Our long term plan to make GitLab as fast as possible with Vue and Webpack
JRuby isn't an option for us because we use too many gems, many of which have compatibility issues with JRuby's implementation of Ruby. This is especially a problem for gems with C extensions.

I think Truffle is the most interesting new development in this realm, if it gets support for C extensions as they plan for it to, it may eventually be reasonable to run GitLab on it. That wouldn't be for a few more years though.

connorshea··on Our long term plan to make GitLab as fast as possible with Vue and Webpack
Once Rails 5.1 comes out and we upgrade to it we'll probably switch to Webpacker. It was an awesome development in the Rails ecosystem and really verified our investment into Webpack.
connorshea··on Our long term plan to make GitLab as fast as possible with Vue and Webpack
We didn't go with TypeScript because we were burnt by CoffeeScript before. People don't know TypeScript or CoffeeScript nearly as much as they know vanilla/ES6 JavaScript. It's easier to hire for and easier to get contributors for.
connorshea··on Our long term plan to make GitLab as fast as possible with Vue and Webpack
Actually we just removed Turbolinks the other day, so this is a non-problem. :)
connorshea··on Our long term plan to make GitLab as fast as possible with Vue and Webpack
The Vue docs are seriously amazing, I couldn't rap my head around React fully because its docs just weren't very good (though they've improved them since I last tried).
connorshea··on Our long term plan to make GitLab as fast as possible with Vue and Webpack
Sorry for the bad experience :(

We're constantly working on improving GitLab's performance, and we have a bunch of issues open for performance fixes/improvements we'll be doing for the upcoming 9.0 release: https://gitlab.com/gitlab-org/gitlab-ce/issues?scope=all&utf...

connorshea··on GitLab Database Incident – Live Report
Even better, have a Chaos Monkey do it ;)
connorshea··on GitLab Database Incident – Live Report
Glad to hear others will learn from our mistakes, we certainly are :)
connorshea··on GitLab Database Incident – Live Report
It'll definitely be a priority now!
connorshea··on GitLab Database Incident – Live Report
Yup, it's never the fault of a person, always of the system. Once we get this resolved we'll definitely look at ways to prevent anything like it in the future.
connorshea··on GitLab 8.15 Released
Danger hosts their website with GitLab Pages[0], iTerm hosts their issue tracker there[1], the game Xonotic is hosted on GitLab.com[2], and then VLC[3] and GNU[4] both have their own instances of GitLab.

[0]: https://gitlab.com/danger-systems/danger.systems

[1]: https://gitlab.com/gnachman/iterm2/issues

[2]: https://gitlab.com/groups/xonotic

[3]: https://code.videolan.org/videolan/VLCKit

[4]: https://git.gnu.io/explore/projects

connorshea··on GitLab 8.15 Released
We've spent quite a bit of time this year improving performance, GitLab.com is still slower than it should be but it's a lot better now than it was in January. Self-hosted instances that meet the recommended specs are already fairly performant, though we're always working to improve things regardless.

As mentioned in the blog post, this release we decreased page size a lot (from 1800kb to 718kb for a given Merge Request).

We're also working on moving to our own infrastructure, the reasoning behind that move is described here: https://about.gitlab.com/2016/11/10/why-choose-bare-metal/

EDIT: Strike that, we've decided against moving to bare metal for now due to the complexity. I somehow missed that decision.

connorshea··on GitLab 8.15 Released
>I'm curious how you guys build features for EE. Is it a completely separate Rails project you handle manually to keep base features in sync with the community edition?

It's the same codebase with some additional code. Every few days we merge CE into EE[1], which always ends up with some merge conflicts – though those are getting better as we learn to engineer around them – and its own problems, but it works pretty well. I think this is a great system, even with its drawbacks, if you want to keep the base product as FOSS. Just be aware of the problems you'll likely run into, and avoid implementing any EE-only features that will cause crazy merge conflicts.

>EE is open source but requires a license. Do you just trust companies won't download the source code and run it. Do you have heartbeat code injected somewhere to ping servers that are running EE to homebase?

It has a built-in system for uploading the license and verifying that the license covers the users of the instance. The license (as in the copyright license) says that users cannot use EE if they get around that. We don't have many cases of piracy as far as we know, and don't care too much. No major enterprise customer would realistically pirate software since that'd be a legal nightmare if they were caught.

>I'm thinking of starting a project, charge money but also open-source it. Curious what your strategies are, especially since the project is still greenfield.

Best of luck! It's awesome to see others try to go for this kind of model, I hope it works for you :)

Some others to look at: Sentry, Mattermost, and Code Climate.

[1]: Example of a CE-to-EE merge request: https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/991

connorshea··on GitLab 8.15 Released
I'm not sure I understand why you're under the impression that you need a 3rd party application for that, as far as I know it's possible with just GitLab and Mattermost. If there are any confusing docs we need to improve I'd be happy to do so :)

Build failures can be sent to Mattermost using our Pipeline webhooks described here: http://docs.gitlab.com/ce/web_hooks/web_hooks.html#pipeline-...

And then the Incoming Webhooks in Mattermost described here: https://docs.mattermost.com/developer/webhooks-incoming.html

connorshea··on GitLab 8.15 Released
Thanks for the honest feedback, it's genuinely useful for improving the product.

Out of curiosity, why use the Docker image over our Omnibus package? Omnibus is generally what we recommend, but if that's not good enough we'd love to know how it can be improved.

connorshea··on GitLab 8.15 Released
We'd strongly recommend that you open an issue to discuss it first, but yeah, of course they are! :)
connorshea··on GitHub lost $66M in nine months of 2016
Are you using GitLab.com or hosting it yourself? We're working on improving GitLab.com, but self-hosting GitLab should be pretty fast in most circumstances.

As for the interface, we're working on improving the design of the product and have just hired a UX Researcher to help with that. Would be happy to hear any specifics you have to offer.

connorshea··on GitHub lost $66M in nine months of 2016
The comprehensive API helps, though that can theoretically be limited if a ton of people try to migrate.
connorshea··on GitHub lost $66M in nine months of 2016
I'm a GitLab Community Advocate, so I'm biased, but off the top of my head:

- Performance, we're working on improving this for GitLab.com but right now it's slower than we'd like. If you run your own instance it'll be fine as long as you meet the recommended specs, GitLab.com struggles because we have so many users by comparison.

- Following users/social network-y things, we haven't really focused on this and don't have a way to follow another user right now (you can watch projects though).

- Third party integrations, we don't have as many third parties integrating with the product as GitHub does, though that's kind of to-be-expected.

And while I'm here, some things we do better (IMO):

- CI, we have it integrated into the product and have Review Apps plus GitLab Pages (which is better than GitHub Pages in some ways, e.g. in that it allows any static site generator and allows building sites dynamically via CI).

- Responsive design, GitHub has a separate mobile site that's not fully-featured compared to the desktop site. I browse on mobile _a lot_ so this is big for me, maybe not for others.

- Community Edition, which has a significant majority of the features of Enterprise Edition, is open source, MIT-Licensed, and anybody can contribute to it.

There are others, but I don't want to shill too hard :P

EDIT: Also I want to mention that we value diversity, I strongly disagree with the grandparent comment about how inclusivity shouldn't be rewarded.

connorshea··on Resolve simple merge conflicts on GitHub
GitLab does have it already: https://docs.gitlab.com/ce/user/project/merge_requests/resol...
connorshea··on Proposed server purchase for GitLab.com
We hope so too ;)
connorshea··on Building a New GitLab Docs Site with Nanoc, GitLab CI, and GitLab Pages
No plans to support Mercurial, it would complicate development a lot. Plus it would be a second-rate citizen and that wouldn't be very nice of us.
connorshea··on Building a New GitLab Docs Site with Nanoc, GitLab CI, and GitLab Pages
Yeah, we're working on improving the search by moving to Algolia for it[1], the current system doesn't work as well as we'd like.

The point was at least partially to share a workflow I hadn't been able to find any other blog posts for, where the docs are hosted in each product's respective repository and needs to be pulled into the docs site before deployment. It's conveniently also a tutorial for our tools, but that isn't the only goal :)

[1]: https://gitlab.com/gitlab-com/gitlab-docs/issues/21

connorshea··on Building a New GitLab Docs Site with Nanoc, GitLab CI, and GitLab Pages
I'd be happy to answer any questions anyone has (about the post or anything else) :)
connorshea··on How We Knew It Was Time to Leave the Cloud
No problem, the thread is pretty long, and it's not necessarily easy to tell without understanding how our blog post process works. :)
connorshea··on How We Knew It Was Time to Leave the Cloud
Unfortunately I don't believe we'll be able to comment on the accuracy of this since the quotes from companies are private information, but I do love math like this :D

(Community Advocate at GitLab)

← PreviousPage 3 of 6Next →