Re: Inactive packager check for F38

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Il 16/02/23 20:26, Mattia Verga ha scritto:
> Il 16/02/23 18:36, Kevin Fenzi ha scritto:
>> On Thu, Feb 16, 2023 at 09:04:01AM -0500, Ben Cotton wrote:
>>> On Thu, Feb 16, 2023 at 6:29 AM Daniel P. Berrangé <berrange@xxxxxxxxxx> wrote:
>>>> I'm a little surprised that the pagure ticket doesn't have the
>>>> maintainer to whom it refers added as a subscriber to the ticket.
>>> As far as I know, you can't subscribe others to a ticket the way you
>>> can add a CC in Bugzilla. We could modify the script to set the person
>>> as the assignee, but
>>>
>>> 1. That's functionally the same as @ing them in the ticket
>>> and...
>>>
>>>> Does pagure.io not have accounts synced for everyone who is a
>>>> Fedora packager ?
>>> ...2. Not as far as I know. If the person never logged in (which you
>>> don't necessarily need to do as a packager), then pagure.io would not
>>> know about them. I see that from time to time with Changes tickets to
>>> FESCo.
>> pagure.io only creates user accounts after the initial login.
>> There's no syncing of anything. pagure.io is intended to be a general
>> source forge and not fedora specific.
>>
>> I'm not sure there's any easy way around this. I suppose the best would
>> be to identify all those users who don't exist on pagure.io that are
>> cced in the tickets and email a copy of the ticket or link to it to
>> their @fedoraproject.org alias.
>>
> Ah, that's indeed a bad design from my side, I didn't take into account
> that users of src.fp.o are not the same of users of pagure.io.
>
> Flagging unknown users in pagure.io should be quite simple, but then we
> have to decide how to handle them. Direct emails are not the best
> option, but the only alternative it come to my mind is to use Bugzilla
> instead of pagure.io to open and manage inactive_packagers tickets.
>
I've pushed https://pagure.io/find-inactive-packagers/pull-request/1440
which will add an extra column to the csv file to mark users not found
in pagure.io.

However, I think something wrong has happened with the last policy run:
I was surprised that so many tickets were filed and my suspects are that
the check against bugzilla hasn't been properly performed. For example:

```

$ python find_inactive_packagers.py check-user mhorky
Checking mhorky activity in Pagure...
No activity detected for user mhorky in https://src.fedoraproject.org
User not found in https://pagure.io
Checking mhorky activity in Bodhi...
Checking mhorky activity in mailing lists...
Checking mhorky activity in bugzilla...
Using RHBugzilla for URL containing .redhat.com
User mhorky made a comment in Bugzilla on 2022_05_31.
Activity detected for user mhorky.

```

This user should not have been detected as inactive if the Bugzilla
check was run. @Ben, maybe you forgot to set the BZ_API_KEY before
running the script?

Mattia

_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
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@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue




[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Users]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]

  Powered by Linux