Proposal on metrics for outstanding GitHub PRs and issues

[Ing. Martin Koci, MBA]

Hello,

apologize for email format (copy&paste). Anyway, here are details:

**<https://inet.openssl.org/issue/PET-285#number-of-outstanding-github-prs-and-issues-%23>

To track the number of actual opened PRs from GitHub and expose it 
publicly. Tracked on daily basis. Concrete requirements/metrics below:

  * How many PRs in total
  * How many Issues in total (features, questions, bugs, regressions, ...)
  * How many of PRs are waiting for review
  * How many of PRs are waiting for an update
  * Optionally: PRs Removal Efficiency
      o How many PRs were closed vs. opened during a period of
        time/-/It's PRs Removal Efficiency - that is the extent to which
        the development team is able to handle and remove the valid PRs
        or defects (issues) that have been opened.
      o To calculate the PRs gap, get a count of the total PRs opened
        and the total number of that were closed by the end of the
        cycle. Calculate a quick percentage.
      o Example of defect gap including formula:
      o


Thanks,

/koca
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mta.openssl.org/pipermail/openssl-project/attachments/20221018/7963112d/attachment.htm>