Re: Council Bi-Weekly Meeting Agenda: 2026-07-15

Todays meeting has concluded. Below are the links to the meetbot logs and
minutes, and a bot-aurelien summary.

Text minutes -
https://meetbot.fedoraproject.org/meeting_matrix_fedoraproject-org/2026-07-15/fedora-council-bi-weekly-meeting.2026-07-15-14.01.txt
HTML minutes -
https://meetbot.fedoraproject.org/meeting_matrix_fedoraproject-org/2026-07-15/fedora-council-bi-weekly-meeting.2026-07-15-14.01.html

Text Log -
https://meetbot.fedoraproject.org/meeting_matrix_fedoraproject-org/2026-07-15/fedora-council-bi-weekly-meeting.2026-07-15-14.01.log.txt
HTML log -
https://meetbot.fedoraproject.org/meeting_matrix_fedoraproject-org/2026-07-15/fedora-council-bi-weekly-meeting.2026-07-15-14.01.log.html

Tickets are being updated in our meeting tracker where applicable
https://forge.fedoraproject.org/council/-/projects/2

== 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



On Mon, Jul 13, 2026 at 4:14 PM Aoife Moloney <[email protected]> wrote:

> Hi all,
>
>
> Please see below the discussion agenda for the upcoming council meeting.
>
> == Agenda ==
> * Reminders and Announcements
> * Ticket Discussions:
> ** #558 - Fedora Forge Useage Policy
> https://forge.fedoraproject.org/council/tickets/issues/558
> ** #513 - Conflict of Interest Guidelines
> https://forge.fedoraproject.org/council/tickets/issues/513
> ** #410 - Abolish Fedora Contributor Agreement
> https://forge.fedoraproject.org/council/tickets/issues/410
> * Next Meeting Topics
> *Open Floor
>
>
> Minutes, summary and outcomes (if any) will be posted to
> discussions.fedoraprojet.org and
> here as an email reply.
>
> All welcome to join us at 1400 UTC +1 (or whatever time 3pm in Ireland
> is in your location, because I am very bad at timezone conversions) in
> #meeting:fedoraproject.org.
>
>
> This agenda is also posted at
>
> https://discussion.fedoraproject.org/t/council-meeting-agenda-2026-07-15/196610
>
>
>
> Kind regards,
> Aoife
>
> --
> Aoife Moloney
>
> Fedora Operations Architect
>
> Fedora Project
>
> Matrix: @amoloney:fedora.im
>
> IRC: amoloney
>


-- 

Aoife Moloney

Fedora Operations Architect

Fedora Project

Matrix: @amoloney:fedora.im

IRC: amoloney

-- 
_______________________________________________
devel mailing list -- [email protected]
To unsubscribe send an email to [email protected]
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/[email protected]
Do not reply to spam, report it: https://forge.fedoraproject.org/infra/tickets/issues/new