Re: Nonresponsive maintainers ( was Re: Red Hat Bugzilla mail FAS field is now handled correctly by Bugzilla sync scripts )
On Fri, Jan 27, 2023 at 1:10 AM Kevin Fenzi wrote: > jaltman I have sent an email to Jeff, and hopefully he will update his bugzilla email. ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Nonresponsive maintainers ( was Re: Red Hat Bugzilla mail FAS field is now handled correctly by Bugzilla sync scripts )
On Thu, Jan 26, 2023 at 05:10:15PM -0800, Kevin Fenzi wrote: > On Tue, Jan 17, 2023 at 02:49:10PM +0100, Michal Konecny wrote: > > Hi everybody, > > > > TL;DR; Check if you have correct e-mail in Red Hat Bugzilla Mail field in > > Fedora Accounts [0]. Empty mail is also OK. > > > > the Red Hat Bugzilla Email field in Fedora Accounts [0] was till now ignored > > by most of the apps. > > > > This was changed now with the latest update to toddlers [1], which contains > > most of the syncing scripts that are run automatically in Fedora Infra > > including distgit_bugzilla_sync [2], packager_bugzilla_sync [3] and > > packagers_without_bugzilla [4] scripts. All these scripts are using shared > > methods for working with Fedora Accounts system. > > > > With the addition of scm_request_processor [5] there was a small change in > > how the Fedora Accounts mails are handled in regard to Red Hat Bugzilla > > mail. This change caused it to first look for Red Hat Bugzilla Mail and then > > look at the personnel e-mail associated with the account if Bugzilla mail is > > not set. > > > > This unfortunately caused issues for some users that had Red Hat Bugzilla > > Mail field set incorrectly. I was the one who did the change and I actually > > forgot about it, because it happened at the beginning of > > scm_request_processor development cycle and I didn't know it could have that > > large impact. So I apologize for any issue this could have caused for you. > > > > If you are one of the users, who were impacted by this change, you can fix > > it by adding correct Red Hat Bugzilla mail to your Fedora Account. You can > > do this in Settings->Emails in Fedora Accounts page [0]. > > > > We will fix the message that is being sent to packagers without Bugzilla > > e-mail to correspond with this change. > > Hello everyone. > > After this we still have 4 users who's bugzilla email does not exist. :( > > They are: > npmccallum Nathaniel has been on the list for 2 or 3 months at this point. I've been wanting to start the non-responsive process a while back but got a bit lazy to look at the exact date when we started sending him emails :( Thanks for starting this Kevin! Pierre signature.asc Description: PGP signature ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Nonresponsive maintainers ( was Re: Red Hat Bugzilla mail FAS field is now handled correctly by Bugzilla sync scripts )
On Tue, Jan 17, 2023 at 02:49:10PM +0100, Michal Konecny wrote: > Hi everybody, > > TL;DR; Check if you have correct e-mail in Red Hat Bugzilla Mail field in > Fedora Accounts [0]. Empty mail is also OK. > > the Red Hat Bugzilla Email field in Fedora Accounts [0] was till now ignored > by most of the apps. > > This was changed now with the latest update to toddlers [1], which contains > most of the syncing scripts that are run automatically in Fedora Infra > including distgit_bugzilla_sync [2], packager_bugzilla_sync [3] and > packagers_without_bugzilla [4] scripts. All these scripts are using shared > methods for working with Fedora Accounts system. > > With the addition of scm_request_processor [5] there was a small change in > how the Fedora Accounts mails are handled in regard to Red Hat Bugzilla > mail. This change caused it to first look for Red Hat Bugzilla Mail and then > look at the personnel e-mail associated with the account if Bugzilla mail is > not set. > > This unfortunately caused issues for some users that had Red Hat Bugzilla > Mail field set incorrectly. I was the one who did the change and I actually > forgot about it, because it happened at the beginning of > scm_request_processor development cycle and I didn't know it could have that > large impact. So I apologize for any issue this could have caused for you. > > If you are one of the users, who were impacted by this change, you can fix > it by adding correct Red Hat Bugzilla mail to your Fedora Account. You can > do this in Settings->Emails in Fedora Accounts page [0]. > > We will fix the message that is being sent to packagers without Bugzilla > e-mail to correspond with this change. Hello everyone. After this we still have 4 users who's bugzilla email does not exist. :( They are: dctrud jaltman npmccallum sbluhm Does anyone know how to contact them? If not, I will file a FESCo ticket in a week indicating that they have no bugzilla email set (or set wrong) and should be removed from any packages they maintain or watch. kevin signature.asc Description: PGP signature ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
