Learn more about these different git repos.
Other Git URLs
There are a couple packages where the commit ACL was not added for the go-sig/rust-sig, because they already have the ticket ACL. The script checks for the presence of any ACLs, not if they are at least commit. Please give the rust-sig commit on rust-temptree and the go-sig commit on golang-rsc-pdf.
commit
ticket
The script currently uses https://src.fedoraproject.org/extras/pagure_bz.json. If we wanted to get more granular data and fix this problem, we'd have to make an API request for every package that matches the criteria every time we run the script. @decathorpe and I agreed that this didn't make sense.
Done and Done.
Metadata Update from @kevin: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Thanks @kevin!
Side note: All three JSON files which are provided by pagure-dist-git (?) at https://src.fedoraproject.org/extras/ are of limited usefulness in different ways ... if a dump of the "complete" package maintainer information were added, this would be way more useful, i.e. something like:
{ "rpms": [ { "project": "foo", "owner": "bar", "admin": ["baz1", "baz2"], "commit": ["baz3", "baz4"], "ticket": ["baz5", "baz6"], "watch": ["baz7", "baz8"], "fedora": "bar", "epel": "baz6", }, ], "modules": {}, "tests": {}, "containers": {}, }
I can't imagine that this would be more expensive to generate than the existing three JSON files, since it queries the same database tables, just puts more of the data from that table into a JSON file ... and this would be way more useful. Should I open an RFE for this with pagure-dist-git?
All three JSON files which are provided by pagure-dist-git (?) at https://src.fedoraproject.org/extras/
They scripts are part of pagure-dist-git and they run on an hourly cron job.
Should I open an RFE for this with pagure-dist-git?
pagure-dist-git development is kind of dead, but I guess it won't hurt.
c.f. https://pagure.io/pagure-dist-git/issue/155
Log in to comment on this ticket.