unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: "pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de>
To: Simon Tournier <zimon.toutoune@gmail.com>
Cc: Wilko Meyer <w@wmeyer.eu>,  help-guix@gnu.org
Subject: Re: documentation on copyright headers?
Date: Sat, 02 Dec 2023 10:37:19 +0100	[thread overview]
Message-ID: <87v89hlzcg.fsf@pelzflorian.de> (raw)
In-Reply-To: <87sf4m7zdb.fsf@gmail.com> (Simon Tournier's message of "Fri, 01 Dec 2023 15:48:16 +0100")

Simon Tournier <zimon.toutoune@gmail.com> writes:
> In the past, the project had been very permissive, where even 2 lines
> only modifying the version and checksum fields lead to hold a Copyright
> on such modification.

In practice, I agree.  Changing the version and checksum of 100 packages
likely does not add up and does not give copyright (it is no creative
act).  Though 4 lines of srfi-1 list processing perhaps do give
copyright.

That said, copyright headers are only for tracking copyright.  They do
not anymore AFAIK help in the legal system (in EU and USA) and are not
always accurate (parts of Guix’ package descriptions and service
documentation are copied from the package’s developer, but that
developer’s copyright is mentioned nowhere).

Regards,
Florian


  reply	other threads:[~2023-12-02  9:38 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-16 14:39 documentation on copyright headers? Wilko Meyer
2023-11-16 17:01 ` Felix Lechner via
2023-11-17  9:54   ` pelzflorian (Florian Pelz)
2023-12-01 14:48 ` Simon Tournier
2023-12-02  9:37   ` pelzflorian (Florian Pelz) [this message]
2023-12-03 19:09   ` Maxim Cournoyer
2024-01-11 17:29     ` Simon Tournier
2024-01-14  0:55       ` Wilko Meyer

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://guix.gnu.org/

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

  git send-email \
    --in-reply-to=87v89hlzcg.fsf@pelzflorian.de \
    --to=pelzflorian@pelzflorian.de \
    --cc=help-guix@gnu.org \
    --cc=w@wmeyer.eu \
    --cc=zimon.toutoune@gmail.com \
    /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).