Taking maintainership of dev-libs/jansson per bug 619904. Opening this to track maintainer changes.
The whole 2nd-class citizen proxy maint thing is dumb, and I'm over it. Please do whatever you need to do to remove me.
Hmm, if this is about https://github.com/gentoo/gentoo/pull/37612 then it's not about proxy-maint at all, as it's recommended for both Developers and Proxy-Maint to go through the arch testing teams (and use the nattka keywords). The guidelines are universal, here. That being said, retiring from proxy-maint is as easy as removing yourself from all (1) packages that have you listed as a maintainer and resolving/closing this bug, I guess. If you are still sure that is what you want to do...
(In reply to Eli Schwartz from comment #2) > Hmm, if this is about https://github.com/gentoo/gentoo/pull/37612 then it's > not about proxy-maint at all, as it's recommended for both Developers and > Proxy-Maint to go through the arch testing teams (and use the nattka > keywords). The guidelines are universal, here. I think he's talking about the first rule here: https://devmanual.gentoo.org/keywording/index.html#stabilization-rules "amd64, x86: If you are the maintainer of a package and own the respective amd64 or x86 hardware, you can do your own testing (stabilization and keywording) of your packages; as long as it is not a core system set dependency." I simply thought he left out amd64 by mistake and he was trying to fix it somehow. Even so, it is recommended to let the arch teams handle stabilizations, and as far as I know that rule is only used when the arch team is lagging. Adding the arches yourself to CC is still not ok, that is true for everyone, including developers. That is solely nattka's job. (In reply to David Zero from comment #1) > The whole 2nd-class citizen proxy maint thing is dumb, and I'm over it. > Please do whatever you need to do to remove me. Please confirm if you still want to retire from proxy maintainers.
