emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Carsten Dominik <carsten.dominik@gmail.com>
To: "Andreas Röhler" <andreas.roehler@easy-emacs.de>
Cc: Bastien <bzg@altern.org>, emacs-orgmode@gnu.org
Subject: Re: Copyright of contributions to org-mode
Date: Wed, 13 Mar 2013 13:56:27 +0100	[thread overview]
Message-ID: <213E9614-E89E-4A1D-8064-C46D25D350DF@gmail.com> (raw)
In-Reply-To: <5140728B.5080505@easy-emacs.de>


On 13 mrt. 2013, at 13:35, Andreas Röhler <andreas.roehler@easy-emacs.de> wrote:

> Am 13.03.2013 13:10, schrieb Bastien:
>> Andreas Röhler <andreas.roehler@easy-emacs.de> writes:
>> 
>>> Or maybe drop that sentence.
>> 
>> Nope: the whole purpose of clarifying is to make it clear what are
>> the licensing terms, when the assignement is needed, and what are the
>> consequences of assigning the copyright.
>> 
>> We should be short but exhaustive here.
>> 
>> The idea is to make sure people understand that sending patches for
>> Org's core is *exactly* like having the patch integrated into Emacs.
>> Both the copyright assignment and the agreement on the licensing terms
>> are preconditions.
>> 
> 
> Hi Bastien, Hi Carsten,
> 
> as these legal matters are of interest to a certain extend:
> 
> 1) does this change/sentence meet the problem arised?

I think so.  Jambunathan tried to argue that his signed copyright assignment papers should only become active at the moment the changes arrive at Emacs.

> 2) is the sentence in question here true, can it be true?
> 
> 1d There was no misunderstanding but displayed frustration, eagerness or whatever.
>   No misunderstanding, no need to clarify the pretended matter.

The motive was disgruntlement, but the argument was based on this perceived loophole.

> 
> 2nd) If someone changes a GPLed file while propagating the changes with a compatible license as mentioned
>     http://www.gnu.org/licenses/license-list.html#GPLCompatibleLicenses:
> 
>     Is org-mode going to create its own legislation excluding this? :)


No, we are not creating legislation.  We are writing down a policy.  If the case your describe should arise, it can be dealt with then.

- Carsten

      parent reply	other threads:[~2013-03-13 12:56 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-13 10:50 Copyright of contributions to org-mode Carsten Dominik
2013-03-13 11:12 ` Andreas Röhler
2013-03-13 11:34   ` Carsten Dominik
2013-03-13 11:13 ` Giovanni Ridolfi
2013-03-13 11:33   ` Carsten Dominik
2013-03-13 11:50     ` Bastien
2013-03-13 12:05       ` Andreas Röhler
2013-03-13 12:10         ` Bastien
2013-03-13 12:35           ` Andreas Röhler
2013-03-13 12:54             ` Bastien
2013-03-13 12:56             ` Carsten Dominik [this message]

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

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=213E9614-E89E-4A1D-8064-C46D25D350DF@gmail.com \
    --to=carsten.dominik@gmail.com \
    --cc=andreas.roehler@easy-emacs.de \
    --cc=bzg@altern.org \
    --cc=emacs-orgmode@gnu.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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).