[gentoo-proxy-maint] How to reactivate after inactive_proxied_maintainer?

[gentoo-proxy-maint] How to reactivate after inactive_proxied_maintainer?

[Oliver Freyermuth]

Hi together,

I've sadly kept a version bump request without updates for some months
(I was actively working with upstream to fix bugs breaking packaging for all distros after a change of buildsystem...). 
Sadly I did not communicate that on the Gentoo bug report, so my proxy maintainer bug is now marked as blocking the dreaded inactive_proxied_maintainer issue. 

In the meantime, a new "packageable" version was released, I've updated sys-cluster/charliecloud and the bug is closed. 

I've learned my lesson and in the future, will ensure to communicate early on Bugzilla if there is a strong reason a bump is held up
(I was still faster than almost all other distros, though :-) ). 

My question is: How do I rid myself of the inactive_proxied_maintainer "state" on Bugzilla? 
Is this done automatically after a while, after a manual review, or should I (am I allowed to) remove the "blocker" bug link from my maintainer bug myself? 

I'm just asking to prevent extra human work in case an automatism triggers retirement and package reassignment,
forcing me to reapply to become a proxy maintainer again, creating extra work for the proxy maintainer project. 

Cheers and a nice weekend to everybody,
	Oliver

Re: [gentoo-proxy-maint] How to reactivate after inactive_proxied_maintainer?

[Joonas Niilola]

[-- Attachment #1.1: Type: text/plain, Size: 2236 bytes --]


On 4/17/20 10:10 PM, Oliver Freyermuth wrote:
> Hi together,
>
> I've sadly kept a version bump request without updates for some months
> (I was actively working with upstream to fix bugs breaking packaging for all distros after a change of buildsystem...). 
> Sadly I did not communicate that on the Gentoo bug report, so my proxy maintainer bug is now marked as blocking the dreaded inactive_proxied_maintainer issue. 
>
> In the meantime, a new "packageable" version was released, I've updated sys-cluster/charliecloud and the bug is closed. 
>
> I've learned my lesson and in the future, will ensure to communicate early on Bugzilla if there is a strong reason a bump is held up
> (I was still faster than almost all other distros, though :-) ). 
>
> My question is: How do I rid myself of the inactive_proxied_maintainer "state" on Bugzilla? 
> Is this done automatically after a while, after a manual review, or should I (am I allowed to) remove the "blocker" bug link from my maintainer bug myself? 
>
> I'm just asking to prevent extra human work in case an automatism triggers retirement and package reassignment,
> forcing me to reapply to become a proxy maintainer again, creating extra work for the proxy maintainer project. 
>
> Cheers and a nice weekend to everybody,
> 	Oliver
>
Hey,

the proxy-maint bugs are *mostly* automated. However the tracker is used
because it's easier to check status on those who have been added there
without needing to go through *every* people.

Basically if you have multiple bugs open for packages you maintain and
you haven't responded / fixed them in a long time, it's a sort of a sign
of inactivity. I know some people are active contributing through Github
even if their last login to bugzilla was +6 months ago, but bugzilla is
still the most important site regarding your packages. Some bugs are
fixed, but not closed. Others have been ignored for months/years.

So please, keep good care of your packages and remember to keep bugzilla
clean on your behalf as well.

To answer your question: If you know you are active again, you can
remove yourself from the tracker. I'm gonna check it at least weekly
from now on, too.


-- juippis



[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 642 bytes --]

Re: [gentoo-proxy-maint] How to reactivate after inactive_proxied_maintainer?

[Oliver Freyermuth]

[-- Attachment #1.1: Type: text/plain, Size: 2973 bytes --]

Am 18.04.20 um 09:08 schrieb Joonas Niilola:
> 
> On 4/17/20 10:10 PM, Oliver Freyermuth wrote:
>> Hi together,
>>
>> I've sadly kept a version bump request without updates for some months
>> (I was actively working with upstream to fix bugs breaking packaging for all distros after a change of buildsystem...). 
>> Sadly I did not communicate that on the Gentoo bug report, so my proxy maintainer bug is now marked as blocking the dreaded inactive_proxied_maintainer issue. 
>>
>> In the meantime, a new "packageable" version was released, I've updated sys-cluster/charliecloud and the bug is closed. 
>>
>> I've learned my lesson and in the future, will ensure to communicate early on Bugzilla if there is a strong reason a bump is held up
>> (I was still faster than almost all other distros, though :-) ). 
>>
>> My question is: How do I rid myself of the inactive_proxied_maintainer "state" on Bugzilla? 
>> Is this done automatically after a while, after a manual review, or should I (am I allowed to) remove the "blocker" bug link from my maintainer bug myself? 
>>
>> I'm just asking to prevent extra human work in case an automatism triggers retirement and package reassignment,
>> forcing me to reapply to become a proxy maintainer again, creating extra work for the proxy maintainer project. 
>>
>> Cheers and a nice weekend to everybody,
>> 	Oliver
>>
> Hey,
> 
> the proxy-maint bugs are *mostly* automated. However the tracker is used
> because it's easier to check status on those who have been added there
> without needing to go through *every* people.
> 
> Basically if you have multiple bugs open for packages you maintain and
> you haven't responded / fixed them in a long time, it's a sort of a sign
> of inactivity. I know some people are active contributing through Github
> even if their last login to bugzilla was +6 months ago, but bugzilla is
> still the most important site regarding your packages. Some bugs are
> fixed, but not closed. Others have been ignored for months/years.
> 
> So please, keep good care of your packages and remember to keep bugzilla
> clean on your behalf as well.
> 
> To answer your question: If you know you are active again, you can
> remove yourself from the tracker. I'm gonna check it at least weekly
> from now on, too.
> 
> 
> -- juippis
> 
> 

Hey,

thanks for the detailed reply! 

Indeed, I will monitor Bugzilla more closely from now on. In my case, it was just a single bug,
and indeed I definitely should have commented on it much earlier to indicate the status. 
I've setup an extra "urlwatch" notification to get reminders in case I ever miss a bugtracker mail. 

I've removed myself from the tracker just now, and want to express a great thank you for all the effort
spent on identifying inactive maintainers. That's of high importance to get rid of outdated / unmaintained packages from the main tree. 

Cheers and thanks a lot,
	Oliver


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]