all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Julien Lepiller <julien@lepiller.eu>
To: guix-devel@gnu.org
Subject: Translation copyright
Date: Mon, 31 Aug 2020 14:20:37 +0200	[thread overview]
Message-ID: <20200831142037.00f77824@tachikoma.lepiller.eu> (raw)

Hi Guix!

I recently submitted a request to savannah admins to open a new project
for our translations (as we discussed back in February, so weblate can
have access to it, but not to the main repos). Amin was kind enough to
answer and noticed something weird with our copyright headers. We have
a lot of different headers in there.

Some of them are "Copyright (C) 2020 Ludovic Courtès" when Ludo
probably never modified the file himself (eg: guix-cookbook.de.po),

Others are "Copyright (C) 2018-2020 the authors of Guix (msgids)" (eg:
guix-manual.de.po)

Some are "Copyright © 2013 Free Software Foundation, Inc." (eg:
packages/vi.po)

Actual authors of translations are listed in the file, because the TP
robot would not accept the file otherwise.  However, the first copyright
header is more related to msgids and should be the same everywhere
(except for years).

I don't think Ludo is the only copyright holder here, and since we
don't require contributors to assign copyright to the FSF, I don't
think the copyright goes to the FSF either.

I'd like to change all of these headers to something like this:

Copyright (C) 2018-2020 the authors of Guix (msgids)

Followed by the copyright of individual translators (or maybe the
previous line is enough?)

This is probably the header to use in the pot files too.

Thank you!


             reply	other threads:[~2020-08-31 12:21 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-31 12:20 Julien Lepiller [this message]
2020-09-03 22:46 ` Translation copyright pelzflorian (Florian Pelz)

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=20200831142037.00f77824@tachikoma.lepiller.eu \
    --to=julien@lepiller.eu \
    --cc=guix-devel@gnu.org \
    /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/guix.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.