unofficial mirror of libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Carlos O'Donell via Libc-alpha <libc-alpha@sourceware.org>
To: Siddhesh Poyarekar <siddhesh@gotplt.org>,
	libc-alpha <libc-alpha@sourceware.org>
Subject: Re: Update to glibc copyright assignment policy
Date: Thu, 29 Jul 2021 09:58:28 -0400	[thread overview]
Message-ID: <a1175763-90f4-1c8c-f965-236f9d945f06@redhat.com> (raw)
In-Reply-To: <b4d9bc3d-ba09-2e10-aa99-f6641ec3a1d7@gotplt.org>

On 7/29/21 6:25 AM, Siddhesh Poyarekar wrote:
> On 7/29/21 1:20 AM, Carlos O'Donell via Libc-alpha wrote:
>> branches. Code shared with other GNU packages via Gnulib will
>> continue to require assignment to the FSF.
> 
> Does that mean we cannot touch the code shared with gnulib if we do
> not assign copyright to the FSF?  Or does it mean that if/when that
> happens, we will stop syncing those bits with gnulib?

The code shared with gnulib carries with it an existing obligation
to the gnulib community that we maintain the existing copyright
protocol for those files to honour that obligation.

My suggestion is that we as a community in glibc need to decide,
on a file-by-file basis what we are going to do. I'm open to other
alternatives too, the following 2 steps are just my suggestion.

(1) Update https://sourceware.org/glibc/wiki/SharedSourceFiles with
    the actual file status.

(2) Make a decision.

* Find a new way to share the code with minimal impact.
  - Carve out glibc-related functions into distinct files that can 
    have DCO.
  - Leave the #_LIBC conditionals with minimal code.

* Stop sharing this code with gnulib, and own it.
  - Delete !#_LIBC code.
  - Simplify.
  - Use internal glibc interfaces
  - etc.

Does that answer your question?

-- 
Cheers,
Carlos.


  reply	other threads:[~2021-07-29 14:09 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-28 19:50 Update to glibc copyright assignment policy Carlos O'Donell via Libc-alpha
2021-07-29 10:25 ` Siddhesh Poyarekar
2021-07-29 13:58   ` Carlos O'Donell via Libc-alpha [this message]
2021-07-29 14:07     ` Siddhesh Poyarekar
2021-07-29 14:21     ` Florian Weimer via Libc-alpha
2021-07-29 19:02       ` Paul Eggert

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://www.gnu.org/software/libc/involved.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=a1175763-90f4-1c8c-f965-236f9d945f06@redhat.com \
    --to=libc-alpha@sourceware.org \
    --cc=carlos@redhat.com \
    --cc=siddhesh@gotplt.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).