unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
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: Sun, 31 Mar 2013 18:57:25 +0200	[thread overview]
Message-ID: <51586AF5.1070309@easy-emacs.de> (raw)
In-Reply-To: <831uav4kr9.fsf@gnu.org>

Am 31.03.2013 18:06, schrieb Eli Zaretskii:
>> Date: Sun, 31 Mar 2013 17:35:41 +0200
>> From: Andreas Röhler <andreas.roehler@easy-emacs.de>
>> Cc: help-gnu-emacs@gnu.org
>>
>>>> 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?
>>
>> Copyright assignment policy stifles cooperation, encourages bad manners, spreads FUD.
>
> But saying that in GNU forums is rude and off-topic.  Please do this
> somewhere else.
>
>
>

Hi Eli,

please consider the case at stake: a great library like psgml.el, which delivered solutions hardly
found elsewhere, was kept nearly unknown for more than a decade.

Don't you accept there is a difference between not bundling code and not mentioning it?
Not to say: discourage it's use.

If you might consider the effect already visible in this thread, you will remark the notion of the explicit consentement of authors for a change or republishing as so 
called matter of respect.

Don't you see the danger which raises for all free software from  there?
All legal tracts and stances are interpreted in the light of habit.
If a court notices the habit of requesting personal consentements for otherwise GPLed code changes as a need,
the story of free software might be over.

Best regards,

Andreas







  reply	other threads:[~2013-03-31 16:57 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 [this message]
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
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

  List information: https://www.gnu.org/software/emacs/

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

  git send-email \
    --in-reply-to=51586AF5.1070309@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.
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).