Live data from Hacker News

Almost Everything We Do Will Be Open

about.gitlab.com

191–200 of 208 posts

Re: Almost Everything We Do Will Be Open

#191
post #189
post #182

Earlier quoted context omitted.

In case this is the policy it would mean we could not delete something like revenge porn ourselves, we would first have to wait for a takedown notice. I don't want to host content like that https://xkcd.com/1357/

> In case this is the policy it would mean we could not delete something like revenge porn ourselves I could argue either way (I'm a bit of a philosopher that way...). It all depends on how you want to run your service. Do you want a reddit-free-for-all-wild-west or do you want to keep it PG-13? Either way - it should be clearly defined where you stand and what you allow/don't allow. Making it a guessing game isn't g…

We make decisions on a case by case basis and people can judge for themselves if they think it is reasonable. Clearly defining where you stand is very hard, and we don't think we'll do a good job at it. Giving a definition and then backtracking won't win us any fans either. Anyway, it will be more PG-13 than the old Reddit.

Re: Almost Everything We Do Will Be Open

#192
post #181
post #177

Earlier quoted context omitted.

> In contracts most terms are not defined. The GPL is one that I know that spells it out [1]: > This License applies to any program or other work which contains a notice placed by the copyright holder saying it may be distributed under the terms of this General Public License. The "Program", below, refers to any such program or work, and a "work based on the Program" means either the Program or any derivative work un…

You have good points, I'll have a lawyer look at this again. I do wonder how would you define the patch file? How would you prevent people splitting up the changeset into multiple patch files? I hope the intent of our license is clear. Most people and organizations want to do the right thing.

Just as an aside - we seem to be crossing paths a lot on here...

I think you should just hire me as your PR and/or developer guy ;). It's always good to have a guy with a different perspective who thinks and plays outside the box. I mean inside the box is so boring....

> I do wonder how would you define the patch file?

Something like....

> A patch file contains the modified file name, author of the change, date, hash with snippets of content recording the changes. A patch file cannot contain enough information to reconstruct the software in whole or modify the CE to include copyrighted features in the EE edition. The author must not knowingly introduce backdoors, exploits, or other code that introduces malicious intent. If the author is identified their gitlab EE license will be revoked irrevocably and permanently and requested to halt any use of gitlab EE.

(However - a patch may still introduce features from the EE edition that were written with original code)

> A patch may be released under whatever license or agreements the author wants without the requirement for permission from Gitlab if it satisfies the previous conditions.

It might be good to add a clause:

> By applying a third party patch you agree to not hold Gitlab liable for any damages or misconfigurations that might happen by applying the patch. You acknowledge by applying a third party patch that it may fix your problem, introduce a new problem, or open a tear in the space-time continuum.

I'm sure you get the idea. I'm tired and I just watched an episode of Doctor Who - so I had to include something related to time :).

Re: Almost Everything We Do Will Be Open

#193
post #192
post #181

Earlier quoted context omitted.

You have good points, I'll have a lawyer look at this again. I do wonder how would you define the patch file? How would you prevent people splitting up the changeset into multiple patch files? I hope the intent of our license is clear. Most people and organizations want to do the right thing.

Just as an aside - we seem to be crossing paths a lot on here... I think you should just hire me as your PR and/or developer guy ;). It's always good to have a guy with a different perspective who thinks and plays outside the box. I mean inside the box is so boring.... > I do wonder how would you define the patch file? Something like.... > A patch file contains the modified file name, author of the change, date, hash…

Thanks! We're hiring https://about.gitlab.com/jobs/ Our lawyer will also study this comment. I'm sure he'll discourage us from offering guaranties against tears in the space-time continuum. Have a good night.

Re: Almost Everything We Do Will Be Open

#194
post #190

Earlier quoted context omitted.

GitLab can do better? What jury decided to take down the GG repo? What checks and balances were in place? You're free to run your company as you see fit but a non-trivial amount of people do care strongly about free speech and due process.

How many major platforms only take down content based on takedown requests and not by their own initiative? We care deeply about free speech too, but please get your own server https://xkcd.com/1357/

http://sealedabstract.com/rants/re-xkcd-1357-free-speech/

If you are legally required to take something down it is kind of different from when you freely choose to do so because you find the content objectionable on ideological grounds. In this case you decided to act against the principles of free speech and network neutrality of your own free will.

Some for instance (GitHub, BitBucket, Google Code) also decided to remove the satirical "C+=" repo from their service, you didn't: https://gitlab.com/femsf/c-plus-equality

For interested parties, there is actually a server that has existed for a while, but this is mostly about the choices you make as a company in the wake of GitHub deleting repos over the use of the word "retarded" and employing an intentionally discriminatory Code of Conduct: https://gitgud.io/gamergate/gamergateop/tree/master

Nobody is arguing this isn't your right as a company, they are just questioning your judgment and reason and if their projects are safe with a company that will remove something that doesn't intellectually agree with the political stance of its CEO.

All these people you saw surging to your service the other day: https://news.ycombinator.com/item?id=10003334

Most of them don't want to deal with the volatility of a professional environment where someone just has to be "offended" and their work could be arbitrarily pulled.

Re: Almost Everything We Do Will Be Open

#195
post #182
post #180

Earlier quoted context omitted.

Would you be ok with a policy of: > We don't delete repos unless explicitly requested by law enforcement or a DMCA takedown notice. What you said could be interpreted as "well...this repo was technically breaking the law so that's why we deleted it" - I would rather say "I deleted it to cooperate with law enforcement". And the DMCA takedown policy is required to protect service providers in the event some idiot decid…

In case this is the policy it would mean we could not delete something like revenge porn ourselves, we would first have to wait for a takedown notice. I don't want to host content like that https://xkcd.com/1357/

That XKCD is one of the worst strawman arguments I've ever seen.

Freedom of Speech is not a law, and it's certainly not just a law found in one single document that applies to the United States. Here's what the United Nation's Universal Deceleration of Human Rights says:

> Everyone has the right to freedom of opinion and expression; this right includes freedom to hold opinions without interference and to seek, receive and impart information and ideas through any media and regardless of frontiers.

Not one word there refers to governments.

The true purpose of freedom of speech is to protect people from the consequences of their speech, because those consequences serve to silence unpopular ideas. Remember that historically unpopular ideas have included freedom of religion, African American civil rights, alternative sexualities, and even heliocentricism.

Re: Almost Everything We Do Will Be Open

#196
post #191
post #189

Earlier quoted context omitted.

> In case this is the policy it would mean we could not delete something like revenge porn ourselves I could argue either way (I'm a bit of a philosopher that way...). It all depends on how you want to run your service. Do you want a reddit-free-for-all-wild-west or do you want to keep it PG-13? Either way - it should be clearly defined where you stand and what you allow/don't allow. Making it a guessing game isn't g…

We make decisions on a case by case basis and people can judge for themselves if they think it is reasonable. Clearly defining where you stand is very hard, and we don't think we'll do a good job at it. Giving a definition and then backtracking won't win us any fans either. Anyway, it will be more PG-13 than the old Reddit.

Under a case by case basis I cannot read the rules and know that my repository won't be deleted by gitlab at some point in the future.

Why would I ever consider trust gitlab with data vital to the future of my company without that certainty?

Re: Almost Everything We Do Will Be Open

#197

Earlier quoted context omitted.

> what's stopping someone from taking code from the EE, modifying it, and including it in the CE? 1. Copyright law. 2. For corporations it's probably more cost effective to pay a subscription than maintain a fork.

1. It's not necessarily easy to prove that the new code has its origin in the existing code. 2. For some corporations, yes, for potential competitors, no. Furthermore, I wasn't talking about a fork, I was talking about committing to CE.

For those marking me down, say why you disagree. At the moment I'm under the impression I hit a raw nerve, I don't think I'm in the wrong.

Re: Almost Everything We Do Will Be Open

#198
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.

I recommend giving Phabricator a try. After evaluating several different tools we ultimately went for Phabricator. When I initially looked at it in ~2012 I was put off for similar reasons:

1. References to pokemon on main pages 2. Confusing names for features 3. Written in PHP (this was an initial bias from my prior experience with the language and belief that such a language wouldn't be used to maintain a large-scale application).

These three points led me to believe that Phabricator was not a first-party application but just PHP glue tying together other open source applications. With this in mind, along with the pokemon, I wrote it off as some highschool/college project and turned my attention elsewhere.

I took a fresh look at it in 2014 and realized several of these misconceptions. The developers of Phab tend to be light-hearted and embrace some humor in development. This has proven to be valuable in sustaining good-natured development teams and keeping code-criticisms well-intentioned. They also have a "serious" setting which tones down some of the language in the application itself.

The feature names can be confusing, which is a valid criticism though after a week or so it doesn't tend to interfere with work. The most difficulty in adopting Phabricator has been getting developers to understand the different development workflow to utilize the code review. Our team sizes range from ~3 to ~8 and haven't had any major problems.

They have an IRC channel which is usually pretty active, and I'm sure any questions or concerns you have can be brought up there.

We've been using it since ~Febuary 2015 and it's been a terrific addition to our development.

Re: Almost Everything We Do Will Be Open

#199
post #182

Earlier quoted context omitted.

In case this is the policy it would mean we could not delete something like revenge porn ourselves, we would first have to wait for a takedown notice. I don't want to host content like that https://xkcd.com/1357/

That XKCD is one of the worst strawman arguments I've ever seen. Freedom of Speech is not a law, and it's certainly not just a law found in one single document that applies to the United States. Here's what the United Nation's Universal Deceleration of Human Rights says: > Everyone has the right to freedom of opinion and expression; this right includes freedom to hold opinions without interference and to seek, receiv…

It depends on how you interpret the XKCD comic. It often gets used to argue "institutions have the moral right to block people if they have unpopular opinions", which goes against the spirit of free speech (even if it's not illegal). I don't know if that's it's original intent - it might just mean "You can't claim you have a constitutional right to swear at people on my forum".

A public forum (which GitLab isn't - it's a place for code more than politics) that doesn't allow civil discussion of on-topic ideas is arguably a bad thing.

From On Liberty, by JS Mill:

> If all mankind minus one, were of one opinion, and only one person were of the contrary opinion, mankind would be no more justified in silencing that one person, than he, if he had the power, would be justified in silencing mankind. Were an opinion a personal possession of no value except to the owner; if to be obstructed in the enjoyment of it were simply a private injury, it would make some difference whether the injury was inflicted only on a few persons or on many. But the peculiar evil of silencing the expression of an opinion is, that it is robbing the human race; posterity as well as the existing generation; those who dissent from the opinion, still more than those who hold it. If the opinion is right, they are deprived of the opportunity of exchanging error for truth: if wrong, they lose, what is almost as great a benefit, the clearer perception and livelier impression of truth, produced by its collision with error.

Of course, Mill assumed that most people are capable of rational thought, and would generally move towards a more correct view of the world when exposed to a marketplace of ideas. The internet doesn't always work like that. However, the alternative to "free speech" is echo chambers, which is probably worse.

But I don't see why GitLab has any real responsibility to allow stuff that's not code (or is just joke code) - it's not a really a marketplace of ideas, it's a place to share code. And given GitLab has a FOSS version, yes, people can get their own server.

Re: Almost Everything We Do Will Be Open

#200
post #199

Earlier quoted context omitted.

That XKCD is one of the worst strawman arguments I've ever seen. Freedom of Speech is not a law, and it's certainly not just a law found in one single document that applies to the United States. Here's what the United Nation's Universal Deceleration of Human Rights says: > Everyone has the right to freedom of opinion and expression; this right includes freedom to hold opinions without interference and to seek, receiv…

It depends on how you interpret the XKCD comic. It often gets used to argue "institutions have the moral right to block people if they have unpopular opinions", which goes against the spirit of free speech (even if it's not illegal). I don't know if that's it's original intent - it might just mean "You can't claim you have a constitutional right to swear at people on my forum". A public forum (which GitLab isn't - it…

> It depends on how you interpret the XKCD comic

Unless either of us can find Randall explaining his intent somewhere (and even then; death of the author probably applies - how sytse used the comic is equally important) all we can do is go by it's working. The comic doesn't say "The First Amendment", it says "Freedom of Speech".

I won't say that the average netizen shouting freedom of speech is educated on the philosophy of liberty or has read JS Mill (I haven't, I need too). But when they say freedom of speech about forums. Freedom of Speech is still a human right, not a clause in the USA constitution. I still think it's a strawman to respond by pointing the limits of the First Amendment.

> Of course, Mill assumed that most people are capable of rational thought, and would generally move towards a more correct view of the world when exposed to a marketplace of ideas. The internet doesn't always work like that. However, the alternative to "free speech" is echo chambers, which is probably worse.

On Liberty was written in 1859. It's an indisputable fact that in all forms of social justice - sexual equality, racial equality, LGBT rights, and far far more - things have been improved enormously during the last 66 years. If Mills ideas have either influenced or reflected the political philosophies of the those 66 years then clearly he's onto something.

Even the internet doesn't change much, human nature is still human nature. Besides, to pick a date, the internet has only been influential since September 1993. Social justice has mostly gotten better since 1993 even if online discourse has gotten worse. It's premature to say we the world is too different to go by On Liberty.

After 66 years of liberty bringing progress we should only attempt to replace liberal ideas with the utmost care, thought and deliberation. And when I see people arguing to limit freedom of speech, I do not see that care and deliberation; if I did a comic saying that Freedom of Speech was merely a clause in one country's legal code would never have gotten popular.

> But I don't see why GitLab has any real responsibility to allow stuff that's not code (or is just joke code) - it's not a really a marketplace of ideas, it's a place to share code.

If they had a clearly written rule saying only code is aloud, or only code and documentation relating to code is aloud then that would be fine.

However once GitLab starts judging repositories based on the ideas they contain and deleting legal repositories they dislike then they have crossed the line.

Post reply on HN