From: Carlos O'Donell <carlos@redhat.com>
To: Florian Weimer <fweimer@redhat.com>, libc-alpha@sourceware.org
Subject: Re: Copyright header for localedata files contributed under DCO
Date: Mon, 6 Sep 2021 10:04:54 -0400 [thread overview]
Message-ID: <ebf6415f-6053-18e1-6e9d-990ab8997f51@redhat.com> (raw)
In-Reply-To: <87pmtq54hs.fsf@oldenburg.str.redhat.com>
On 9/3/21 6:37 AM, Florian Weimer via Libc-alpha wrote:
> The localedata files currently contain this:
>
> % This file is part of the GNU C Library and contains locale data.
> % The Free Software Foundation does not claim any copyright interest
> % in the locale data contained in this file. The foregoing does not
> % affect the license of the GNU C Library as a whole. It does not
> % exempt you from the conditions of the license if your use would
> % otherwise be governed by that license.
>
> I think the wording is less than satisfying because it's unclear whether
> the patch submitter (or someone else) retains any copyright claims to
> the file. With localedata patches submitted under the DCO, this becomes
> even more confusing.
I agree, with DCO there could be additional copyright authors.
> Therefore, I proposed to
>
> comment_char %
> escape_char /
>
> % Copyright The GNU Toolchain Authors.
This is the only important line that is required IMO.
> % This file is part of the GNU C Library.
> %
> % The GNU C Library is free software; you can redistribute it and/or
> % modify it under the terms of the GNU Lesser General Public
> % License as published by the Free Software Foundation; either
> % version 2.1 of the License, or (at your option) any later version.
> %
> % The GNU C Library is distributed in the hope that it will be useful,
> % but WITHOUT ANY WARRANTY; without even the implied warranty of
> % MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
> % Lesser General Public License for more details.
> %
> % You should have received a copy of the GNU Lesser General Public
> % License along with the GNU C Library; if not, see
> % <https://www.gnu.org/licenses/>.
This looks good to me and it adds license information.
> The main reason is to keep the contribution process simple. For
> example, we do not need to argue with the submitter whether they
> actually can disclaim copyright or database protection rights.
Agreed.
> Since the FSF disclaims copyright, we can also apply this header to
> mixed FSF/DCO files once the need arises.
As a project stewards I think you're taking this in the right direction.
Please feel free to involve min the review of patches that include the
new header.
--
Cheers,
Carlos.
next prev parent reply other threads:[~2021-09-06 14:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-03 10:37 Florian Weimer
2021-09-04 1:06 ` Mike Frysinger
2021-09-03 20:55 ` Florian Weimer
2021-09-05 3:22 ` Mike Frysinger
2021-09-05 5:17 ` Florian Weimer
2021-09-06 14:03 ` Carlos O'Donell
2021-09-06 21:45 ` Mike Frysinger
2021-09-06 14:04 ` Carlos O'Donell [this message]
2021-12-16 18:51 ` Maxim Kuvyrkov
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=ebf6415f-6053-18e1-6e9d-990ab8997f51@redhat.com \
--to=carlos@redhat.com \
--cc=fweimer@redhat.com \
--cc=libc-alpha@sourceware.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.
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).