Here’s the agenda for the Council meeting 2026-07-15T14:00:00Z→2026-07-15T15:00:00Z:
As per our meeting planner board, we will aim to make progress on the tickets in the ‘discussion’ column in this weeks meeting.
All are welcome to join us in #fedora-meeting.
More information about the council meeting and rolling agenda can be found on the council meetings wiki page.
Todays meeting has concluded. Below are the links to the meetbot logs and minutes, and a bot-aurelien summary.
Tickets are being updated in our meeting tracker where applicable Making sure you're not a bot!
== Bot Aurelien Summary ==
=== Key Discussion Points ===
=== Conflict of Interest Guidelines - #513 ===
There is a private draft document for these guidelines.
A discussion was held on whether a formal policy is necessary and what its scope should be.
Some members felt the definition of a “conflict of interest” is tricky to formalize, as normal project work (like voting on a policy) could negatively impact others but is not a conflict of interest.
The initial reason for the document being private might be due to legal consultations, but there’s a consensus to make it public for community feedback.
=== Fedora Forge Usage Policy - #558 ===
The main point of contention is the proposed policy to automatically archive inactive repositories.
Arguments for archiving: It helps new contributors identify inactive projects, reduces clutter, and removes potential targets for spam. It provides a mechanism for dealing with orphaned projects.
Arguments against a fixed-time archiving policy: Some projects/repositories are intentionally inactive for long periods without being abandoned. Defining “inactivity” is difficult and could create unnecessary work. It may cause SIGs to move their code elsewhere to avoid dealing with the policy.
Proposed compromises:
Make archiving a “best practice” for owners to do themselves.
Allow Infra to archive repos after a long period (e.g., 12 months) only after trying to contact the owners.
Archive entire inactive SIG organizations rather than individual repositories.
Ensure that un-archiving is a simple, self-service action for repository owners.
It was noted that the policy should cover edge cases like Fedora Remixes.
== Action Items ==
=== Conflict of Interest Guidelines - #513 ===
* The Council will publish the current draft of the Conflict of Interest Guidelines on Discourse for a two-week public feedback period.
* The Council will discuss the guidelines and the community feedback at the next meeting.
=== Fedora Forge Usage Policy #558 ===
* The Fedora Council has formally taken ownership of finalizing and publishing the Fedora Forge Usage Policy.
* The discussion on archiving inactive repositories will continue asynchronously to reach a resolution before the policy is published.
Our next meeting is scheduled for Wednesday, 29 July 2026 in #fedora-meeting on Martrix @ 1400 UTC, and some discussion happens in #fedora-council room around our formal meeting time. All are welcome to join both the meeting and the general council channel.
Kindest regards,
Aoife