linux-sparse.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rob Taylor <rob.taylor@codethink.co.uk>
Cc: linux-sparse@vger.kernel.org, torvalds@linux-foundation.org
Subject: Re: License Questions
Date: Fri, 07 Sep 2007 13:07:04 +0100	[thread overview]
Message-ID: <46E13EE8.5050508@codethink.co.uk> (raw)
In-Reply-To: <1189144403.7105.13.camel@localhost>

Mathias Hasselmann wrote:
> 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?

Oh dear, I just found out that Debian considers OSL 1.1 non-free, though
not for this clause (which does seem particularly onerous), but for
clause 10.

That could be a problem for us GLib guys, as that would force gnome into
contrib!

Rob

> Thank you,
> Mathias
> 
> [1] http://taschenorakel.de/git/sparse


-- 
Rob Taylor, Codethink Ltd. -  http://codethink.co.uk

  reply	other threads:[~2007-09-07 12:03 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-07  5:53 License Questions Mathias Hasselmann
2007-09-07 12:07 ` Rob Taylor [this message]
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=46E13EE8.5050508@codethink.co.uk \
    --to=rob.taylor@codethink.co.uk \
    --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).