openbmc/phosphor-ecc: Notification of unresponsiveness
Andrew Jeffery
andrew at aj.id.au
Fri Jun 16 14:50:35 AEST 2023
Hello George and Will,
A complaint has been raised to the Technical Oversight Forum that one or more patches to openbmc/phosphor-ecc 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/phosphor-ecc can be found below:
https://github.com/openbmc/technical-oversight-forum/issues/27#issuecomment-1589985292
The specific patches identified by the complaint are:
1. 63285: clang-format: copy latest and re-format
https://gerrit.openbmc.org/c/openbmc/phosphor-ecc/+/63285
If you are unable to continue with your maintenance role for openbmc/phosphor-ecc 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