From: Joseph Myers <joseph@codesourcery.com>
To: Alexandre Oliva <oliva@gnu.org>
Cc: Carlos O'Donell <carlos@redhat.com>,
"Ryan S. Arnold" <ryan.arnold@gmail.com>,
Paul Eggert <eggert@cs.ucla.edu>,
Maxim Kuvyrkov <maxim.kuvyrkov@linaro.org>,
Jakub Jelinek <jakub@redhat.com>, Andreas Schwab <schwab@suse.de>,
libc-alpha <libc-alpha@sourceware.org>
Subject: Re: [Action Required] glibc decision to use CTI services.
Date: Wed, 30 Aug 2023 17:31:13 +0000 [thread overview]
Message-ID: <cc4f81c9-29b7-76af-b188-a6db4f32bcb@codesourcery.com> (raw)
In-Reply-To: <orsf805tyf.fsf@lxoliva.fsfla.org>
On Wed, 30 Aug 2023, Alexandre Oliva wrote:
> Even then, this would IMHO be a move for GNU to decide, or at the very
> least be consulted on, according to its own values and priorities,
> something that all mantainers appointed by GNU, myself included,
> committed ourselves to observe, prioritize and uphold as maintainers of
> GNU packages. I encourage other maintainers to justify their responses
> based on GNU's values and priorities, as they understand them.
I believe the LF has already agreed to implement the hosting entirely with
free software. Naturally we should make sure that other requirements from
https://www.gnu.org/software/repo-criteria.en.html such as "Does not
discriminate against classes of users, or against any country. (C2)" and
"Permits access via Tor (we consider this an important site function).
(C3)" are met, though I don't expect problems there. Several criteria are
trivally met or inapplicable simply because they concern things that are
beyond the scope of this proposed hosting (for example, recommending
particular choices of license, or offering choices of license, is entirely
outside the scope of what these hosting facilities do, just as it's
outside the scope of what Sourceware does - those are criteria for
general-purpose hosting sites that anyone might add a package to).
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2023-08-30 17:31 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <b84ea4a5-651a-1a4c-06c8-e9ade4b7d702@redhat.com>
2023-08-30 17:19 ` Alexandre Oliva
2023-08-30 17:31 ` Joseph Myers [this message]
2023-08-31 19:59 ` Paul Eggert
2023-09-01 6:03 ` Sam James
2023-09-01 8:55 ` Florian Weimer
2023-09-01 9:02 ` Sam James
2023-09-01 9:21 ` dmarc, dkim and From rewriting Mark Wielaard
2023-09-01 11:52 ` Florian Weimer
2023-09-01 9:03 ` [Action Required] glibc decision to use CTI services Andrew Pinski
2023-09-01 11:49 ` Florian Weimer
2023-09-01 13:32 ` Frank Ch. Eigler
2023-09-01 12:30 ` Siddhesh Poyarekar
2023-09-01 14:54 ` Paul Eggert
2023-09-01 16:08 ` Siddhesh Poyarekar
2023-09-01 15:01 ` Sam James
2023-09-01 16:19 ` Frank Ch. Eigler
2023-09-01 16:30 ` Siddhesh Poyarekar
2023-09-02 18:25 ` Mark Wielaard
2023-09-01 9:08 ` Mark Wielaard
2023-09-03 6:31 ` Alexandre Oliva
2023-09-27 13:49 ` Carlos O'Donell
2023-10-04 0:09 ` Paul Eggert
2023-09-01 15:09 ` Alexandre Oliva
2023-09-27 13:50 ` Carlos O'Donell
2024-02-13 0:43 ` Carlos O'Donell
2024-02-19 21:22 ` Alexandre Oliva
2024-02-19 22:03 ` DJ Delorie
2024-02-20 1:49 ` Mark Wielaard
2024-02-20 3:01 ` Alexandre Oliva
2023-08-31 8:37 ` Mark Wielaard
2023-09-01 15:08 ` Alexandre Oliva
2023-08-31 10:34 ` Florian Weimer
2023-09-04 6:09 ` Alexandre Oliva
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=cc4f81c9-29b7-76af-b188-a6db4f32bcb@codesourcery.com \
--to=joseph@codesourcery.com \
--cc=carlos@redhat.com \
--cc=eggert@cs.ucla.edu \
--cc=jakub@redhat.com \
--cc=libc-alpha@sourceware.org \
--cc=maxim.kuvyrkov@linaro.org \
--cc=oliva@gnu.org \
--cc=ryan.arnold@gmail.com \
--cc=schwab@suse.de \
/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).