Hi all,
CommOps received a request to build metrics for (1) what packages are
updated every Fedora release, and (2) how long on average package
reviews take; however, we do not have capacity to take this request. Per
discussion at Nest, I am following up on Fedora Infrastructure list to
explore if there is capacity elsewhere for this work.
The ticket with this request was opened by Brian Exelbierd in March
2018. The CommOps team first approached this work two years ago, but our
volunteer team does not have capacity to meet this request:
https://pagure.io/fedora-commops/issue/144
At Nest, we briefly discussed with cverna in the CommOps metrics hack
session that this request is more likely a question of which system to
query and how (versus building new tooling or collecting new data).
I was actioned to open a discussion on the Infrastructure mailing list
to explore if this is of interest to the Fedora Packaging community. If
so, the C.P.E. team may be able to redirect this request to the right place.
I am closing the CommOps ticket once I send this mail, but I am happy to
move the request to a new Pagure issue in a different repo if someone is
interested in taking up this request.
Thanks!
--
Cheers,
Justin W. Flory (he/him)
https://jwf.io
TZ=America/New_York
Attachment:
signature.asc
Description: OpenPGP digital signature
_______________________________________________ infrastructure mailing list -- infrastructure@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to infrastructure-leave@xxxxxxxxxxxxxxxxxxxxxxx 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/infrastructure@xxxxxxxxxxxxxxxxxxxxxxx
