Below is today’s meeting summary, provided by bot Aurelien, and links to the logs and minutes, provided by meetbot. This email is not provided by any bot, just a mere human.
-
Fedora Forge Usage Policy (#558)
- The policy is in its second week of the community feedback period. A revised version has been posted.
- The main point of discussion was the handling of Personally Identifiable Information (PII).
- There was debate on whether the policy should go into detail about PII, or if it’s already covered by the Fedora Code of Conduct (CoC).
- It was noted that the CoC covers publishing private information, but having a note in the Forge policy could serve as a first-line reminder before an issue needs to be escalated to the CoC committee.
- The council agreed to create a third version of the policy. This version will move the mention of PII from the “Prohibited Articles” section to the “Code of Conduct” section with simplified wording, and incorporate other feedback received. The community will have another week to provide feedback on this new version.
-
Conflict of Interest Guidelines (#513)
- The initial discussion focused on adding a simple sentence to governance documents to prevent individuals “directly involved” in a conduct issue from making decisions about it.
- The ambiguity of “directly involved” and the distinction between public (e.g., non-responsive maintainer) and private decisions proved difficult to resolve.
- The conversation shifted towards establishing a process for oversight rather than defining a strict rule.
- A new proposal was formulated to have governance groups request oversight or mediation from the FPL/FCA/FOA in private decisions where a conflict of interest might exist.
- The council agreed on specific wording for this proposal, changing “may” to “should” to make the recommendation stronger. This new text will be posted for community feedback as a replacement for creating a larger, more complex policy.
Action Items
-
@amoloney: Continue managing feedback for the Fedora Forge Usage Policy, create a version 3 incorporating the discussed PII changes, and post it for another week of community review.
-
@amoloney: Post the agreed-upon statement regarding conflict of interest and oversight to the relevant discussion thread for community feedback.