unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Brice Waegeneire <brice@waegenei.re>,
	39522@debbugs.gnu.org, Nicolas Goaziou <mail@nicolasgoaziou.fr>
Subject: [bug#39522] When to add a copyright line?
Date: Fri, 14 Feb 2020 15:04:06 +0100	[thread overview]
Message-ID: <87mu9lgt9l.fsf_-_@gnu.org> (raw)
In-Reply-To: <handler.39522.D39522.15814455763176.notifdone@debbugs.gnu.org> (GNU bug Tracking System's message of "Tue, 11 Feb 2020 18:27:03 +0000")

Hello!

> Brice Waegeneire <brice@waegenei.re> writes:
>
>> I wrote a new patch with your suggestion.
>
> Thank you! I applied it as 81565d23df3080b4d43d2ce0bfa49251827a34e9.
>
>> Sorry for the missing copyright lines in the previous patches you
>> merged, I thought it was non-mandatory on trivial modifications.
>
> I honestly do not know if it is mandatory in this case. However, trivial
> modifications may pile up and it could become a concern at some point.

FWIW, I agree with both of you.  :-)

Technically, a contribution is not considered “legally significant” if
it is below 15 lines of code or so (info "(maintain) Legally
Significant").

Furthermore, copyright only applies to things that are “inventive”,
which typically means there’s more than one way to do it.  Thus, one
could argue about whether some of our package definitions are
copyrightable at all (in the EU, there’s a “sui generis” database right
though, so it could fall under that, but IANAL.)

Anyway, long story short: I agree with Nicolas that it’s easier to just
always add a copyright line, and it’s better than forgetting to add one.

Ludo’.

      parent reply	other threads:[~2020-02-14 14:05 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-09  9:11 [bug#39522] [PATCH] gnu: dunst: Build dunstify Brice Waegeneire
2020-02-09 23:45 ` Nicolas Goaziou
2020-02-10  8:57   ` Brice Waegeneire
2020-02-11 18:26     ` bug#39522: " Nicolas Goaziou
2020-02-10  8:51 ` [bug#39522] [PATCH v2] " Brice Waegeneire
     [not found] ` <handler.39522.D39522.15814455763176.notifdone@debbugs.gnu.org>
2020-02-14 14:04   ` Ludovic Courtès [this message]

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=87mu9lgt9l.fsf_-_@gnu.org \
    --to=ludo@gnu.org \
    --cc=39522@debbugs.gnu.org \
    --cc=brice@waegenei.re \
    --cc=mail@nicolasgoaziou.fr \
    /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 public inbox

	https://git.savannah.gnu.org/cgit/guix.git

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).