Meeting Minutes - Office Hours for CTI - 2026-05-29
Carlos O'Donell
carlos@redhat.com
Fri Jun 5 17:55:36 GMT 2026
On 5/29/26 8:55 PM, Andrew Pinski wrote:
> On Fri, May 29, 2026 at 12:10 PM Carlos O'Donell <carlos@redhat.com> wrote:
>> * Carlos: We just finalized an updated SOW with LF IT that is the same as the previous 2024 SOW, and next steps are to start public discussions about service transitions and dates.
>
> The SOW in 2024 didn't have enough about the transition and who was
> going to do the work and acceptance criteria of the move. So Why reuse
> it? I made a mention about this before. But it seems like nothing has
> changed here.
Andrew,
The SOW is intended to provide the high level structure to the contract
and what is being provided, by whom, and how much it costs.
That hasn't changed, so the SOW hasn't changed.
There are provisions in the cost structure for the initial bootstrapping
and onboarding to support the transition and update of services.
Do you have a reference to what you previously requested?
May you please restate here what you were looking for and I can see if
the CTI TAC can answer those questions?
I think the upcoming breakdown we'll be working on with glibc, CTI TAC,
and LF IT, may be what you're looking to review?
> I sitll think glibc should start thinking about using the forge before
> any other dicussion going forward with respect to hosting.
I disagree that we should start with that.
I do agree that we should be talking about using a Forge for development.
I'm happy for the glibc developers to start working on the Sourceware Forge
to experiment and develop work flows that everyone can use.
I expect that experimentation to take time.
--
Cheers,
Carlos.
More information about the Libc-alpha
mailing list