git/list[1] front-page[2] threads[3] people[4] search[5] about
 

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

From
Philip Oakley <philipoakley@iee.org>
Date
Jan 31, 2016, 21:00 UTC
Message-ID
<1454274011-4880-1-git-send-email-philipoakley@iee.org>
In-Reply-To
<alpine.DEB.2.20.1601280913450.2964@virtualbox>

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 in a Git repository for fear that Git's GPL2 licence may somehow 'infect' the respository.

Add simple statements highlighting Git's licence, it's use for Linux, to imply industrial-strength, and that users should apply a suitable licence of their choice because the Git GPL licence does not apply to their repo data.

It should be noted that a 'git init' will create a repo that while empty of user data does provide the .git directory structure, which includes a number of template files ('hooks\pre-rebase.sample' is explicitly copyright), default refs and config file. Some may suggest that these carry the GPL2 to the repo.

The GPL2 will still apply to the hook templates and the other template files, but these, even if modified (becoming derived works) would be distributed with the repo, satisfying the GPL.

The new content copyright belongs to user. Request that they state their licence terms in line with recent FOSS industry practice.

Signed-off-by: Philip Oakley <philipoakley@iee.org>
---
asciidoc formatting not checked.

The fear of 'infection' of a repo by the templates copied to the repo by 'git init', should not be underestimated, given the need for the Bison exception. Sometimes it has to be spelt out why it's not an issue (in the commit messsage)

https://help.github.com/articles/open-source-licensing/
http://thread.gmane.org/gmane.comp.version-control.git/284715/
---
 Documentation/git.txt | 11 +++++++++++
 1 file changed, 11 insertions(+)
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
 	    `hg` to allow the `git-remote-hg` helper)
 
+Licencing: Your data, and the Git tool[[Licencing]]
+---------------------------------------------------
+
+Git is an open source tool provided under GPL2.
+Git was designed to be, and is, the version control system
+for the Linux codebase.
+Your respository data created by Git is not subject to Git's GNU2
+licence, see GPL FAQs
+http://www.gnu.org/licenses/old-licenses/gpl-2.0-faq.en.html#TOCGPLOutput).
+
+User should apply a licence of their own choice to their repository data.
 
 Discussion[[Discussion]]
 ------------------------
-- 
2.7.0.windows.1
Previous: Philip OakleyNext: Junio C Hamano
Message 6 of 15 in “GPL v2 authoritative answer on stored code as a derived work”
  1. Jonathan SmithJan 25, 2016
  2. Junio C HamanoJan 25, 2016
  3. Philip OakleyJan 27, 2016
  4. Johannes SchindelinJan 28, 2016
  5. Philip OakleyJan 31, 2016
  6. Git doc: GPL2 does not apply to repo dataPhilip Oakley, Jan 31, 2016
  7. Junio C HamanoJan 31, 2016
  8. Jonathan SmithJan 31, 2016
  9. Johannes SchindelinFeb 1, 2016
  10. Matthieu MoyFeb 1, 2016
  11. Jeff KingFeb 1, 2016
  12. Jeff KingFeb 1, 2016
  13. Philip OakleyFeb 1, 2016
  14. Philip OakleyFeb 1, 2016
  15. Philip OakleyFeb 1, 2016

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.