From: Siddhesh Poyarekar <siddhesh@gotplt.org>
To: cti-tac@lists.linuxfoundation.org
Subject: [PATCH 5/5] faq: Reformat so that it's not a list
Date: Thu, 7 Mar 2024 14:30:19 -0500 [thread overview]
Message-ID: <20240307193019.4028812-6-siddhesh@gotplt.org> (raw)
In-Reply-To: <20240307193019.4028812-1-siddhesh@gotplt.org>
Making it into subheadings and content instead not only makes it cleaner
looking, it also gives us a nifty bar on the right to scroll through
questions.
Signed-off-by: Siddhesh Poyarekar <siddhesh@gotplt.org>
---
source/faq/index.rst | 223 ++++++++++++++++++++-----------------------
1 file changed, 106 insertions(+), 117 deletions(-)
diff --git a/source/faq/index.rst b/source/faq/index.rst
index cb8a458..84ff30f 100644
--- a/source/faq/index.rst
+++ b/source/faq/index.rst
@@ -6,123 +6,112 @@ FAQ
You have questions we have answers!
-* Q: Can we keep deploying services as we have?
-
- * A: No. The GNU Toolchain is a critical foundation of trust for the GNU/Linux
- ecosystem and the demands on its infrastructure, services, and security
- requirements have grown over time. The trend of increasing complexity to
- support its development and associated financial demands will not abate.
- Different projects have different risk tolerances and the GNU Toolchain
- must meet more stringent expectations to maintain the trust of the
- ecosystem. It is with this context in mind that CTI has been formed.
-
-* Q: What concrete steps will CTI help with?
-
- * A: Some of the major goals include:
-
- * Isolating all services in VMs or containers to increase service
- security and reduce service resource interference.
-
- * Allow volunteers to focus efforts outside of core infrastructure
- maintenance.
-
- * Prepare for additional software supply chain requirements from
-
-* Q: Why are you currently using Linux Foundation IT as the service provider?
-
- * A: The CTI TAC recommendation is to use Linux Foundation IT services
- for core infrastructure. The LF IT team already supports many of
- the same services for the Linux kernel and at scale. The migration
- would involve moving services from Sourceware.org to LF IT servers.
- We continue to be thankful and appreciative of the time spent by
- Sourceware.org volunteers in support of the current services.
-
-* Q: What is the urgency vs what is the timeline?
-
- * A: The GNU Toolchain community should be making consistent forward
- progress to improve our infrastructure and cybersecurity position.
- Showing progress is important for the ecosystem to trust us as a
- secure and critical part of the software supply chain. We should
- not wait until there are Cybersecurity regulations that are beyond
- our ability to comply with as the FOSS ecosystem of tooling and
- infrastructure. Projects of similar scope and importance have been
- deploying significant resources for the use of the development community.
-
-* 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?
-
- * A: The CTI TAC is the point of contact for volunteers. CTI can fund
- multiple activities, by multiple entities, and the way in which the
- volunteers engage may differ between them.
-
-* Q: How does this project relate to the GNU Project or the Free Software
- Foundation (FSF)?
-
- * A: Many of the GNU Toolchain components are a part of the GNU
- Project, and contribute to the development of the GNU system.
- The FSF supports the GNU Project, and in turn supports the GNU
- Toolchain. The GNU Toolchain community works with the FSF via a
- working together fund (https://www.fsf.org/working-together/fund)
- to support the development of the GNU Toolchain directly.
- The Core Toolchain Infrastructure project is distinct from the
- GNU Project and the FSF.
-
-* Q: How does this project relate to the GCC Compile Farm Project
- (https://gcc.gnu.org/wiki/CompileFarm)?
-
- * A: The GCC Compiler Farm is a unique resource for the GNU Toolchain
- and provides interactive systems for developers to manually test on
- a wide variety of hardware and software configurations. This is not
- exactly the same set of requirements that the community might have
- for securing a supply chain, or using modern CI/CD workflows.
-
-* Q: How will the composition of the Core Toolchain infrastructure project
- reflect the communities it supports?
-
- * A: Members of the GNU Toolchain community will always be invited to
- become members of the technical advisory council for the project.
-
-* Q: What is the composition of the project steering committee?
-
- * A: The project steering committee will be composed of sponsoring
- members of the Linux Foundation and members of the GNU Toolchain
- community.
-
-* Q: What does the project TAC do?
-
- * A: The TAC takes input from the GNU Toolchain community and works
- with the members to, implement, and resolve prioritized requirements.
-
-* Q: Is the GNU Toolchain development model going to change?
-
- * A: No. The aim of the project is to provide additional infrastructure
- for the community that is being made available to support the
- GNU Toolchain. All development changes will always be driven by the
- community.
-
-* Q: Is Sourceware (https://sourceware.org/) going to be deprecated?
-
- * A: The GNU Toolchain Infrastructure project is distinct from Sourceware.
- The intent is to move critical infrastructure from Sourceware to the
- Core Toolchain Infrastructure project to provide paid services.
-
-* Q: Who can use the new infrastructure?
-
- * A: That depends on the requirements given by the GNU Toolchain community.
- The requirements from the community are input to the steering committee,
- and so the answer depends largely on exactly what was the intended purpose.
-
-* Q: What can the new infrastructure be used for?
-
- * A: That depends on the requirements given by the GNU Toolchain community.
- The requirements from the community are input to the steering committee,
- and so the answer depends largely on exactly what was the intended purpose.
-
-* Q: Are there any presentations covering CTI?
-
- * Yes, in October 2022 the CTI TAC gave an FSF hosted community Q&A:
- https://media.libreplanet.org/u/libreplanet/m/the-gti-project-a-conversation-and-community-q-a/
+Can we keep deploying services as we have?
+""""""""""""""""""""""""""""""""""""""""""
+No. The GNU Toolchain is a critical foundation of trust for the
+GNU/Linux ecosystem and the demands on its infrastructure, services, and
+security requirements have grown over time. The trend of increasing complexity
+to support its development and associated financial demands will not abate.
+Different projects have different risk tolerances and the GNU Toolchain must
+meet more stringent expectations to maintain the trust of the ecosystem. It is
+with this context in mind that CTI has been formed.
+
+What concrete steps will CTI help with?
+"""""""""""""""""""""""""""""""""""""""
+Some of the major goals include:
+
+* Isolating all services in VMs or containers to increase service security and
+ reduce service resource interference.
+
+* Allow volunteers to focus efforts outside of core infrastructure maintenance.
+
+* Prepare for additional software supply chain requirements from
+
+Why are you currently using Linux Foundation IT as the service provider?
+""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""
+The CTI TAC recommendation is to use Linux Foundation IT services for
+core infrastructure. The LF IT team already supports many of the same services
+for the Linux kernel and at scale. The migration would involve moving services
+from Sourceware.org to LF IT servers. We continue to be thankful and
+appreciative of the time spent by Sourceware.org volunteers in support of the
+current services.
+
+What is the urgency vs what is the timeline?
+""""""""""""""""""""""""""""""""""""""""""""
+The GNU Toolchain community should be making consistent forward progress
+to improve our infrastructure and cybersecurity position. Showing progress is
+important for the ecosystem to trust us as a secure and critical part of the
+software supply chain. We should not wait until there are Cybersecurity
+regulations that are beyond our ability to comply with as the FOSS ecosystem of
+tooling and infrastructure. Projects of similar scope and importance have been
+deploying significant resources for the use of the development community.
+
+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?
+""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""
+The CTI TAC is the point of contact for volunteers. CTI can fund multiple
+activities, by multiple entities, and the way in which the volunteers engage
+may differ between them.
+
+How does this project relate to the GNU Project or the Free Software Foundation (FSF)?
+""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""
+Many of the GNU Toolchain components are a part of the GNU Project, and
+contribute to the development of the GNU system. The FSF supports the GNU
+Project, and in turn supports the GNU Toolchain. The GNU Toolchain community
+works with the FSF via a `working together fund
+<https://www.fsf.org/working-together/fund>`_ to support the development of the
+GNU Toolchain directly. The Core Toolchain Infrastructure project is distinct
+from the GNU Project and the FSF.
+
+How does this project relate to the `GCC Compile Farm Project <https://gcc.gnu.org/wiki/CompileFarm>`_?
+"""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""
+The GCC Compiler Farm is a unique resource for the GNU Toolchain and
+provides interactive systems for developers to manually test on a wide variety
+of hardware and software configurations. This is not exactly the same set of
+requirements that the community might have for securing a supply chain, or
+using modern CI/CD workflows.
+
+How will the composition of the Core Toolchain infrastructure project reflect the communities it supports?
+""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""
+Members of the GNU Toolchain community will always be invited to become members
+of the technical advisory council for the project.
+
+What is the composition of the project steering committee?
+""""""""""""""""""""""""""""""""""""""""""""""""""""""""""
+The project steering committee will be composed of sponsoring members of
+the Linux Foundation and members of the GNU Toolchain community.
+
+What does the project TAC do?
+"""""""""""""""""""""""""""""
+The TAC takes input from the GNU Toolchain community and works with the
+members to, implement, and resolve prioritized requirements.
+
+Is the GNU Toolchain development model going to change?
+"""""""""""""""""""""""""""""""""""""""""""""""""""""""
+No. The aim of the project is to provide additional infrastructure for
+the community that is being made available to support the GNU Toolchain. All
+development changes will always be driven by the community.
+
+Is `Sourceware <https://sourceware.org/>`_ going to be deprecated?
+""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""
+The GNU Toolchain Infrastructure project is distinct from Sourceware.
+The intent is to move critical infrastructure from Sourceware to the Core
+Toolchain Infrastructure project to provide paid services.
+
+Who can use the new infrastructure?
+"""""""""""""""""""""""""""""""""""
+That depends on the requirements given by the GNU Toolchain community.
+The requirements from the community are input to the steering committee, and so
+the answer depends largely on exactly what was the intended purpose.
+
+What can the new infrastructure be used for?
+""""""""""""""""""""""""""""""""""""""""""""
+That depends on the requirements given by the GNU Toolchain community.
+The requirements from the community are input to the steering committee, and so
+the answer depends largely on exactly what was the intended purpose.
+
+Are there any presentations covering CTI?
+"""""""""""""""""""""""""""""""""""""""""
+Yes, in October 2022 the CTI TAC gave an `FSF hosted community Q&A <https://media.libreplanet.org/u/libreplanet/m/the-gti-project-a-conversation-and-community-q-a/>`_.
-----------------
--
2.43.0
next prev parent reply other threads:[~2024-03-07 19:37 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-07 19:30 [PATCH 0/5] Multiple website cleanups Siddhesh Poyarekar
2024-03-07 19:30 ` [PATCH 1/5] projects/glibc: slightly adjust the structure Siddhesh Poyarekar
2024-03-07 20:22 ` Carlos O'Donell
2024-03-07 20:38 ` Siddhesh Poyarekar
2024-03-07 20:45 ` Carlos O'Donell
2024-03-07 19:30 ` [PATCH 2/5] Add a toplevel README Siddhesh Poyarekar
2024-03-07 20:24 ` Carlos O'Donell
2024-03-07 20:25 ` Carlos O'Donell
2024-03-07 21:00 ` Siddhesh Poyarekar
2024-03-07 21:06 ` Carlos O'Donell
2024-03-07 21:54 ` Siddhesh Poyarekar
2024-03-07 19:30 ` [PATCH 3/5] services: Clean up links to projects Siddhesh Poyarekar
2024-03-07 20:25 ` Carlos O'Donell
2024-03-07 19:30 ` [PATCH 4/5] tac/audit: Minor cleanups Siddhesh Poyarekar
2024-03-07 20:26 ` Carlos O'Donell
2024-03-07 19:30 ` Siddhesh Poyarekar [this message]
2024-03-07 20:27 ` [PATCH 5/5] faq: Reformat so that it's not a list Carlos O'Donell
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=20240307193019.4028812-6-siddhesh@gotplt.org \
--to=siddhesh@gotplt.org \
--cc=cti-tac@lists.linuxfoundation.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 NNTP newsgroup(s).