openbmc/pfr-manager: Notification of unresponsiveness

Andrew Jeffery andrew at aj.id.au
Fri Jun 16 15:01:06 AEST 2023


Hello AppaRao and Vikram,

A complaint has been raised to the Technical Oversight Forum that one or more patches to openbmc/pfr-manager have not been responded to in a reasonable timeframe.

This is the first notice of a complaint of unresponsiveness.

The project has recently defined some constraints on timeliness for reviews. This helps to set expectations for both contributors and maintainers. Maintainers are expected to find time to provide feedback on patches inside one month of them being pushed to Gerrit. Upon complaint, missing this deadline forms one count of unresponsiveness. If a subproject's maintainers receive three notices of unresponsiveness within a 12 month period then the Technical Oversight Forum will seek to introduce new maintainers to the subproject.

Further details and considerations of this policy can be found at the following location:

https://github.com/openbmc/docs/blob/master/process/subproject-maintainership.md

The complaint regarding openbmc/pfr-manager can be found below:

https://github.com/openbmc/technical-oversight-forum/issues/27#issuecomment-1589985292

The specific patches identified by the complaint are:

1. 63270: clang-format: copy latest and re-format
   https://gerrit.openbmc.org/c/openbmc/pfr-manager/+/63270

If you are unable to continue with your maintenance role for openbmc/pfr-manager then please work with the community identify others who are capable and willing. Please consider the expectations set out in the community membership documentation as part of this effort:

https://github.com/openbmc/docs/blob/master/community-membership.md

On behalf of the Technical Oversight Forum,

Andrew


More information about the openbmc mailing list