All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Ted Ts'o" <tytso@mit.edu>
To: "Luis R. Rodriguez" <mcgrof@do-not-panic.com>
Cc: Richard Fontana <fontana2012@gmail.com>,
	"Bradley M. Kuhn" <bkuhn@ebb.org>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 4/4] copyleft-next: embrace the Signed-off-by practice
Date: Thu, 12 Jul 2012 11:27:40 -0400	[thread overview]
Message-ID: <20120712152740.GB14792@thunk.org> (raw)
In-Reply-To: <1342053889-32066-5-git-send-email-mcgrof@do-not-panic.com>

On Wed, Jul 11, 2012 at 05:44:49PM -0700, Luis R. Rodriguez wrote:
> From: "Luis R. Rodriguez" <mcgrof@do-not-panic.com>
> 
> The idea is taken from Linus Torvald's subsurface
> project [0] README file. The Signed-off-by is widely
> used in public projects and we stand to gain to make
> its usage more prevalent. The meaning of the
> Signed-off-by is borrowed from the Linux kernel's.
> 
> [0] git://github.com/torvalds/subsurface.git
> 
> Signed-off-by: Luis R. Rodriguez <mcgrof@do-not-panic.com>

I wonder why you're cc'ing the linux-kernel mailing list?  I've
checked the copyleft-next clause, and the anti-Tivoization clauses,
which was one of the primary reasons articulated by many kernel
developers --- including Linus Torvalds --- for not using GPLv3, is
still in the Copyleft-next license.

My understanding of Richard Fontana's past public positions was that
he was supportive of that part of the GPLv3 license, and so I had
assumed the Copyleft-next effort would be irrelevant as far as the
Linux Kernel was concerned.

Even if I am wrong about that (and I would be delighted if the answer
was that one of the Copyright-next's goals was to resolve this barrier
of the kernel moving off of GPLv2), it still would seem to me to be
out of scope of the LKML.

Regards,

							- Ted

  reply	other threads:[~2012-07-12 15:27 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-12  0:44 [PATCH 0/4] copyleft-next: first set of patches Luis R. Rodriguez
2012-07-12  0:44 ` [PATCH 1/4] copyleft-next: remove issue tracker references Luis R. Rodriguez
2012-07-12  0:44 ` [PATCH 2/4] copyleft-next: more project name updates Copyleft.next->copyleft-next Luis R. Rodriguez
2012-07-12  0:44 ` [PATCH 3/4] copyleft-next: rename the file COPYLEFT.next to copyleft-next Luis R. Rodriguez
2012-07-12  0:44 ` [PATCH 4/4] copyleft-next: embrace the Signed-off-by practice Luis R. Rodriguez
2012-07-12 15:27   ` Ted Ts'o [this message]
2012-07-12 17:30     ` Luis R. Rodriguez
2012-07-12 17:57       ` Ted Ts'o
2012-07-12 18:16         ` Luis R. Rodriguez
2012-07-12 19:41     ` Richard Fontana

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=20120712152740.GB14792@thunk.org \
    --to=tytso@mit.edu \
    --cc=bkuhn@ebb.org \
    --cc=fontana2012@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mcgrof@do-not-panic.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.