As an experienced Fedora package maintainer and a member of the team currently working on ELN, I would like to be added to the provenpackager group for the purposes of efficiently taking care of minor ELN related issues with packages.
Thank you for your consideration.
FAS ID: merlinm
mmathesi@redhat.com
I asked @merlinm to request provenpackager access. He's going to be my backup (particularly when I'm away on PTO) for all ELN-related build issues. As such, he will need provenpackager permissions.
+1 from me
Metadata Update from @churchyard: - Issue tagged with: provenpackager
Announced to sponsors. Sponsors, please vote here.
wrt ELN, is the intent still to do changes via Pull Requests and only use the provenpackager right once there is no response?
https://fedoraproject.org/wiki/Changes/ELN_Buildroot_and_Compose#What_if_packages_don.27t_build_on_ELN.3F
wrt ELN, is the intent still to do changes via Pull Requests and only use the provenpackager right once there is no response? https://fedoraproject.org/wiki/Changes/ELN_Buildroot_and_Compose#What_if_packages_don.27t_build_on_ELN.3F
Absolutely, yes. This is entirely about Merlin being able to perform the builds, not about making mass-changes.
AFAIK any account from the packager group can trigger builds for existing commits.
For clarity, I am not opposed to this, I just try to understand the reasoning better.
Really? Huh... I always assumed that was restricted to committers.
Example: https://koji.fedoraproject.org/koji/taskinfo?taskID=45595944
@sgallagh It's only needed for commit access, not for triggering builds.
Still, merging stallled pull requests requires commit access to packages, so this request is reasonable. +1 from me
EDIT: I'll change my vote to ±0 until any issues are cleared up.
I see that Merlin is not maintaining much packages, I checked some of them and they don't comply to our guidelines (not to mention that they exist only as a modular RPMs which is not anymore allowed by our policies).
as per:
skilled package maintainers who are experienced in a wide variety of package types and who are familiar with the packaging guidelines
-1
But definitely @merlinm is welcome to perform ELN rebuilds.
I do see only 3 RPM packages being (co-)maintained by Merlin. Of those, standard-test-roles has astepano as the main admin, and the 2 remaining have been obsoleted in non-modular Fedora after F29.
Only 1 package review done: https://bugzilla.redhat.com/buglist.cgi?classification=Fedora&component=Package%20Review&email1=mmathesi%40redhat.com&emailassigned_to1=1&emailtype1=equals&product=Fedora
Also, only 4 review requests submitted: https://bugzilla.redhat.com/buglist.cgi?classification=Fedora&component=Package%20Review&email1=mmathesi%40redhat.com&emailreporter1=1&emailtype1=equals&product=Fedora
Only 3 of those actually made it into non-modular Fedora and not for long, as @torsava noticed.
So, -1 from me. Doesn't look like an "experienced package maintainer" to me.
I am withdrawing my request since it appears I do not need provenpackager privileges for the originally intended purposes.
I defense of my claim to be an "experienced package maintainer", although I may not personally own many packages/modules, I have submitted countless dist-git PRs and patches for packages maintained by others.
Metadata Update from @merlinm: - Issue close_status updated to: Insufficient data - Issue status updated to: Closed (was: Open)
Alright, but you haven't told us that. :) Please provide links next time.