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

Re: Licensing a file format (was Re: SVN Branch Description Format)

From
Jonathan Nieder <jrnieder@gmail.com>
Date
Mar 19, 2012, 01:34 UTC
Message-ID
<20120319013422.GC19680@burratino>
In-Reply-To
<4F668BD4.70808@pileofstuff.org>
Hi Andrew,
Andrew Sayers wrote:
> I'm planning to release the spec under a Creative Commons
> Attribution-NoDerivs license
[...]
> So the big question - would you be more inclined to use/contribute to
> the SVN Branch Description Format if it had a different license?

Yes. By the way, I think fear of forking/discussion of potential improvements/translation into other languages in the context of standards is misguided. If you would like legal protection for your standard, that is what trademark law is for.

Kind regards, Jonathan

Previous: Andrew SayersNext: Andrew Sayers
Message 5 of 10 in “SVN Branch Description Format”
  1. Andrew SayersMar 11, 2012
  2. Steven MichalskeMar 18, 2012
  3. Andrew SayersMar 19, 2012
  4. Licensing a file format (was Re: SVN Branch Description Format)Andrew Sayers, Mar 19, 2012
  5. Jonathan NiederMar 19, 2012
  6. Andrew SayersMar 19, 2012
  7. Jeff KingMar 20, 2012
  8. SVN Branching Language (was Re: SVN Branch Description Format)Andrew Sayers, Mar 23, 2012
  9. Ramkumar RamachandraMar 30, 2012
  10. Andrew SayersMar 31, 2012

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.