Meeting Minutes - Office Hours for CTI - 2026-06-05

[Carlos O'Donell]

On 6/5/26 4:12 PM, Andrew Pinski wrote:
> On Fri, Jun 5, 2026 at 12:04 PM Andrew Pinski <pinskia@gmail.com> wrote:
>>
>> On Fri, Jun 5, 2026 at 8:42 AM Carlos O'Donell <carlos@redhat.com> wrote:
>>>
>>> Agenda:
>>>    * Discussed where to put the glibc services transition plan.
>>>    * Discussed adding it to the glibc wiki.
>>>    * Started document here: https://sourceware.org/glibc/wiki/service-transition-plan
>>>    * Next steps are to get the community involved in the discussions.
>>
>> I am not sure August 20th is duable.
>> Where is the plans for bugzilla integration with git? And changing the
>> git hooks? I have NOT seen any plan on the git hooks yet.
>> Where is the plans for linking to the old mail archives? Are there
>> plans on hosting the full mail archives on CTI services? I have not
>> seen any mention of either of these issues anywhere.
>> Why is the forge not an option? Just because CTI says so or is it
>> because the glibc community didn't know that was an option?
>> The transition plan is weak and has too many TBDs to even think about
>> August 20th as a cut over date.
>> What is the rush here; is it because the money needs to be spent? Can
>> we do this correctly and that includes doing a forge for glibc? Why
>> not put some of that money towards improving a forge? Instead of
>> hosting?
>>
>> What features does CTI services provides that is not already handled
>> by sourceware? Why can't money go towards improving sourceware? Or
>> even stuff like the forge. Why spend extra money on an extra host?
> 
> A couple more open questions about the migration which is seems not to
> be thought of.
> What happens to the old email addresses? does it become a forwarded
> one to the new one?

The current plan has the existing mailing list become archived and
stop accepting emails.

I think providing information in the bounce would be useful.

If we do want to forward, then from-rewriting would let us see
which emails were sent to the old list and get those systems
adjusted vs. ARC/SRS.

> Do you keep the same registration or do you need to re-register for
> the new glibc email list?

You do not need to re-register, the plan is to export the subscriber
list and migrate to the new services.

We will avoid double sending email, and send out instructions if
people want to unregister, or register a different email.

> What about git repro(s) on sourceware, do they become mirrors or just
> stop updating?

We recommend they become read-only mirrors so we can smoothly transition
buildbots and other pre-commit CI services without needing a flag day.

> What about the buildbots? Are they are going to be stopped using
> sourceware and used CTI services instead?
That's up to the buildbot owners?

The buildbots could, with the read-only mirrors, keep doing their thing.

I can work with the buildbot owners to update.

-- 
Cheers,
Carlos.