Hi,
I'm a packager for ~3 years now and also maintain the Astronomy Spin and just got the LXQt Spin approved for Fedora 26. Now I decided to request becoming a proven packager as I'd like to be able to help with rebuilds required for updated libaries etc. When working on LXQt I've been in that situation too where I had to ask the maintainers of depending packages to rebuild them. In that case I could rebuild by myself, ensure proper timing more easily and do not have to bother the maintainers.
My packaging related activities: * Main contact of ~50 packages * Co-maintaining 30 packages (and many more through KDE SIG and LXQt SIG) * Member of KDE SIG, helping with new required packages and reviews * Member of LXQt SIG, currently maintaining most of the packages * Member of Python SIG, many of my packages are Python packages * Maintainer of Astronomy Spin and new (for F26) LXQt Spin * >80 reviews, check https://bugzilla.redhat.com/buglist.cgi?component=Package%20Review&email1=lupinix%40mailbox.org&emailassigned_to1=1&emailtype1=substring&list_id=7070581&query_format=advanced
I am lupinix' sponsor and worked (still ongoing) a lot with him on packages and reviews. He has good knowledge in packaging and keeps up2date with changes in guidelines. That said, here's my
+1
big +1
from me. I couldn't really add anything new to the statement made by @besser82
+1 here.
+1 says it all :)
It's been a week and I see 7 +1's and 0 -1's so this is approved.
Use your powers wisely.
:ramen:
Metadata Update from @kevin: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Thank you :) I got the following mail:
kevin kevin@scrye.com has upgraded you to sponsor status in the 'packager' group of the Fedora Accounts System This change is effective immediately for new operations, and should propagate into the e-mail aliases within an hour.
It looks like I have the right to sponsor new packagers now, not the provenpackager rights. I also double checked other indications like zodbot and Badges.
Metadata Update from @lupinix: - Issue status updated to: Open (was: Closed)
oops. I have no idea why I misprocessed this. ;(
Should be all fixed now.
:city_dusk:
Again, thank you :) Looks fine now