Re: Inactive packager check for F38

2023-02-22 Thread Sérgio Basto
On Wed, 2023-02-15 at 14:02 -0500, Ben Cotton wrote: > In accordance with FESCo's Inactive Packager Policy[1], packagers > that > have been identified as inactive have a ticket in the > find-inactive-packagers repo[2]. One week after the final release, > packagers who remain inactive will be

Re: Inactive packager check for F38

2023-02-18 Thread Mattia Verga via devel
Il 16/02/23 21:45, Mattia Verga ha scritto: > 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é wrote: > I'm a little surprised

Re: Inactive packager check for F38

2023-02-18 Thread Mattia Verga via devel
Il 17/02/23 17:14, Ben Cotton ha scritto: > On Fri, Feb 17, 2023 at 1:48 AM Mattia Verga via devel > wrote: >> During the weekend I can write down a script reusing partial code from >> the find_inactive_packagers script and purge the ticket list from users >> that showed activity in RH bugzilla,

Re: Inactive packager check for F38

2023-02-17 Thread Ben Cotton
On Fri, Feb 17, 2023 at 1:48 AM Mattia Verga via devel wrote: > > During the weekend I can write down a script reusing partial code from > the find_inactive_packagers script and purge the ticket list from users > that showed activity in RH bugzilla, let me know if you want me to > proceed. Or I

Re: Inactive packager check for F38

2023-02-16 Thread Mattia Verga via devel
Il 16/02/23 22:30, Ben Cotton ha scritto: > On Thu, Feb 16, 2023 at 3:45 PM Mattia Verga via devel > wrote: >> 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? > I didn't forget, I

Re: Inactive packager check for F38

2023-02-16 Thread Ben Cotton
On Thu, Feb 16, 2023 at 3:45 PM Mattia Verga via devel wrote: > > 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? I didn't forget, I intentionally did not. I thought we had already

Re: Inactive packager check for F38

2023-02-16 Thread Mattia Verga via devel
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é >>> wrote: I'm a little surprised that the pagure ticket doesn't have the

Re: Inactive packager check for F38

2023-02-16 Thread Mattia Verga via devel
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é >> wrote: >>> I'm a little surprised that the pagure ticket doesn't have the >>> maintainer to whom it refers added as a subscriber to

Re: Inactive packager check for F38

2023-02-16 Thread Kevin Fenzi
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é > 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

Re: Inactive packager check for F38

2023-02-16 Thread Ben Cotton
On Thu, Feb 16, 2023 at 6:29 AM Daniel P. Berrangé 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

Re: Inactive packager check for F38

2023-02-16 Thread Ben Cotton
On Wed, Feb 15, 2023 at 5:20 PM Paul Wouters wrote: > > How many packages depend _only_ on people from this list? Eg are likely > to be unmaintained ? There's a command in the script that will check the impact, but I'm going to hold off on running it for a bit. It takes a long time to iterate

Re: Inactive packager check for F38

2023-02-16 Thread Stephen Smoogen
On Thu, 16 Feb 2023 at 08:25, Stephen Smoogen wrote: > > > On Thu, 16 Feb 2023 at 05:56, Richard W.M. Jones > wrote: > >> On Wed, Feb 15, 2023 at 02:02:54PM -0500, Ben Cotton wrote: >> > In accordance with FESCo's Inactive Packager Policy[1], packagers that >> > have been identified as inactive

Re: Inactive packager check for F38

2023-02-16 Thread Stephen Smoogen
On Thu, 16 Feb 2023 at 05:56, Richard W.M. Jones wrote: > On Wed, Feb 15, 2023 at 02:02:54PM -0500, Ben Cotton wrote: > > In accordance with FESCo's Inactive Packager Policy[1], packagers that > > have been identified as inactive have a ticket in the > > find-inactive-packagers repo[2]. One week

Re: Inactive packager check for F38

2023-02-16 Thread Daniel P . Berrangé
On Thu, Feb 16, 2023 at 10:55:55AM +, Richard W.M. Jones wrote: > On Wed, Feb 15, 2023 at 02:02:54PM -0500, Ben Cotton wrote: > > In accordance with FESCo's Inactive Packager Policy[1], packagers that > > have been identified as inactive have a ticket in the > > find-inactive-packagers

Re: Inactive packager check for F38

2023-02-16 Thread Richard W.M. Jones
On Wed, Feb 15, 2023 at 02:02:54PM -0500, Ben Cotton wrote: > In accordance with FESCo's Inactive Packager Policy[1], packagers that > have been identified as inactive have a ticket in the > find-inactive-packagers repo[2]. One week after the final release, > packagers who remain inactive will be

Re: Inactive packager check for F38

2023-02-15 Thread Paul Wouters
On Wed, 15 Feb 2023, Ben Cotton wrote: For the curious, here are the stats from today's run: ### Found 2129 users in the packager group. ### ### Found 914 users with no activity in pagure/src.fp.org over the last year. ### ### Found 845 users which also show no activity in Bodhi over the last

Inactive packager check for F38

2023-02-15 Thread Ben Cotton
In accordance with FESCo's Inactive Packager Policy[1], packagers that have been identified as inactive have a ticket in the find-inactive-packagers repo[2]. One week after the final release, packagers who remain inactive will be removed from the packager group. (Note that pagure.io is one of the

Inactive packager check for F38

2023-02-15 Thread Ben Cotton
In accordance with FESCo's Inactive Packager Policy[1], packagers that have been identified as inactive have a ticket in the find-inactive-packagers repo[2]. One week after the final release, packagers who remain inactive will be removed from the packager group. (Note that pagure.io is one of the