From: Paul Eggert <eggert@cs.ucla.edu>
To: Carlos O'Donell <carlos@redhat.com>,
Joseph Myers <joseph@codesourcery.com>,
Alexandre Oliva <oliva@gnu.org>
Cc: "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: Tue, 3 Oct 2023 17:09:19 -0700 [thread overview]
Message-ID: <4ed6a7ae-8c71-fcdd-985f-4ab5b93cc7f0@cs.ucla.edu> (raw)
In-Reply-To: <abfb9308-66b5-b843-6169-d569b062ceaa@redhat.com>
On 9/27/23 06:49, Carlos O'Donell wrote:
> CTI is the project providing the services. CTI asks the provider, LF IT, to adhere
> to our requirements which include the use of only FOSS in the deployment of the
> services.
>
> I will work with the CTI TAC and LF IT to setup documents that detail the requests
> and what will be provided and I'll publish those publicly.
>
> We have also had requests for ensuring that we have a proper strategy for changing
> providers. I will document those also. Some services are quite hard in reality
> like Bugzilla or Patchwork which have databases that need duplication.
Thanks, this is exactly the sort of thing I was looking for.
next prev parent reply other threads:[~2023-10-04 0:09 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
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 [this message]
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=4ed6a7ae-8c71-fcdd-985f-4ab5b93cc7f0@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).