From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: Simon Tournier <zimon.toutoune@gmail.com>
Cc: Wilko Meyer <w@wmeyer.eu>, help-guix@gnu.org
Subject: Re: documentation on copyright headers?
Date: Sun, 03 Dec 2023 14:09:29 -0500 [thread overview]
Message-ID: <871qc3yufq.fsf@gmail.com> (raw)
In-Reply-To: <87sf4m7zdb.fsf@gmail.com> (Simon Tournier's message of "Fri, 01 Dec 2023 15:48:16 +0100")
Hi,
Simon Tournier <zimon.toutoune@gmail.com> writes:
> Hi,
>
> On Thu, 16 Nov 2023 at 15:39, Wilko Meyer <w@wmeyer.eu> wrote:
>
>> - why a copyright header has to be inserted
>> - if a copyright header has to be inserted for all files that are
>> subject to changes (is there a treshold? can it be left out for minor
>> changes to files etc.?) of a sent patch.
>
> As a rule of thumb, each time your change is non-trivial – say more than
> 5 modified or new lines in one specific file – it deserves a Copyright
> header on that specific file. Note that deleting only does not count,
> i.e., Copyright does not apply
>
> 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. Now, it should be avoided, IMHO.
I think it should be avoided as well, the long list of copyrights are
already a bit messy to maintain across trees :-).
info '(maintain) Legally Significant' offers as advice that changes of
15 lines or less or not legally significant for copyright.
--
Thanks,
Maxim
next prev parent reply other threads:[~2023-12-03 19:10 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)
2023-12-03 19:09 ` Maxim Cournoyer [this message]
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=871qc3yufq.fsf@gmail.com \
--to=maxim.cournoyer@gmail.com \
--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).