openbmc/ipmi-fru-parser: Second notification of unresponsiveness

[Andrew Jeffery]

Hello Ratan and Vernon,

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

This is the second notice of a complaint of unresponsiveness within the past 12 months. The first notice can be found here:

https://lore.kernel.org/openbmc/f086d7a4-7363-4e90-b070-af7ab65a6475@app.fastmail.com/

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 complaints regarding openbmc/ipmi-fru-parser can be found below:

1. https://github.com/openbmc/technical-oversight-forum/issues/27#issuecomment-1632793299
2. https://github.com/openbmc/technical-oversight-forum/issues/27#issuecomment-1632803581

The specific patches identified by the complaints are:

1. 63228: clang-format: copy latest and re-format
   https://gerrit.openbmc.org/c/openbmc/ipmi-fru-parser/+/63228

2. 58446: fru-parser: Remove the use of mktime
   https://gerrit.openbmc.org/c/openbmc/ipmi-fru-parser/+/58446

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

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

On behalf of the Technical Oversight Forum,

Andrew