Re: [RFC/PATCH] Git doc: GPL2 does not apply to repo data

2016-02-01 Thread Philip Oakley
From: "Philip Oakley" We should leave the lawyering to real lawyers and we should not add unnecessary work of interpreting our amateurish loose statement to our laywers. Given Jonathan's question, and your earlier feedback, it did feel that a bit of clear blue water would be useful between G

Re: [RFC/PATCH] Git doc: GPL2 does not apply to repo data

2016-02-01 Thread Philip Oakley
From: "Jeff King" On Mon, Feb 01, 2016 at 08:49:55AM +0100, Matthieu Moy wrote: - Original Message - > For less tech-savvy managers, I found that name dropping works quite > well > (read: naming a couple of well-known companies/products that switched > to > Git). In the same catego

Re: [RFC/PATCH] Git doc: GPL2 does not apply to repo data

2016-02-01 Thread Philip Oakley
From: "Junio C Hamano" Philip Oakley writes: diff --git a/Documentation/git.txt b/Documentation/git.txt index bff6302..137c89c 100644 --- a/Documentation/git.txt +++ b/Documentation/git.txt @@ -1132,6 +1132,17 @@ of clones and fetches. - any external helpers are named by their protocol (e.

Re: [RFC/PATCH] Git doc: GPL2 does not apply to repo data

2016-02-01 Thread Jeff King
On Mon, Feb 01, 2016 at 03:14:31AM -0500, Jeff King wrote: > On a more serious note, this FAQ (and the one right after) might be > useful for convincing people: > > http://www.gnu.org/licenses/gpl-faq.en.html#GPLOutput > > Data that git stores is not strictly "output", but I think the answers

Re: [RFC/PATCH] Git doc: GPL2 does not apply to repo data

2016-02-01 Thread Jeff King
On Mon, Feb 01, 2016 at 08:49:55AM +0100, Matthieu Moy wrote: > - Original Message - > > For less tech-savvy managers, I found that name dropping works quite well > > (read: naming a couple of well-known companies/products that switched to > > Git). > > In the same category: "GitHub has 1

Re: [RFC/PATCH] Git doc: GPL2 does not apply to repo data

2016-01-31 Thread Matthieu Moy
- Original Message - > For less tech-savvy managers, I found that name dropping works quite well > (read: naming a couple of well-known companies/products that switched to > Git). In the same category: "GitHub has 12 millions users" works rather well. -- Matthieu Moy http://www-verimag.i

RE: [RFC/PATCH] Git doc: GPL2 does not apply to repo data

2016-01-31 Thread Johannes Schindelin
Hi Jonathan, On Sun, 31 Jan 2016, Jonathan Smith wrote: > I'll be taking all of your contributions as ammo as I continue to fight > for Git here. I would hope that it is unnecessary to point weapons at managers to "convince" them to use Git. In the meantime, I think we have accumulated a lot of

RE: [RFC/PATCH] Git doc: GPL2 does not apply to repo data

2016-01-31 Thread Jonathan Smith
doc: GPL2 does not apply to repo data Philip Oakley writes: > diff --git a/Documentation/git.txt b/Documentation/git.txt index > bff6302..137c89c 100644 > --- a/Documentation/git.txt > +++ b/Documentation/git.txt > @@ -1132,6 +1132,17 @@ of clones and fetches. > - any e

Re: [RFC/PATCH] Git doc: GPL2 does not apply to repo data

2016-01-31 Thread Junio C Hamano
Philip Oakley writes: > diff --git a/Documentation/git.txt b/Documentation/git.txt > index bff6302..137c89c 100644 > --- a/Documentation/git.txt > +++ b/Documentation/git.txt > @@ -1132,6 +1132,17 @@ of clones and fetches. > - any external helpers are named by their protocol (e.g., use >

[RFC/PATCH] Git doc: GPL2 does not apply to repo data

2016-01-31 Thread Philip Oakley
Some potential commercial users may be put off by the FUD (Fear, Uncertainty and Doubt) that has been raised in the past regarding the use of FOSS software. In such communities, even the legal advice may be misinformed and over-cautious regarding the storage of code and other intellectual property