Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Almost Everything We Do Will Be Open

about.gitlab.com

Post reply on HN
Print view View original

81–90 of 208 posts

Re: Almost Everything We Do Will Be Open

#81

Post by skyraider »

jobvandervoort wrote: post #75
skyraider wrote: post #72

GitLab Enterprise user here. GitLab's open-source policy is one of the major reasons we chose it (along with self-hosting and fairly modern, built-in continuous integration), but the GitLab community could use some additional design and documentation effort. Things that almost make me want to switch back to GitHub: - GitLab is really hard to look at. All of our devs are having trouble visually locating comments in di…

Thanks for the feedback, we really appreciate it! The quick reply to your comments is: we're working on almost all of it. > - GitLab is really hard to look at. All of our devs are having trouble visually locating comments in diffs. We're always scrolling through the left-side menu looking for the issues tab. It's hard to visually differentiate between items like comments in merge requests. Our eyes just can't find an…

Super.. good to hear! Ideally the community can get a little more involved in design/UX too. I'm not sure if GitLab plans to set the tone there first - perhaps that's also on the roadmap.

> Would Roboto work, for instance?

Maybe the typeface isn't so much the issue as the layout? On the issue view, comments and descriptions have different positioning and styling. Also, important information lives above the issue title, which is unexpected.

Being unable to trigger CI builds based on merge requests (which can dispatch a build for a commit ID, but you've probably already pushed that commit) is probably the most problematic for us at the moment.

Maybe it would be cool if GitLab came up with some basic design principles/goals and accepted contributions toward that end. I know we'd be interested in contributions here and there to improve workflow/UX.

Re: Almost Everything We Do Will Be Open

#82

Post by scrollaway »

sytse wrote: post #13
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.

Your wording is fine. Parent is being far too cynical.

Re: Almost Everything We Do Will Be Open

#83

Post by sytse »

codegeek wrote: post #54

Good timing. Recently installed Gitlab Community edition on DigitalOcean (one click install) and so far loving it. Some issues: - Does it have a default task management tool or we need to integrate a 3rd party ? Couldn't find it in the forums yet - The UI is a bit clunky in terms of navigation. For example, being able to move from the homepage level to specific project back and forth is a bit confusing. Would love a…

For task management you can use the build in issues and tools that integrate with that https://about.gitlab.com/applications/#scrum-boards

Your navigation remarks are spot on and inspired me to make this issue https://gitlab.com/gitlab-org/gitlab-ce/issues/2225

Doesn't the lockout expire at some point? I agree it would be nice to reset from the UI.

Mmm, I thought that if an admin added a user they didn't have to verify their email.

Do you mean something like project services? http://doc.gitlab.com/ce/integration/README.html

I agree that your shouldn't change .rb files. Please contribute any improvements you make so we can include them.

Re: Almost Everything We Do Will Be Open

#84

Post by klapinat0r »

zxcvcxz wrote: post #19

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…

Which tools are you talking about?

Re: Almost Everything We Do Will Be Open

#85

Post by ZenoArrow »

KingMob wrote: post #37
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.

Perhaps it's just me, but when they said the enterprise edition was "publicly viewable source code", I assumed they just meant it was "publicly viewable", with no further rights implied. I don't think they're really openwashing here, and the article was pretty clear to me. Besides, the community edition and CI code are both true open source.

Isn't there a slight problem with having the EE code publicly viewable?

What I mean by this is, what's stopping someone from taking code from the EE, modifying it, and including it in the CE?

On the flip side, what if a feature released to CE is too similar to code in EE, even if the author of the patch never read the EE code for inspiration? Would GitLab be within their rights to stop it?

With these issues in mind, it makes more sense to me to have the EE code available by request only.

Re: Almost Everything We Do Will Be Open

#86

Post by r0naa »

I am moving my stuff to a self-hosted GitLab.

If you are interested in knowing why:

- I personally find it a little bit irritating that Github wants to promote "open-source/free-software", but haven't open sourced their own tools/product.

- I was disappointed by the way Github handled some internal problems

- I don't trust Github anymore; I want to be in control of my data.

Re: Almost Everything We Do Will Be Open

#87

Post by krupan »

r0naa wrote: post #86

I am moving my stuff to a self-hosted GitLab. If you are interested in knowing why: - I personally find it a little bit irritating that Github wants to promote "open-source/free-software", but haven't open sourced their own tools/product. - I was disappointed by the way Github handled some internal problems - I don't trust Github anymore; I want to be in control of my data.

"they/them" refers to someone other than gitlab?

Re: Almost Everything We Do Will Be Open

#88

Post by [deleted] »

nightcracker wrote: post #23
jobvandervoort wrote: post #10

Earlier quoted context omitted.

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

Well, you are. Let me read to you the definition of Open Source: > Open source software is software that can be freely used, changed, and shared (in modified or unmodified form) by anyone.

[deleted]

Re: Almost Everything We Do Will Be Open

#89

Post by r0naa »

krupan wrote: post #87
r0naa wrote: post #86

I am moving my stuff to a self-hosted GitLab. If you are interested in knowing why: - I personally find it a little bit irritating that Github wants to promote "open-source/free-software", but haven't open sourced their own tools/product. - I was disappointed by the way Github handled some internal problems - I don't trust Github anymore; I want to be in control of my data.

"they/them" refers to someone other than gitlab?

Thank you for pointing that out! they was referring to Github.

Re: Almost Everything We Do Will Be Open

#90

Post by spike021 »

krupan wrote: post #87
r0naa wrote: post #86

I am moving my stuff to a self-hosted GitLab. If you are interested in knowing why: - I personally find it a little bit irritating that Github wants to promote "open-source/free-software", but haven't open sourced their own tools/product. - I was disappointed by the way Github handled some internal problems - I don't trust Github anymore; I want to be in control of my data.

"they/them" refers to someone other than gitlab?

Sounds like they're referring to GitHub.
Post reply on HN