CY24: Migrate glibc to CTI services

In 2024 the goal is to migrate the glibc project to use CTI services.

Current Status

As of 2024-06-28 we have finalized a statement of work with the service provider, Linux Foundation IT, and recorded it here on the CTI TAC mailing list.

Next steps

  • Plan for CTI Board meeting to approve budget spend for SOW.

  • Start transition planning with Linux Foundation IT team.

Notes

  • Revisited discussion with Paul Eggert and attain resolution in March 2024 to move forward. Posted originally here

  • 2024-03-08: CTI website launched on March 8th 2024 to attempt to resolve requests for documentation from Paul Eggert.

  • The GNU Maintainers for the glibc project were asked to make a decision on switching to the services provided by CTI and currently the following support has been tallied:

    • Ryan Arnold - Yay

    • Paul Eggert - Nay

    • Jakub Jelinek - Abstain

    • Maxim Kuvyrkov - Yay

    • Joseph Myers - Yay

    • Carlos O’Donell - Yay

    • Alexandre Oliva - Nay

    • Andreas Schwab - No statement

  • As of 2024-02-28 feedback from the stewards was being incorporated into this document to provide assurances that FOSS would be used to provide services and that there was a checking mechanism in place for services to remain FOSS.

  • Community feedback was collected from July to August 2023.

Service migration

The following is the suggested list of services to be migrated (with notes):

  • Mailing lists

    • Support public-inbox for mailing list archives.

    • Use of public-inbox means archives can be cloned and copied.

    • Use of LF IT Subspace mailing list services (mlmmj, postfix).

  • bug database

    • Consider starting fresh in new Bugzilla 5.0.4+ instance and freeze old product.

    • glibc component in sourceware instance marked “Not open for new bugs.”

    • No easy way to clone this but we can discuss options.

    • Isolate bugzilla from other services.

  • git

    • Migrate to gitolite

    • Community manages access via gitolite keys.

    • Minimize all access to sources and isolate from other processes.

    • Minimal server side web hooks where required.

    • Isolate git service from other services.

    • Stop supporting svn/cvs and provide tarball dumps.

  • wiki

    • Migrate to git-based documentation with existing content copied over.

    • Suggest rst/Sphinx or similar to existing discussions for GCC docs.

    • Sphinx with themes can provide a lot of flexibility for display.

    • Isolate wiki service from other services.

  • patch management

    • Continue patchwork usage and maintenance of isolated instance

    • Required for community driven pre-commit CI

    • LF IT hosting patchwork instance with community hosting bots.

    • Isolate patchwork from other services.

  • Website

    • Provide a simple static site.

    • Isolate web hosting from other services.

  • Meeting

    • Already migrated away from proprietary solutions.

    • Continue to use LF IT BBB instance for glibc meetings including weekly patch review.

    • Isolate BBB from other services.

The current list of glibc services were put together as part of the CTI TAC glibc service enumeration.