#513 Conflict of Interest guidelines
Opened 7 months ago by pbrobinson. Modified 2 days ago

I have searched documentation and used an internet search but didn't find anything.

Fedora should have a documented general purpose set of guidelines on conflict of interest.

These should be structured to guide committees, SIGs, working groups or even the council on what would construe a conflict of interest such where a ticket is opened by a member of a committee and there may be a conflicting interest, such as the change or proposal is theirs, and how the individual and the rest of the committee should act in relation to this (such as removing themselves from the discussion/ticket etc) so as to not bias and influence the results in favour of the individual/their proposal or against other competing individuals/proposals.

There should also likely be a process for reporting conflicts of interest.


Huge +1. I am in full support of creating this type of document. In a recent meeting with the FPL and FCA, we discussed this topic. AIUI, the Code of Conduct committee may not have the resources to drive this work, so I suggest the Council take ownership of crafting these guidelines and submitting them to the Code of Conduct Committee to review and ratify.

I will take this ticket to ensure this is being worked on, and will suggest the council action this as work to do during our upcoming f2f meeting in February and have a draft completed and ready for review from this meeting.

Metadata Update from @amoloney:
- Issue assigned to amoloney
- Issue tagged with: code-of-conduct, policies

6 months ago

I would like to propose making this ticket public, in order to more transparently track the development work on this ticket.

Fine by me, I mostly opened tickets as non-public to let the council handle how they wanted particular tickets to be

@pbrobinson Thanks for following up and ACKing. I will now make this ticket public, and add a new comment after making it public to create an email notification for repository watchers.

Metadata Update from @jflory7:
- Issue private status set to: False (was: True)

a month ago

This ticket is now public.

Following the council meeting today, @jspaleta will draft <something> that the council and community can provide feedback and iterate on via discussion.fedoraproject.org.

See minutes here https://meetbot.fedoraproject.org/meeting_matrix_fedoraproject-org/2025-06-18/fedora-council-meeting.2025-06-18-14.02.txt

Metadata Update from @amoloney:
- Issue assigned to jspaleta (was: amoloney)

a month ago

During the Fedora Council meeting on July 2, 2025, @jspaleta confirmed he is drafting the Conflict of Interest policy. He expects to share the first version with the Council for asynchronous review ahead of the next meeting on July 16.

Action Items

  • @jspaleta will share a first draft of the Conflict of Interest policy for Council review no later than July 16, 2025, to discuss at the next Council meeting.

Metadata Update from @jflory7:
- Issue marked as depending on: #538
- Issue tagged with: Next Meeting

15 days ago

I've got a draft google doc that can probably use some review.
Council members should have commenter/suggestion access.
https://docs.google.com/document/d/1QWLPur0G590GjhZXuYyZy2GYYaegM3VicbuaxX-pQ2s/edit?usp=sharing

This was discussed briefly at todays meeting. @jspaleta is working on a second draft for council review and will try to target the next council meeting on July 30 for feedback.

Metadata Update from @amoloney:
- Issue untagged with: Next Meeting
- Issue tagged with: In Progress

2 days ago

Log in to comment on this ticket.