unofficial mirror of libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Siddhesh Poyarekar <siddhesh@gotplt.org>
To: Carlos O'Donell <carlos@redhat.com>,
	libc-alpha <libc-alpha@sourceware.org>
Subject: Re: Update to glibc copyright assignment policy
Date: Thu, 29 Jul 2021 19:37:02 +0530	[thread overview]
Message-ID: <37be148e-f0a7-0930-3d6e-494d868538eb@gotplt.org> (raw)
In-Reply-To: <a1175763-90f4-1c8c-f965-236f9d945f06@redhat.com>

On 7/29/21 7:28 PM, Carlos O'Donell wrote:
> 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?
> 

Yes it does, thank you.  I agree that taking a call on a case by case 
basis seems like the right way to go about it.

Thanks,
Siddhesh

  reply	other threads:[~2021-07-29 14:13 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
2021-07-29 14:07     ` Siddhesh Poyarekar [this message]
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=37be148e-f0a7-0930-3d6e-494d868538eb@gotplt.org \
    --to=siddhesh@gotplt.org \
    --cc=carlos@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).