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

91–100 of 208 posts

Re: Almost Everything We Do Will Be Open

#91

Post by hikarudo »

p0nce wrote: post #78
pyre wrote: post #77

Earlier quoted context omitted.

Sometimes I end up on Bitbucket pages for a repo, and have a hard time locating how I can view the directory tree of the repo. I wouldn't call this "superior." It's not unfixable, but definitely not superior.

Precisely the one reason I can't bother to use it for real: I'd like the source tree to be the default view.

Settings -> Repository details -> Landing page -> Source

Re: Almost Everything We Do Will Be Open

#92

Post by avinassh »

How does the licensing works? Can anyone explain me? [0]

> This software and associated documentation files (the "Software") can only be used with a valid GitLab subscription for the correct number of users. You are free to modify this Software and publish patches. It is forbidden to copy, merge, publish, distribute, sublicense, and/or sell copies of the Software.

Isn't the third line contradicting with the fourth or have I misunderstood?

[0] - https://gitlab.com/gitlab-org/gitlab-ee/blob/master/LICENSE

Re: Almost Everything We Do Will Be Open

#93

Post by scrollaway »

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.

Great, the age-old debate on what is and isn't open source vs free software. We really needed that in here.

Y'all need to stop whining about the irrelevant when companies like these are doing literally everything else right. It's pretty damn ungrateful.

Re: Almost Everything We Do Will Be Open

#94

Post by superuser2 »

avinassh wrote: post #92

How does the licensing works? Can anyone explain me? [0] > This software and associated documentation files (the "Software") can only be used with a valid GitLab subscription for the correct number of users. You are free to modify this Software and publish patches. It is forbidden to copy, merge, publish, distribute, sublicense, and/or sell copies of the Software. Isn't the third line contradicting with the fourth or…

A patch - literally a file generated by "diff" - only incidentally contains the original code, mostly your new functions and modifications. So you can't distrbute a patched version of the software, only the patch itself.

Re: Almost Everything We Do Will Be Open

#95

Post by mrmondo »

oblio wrote: post #74
odonnellryan wrote: post #42

Earlier quoted context omitted.

Not to be rude, but isn't their software open source? Can't you try and patch it yourself?

If I've read his post correctly he's a paying customer. Surely that has to count for something :)

As well as logging that ticket publicly in case anyone had a contribution to fix the issue gitlab was contacted through the paid subscribers channel and their response was that they would follow it up on that public issue. I don't have an issue with that so let's wait and see A) what the fix is and more importantly B) what lessons were learnt from the regression.

Re: Almost Everything We Do Will Be Open

#97

Post by mrmondo »

ausjke wrote: post #57

Still using Redmine for self-hosting here, Gitlab is too heavy for small teams. Thought about trying Phabricator but then its various components with strange names stopped me from trying, plus it seems clunky for small team too.

We use Redmine for ticket / issue / task tracking as well as rough timesheeting, and we use gitlab and gitlab CI along side it. I quite like how quick Redmine is and how it just gets out of your way. We find gitlab to be pretty quick however upgrades are painful due to regular bugs / regressions.

Ideally I'd like to see something like Taiga and Gogs together which I think would absolutely fly.

Re: Almost Everything We Do Will Be Open

#98

Post by btashton »

I set up gitlab internally a couple years ago and it has been a pleasure. One big thing I fight is we have a lot of micro services that we want to have the same label set for and would like to manage against the same milestones. It would be really nice if label sets and milestones could be created for a group.

Re: Almost Everything We Do Will Be Open

#99

Post by jordigh »

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.

    I find it surprising there are no free solutions for large binary
    files other than perforce.
There's in fact lots of tooling in Mercurial to handle this precise problem, as well as gigantic repos. Mercurial's extensibility with these scaling problems, in fact, is why Facebook has chosen it. If you're not married to git, try checking out Facebook's Mercurial extensions.

Re: Almost Everything We Do Will Be Open

#100

Post by JoshTriplett »

hikarudo wrote: post #91
p0nce wrote: post #78

Earlier quoted context omitted.

Precisely the one reason I can't bother to use it for real: I'd like the source tree to be the default view.

Settings -> Repository details -> Landing page -> Source

Sure, but that should be the default setting, even if it can be changed.
Post reply on HN