public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Siddhesh Poyarekar <siddhesh@gotplt.org>
To: Alexandre Oliva <oliva@gnu.org>
Cc: GNU C Library <libc-alpha@sourceware.org>
Subject: Re: GNU C Library as its own CNA?
Date: Fri, 8 Sep 2023 06:58:53 -0400	[thread overview]
Message-ID: <16843bf8-f621-30fb-fbbf-d6b8ce633486@gotplt.org> (raw)
In-Reply-To: <orbkedj46k.fsf@lxoliva.fsfla.org>

On 2023-09-07 13:14, Alexandre Oliva wrote:
> On Sep  7, 2023, Siddhesh Poyarekar <siddhesh@gotplt.org> wrote:
> 
>> Maybe they were looking at GNU as a root CNA under Mitre
> 
> No, the invitation was from Red Hat, same thing you describe.

Then it's not as root, which means it would be a single CNA for all of GNU.

>> I think it's much
>> easier for individual packages to do this
> 
> It should be just as easy for GNU to do that, and then GNU packages can
> enroll even more easily.  That was the picture I got from the
> interactions at the time anyway, and it seemed to make sense.

A single non-root CNA for all of the GNU project doesn't make sense to 
me, given that packages have very distinct communities and needs.  Maybe 
there's a case for some packages to band together because, e.g. they 
have small communities and a single group could handle their security 
needs but for projects like glibc and the other toolchain projects I 
think it makes sense to have separate CNAs.  I don't mind helping other 
GNU maintainers that want to set up their own CNA; for toolchain 
projects other than glibc I'm happy to be directly involved too since I 
actively work on them.

Thanks,
Sid

  reply	other threads:[~2023-09-08 10:58 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-28 15:56 Siddhesh Poyarekar
2023-07-28 16:09 ` Florian Weimer
2023-07-28 16:11   ` Siddhesh Poyarekar
2023-07-28 16:41 ` Joseph Myers
2023-07-28 17:28   ` Paul Eggert
2023-09-06 11:41     ` Siddhesh Poyarekar
2023-09-06 12:33     ` Florian Weimer
2023-09-06 16:00       ` Paul Eggert
2023-09-06 16:33         ` Florian Weimer
2023-09-06 17:04           ` Paul Eggert
2023-07-31 17:42   ` Siddhesh Poyarekar
2023-09-06 11:40 ` Siddhesh Poyarekar
2023-09-06 18:35   ` Alexandre Oliva
2023-09-06 18:57     ` Siddhesh Poyarekar
2023-09-06 19:02       ` Paul Eggert
2023-09-06 22:01       ` Alexandre Oliva
2023-09-07  0:56         ` Siddhesh Poyarekar
2023-09-07  3:27           ` Alexandre Oliva
2023-09-07 10:48             ` Siddhesh Poyarekar
2023-09-07 15:46               ` Florian Weimer
2023-09-07 17:14               ` Alexandre Oliva
2023-09-08 10:58                 ` Siddhesh Poyarekar [this message]
2023-09-10 16:57                   ` Alexandre Oliva
2023-09-11  7:46                     ` Florian Weimer
2023-09-11 12:59                       ` Carlos O'Donell
2023-09-11  9:58                     ` Siddhesh Poyarekar
2023-09-11 12:47 ` Carlos O'Donell
2023-09-12 11:40   ` Siddhesh Poyarekar
2023-09-12 13:15     ` Adhemerval Zanella Netto

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=16843bf8-f621-30fb-fbbf-d6b8ce633486@gotplt.org \
    --to=siddhesh@gotplt.org \
    --cc=libc-alpha@sourceware.org \
    --cc=oliva@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.
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).