Fedora-Council/tickets ticket #525: Community Initiative Proposal: Git Forge Initiative 2025

[t2dbot (Tickets to Discussion Bridge)]

@amoloney filed Fedora-Council/tickets ticket #525. Discuss here and record votes and decisions in the ticket.

Ticket text:

@@amoloney

Proposing this work as a [What are Community Initiatives? :: Fedora Docs community initiative] on behalf of the people already engaging in the work and requesting a formal council vote to officially recognise this as one.

Full proposal can be found on the [Objectives/Git Forge Initiative 2025 - Fedora Project Wiki wiki page]. The lead for this initiative is @ryanlerch and I have been unofficially/officially been assigned as council executive sponsor, so lets formalise this please.

[mattdm (Matthew Miller)]

The updated plan looks great to me. I have one minor quibble — I think shutting down new projects should come after the sunset announcement, not before. Unless it already happened on Monday and no one noticed.

[bookwar (Aleksandra Fedorova)]

I think I am missing a CI story.

Afaik currently, we have Pagure CI and Zuul CI enabled for the pagure.io.

Is offering some sort of CI within the scope of the phase one before we sunset pagure.io?

[kevin (Kevin Fenzi)]

Woah, so that plan has:

“June 30, 2025 or after all relevant projects migrated: Pagure.io Read-Only”

Thats… really really not much time.

Upstream projects move slowly. Many are not even aware of this.
Do we really think we can get everyone to move in ~3months?

June 30th 2026 perhaps?

Also, the Datacenter move has moved to june…