I've created a topic on Fedora Discussion for this ticket.

Please keep this ticket focused. Discuss there, and record votes and decisions here. Thanks!

At Flock this was a general topic of conversation, and as someone who is overseeing this work on behalf of the council, I was able to meet with Tomas Hckra who is leading this investigation and work on a proposed timeline. We are aiming to adhere to these dates:

• End of October ’24 – the report comparing the two git forges against the list of user stories/requirements is finished and submitted to Fedora Council for review.
• Around the same time – the report is also made public
• Mid – End of November ’24 – A decision is made on what git forge the project will migrate to
• December ’24 – A migration plan for the project is created and shared publicly
• January ’25 – A Giant Change Proposal, likely spanning many releases, is created and proposed.
• Sometime a little later (probably Feb/Mar ’25) – The change proposal is iterated on based on feedback if appropriate, and the Change is broken down into smaller changes targeting specific Fedora releases so the migration can be rolled out slowly and with care

This is to serve as a high level guide, and a more granular timeline or schedule can be created. Does this meet the councils approval?

Seems basically good to me.

If ARC can get their report done faster, that'd be even better, but it's not that far off at this point and it's important to get good community feedback.

Once it gets to us, I think we should aim for a decision within a week or at most two. Let's not keep people hanging any longer, and give more time for the migration planning.

I think "Community Initiative" is the right container to hold multiple Changes over the course of several releases. (Oh god, please not "many".)

After a week I will consider this initial timeline agreed to by the council and work with CPE and Fedora QA to confirm that this meets their expectation too. Given we are in F41 release time, we can and should allow for some flexibility on this proposal to release well and on time and I suggest we create a formal schedule for the Git Forge work to follow once milestone dates are confirmed. I can action this.

I also agree that the overall migration does fit as an initiative, and will request that it takes this form when we are rolling this out early next year.