Disclosure: I work for GitLab
[0]: pages.gitlab.io [1]: https://about.gitlab.com/2016/12/07/building-a-new-gitlab-do...
657 karma · joined August 30, 2014
Disclosure: I work for GitLab
[0]: pages.gitlab.io [1]: https://about.gitlab.com/2016/12/07/building-a-new-gitlab-do...
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.
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.
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...
[0]: https://gitlab.com/danger-systems/danger.systems
[1]: https://gitlab.com/gnachman/iterm2/issues
[2]: https://gitlab.com/groups/xonotic
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.
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
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
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.
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.
- 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.
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 :)
(Community Advocate at GitLab)