all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Stefan Monnier via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Markus Triska <triska@metalevel.at>
Cc: 58196@debbugs.gnu.org
Subject: bug#58196: Trivial update to ediprolog
Date: Tue, 25 Oct 2022 15:49:01 -0400	[thread overview]
Message-ID: <jwvo7tz3d46.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <87sfjfath5.fsf@metalevel.at> (Markus Triska's message of "Sun, 23 Oct 2022 09:29:10 +0200")

>> [ BTW, you've signed the copyright paperwork which transferred the
>>   copyright to the FSF, so you technically do not own the copyright to
>>   that file any more, so your upstream code's copyright line is
>>   incorrect.  ]
>
> The jurisdiction where I reside guarantees authors' rights as opposed to
> copyright.

Yes, they use different names, but they work pretty much in the same way.

> Certain rights I have as the sole author of ediprolog.el
> cannot be transferred,

The same for copyright law in North America.  They're just called
differently, but by and large they work the same.

> except by inheritance, even if I wanted to transfer them (§ 23
> Abs. 3 UrhG). The rights I have as the author of ediprolog.el include
> the right to decide whether and how to display that I am its author (§
> 20 Abs. 1 UrhG).
>
> In the master file of ediprolog.el, I am using the copyright notice as
> the usual way ("übliche Weise") in which authorship is indicated in
> code. This is to satisfy the conditions of § 12 UrhG to indicate me as
> the author of the code. Since I am the author, the notice it correct.

Fine, then it's not technically incorrect, but it's still inconvenient
for us and it's misleading when interpreted based on the meaning of
those words in some other jurisdictions.  In contrast, you also have

    ;; Author: Markus Triska <triska@metalevel.at>

in that file, which should be very clear to everyone and makes your
copyright line redundant (in addition to inconvenient for us and
misleading in some contexts).

> I have the rights I mentioned also without this notice, and therefore I
> accept changes you make to this notice if they are required to
> distribute ediprolog.el on ELPA. The master file I provide in the
> jurisdiction where I reside will retain the notice for the reason above.

If all authors of all GNU ELPA packages were to ask for special
treatment for their pet detail, I'd have given up on GNU ELPA
a long time ago.


        Stefan






  reply	other threads:[~2022-10-25 19:49 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-30 16:59 bug#58196: 27.0.50; ediprolog 2.2: Please upload the new version to ELPA Markus Triska
2022-10-01 12:56 ` Lars Ingebrigtsen
2022-10-01 14:57 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-01 17:01   ` Markus Triska
2022-10-01 18:37     ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-02 19:49       ` Markus Triska
2022-10-02 20:07         ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-02 20:24           ` Markus Triska
2022-10-02 21:08             ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-03  0:43               ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-18 14:34 ` bug#58196: Trivial update to ediprolog Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-26 13:26   ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-26 13:32     ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-27 21:11       ` Markus Triska
2022-10-28  2:08         ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-28  3:06           ` Stefan Kangas
2022-10-28  3:35             ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-28  6:35             ` Eli Zaretskii
2022-10-28 12:37               ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-28  3:09           ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-28 16:49             ` Markus Triska
2022-10-28 18:07               ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-28 20:01                 ` Stefan Kangas
2022-10-28 20:20                   ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-28 20:51                     ` Stefan Kangas
2022-10-28 21:54                       ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-22 16:20 ` Markus Triska
2022-10-22 16:51   ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-23  7:29 ` Markus Triska
2022-10-25 19:49   ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2024-01-10 10:54 ` bug#58196: 27.0.50; ediprolog 2.2: Please upload the new version to ELPA Stefan Kangas
2024-01-10 22:11   ` Markus Triska
2024-01-10 23:18     ` Stefan Kangas
2024-01-14  7:40       ` Markus Triska
2024-01-14 10:17         ` Stefan Kangas

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=jwvo7tz3d46.fsf-monnier+emacs@gnu.org \
    --to=bug-gnu-emacs@gnu.org \
    --cc=58196@debbugs.gnu.org \
    --cc=monnier@iro.umontreal.ca \
    --cc=triska@metalevel.at \
    /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.