From: Carlos O'Donell <carlos@redhat.com>
To: "Frank Ch. Eigler" <fche@redhat.com>
Cc: cti-tac@lists.linuxfoundation.org
Subject: Re: suggested website faq addendum
Date: Fri, 8 Mar 2024 14:41:45 -0500 [thread overview]
Message-ID: <2407e9d6-7cb0-4b4b-bd53-816ea581ab3c@redhat.com> (raw)
In-Reply-To: <20240307223803.GA25065@redhat.com>
On 3/7/24 17:38, Frank Ch. Eigler wrote:
> Hi -
>
>> Please feel free to provide a diff to the sources so we can look at
>> your suggested changes.
>
> Here it is. I'm afraid I'm unable to provide answers to the questions.
Thanks!
Public readonly repos are also up now:
https://git.coretoolchain.dev/
> --- index.rst.txt.orig 2024-03-07 16:17:06.726132460 -0500
> +++ index.rst.txt 2024-03-07 16:20:31.854901376 -0500
> @@ -16,6 +16,13 @@
> must meet more stringent expectations to maintain the trust of the
> ecosystem. It is with this context in mind that CTI has been formed.
>
> + For example, the following demands and expectations are based on the
> + following origins:
> +
> + ? ?
> + ? ?
> +
> +
> * Q: What concrete steps will CTI help with?
>
> * A: Some of the major goals include:
> @@ -48,6 +55,13 @@
> infrastructure. Projects of similar scope and importance have been
> deploying significant resources for the use of the development community.
>
> +* Q: Are there plans to construct a feasibility-confirming prototype of
> + the entire constellation of enumerated services for a CTI project
> + before its migration is decided?
> +
> + * A: ?
> +
> +
> * Q: Sourceware volunteers have fielded requests and organized volunteer
> efforts that have worked well. Does LF allow volunteers to administer
> the servers together with them? Have they in the past?
>
--
Cheers,
Carlos.
prev parent reply other threads:[~2024-03-08 19:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-07 19:59 suggested website faq addendum Frank Ch. Eigler
2024-03-07 20:20 ` Carlos O'Donell
2024-03-07 22:38 ` Frank Ch. Eigler
2024-03-08 19:41 ` Carlos O'Donell [this message]
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=2407e9d6-7cb0-4b4b-bd53-816ea581ab3c@redhat.com \
--to=carlos@redhat.com \
--cc=cti-tac@lists.linuxfoundation.org \
--cc=fche@redhat.com \
/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 NNTP newsgroup(s).