GNU Toolchain Infrastructure at gcc cauldron
- 1. GNU Toolchain Infrastructure and the GTI Project. GNU Tools Cauldron 2022 Carlos O’Donell, David Edelsohn
- 2. Services today - Covered by Mark and Frank’s part of the BoF - Many well served services.
- 3. Services in the future - If everything is fine with our current services what is there to talk about?
- 4. Challenges for the infrastructure - Fiscal support for the infrastructure - New hardware / New services. - Cybersecurity requirements - Server security audits / Beyond just signing tarballs. - Forthcoming Software Supply Chain requirements. - Continuity planning - Who maintains the services when we’re gone?
- 5. Existing and new sponsors - The FSF is the current fiscal sponsor for the GNU Project. - GNU Toolchain Working Together Fund (current sponsor for Cauldron Travel Grants) - Red Hat is the current fiscal sponsor of Sourceware. - Proposed SFC project membership for Sourceware. - OpenSSF and major sponsors have pledged an estimated $400K annually for expanded and hardened infrastructure services for the GNU Toolchain - Open, transparent, public infrastructure Technical Advisory Council - Infrastructure guided by the GNU Toolchain projects community to serve the GNU Toolchain projects - Originally started as the Core Infrastructure Initiative which supported many FOSS projects including Debian, OpenSSH, and OpenSSL.
- 6. How can our sponsors support us? - Write public proposal - Discuss public proposal - Find funding for the proposal Example: - We want to fund Travel Grants for the GNU Tools Cauldron. - GNU Toolchain Working together fund trustees agreed. - GNU Tools Cauldron committee added Travel grants to the conference.
- 7. What other proposals do we have? - Move core services to managed infrastructure.
- 8. Proposal: Managed services with the Linux Foundation IT - Leverage existing services being provided to the Linux Kernel community - Large IT team with extensive experience maintaining Linux kernel and Yocto services - Linux Kernel IT has similar workflow, processes and requirements - Don’t reinvent the wheel or build duplicate infrastructure where there is no additional value - Continue using our distributed development model - Only FOSS tools: mailing lists, git, issue tracking, etc. - Existing Sourceware, including inactive projects, archived online for historical preservation.