From: Jonathan Nieder <jrnieder@gmail.com>
To: Andrew Sayers <andrew-20120318@pileofstuff.org>
Cc: Git Mailing List <git@vger.kernel.org>,
Sam Vilain <sam@vilain.net>, Stephen Bash <bash@genarts.com>,
Nathan Gray <n8gray@n8gray.org>, Jeff King <peff@peff.net>,
Sverre Rabbelier <srabbelier@gmail.com>,
Dmitry Ivankov <divanorama@gmail.com>,
Ramkumar Ramachandra <artagnon@gmail.com>,
David Barr <davidbarr@google.com>,
semen.vadishev@tmatesoft.com
Subject: Re: Licensing a file format (was Re: SVN Branch Description Format)
Date: Sun, 18 Mar 2012 20:34:22 -0500 [thread overview]
Message-ID: <20120319013422.GC19680@burratino> (raw)
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
next prev parent reply other threads:[~2012-03-19 1:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-11 10:59 SVN Branch Description Format Andrew Sayers
2012-03-18 23:18 ` Steven Michalske
2012-03-19 1:28 ` Andrew Sayers
2012-03-19 1:28 ` Licensing a file format (was Re: SVN Branch Description Format) Andrew Sayers
2012-03-19 1:34 ` Jonathan Nieder [this message]
2012-03-19 20:31 ` Andrew Sayers
2012-03-20 22:59 ` Jeff King
2012-03-23 0:08 ` SVN Branching Language " Andrew Sayers
2012-03-30 4:06 ` SVN Branch Description Format Ramkumar Ramachandra
2012-03-31 1:27 ` Andrew Sayers
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20120319013422.GC19680@burratino \
--to=jrnieder@gmail.com \
--cc=andrew-20120318@pileofstuff.org \
--cc=artagnon@gmail.com \
--cc=bash@genarts.com \
--cc=davidbarr@google.com \
--cc=divanorama@gmail.com \
--cc=git@vger.kernel.org \
--cc=n8gray@n8gray.org \
--cc=peff@peff.net \
--cc=sam@vilain.net \
--cc=semen.vadishev@tmatesoft.com \
--cc=srabbelier@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).