All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Hansen <rhansen@bbn.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Junio C Hamano <gitster@pobox.com>,
	Git Mailing List <git@vger.kernel.org>
Subject: Re: [PATCH/RFC] Developer's Certificate of Origin: default to COPYING
Date: Thu, 12 Sep 2013 19:15:38 -0400	[thread overview]
Message-ID: <52324B1A.2030001@bbn.com> (raw)
In-Reply-To: <CA+55aFyQZ8EiOg+CZy-KMaX0Hnkdmvq1+8b9p6uuMuHAUzYaAg@mail.gmail.com>

On 2013-09-12 18:44, Linus Torvalds wrote:
> On Thu, Sep 12, 2013 at 3:30 PM, Junio C Hamano <gitster@pobox.com> wrote:
>> Linus, this is not limited to us, so I am bothering you; sorry about
>> that.
>>
>> My instinct tells me that some competent lawyers at linux-foundation
>> helped you with the wording of DCO, and we amateurs shouldn't be
>> mucking with the text like this patch does at all, but just in case
>> you might find it interesting...
> 
> There were lawyers involved, yes.
> 
> I'm not sure there is any actual confusion, because the fact is,
> lawyers aren't robots or programmers, and they have the human
> qualities of understanding implications.

Well stated.  :)

> So I'm actually inclined to
> not change legal text unless a lawyer actually tells me that it's
> needed.

Is it worthwhile to poke a lawyer about this as a precaution?  (If so,
who?)  Or do we wait for a motivating event?

> 
> Plus even if this change was needed, why would anybody point to
> "COPYING". It's much better to just say "the copyright license of the
> file", knowing that different projects have different rules about this
> all, and some projects mix files from different sources, where parts
> of the tree may be under different licenses that may be explained
> elsewhere..

I agree that your phrasing is better.

-Richard

  reply	other threads:[~2013-09-12 23:15 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-12 22:11 [PATCH/RFC] Developer's Certificate of Origin: default to COPYING Richard Hansen
2013-09-12 22:30 ` Junio C Hamano
2013-09-12 22:44   ` Linus Torvalds
2013-09-12 23:15     ` Richard Hansen [this message]
2013-09-12 23:24       ` Theodore Ts'o
2013-09-12 23:25       ` Linus Torvalds
2013-09-13  1:18         ` W. Trevor King

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=52324B1A.2030001@bbn.com \
    --to=rhansen@bbn.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --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 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.