From: "Andreas Röhler" <andreas.roehler@easy-emacs.de>
To: help-gnu-emacs@gnu.org
Subject: Re: Basic legal question: Publication of a fix to psgml
Date: Wed, 03 Apr 2013 09:54:43 +0200 [thread overview]
Message-ID: <515BE043.8030900@easy-emacs.de> (raw)
In-Reply-To: <87ppydxqh4.fsf@scipolis.de>
Am 02.04.2013 10:54, schrieb Nicolas Neuss:
> Bastien <bzg@altern.org> writes:
>
>> Hi,
>>
>> Andreas Röhler <andreas.roehler@easy-emacs.de> writes:
>>
>>> When using GPLed code, you may simply publish your changed code
>>> GPLed again.
>>
>> More precisely, GPLed code gives you the right to reuse and publish
>> the code in your code if it's published under the same license.
>>
>> So yes, you can publish your changes to this code.
>>
>>> Thanks giving another example wrt to the noxious results of
>>> copyright assigment policy, which undermines goals of GPL.
>>
>> Why pushing your agenda against copyright assignment into this thread?
>>
>> I don't think it is irrevelant.
>>
>> The question is "Can I publish the changes?" and the answer is "Yes".
>>
>> As for including psgml into GNU ELPA, the answer is "Not until all
>> authors have sign the FSF copyright assignment".
>>
>> This is a policy that is particular to GNU Emacs and some other GNU
>> projects. It shows respect for potential authors (by not including
>> their code without their permission) and protects actual authors (by
>> allowing them to rely on the fact that changes against Emacs code by
>> signed contributors can be part of Emacs.)
>
> I think there is a more important reason for those copyright
> assignments: The FSF considers its projects as so central for free
> software that their copyright status has to be beyond any doubt.
>
> For example, there could arise severe damage if some malicious company
> (you name it) suddenly claimed that central pieces of GNU software were
> contributed (maybe years ago) by some of their employees without
> employer's permission.
>
In which way a CA-paper could avoid that?
What about the opposite danger: a company signs, provides crucial parts and withdraws CA?
See current discussions at emacs-devel on a lower scale.
Emacs got a lot of re-write already for pur CA-reasons.
Isn't that spoiled human labor in the light of GPL?
Andreas
> Nicolas
>
> [I will read answers to this, but (probably) not respond, because I also
> think that this is the wrong newsgroup for this discussion.]
>
>
>
next prev parent reply other threads:[~2013-04-03 7:54 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-31 11:49 Basic legal question: Publication of a fix to psgml Florian v. Savigny
2013-03-31 13:27 ` Dmitry Gutov
2013-03-31 14:53 ` Andreas Röhler
2013-03-31 15:09 ` Bastien
2013-03-31 15:33 ` Bastien
2013-03-31 15:36 ` Andreas Röhler
2013-03-31 15:46 ` Bastien
2013-03-31 15:35 ` Andreas Röhler
2013-03-31 16:06 ` Eli Zaretskii
2013-03-31 16:57 ` Andreas Röhler
2013-03-31 18:57 ` Eli Zaretskii
2013-03-31 19:49 ` Andreas Röhler
2013-03-31 20:01 ` Eli Zaretskii
2013-03-31 21:56 ` Florian v. Savigny
2013-04-01 16:08 ` Bastien
2013-04-01 17:24 ` Florian v. Savigny
[not found] ` <mailman.23150.1364742598.855.help-gnu-emacs@gnu.org>
2013-04-02 8:54 ` Nicolas Neuss
2013-04-03 7:54 ` Andreas Röhler [this message]
2013-04-03 8:02 ` Dmitry Gutov
2013-04-03 8:16 ` Andreas Röhler
2013-04-03 8:29 ` Bastien
2013-04-03 12:03 ` Andreas Röhler
[not found] ` <mailman.23376.1364990549.855.help-gnu-emacs@gnu.org>
2013-04-03 17:04 ` B. T. Raven
2013-04-04 8:38 ` Andreas Röhler
2013-04-03 10:02 ` Phillip Lord
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=515BE043.8030900@easy-emacs.de \
--to=andreas.roehler@easy-emacs.de \
--cc=help-gnu-emacs@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
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.