public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Mike Frysinger <vapier@gentoo.org>
To: Florian Weimer <fweimer@redhat.com>
Cc: libc-alpha@sourceware.org
Subject: Re: Copyright header for localedata files contributed under DCO
Date: Mon, 6 Sep 2021 17:45:52 -0400	[thread overview]
Message-ID: <YTaMEEFhhC+Mh44+@vapier> (raw)
In-Reply-To: <87mtor38jn.fsf@oldenburg.str.redhat.com>

[-- Attachment #1: Type: text/plain, Size: 1445 bytes --]

On 05 Sep 2021 07:17, Florian Weimer via Libc-alpha wrote:
> * Mike Frysinger:
> > i'm saying the files should disclaim all copyright.  the point is to convey
> > that these are data files where copyright shouldn't be relevant.
> 
> That's a very U.S.-centric perspective.  Many countries do not allow
> authors to disclaim copyright (at best such a declaration would
> interpreted as something like CC0).  And many countries also offer some
> kind of protection to organized collections of facts.

i'm aware of the thorny issues that some countries don't understand the concept
of public domain.  that is orthogonal to facts can't be copyrighted in the first
place.  iiuc, the FSF position on these files is that these are a list of facts
and as such, aren't eligble for copyright, so the notice at the top of the file
is making that clear (instead of the reasonable assumption that it's under the
top level COPYING* i.e. GPL-2 or LGPL-2).

i'll point out that these issues are not new.  it has always been this way, and
DCO doesn't really change it.

if you want to be super pessimistic and put something like CC0 on it, that's
fine, but we still need a check enforcing it.

> And I don't want to create a third type of contributions.

you've lost me.  requiring certain files be licensed in a certain way is not a
new issue.  we already won't accept contributions if people try to use something
like WTFPL.
-mike

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  parent reply	other threads:[~2021-09-06 21:45 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 [this message]
2021-09-06 14:04 ` Carlos O'Donell
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=YTaMEEFhhC+Mh44+@vapier \
    --to=vapier@gentoo.org \
    --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).