From: Paul Eggert <eggert@cs.ucla.edu>
To: Joseph Myers <joseph@codesourcery.com>, Alexandre Oliva <oliva@gnu.org>
Cc: Carlos O'Donell <carlos@redhat.com>,
"Ryan S. Arnold" <ryan.arnold@gmail.com>,
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: Thu, 31 Aug 2023 12:59:11 -0700 [thread overview]
Message-ID: <15af1715-3530-7c29-7595-5abe48c18e8b@cs.ucla.edu> (raw)
In-Reply-To: <cc4f81c9-29b7-76af-b188-a6db4f32bcb@codesourcery.com>
On 2023-08-30 10:31, Joseph Myers wrote:
> I believe the LF has already agreed to implement the hosting entirely with
> free software.
Where is this agreement written down? I didn't see it in the URLs
mentioned at the start of this thread.
Too often it is tempting to use non-free software in these enterprises,
and we need to have an agreement and a commitment about an enforcement
mechanism that detects and repairs things if somebody falls victim to
this temptation (and of course that guides people away from succumbing
to the temptation in the first place). This detection and enforcement
mechanism has to be usable by glibc software contributors and
maintainers, not just by the CTI providers.
As I'm new to this (I just read yesterday that a decision is wanted by
today) I'll vote NAY until I see something more binding about this
important issue.
> Naturally we should make sure that other requirements from
> https://www.gnu.org/software/repo-criteria.en.html ... are met, though I don't expect problems there.
Although I don't expect problems either, I'd like to see this written
down as well.
next prev parent reply other threads:[~2023-08-31 19:59 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
2023-08-31 19:59 ` Paul Eggert [this message]
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=15af1715-3530-7c29-7595-5abe48c18e8b@cs.ucla.edu \
--to=eggert@cs.ucla.edu \
--cc=carlos@redhat.com \
--cc=jakub@redhat.com \
--cc=joseph@codesourcery.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).