On Thu, 22 May 2025 at 19:20, Roy Bekken <roy.bek...@gmail.com> wrote: > > FESCO stated they was assembling the facts back in december but wanted to > discuss it with the revoked person first.
I had a conversation with a member of FESCo and the FPL about the situation some time ago. > I’ve have not seen anymore on that since then so I assume they are still > working on it > > > > On Thu, 22 May 2025 at 19:08, Yaakov Selkowitz <yselk...@redhat.com> wrote: >> >> On 5/22/25 11:15, Matthew Miller wrote: >> > The Fedora Council overturns FESCo's decision [3284] to remove Proven >> > Packager rights from a contributor. >> > >> > FESCo didn't have a specific policy for dealing with a request to remove >> > Proven Packager rights. In addition, the FESCo process was handled entirely >> > in private. The contributor didn't receive a formal notification or warning >> > from FESCo, and felt blindsided by the official decision when and how it >> > was >> > announced. The Fedora Council would like to extend our sincerest apology on >> > behalf of the Fedora Project to them. >> > >> > The lack of a defined process for situations like this needs to be >> > addressed >> > before such a decision can be made, including provisions for appropriate >> > warnings and chances to respond by the contributor. In addition, the >> > announcement of a decision should not publicly identify the person. >> > >> > Fedora Council is also asking FESCo to review and improve our packaging >> > guidelines and governance policies. For example, the guidelines for >> > architecture teams[1] and the proven-packager guidelines[2] do not align >> > (even though both are written and current policies) and must be reconciled. >> > >> > The Council and the Code of Conduct Committee will be happy to review and >> > collaborate with FESCo on these topics should they wish. >> > >> > -- Matthew, on behalf of the whole Fedora Council >> >> Is the *middle* of an election cycle -- when some have already voted -- >> really the time for this? Couldn't this have been done beforehand? Is >> FESCo planning on responding to this also during the elections? >> >> -- >> Yaakov Selkowitz >> Principal Software Engineer, Emerging RHEL >> Red Hat, Inc. >> >> -- >> _______________________________________________ >> devel mailing list -- devel@lists.fedoraproject.org >> To unsubscribe send an email to devel-le...@lists.fedoraproject.org >> 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/devel@lists.fedoraproject.org >> Do not reply to spam, report it: >> https://pagure.io/fedora-infrastructure/new_issue > > -- > _______________________________________________ > devel mailing list -- devel@lists.fedoraproject.org > To unsubscribe send an email to devel-le...@lists.fedoraproject.org > 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/devel@lists.fedoraproject.org > Do not reply to spam, report it: > https://pagure.io/fedora-infrastructure/new_issue -- _______________________________________________ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org 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/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue