Almost Everything We Do Will Be Open • Hacker News Board

Re: Almost Everything We Do Will Be Open

#11

Post by jobvandervoort » Fri, Aug 07, 2015, 1:20 PM UTC

aardshark wrote: post #8

So if customers want to contribute to fixes for issues they raise, is there a an easy way for them to do that without revealing who they are?

Yes. All our customers have a direct line to our support. We ask them to raise issues there, not on the public issue tracker.

Re: Almost Everything We Do Will Be Open

#12

Post by TheLoneWolfling » Fri, Aug 07, 2015, 1:21 PM UTC

jobvandervoort wrote: post #10

davexunit wrote: post #9

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

> It is forbidden to copy, merge, publish, distribute, sublicense, and/or sell copies of the Software.

Re: Almost Everything We Do Will Be Open

#13

Post by sytse » Fri, Aug 07, 2015, 1:21 PM UTC

davexunit wrote: post #9

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

The article is about the issues that will almost all be open. The complete quote you refer to is is "In fact, even our proprietary version of GitLab, GitLab Enterprise Edition, has a publicly viewable source code.". Can we be any more clear it is proprietary? We think it is notable that even the source code and issues of out proprietary edition are publicly viewable.

Re: Almost Everything We Do Will Be Open

#14

Post by philtar » Fri, Aug 07, 2015, 1:22 PM UTC

I apologize in advance for my short sighted question as I don't really know much about gitlab but my question is: does this mean anything for large file support in the community edition? I find it surprising there are no free solutions for large binary files other than perforce. Compared to most tools indie game devs use, perforce is a dinosaur.

Re: Almost Everything We Do Will Be Open

#15

Post by jobvandervoort » Fri, Aug 07, 2015, 1:22 PM UTC

scrollaway wrote: post #4

jobvandervoort wrote: post #2

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.

That's great to hear.

You can give it a try / use it for free at GitLab.com (public and private).

We would love to hear what hardcore GitHub fans like you miss in GitLab. We want to be better.

Re: Almost Everything We Do Will Be Open

#16

Post by jobvandervoort » Fri, Aug 07, 2015, 1:24 PM UTC

athoik wrote: post #5

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

For sensitive issues you can email us at support at gitlab dot com.

Re: Almost Everything We Do Will Be Open

#17

Post by Mathiasdm » Fri, Aug 07, 2015, 1:24 PM UTC

philtar wrote: post #14

I apologize in advance for my short sighted question as I don't really know much about gitlab but my question is: does this mean anything for large file support in the community edition? I find it surprising there are no free solutions for large binary files other than perforce. Compared to most tools indie game devs use, perforce is a dinosaur.

Mercurial has had support for large binary files using the 'largefiles' extension for several years now.

Re: Almost Everything We Do Will Be Open

#18

Post by jobvandervoort » Fri, Aug 07, 2015, 1:25 PM UTC

philtar wrote: post #14

I apologize in advance for my short sighted question as I don't really know much about gitlab but my question is: does this mean anything for large file support in the community edition? I find it surprising there are no free solutions for large binary files other than perforce. Compared to most tools indie game devs use, perforce is a dinosaur.

We will not bring Git Annex [0] to the community edition.

However, we do accept merge requests for Git LFS support [1]. This means that if this is contributed to GitLab, it will be available in the Community Edition.

[0]: http://doc.gitlab.com/ee/workflow/git_annex.html

[1]: http://feedback.gitlab.com/forums/176466-general/suggestions...

Re: Almost Everything We Do Will Be Open

#19

Post by zxcvcxz » Fri, Aug 07, 2015, 1:27 PM UTC

Decided to switch to gitlab when I realized github refused to release their tools on Linux even though according to stackoverflow statistics Linux users make up over 20% of programmers, matching the number of OS X programmers.

It's unfortunate that they make a living off open source software created by a lead Linux developer but they act like Linux doesn't even exist.

Not a big deal though, the userbase on github is worse than facebook or 9gag.

Gitlab isn't much better than github when it comes to openess, but it seems to be the best alternative so far.

Re: Almost Everything We Do Will Be Open

#20

Post by nhumrich » Fri, Aug 07, 2015, 1:29 PM UTC

Just saw that gitlab now offers free hosting, you only pay for support (only if you want it). Do enough people really pay for support in order to keep gitlab from going under? Free software is one thing, but free hosting? It just blows my mind how they can offer such a thing.