#517 Proposals for lessons learned from the recent provenpackager revocation incident
Closed: resolved by jflory7. Opened by till.

I am not sure what's the best place to propose these issues so I start with an issue here.

Here are some ideas about what to improve in our processes to avoid issues like the recent incident:

  • Provide training to elected members that can revoke privileges against the affected persons will such as crucial conversations - https://cruciallearning.com/courses/crucial-conversations-for-dialogue/miniseries/
  • Require that any government body provides specific feedback to people whose privileges they would like to revoke using best principles such as SBI (https://engagedly.com/blog/importance-of-sbi-when-giving-feedback-in-workplace/)
  • Require that the person whose privileges are revoked against their will have the opportunity to defend themselves when the government body discusses to revoke their privileges. Also allow someone to assist the person with their defense given that otherwise there is a huge majority in the government body compared to a single person having to defend themselves.
  • Consider to have these kind of discussions be done in public given that this is also best practice for regular trials (see https://www.ohchr.org/en/instruments-mechanisms/instruments/international-covenant-civil-and-political-rights#article-14 ) and to some degree the discussions about revoking a persons privileges are comparable to a trial.

For reference I have already filed a number of council tickets for things surrounding this but I filed them as private for the council to decide how/when to open them (unfortunately pagure doesn't have a comment only for contributors, RO for all mode, I have actually filed RFEs for the new forge for these sort of features).

Hi @till , thank you for the helpful suggestion! I particularly like the idea of being able to offer crucial conversations and giving feedback supports. Im not sure we can enforce that people take these courses, as I dont know does the project have the budget to facilitate this, but I think we can certainly encourage people who are elected (and hired in) to FESCo, Council and Mindshare to consider taking some time to take these types of courses if they are available to them through Red Hat or even LinkedIn or the ones you suggest.

The council has been reviewing this incident since December, and discussing it at length in our private channel. We believe we have received all of the information we can to understand the events and we intend to meet during the week beginning January 20th to finalise our intentions on how to close out this issue with outcomes that are fair, clear, and will allow the project to move forward in a more positive and stronger way by introducing new guidelines, and recommending changes to some of our current ones.

For any changes we propose, we will be using the Policy Change Policy which allows for our communities feedback before anything might be changed.

Ill keep this ticket open as its a great way to provide updates transparently on what the council is doing, and thanks again for your helpful suggestions! :)

Metadata Update from @amoloney:
- Issue assigned to dcantrell

Per @mattdm's devel-announce post, subject Fedora Council statement on Proven Packager situation, the Fedora Council considers this matter resolved. Please open a new ticket if there are further follow-ups or specific policy proposals.

Metadata Update from @jflory7:
- Issue close_status updated to: resolved
- Issue status updated to: Closed (was: Open)

Metadata