Meeting Minutes - Office Hours for CTI - 2026-09-04

Meeting Minutes - Office Hours for CTI - 2026-09-04

[Carlos O'Donell via Gdb]

CTI: https://cti.coretoolchain.dev/

The CTI project holds Office Hours every Friday, these are the minutes for this Friday's meeting.

The CTI project in collaboration with glibc is working on: https://cti.coretoolchain.dev/projects/glibc.html

Posting across the project mailing lists since some developers had questions and are only subscribed on some lists.

​Agenda:
  - Discussed critical services transition plan.
  - https://sourceware.org/glibc/wiki/service-transition-plan
  - Discussed options for VCS to email.
https://git.kernel.org/pub/scm/linux/kernel/git/mricon/korg-helpers.git/tree/git-mailbomb-cron.py
  - Discussed options for VCS to bugzilla. https://git.kernel.org/pub/scm/utils/bugspray/bugspray.git
  - Reviewed any situations that From rewriting occurs.
  - Konstantin: No from rewriting occurs.
  - Carlos: OK, so we don't need any commit protection mechanisms to avoid the rewritten from entering the commit author.
   - Reviewed email forwarding. Requires Sourceware.org forwarding becomes subspace.kernel.org. One address is canonical and one is accepted. The problem then if Sourceware turns this off.
   - No need to discuss ARC/SRS, just postfix.
   - In practice this kind of email forwarding goes on permanently.
  - CTI TAC, and glibc have to resolve mailing list names etc.
  - Discussed domain names and project sources. Fewer domain names reduces reliance on certificates and subsequent breakage.
   - Carlos: Preference for "git.coretoolchain.dev/[project name]"?
   - Konstantin: We are able to work with different URLs for different projects, but it is simpler with a single url.
   - Discussed transitioning git and the need for cgit?
   - Konstantin: You get this by default when setting up git (cgit, gitolite).
  - Noted https://git.kernel.org/pub/scm/utils/b4/b4.git/bugs/ as the mechanism for storing bugs that could be a replacement for bugzilla. Talk at LPC "b4 review" and "b4 bugs"
  - Discussed if we need distinct DNS entries to have the redundancy that we would want?
  - No. Distinct DNS is not required to support high availability proxy. However, for git pushes and git pulls we do have distinct URLs that would deliver different services.
   - TODO: Decide on push url.
  - Resolved remaining TODO items in the transition plan.
  - Discussed with LF IT looking at the plan.
  - Noted that with distinct URL names we can have better isolation and facilitate internal or external moves. If each (project, service) pair uses a different DNS name, future moves (within or outside of CTI) can be much more transparent rather than requiring a system under the shared name to handle redirecting things to the system implementing a given (project, service) pair.

-- 
Cheers,
Carlos.

Re: Meeting Minutes - Office Hours for CTI - 2026-09-04

[Andrew Pinski via Gdb]

On Fri, Sep 4, 2026 at 2:37 PM Carlos O'Donell <carlos@redhat.com> wrote:
>
> CTI: https://cti.coretoolchain.dev/
>
> The CTI project holds Office Hours every Friday, these are the minutes for this Friday's meeting.
>
> The CTI project in collaboration with glibc is working on: https://cti.coretoolchain.dev/projects/glibc.html
>
> Posting across the project mailing lists since some developers had questions and are only subscribed on some lists.
>
> Agenda:
>   - Discussed critical services transition plan.
>   - https://sourceware.org/glibc/wiki/service-transition-plan
>   - Discussed options for VCS to email.
> https://git.kernel.org/pub/scm/linux/kernel/git/mricon/korg-helpers.git/tree/git-mailbomb-cron.py
>   - Discussed options for VCS to bugzilla. https://git.kernel.org/pub/scm/utils/bugspray/bugspray.git
>   - Reviewed any situations that From rewriting occurs.
>   - Konstantin: No from rewriting occurs.
>   - Carlos: OK, so we don't need any commit protection mechanisms to avoid the rewritten from entering the commit author.
>    - Reviewed email forwarding. Requires Sourceware.org forwarding becomes subspace.kernel.org. One address is canonical and one is accepted. The problem then if Sourceware turns this off.
>    - No need to discuss ARC/SRS, just postfix.
>    - In practice this kind of email forwarding goes on permanently.
>   - CTI TAC, and glibc have to resolve mailing list names etc.
>   - Discussed domain names and project sources. Fewer domain names reduces reliance on certificates and subsequent breakage.
>    - Carlos: Preference for "git.coretoolchain.dev/[project name]"?
>    - Konstantin: We are able to work with different URLs for different projects, but it is simpler with a single url.
>    - Discussed transitioning git and the need for cgit?
>    - Konstantin: You get this by default when setting up git (cgit, gitolite).
>   - Noted https://git.kernel.org/pub/scm/utils/b4/b4.git/bugs/ as the mechanism for storing bugs that could be a replacement for bugzilla. Talk at LPC "b4 review" and "b4 bugs"

This is NOT a replacement for bugzilla. This is a step backwards.

>   - Discussed if we need distinct DNS entries to have the redundancy that we would want?
>   - No. Distinct DNS is not required to support high availability proxy. However, for git pushes and git pulls we do have distinct URLs that would deliver different services.
>    - TODO: Decide on push url.
>   - Resolved remaining TODO items in the transition plan.
>   - Discussed with LF IT looking at the plan.
>   - Noted that with distinct URL names we can have better isolation and facilitate internal or external moves. If each (project, service) pair uses a different DNS name, future moves (within or outside of CTI) can be much more transparent rather than requiring a system under the shared name to handle redirecting things to the system implementing a given (project, service) pair.
>
> --
> Cheers,
> Carlos.
>

Re: Meeting Minutes - Office Hours for CTI - 2026-09-04

[Zack Weinberg via Gdb]

On Fri, Sep 4, 2026, at 5:36 PM, Carlos O'Donell wrote:
> CTI: https://cti.coretoolchain.dev/
>
> The CTI project holds Office Hours every Friday, these are the minutes
> for this Friday's meeting.

Once again I must ask that you stop holding synchronous meetings. Your
insistence on making decisions in synchronous meetings is a major
contributing factor to why CTI's proposed infrastructure changes have
been and are continuing to be so very contentious.

It may be helpful to spin up a new dedicated mailing list, instead, but
as long as major, disruptive, hotly contended transitions are on the
table, all of the potentially affected projects' main mailing lists need
to be cc:ed on *every message*.

For closely related reasons, please post the *full text* of all the
documents you linked from your minutes *directly to the mailing lists*,
so that there is a permanent record of what those documents said at the
time you linked to them.

zw