Re: [RFC] Detailing a service transition plan for glibc to CTI for August 2026.

On Sun, 2 Aug 2026, Mark Wielaard wrote:

>  We have reviewed the proposed migration plans, and have found no
> technical need for overseer consent or assistance.  As we have said
> before, FOSS projects are welcome to come, stay, and leave sourceware.
> Proposers of this idea already have all the data/access required.

The basic requirement at an administrative level is: at an agreed time 
time, switch the existing mailing list addresses to forward to the new 
list addresses, and block all future commits to the git repository (either 
making it into a mirror or simply leaving it readonly), preferably also 
redirecting https accesses to the new location (I don't think git:// 
supports such redirection).

Blocking commits can be done by a user account in the right group with 
shell access, by setting up appropriate hooks.  Redirecting list addresses 
and setting up https:// redirections for the git repository may require 
other access.  Making git into a mirror would require some mirroring cron 
job (and might complicate the hooks to allow mirror updates while 
disallowing ref updates from other sources).

-- 
Joseph S. Myers
[email protected]