Live data from Hacker News

Almost Everything We Do Will Be Open

about.gitlab.com

1–10 of 208 posts

Re: Almost Everything We Do Will Be Open

#3
Announcement itself is fine. The way you contrast "open" with "proprietary" is a bit jarring. It should be free versus proprietary, but if you find that undesirable, then just go with open/closed.

EDIT: Quite predictably, I got downvoted for asking people to use proper terminology and for promoting free software.

Re: Almost Everything We Do Will Be Open

#4

As always, if anyone has any questions, we're here.

Well done guys. I've been thinking about completely open models for a while now; we have a similar model at work (on FOSS as well).

I'm a hardcore Github fan but I'm really impressed with what you've all been doing. The more I see your work, the more I want to switch.

Re: Almost Everything We Do Will Be Open

#7
post #5

What about security issues? Those will be in public too? Or you should contact by email when you have a security issue.

"Sensitive issues, such as security issues with GitLab, will still be handled internally. We’ll create tracking issues for these on the public issue trackers that don’t contain exploitable information."

Re: Almost Everything We Do Will Be Open

#10

This article uses a bit of openwashing to make "publicly viewable source code" seem "open". It's not. It's proprietary.

It is, we don't intent to be vague about this. I hadn't heard of the term openwashing, but I understand the criticism.

See also our license for our proprietary GitLab Enterprise Edition: https://gitlab.com/gitlab-org/gitlab-ee/blob/master/LICENSE

And the license for our open source GitLab Community Edition (MIT Expat): https://gitlab.com/gitlab-org/gitlab-ce/blob/master/LICENSE

Post reply on HN