From: Mathias Hasselmann <mathias.hasselmann@gmx.de>
To: linux-sparse@vger.kernel.org
Cc: torvalds@linux-foundation.org
Subject: License Questions
Date: Fri, 07 Sep 2007 07:53:23 +0200 [thread overview]
Message-ID: <1189144403.7105.13.camel@localhost> (raw)
[-- Attachment #1: Type: text/plain, Size: 1121 bytes --]
Hello,
Sparse uses The Open Software License v. 1.1 which contains this clause:
9) Acceptance and Termination. If You distribute copies of the
Original Work or a Derivative Work, You must make a reasonable
effort under the circumstances to obtain the express and
volitional assent of recipients to the terms of this License.
What does this mean for hosting a public git repository[1] to organize
sparse patches? Do I have to put some "Accept License" page in front
of it? How do I force git to show that "Accept License" page when
downloading from that repository?
What does this clause mean for sending patches to the mailing list.
Shouldn't the patches be attached as password protected source archive
and the message contain something like "By extracting that archive you
declare to obey the terms of The Open Software License"?
Maybe that password thing is a solution for making git repositories
OSL compliant?
Thank you,
Mathias
[1] http://taschenorakel.de/git/sparse
--
Mathias Hasselmann <mathias.hasselmann@gmx.de>
http://taschenorakel.de/
[-- Attachment #2: Dies ist ein digital signierter Nachrichtenteil --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next reply other threads:[~2007-09-07 5:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-07 5:53 Mathias Hasselmann [this message]
2007-09-07 12:07 ` License Questions Rob Taylor
2007-09-07 15:24 ` Rob Taylor
2007-09-07 20:54 ` Mathias Hasselmann
2007-09-07 22:18 ` Linus Torvalds
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=1189144403.7105.13.camel@localhost \
--to=mathias.hasselmann@gmx.de \
--cc=linux-sparse@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
/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).