unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: "pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de>
To: help-guix@gnu.org
Cc: Wilko Meyer <w@wmeyer.eu>,  Felix Lechner <felix.lechner@lease-up.com>
Subject: Re: documentation on copyright headers?
Date: Fri, 17 Nov 2023 10:54:51 +0100	[thread overview]
Message-ID: <878r6w66xg.fsf@pelzflorian.de> (raw)
In-Reply-To: <871qcpy6n8.fsf@lease-up.com> (Felix Lechner via's message of "Thu, 16 Nov 2023 09:01:15 -0800")

Hello.

Felix Lechner via <help-guix@gnu.org> writes:
> For an active project like Guix, I personally tend not to add copyright
> notices unless I create a new file or unless my contribution appears so
> significant that another party would have to expend some effort in order
> to recreate it.
>
> Either way, it's better to add copyright notices. In case of doubt,
> please add one regardless of what people say.

IANAL, but even small contributions of code should be given a copyright
header, because when the same person makes many small code
contributions, these add up.  This does not mean that someone who is in
the copyright headers already really has copyright, as I believe could
be seen in the SFC vs. VMWare lawsuit.

Regards,
Florian


  reply	other threads:[~2023-11-17  9:55 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) [this message]
2023-12-01 14:48 ` Simon Tournier
2023-12-02  9:37   ` pelzflorian (Florian Pelz)
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=878r6w66xg.fsf@pelzflorian.de \
    --to=pelzflorian@pelzflorian.de \
    --cc=felix.lechner@lease-up.com \
    --cc=help-guix@gnu.org \
    --cc=w@wmeyer.eu \
    /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).