+1. despite maintaining activity, @fab never responds to any of my bugzillas or attempts of direct contact

+1. despite maintaining activity, @fab never responds to any of my bugzillas or attempts of direct contact

"never responds to any of my bugzillas"..really? The last entry was create less than a week ago to one of your automatically generated Bugzilla entries. I guess that doesn't count...

issues to fix:... https://bugzilla.redhat.com/show_bug.cgi?id=2091345

This Bugzilla entry which was opened by the reporter contains a request directed at the reporter but no feedback was provided in the last four weeks.

This is definitely not a case of a packager being inactive in Fedora, or even a case of being totally nonresponsive across the board.

At the same time, I agree with @churchyard that I am usually not able to draw attention to bugs and PR’s in practice, even when using @ mentions, NEEDINFO, and/or direct email. See, for example, https://bugzilla.redhat.com/show_bug.cgi?id=2105059 and https://src.fedoraproject.org/rpms/python-aiomysql/pull-request/1.

This comment is not a vote.

Examples from the Python 3.11 update only:

https://bugzilla.redhat.com/show_bug.cgi?id=2058155
https://bugzilla.redhat.com/show_bug.cgi?id=2098826
https://bugzilla.redhat.com/show_bug.cgi?id=2099090
https://bugzilla.redhat.com/show_bug.cgi?id=2099115
https://bugzilla.redhat.com/show_bug.cgi?id=2113633
https://bugzilla.redhat.com/show_bug.cgi?id=2113659
https://bugzilla.redhat.com/show_bug.cgi?id=2114560
https://bugzilla.redhat.com/show_bug.cgi?id=2019852
https://bugzilla.redhat.com/show_bug.cgi?id=2021804
https://bugzilla.redhat.com/show_bug.cgi?id=2022284

Bugzilla query for NEW bugzillas: https://bugzilla.redhat.com/buglist.cgi?bug_status=NEW&email1=mail%40fabian-affolter.ch&emailassigned_to1=1&emailtype1=exact

On Wed, 2022-09-21 at 19:28 +0000, Fabian Affolter wrote:

fab added a new comment to an issue you are following:
``

+1. despite maintaining activity, @fab never responds to any of my bugz=
illas or attempts of
direct contact
=20
"never responds to any of my bugzillas"..really? The last entry was creat=
e less than a week ago
to one of your automatically generated Bugzilla entries. I guess that doe=
sn't count...
=20
issues to fix:... https://bugzilla.redhat.com/show_bug.cgi?id=3D2091345
=20
This Bugzilla entry which was opened by the reporter contains a request d=
irected at the reporter
but no feedback was provided in the last four weeks.=20
``
=20
To reply, visit the link below or just reply to this email
https://pagure.io/fesco/issue/2872

The issue referenced was missed by myself, so apologies there. It would have been better marked for NEEDINFO and then it would appeared in the daily outstanding requests email. To note the request was made 3 months after original report.

rednotebook 2.25 has now been available for some time and no action. My issue is with lack of
timely response to bugzilla and no reply ever to direct email. I have offered to co-maintain, that
has also been ignored. Teaming up would have resolved this long ago and rednotebook users and those EPEL users would have the latest and greatest now.

Regards

Phil

@fab Would you be willing to add more people as comaintainers? It sounds like that'd help address the issues.

@fab Would you be willing to add more people as comaintainers? It sounds like that'd help address the issues.

Look at the non-maintainer process. I should be given admin today. This has gone on too long.

Another example is this 2-pages long list of Pull Request: https://src.fedoraproject.org/user/fab/requests?type=actionable&status=open

However, I must note that it can also contain pull requests where @fab responded with a query that was never answered. But OTOH it does not contain pull requests already merged by a provenpackager.

To note the request was made 3 months after original report.

Oh, I'm sorry that it took too long for your opinion.

Would you be willing to add more people as comaintainers?

Sure. I'm usually a bit cautious because more co-maintainers doesn't mean that things get done quicker.

I should be given admin today. This has gone on too long.

Well, @kathenas has now commit access. The method is a bit questionable but I don't care as this is in the past.

Another example is this 2-pages long list of Pull Request: https://src.fedoraproject.org/user/fab/requests?type=actionable&status=open

So, what? I guess that all lists of people which maintain a couple of hundreds packages is that long. If it's shorter then it could mean that you get paid to keep it short.

No, I am just showing examples to justify my "never responds to Bugzilla" comment, because I had a hard time reaching you via Bugzilla, email, or pull requests for the past year. Sorry, if that hurt your feelings.

No, I am just showing examples to justify my "never responds to Bugzilla" comment

I don't know where you get your numbers but in the last 6 months alone I "responded" (in fact the infrastructure created the responses in the Bugzilla entries) with action to over 50 of your reports. I guess that this doesn't count as those were not personalized comments on your automated Bugzilla entries.

Looks like that I missed that this is a KPI now.

To note the request was made 3 months after original report.

Oh, I'm sorry that it took too long for your opinion.

Would you be willing to add more people as comaintainers?

Sure. I'm usually a bit cautious because more co-maintainers doesn't mean that things get done quicker.

I should be given admin today. This has gone on too long.

Well, @kathenas has now commit access. The method is a bit questionable but I don't care as this is in the past.

Another example is this 2-pages long list of Pull Request: https://src.fedoraproject.org/user/fab/requests?type=actionable&status=open

So, what? I guess that all lists of people which maintain a couple of hundreds packages is that long. If it's shorter then it could mean that you get paid to keep it short.

Thanks @fab for the commit access. To avoid duplicated work, I am updating rednotebook currently. I hope we can work together in the future to keep this package fresh and the best version that Jendrik (upstream) wishes users to have.

I now see this issue as closed and will close it now and accept that @fab and myself will do our best to do the best for this package.

Regards

Phil