I did a quick pass through these tickets and left a comment ahead of the meeting. It seems like #558 Fedora Forge Usage Policy is the heaviest lift and may require some pre-reading to make the most of our meeting time.
Not sure if #568 Budget Repo Migration needs discussion or just action. I explained on the ticket too, but I would be content to let the private issues in that repo be purged and deleted, not carried forward into perpetuity. There is some very sensitive data in that repo, none of which is actually important or relevant for day-to-day functioning of Fedora. I think we should just go ahead and run the Forgejo migration tool on the public data and call it a day. (I could take this action since I guess this repo is mostly associated with my role specifically.)
As always, thank you to bot Aurélien and human Aurélien for the summary of the meeting
Announcements: An official announcement regarding Shaun McCance and Justin Flory and the FCA Position is now live.
Ticket Discussions and Outcomes
Fedora Forge Usage Policy (#558): The council discussed the policy for archiving inactive repositories. They agreed to revise the clause to state that organization owners are responsible for archiving their dormant repos. The Infrastructure team reserves the right to archive repos in inactive organizations after attempting to contact the owners, removing the previously proposed automatic 6-month timeframe.
#410 (Abolish FPCA): Closed as deferred/wont-fix, as the council lacks the capacity to perform the necessary due diligence for such a significant change.
#460 (Re-licence fedora-logos): Closed as wont-fix, adhering to advice from Red Hat legal that re-licensing is not possible.
Fedora Budget Repo Migration (#568): In light of the upcoming Pagure shutdown, the council agreed to migrate the Fedora Budget repository to the Council’s space on Fedora Forge. All private issues containing personal and financial data will be permanently deleted and not migrated due to privacy concerns.
Conflict of Interest Policy: Discussion on this policy is deferred to the next meeting to allow members more time to review feedback.
FESCo Council Representative: Council members were asked to provide feedback on a FESCo ticket (#3613) aimed at updating the documentation for the FESCo council representative’s responsibilities.
Action Items
@amoloney: Edit the Fedora Forge usage policy with the agreed-upon changes and start the two-week community feedback process on Thursday, July 30, 2026.
@amoloney: Redraft the Conflict of Interest policy guidelines, incorporating feedback, and post the new draft to the discussion forum before the next council meeting on August 12, 2026.
All Council Members: Review and provide feedback on FESCo ticket #3613 regarding the FESCo representative’s responsibilities.
