Proposing this work as a [https://docs.fedoraproject.org/en-US/project/initiatives/ 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 [https://fedoraproject.org/wiki/Objectives/Git_Forge_Initiative_2025 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.
After discussing with @ryanlerch and @humaton we have decided to split this initiative into two phases. Phase one will address Project Hosting. Phase two will address src.fedoraproject.org (dist-git). We will update this proposal to outline plans for phase 1, which we estimate will take 6 months and will include deploying our own instance of Forgejo for project hosting and a plan for project migrations. This is points 1 - 2 of the current proposal, but with more detail.
Phase two will describe points 3 - 5 when there has been time to discuss and create a solution.
I will close this ticket and reopen when the proposal page has been re-edited to describe plans for phase one - project hosting & migration.
Metadata Update from @amoloney: - Issue close_status updated to: no action needed - Issue status updated to: Closed (was: Open)
Metadata Update from @amoloney: - Issue status updated to: Open (was: Closed)
Reopening this issue as there is a more detailed plan available for review by the council from the project team https://codeberg.org/fedora/forgejo-deployment/wiki/Home#phase-one-general-forge
Feedback on the proposed dates and scope of work would be appreciated before resubmitting it as an official request to be supported as a community initiative.
Metadata Update from @amoloney: - Issue untagged with: ticket-vote - Issue tagged with: Next Meeting
Discussion here, btw: https://discussion.fedoraproject.org/t/fedora-council-tickets-ticket-525-community-initiative-proposal-git-forge-initiative-2025/146099
+1
Metadata Update from @mattdm: - Issue close_status updated to: approved - Issue status updated to: Closed (was: Open)
Reopening this issue to test a mirroring function for tracking purposes in the CLE jira tracker to help with status reporting and syncing of work.
Closing this initiative as approved again since some months have passed here. If there needs to be an "open" issue somewhere upstream outside of the Red Hat JIRA, this probably needs to be an issue opened on the repo where the git forge work is being planned.
approved
For example, see this git tracking repo for tasks related to the Fedora Docs Initiative. The Red Hat JIRA downstream tracking issues could link into issues tracked over there instead of this repository.
Metadata Update from @jflory7: - Issue close_status updated to: approved - Issue status updated to: Closed (was: Open)
Metadata Update from @jflory7: - Issue untagged with: Next Meeting - Issue assigned to amoloney
Log in to comment on this ticket.