Re: Inactive packager check for F38
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 removed from the packager > group. > (Note that pagure.io is one of the systems checked for activity, so > commenting on your ticket that you're still around will prevent you > from showing up in the second round.) > > If you have suggestions for improvement, look for the open feature > issues[3] and file an issue in the find-inactive-packagers repo[4] if > it's not there already. > > 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 year. ### > ### Found 812 users which show also no activity in mailing lists over > the last year. ### > ### Found 812 users which also show no activity in Bugzilla over the > last year. ### > > As we approach > > [1] > https://docs.fedoraproject.org/en-US/fesco/Policy_for_inactive_packagers/ > [2] > https://pagure.io/find-inactive-packagers/issues?tags=inactive_packager=Open > [3] https://pagure.io/find-inactive-packagers/issues?tags=feature > [4] https://pagure.io/find-inactive-packagers/new_issue I think we may though in one way to avoid retire packages after 6 weeks of being orphan when they still perfectly usable. For example slim-1.3.6-22.fc36 was retired when a user want use it and now want un-retire it For example on Java many packages was retired and we still use it, like hsqldb1. IMHO the retirement of the packages just because the packager maintainer was inactive or unresponsive or just leave the project, bring to us others problems and much more work for others packager maintainers (like me) . I don't know really what is better but I think the process can be improved Best regards, -- Sérgio M. B. ___ 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: Inactive packager check for F38
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 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. > I've also pushed https://pagure.io/find-inactive-packagers/pull-request/1446 that will add a tag to the tickets whose users are not recognized in pagure.io. However, there's no way in Pagure APIs to add that tag to already created tickets... I've done a comparison between currently opened tickets and users which would be marked as not recognized with the new script and I got 369 users \o/ So those 369 didn't get the notification about the current policy run. Mattia ___ 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: Inactive packager check for F38
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, let me know if you want me to >> proceed. Or I can provide a list of users, but I think that will be a >> long list for manual processing... > People who were active in Bugzilla will get noticed on the step-two > run and not removed, so I don't think it's necessary to go through and > clean those up now unless you really want to. > Yeah, I agree it is not mandatory to purge those tickets before step-two, but not doing so will cause check-impact to output a lot of garbage and to cause false alarms to packagers. Mattia ___ 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: Inactive packager check for F38
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 can provide a list of users, but I think that will be a > long list for manual processing... People who were active in Bugzilla will get noticed on the step-two run and not removed, so I don't think it's necessary to go through and clean those up now unless you really want to. -- Ben Cotton He / Him / His Fedora Program Manager Red Hat TZ=America/Indiana/Indianapolis ___ 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: Inactive packager check for F38
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 intentionally did not. I thought we had already > modified the script to use `~/.bugzillarc` via the python-bugzilla > library (the scripts for processing Change proposals and handling > branch/EOL events does this). But apparently we did not, since > https://pagure.io/find-inactive-packagers/issue/5 is still open. I'll > prioritize that for next week if the COVID brain fog has lifted by > then. I did find it suspicious that the mailing list and Bugzilla > count matched exactly, but ...again... brain fog. > > I'll also knock out #6 (which is #5 except for the Pagure API key) at > the same time. This will make the SOP for future me and my successors > easier to follow. > 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 can provide a list of users, but I think that will be a long list for manual processing... Meanwhile, I'll try to fix some bugs that arose during this run, as time permits. Mattia ___ 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: Inactive packager check for F38
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 modified the script to use `~/.bugzillarc` via the python-bugzilla library (the scripts for processing Change proposals and handling branch/EOL events does this). But apparently we did not, since https://pagure.io/find-inactive-packagers/issue/5 is still open. I'll prioritize that for next week if the COVID brain fog has lifted by then. I did find it suspicious that the mailing list and Bugzilla count matched exactly, but ...again... brain fog. I'll also knock out #6 (which is #5 except for the Pagure API key) at the same time. This will make the SOP for future me and my successors easier to follow. -- Ben Cotton He / Him / His Fedora Program Manager Red Hat TZ=America/Indiana/Indianapolis ___ 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: Inactive packager check for F38
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 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@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: Inactive packager check for F38
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 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. Mattia ___ 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: Inactive packager check for F38
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 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. 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
Re: Inactive packager check for F38
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 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. -- Ben Cotton He / Him / His Fedora Program Manager Red Hat TZ=America/Indiana/Indianapolis ___ 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: Inactive packager check for F38
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 over all of the tickets and the resulting packages, with the result that people have responded by the time the script finishes. In another couple of weeks, the "I'm still here!"s will settle down and the output will be more reliable. I'll share it then. -- Ben Cotton He / Him / His Fedora Program Manager Red Hat TZ=America/Indiana/Indianapolis ___ 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: Inactive packager check for F38
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 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 systems checked for activity, so >> > commenting on your ticket that you're still around will prevent you >> > from showing up in the second round.) >> > >> > If you have suggestions for improvement, look for the open feature >> > issues[3] and file an issue in the find-inactive-packagers repo[4] if >> > it's not there already. >> >> Just an FYI, I was talking to armbru about this ticket: >> >> https://pagure.io/find-inactive-packagers/issue/1181 >> >> Although he does not mind losing packager status, he does say that he >> did not receive any email to the @redhat.com address about this >> ticket. >> >> It may be that the email was lost in a filter as somtimes happens. >> But maybe we're not sending out emails to the packagers? >> >> > So this may be a problem with how pagure recognizes 'users' it can expand > with @. If you notice in that ticket the account is not 'blue' or > highlighted. Contrast that with > https://pagure.io/find-inactive-packagers/issue/1436 where gotmax23bot is > expandable. > > What this means is that the pagure database knows the link between > gotmax23bot and an email address, but had no way of knowing armbru was an > actual user. I believe the Pagure database does not automatically link @ > with fas accounts so I expect we have a bunch of tickets which aren't > useful. > > > OK looking through the tickets, most of the ones I clicked on did not have 'accounts' that the backing pagure.io thought were expandable. I believe another method is going to be needed to get in touch with these individuals. -- Stephen Smoogen, Red Hat Automotive Let us be kind to one another, for most of us are fighting a hard battle. -- Ian MacClaren ___ 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: Inactive packager check for F38
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 after the final release, > > packagers who remain inactive will be removed from the packager group. > > (Note that pagure.io is one of the systems checked for activity, so > > commenting on your ticket that you're still around will prevent you > > from showing up in the second round.) > > > > If you have suggestions for improvement, look for the open feature > > issues[3] and file an issue in the find-inactive-packagers repo[4] if > > it's not there already. > > Just an FYI, I was talking to armbru about this ticket: > > https://pagure.io/find-inactive-packagers/issue/1181 > > Although he does not mind losing packager status, he does say that he > did not receive any email to the @redhat.com address about this > ticket. > > It may be that the email was lost in a filter as somtimes happens. > But maybe we're not sending out emails to the packagers? > > So this may be a problem with how pagure recognizes 'users' it can expand with @. If you notice in that ticket the account is not 'blue' or highlighted. Contrast that with https://pagure.io/find-inactive-packagers/issue/1436 where gotmax23bot is expandable. What this means is that the pagure database knows the link between gotmax23bot and an email address, but had no way of knowing armbru was an actual user. I believe the Pagure database does not automatically link @ with fas accounts so I expect we have a bunch of tickets which aren't useful. > Rich. > > > 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 > year. ### > > ### Found 812 users which show also no activity in mailing lists over > > the last year. ### > > ### Found 812 users which also show no activity in Bugzilla over the > > last year. ### > > > > As we approach > > > > [1] > https://docs.fedoraproject.org/en-US/fesco/Policy_for_inactive_packagers/ > > [2] > https://pagure.io/find-inactive-packagers/issues?tags=inactive_packager=Open > > [3] https://pagure.io/find-inactive-packagers/issues?tags=feature > > [4] https://pagure.io/find-inactive-packagers/new_issue > > > > > > -- > > Ben Cotton > > He / Him / His > > Fedora Program Manager > > Red Hat > > TZ=America/Indiana/Indianapolis > > ___ > > devel-announce mailing list -- devel-annou...@lists.fedoraproject.org > > To unsubscribe send an email to > devel-announce-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-annou...@lists.fedoraproject.org > > Do not reply to spam, report it: > https://pagure.io/fedora-infrastructure/new_issue > > ___ > > 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 > > -- > Richard Jones, Virtualization Group, Red Hat > http://people.redhat.com/~rjones > Read my programming and virtualization blog: http://rwmj.wordpress.com > Fedora Windows cross-compiler. Compile Windows programs, test, and > build Windows installers. Over 100 libraries supported. > http://fedoraproject.org/wiki/MinGW > ___ > 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 > -- Stephen Smoogen, Red Hat Automotive Let us be kind to one another, for most of us are fighting a hard battle. -- Ian MacClaren ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct:
Re: Inactive packager check for F38
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 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 systems checked for activity, so > > commenting on your ticket that you're still around will prevent you > > from showing up in the second round.) > > > > If you have suggestions for improvement, look for the open feature > > issues[3] and file an issue in the find-inactive-packagers repo[4] if > > it's not there already. > > Just an FYI, I was talking to armbru about this ticket: > > https://pagure.io/find-inactive-packagers/issue/1181 > > Although he does not mind losing packager status, he does say that he > did not receive any email to the @redhat.com address about this > ticket. > > It may be that the email was lost in a filter as somtimes happens. > But maybe we're not sending out emails to the packagers? 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. Does pagure.io not have accounts synced for everyone who is a Fedora packager ? With regards, Daniel -- |: https://berrange.com -o-https://www.flickr.com/photos/dberrange :| |: https://libvirt.org -o-https://fstop138.berrange.com :| |: https://entangle-photo.org-o-https://www.instagram.com/dberrange :| ___ 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: Inactive packager check for F38
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 removed from the packager group. > (Note that pagure.io is one of the systems checked for activity, so > commenting on your ticket that you're still around will prevent you > from showing up in the second round.) > > If you have suggestions for improvement, look for the open feature > issues[3] and file an issue in the find-inactive-packagers repo[4] if > it's not there already. Just an FYI, I was talking to armbru about this ticket: https://pagure.io/find-inactive-packagers/issue/1181 Although he does not mind losing packager status, he does say that he did not receive any email to the @redhat.com address about this ticket. It may be that the email was lost in a filter as somtimes happens. But maybe we're not sending out emails to the packagers? Rich. > 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 year. > ### > ### Found 812 users which show also no activity in mailing lists over > the last year. ### > ### Found 812 users which also show no activity in Bugzilla over the > last year. ### > > As we approach > > [1] https://docs.fedoraproject.org/en-US/fesco/Policy_for_inactive_packagers/ > [2] > https://pagure.io/find-inactive-packagers/issues?tags=inactive_packager=Open > [3] https://pagure.io/find-inactive-packagers/issues?tags=feature > [4] https://pagure.io/find-inactive-packagers/new_issue > > > -- > Ben Cotton > He / Him / His > Fedora Program Manager > Red Hat > TZ=America/Indiana/Indianapolis > ___ > devel-announce mailing list -- devel-annou...@lists.fedoraproject.org > To unsubscribe send an email to devel-announce-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-annou...@lists.fedoraproject.org > Do not reply to spam, report it: > https://pagure.io/fedora-infrastructure/new_issue > ___ > 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 -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones Read my programming and virtualization blog: http://rwmj.wordpress.com Fedora Windows cross-compiler. Compile Windows programs, test, and build Windows installers. Over 100 libraries supported. http://fedoraproject.org/wiki/MinGW ___ 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: Inactive packager check for F38
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 year. ### How many packages depend _only_ on people from this list? Eg are likely to be unmaintained ? Paul ___ 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
Inactive packager check for F38
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 systems checked for activity, so commenting on your ticket that you're still around will prevent you from showing up in the second round.) If you have suggestions for improvement, look for the open feature issues[3] and file an issue in the find-inactive-packagers repo[4] if it's not there already. 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 year. ### ### Found 812 users which show also no activity in mailing lists over the last year. ### ### Found 812 users which also show no activity in Bugzilla over the last year. ### As we approach [1] https://docs.fedoraproject.org/en-US/fesco/Policy_for_inactive_packagers/ [2] https://pagure.io/find-inactive-packagers/issues?tags=inactive_packager=Open [3] https://pagure.io/find-inactive-packagers/issues?tags=feature [4] https://pagure.io/find-inactive-packagers/new_issue -- Ben Cotton He / Him / His Fedora Program Manager Red Hat TZ=America/Indiana/Indianapolis ___ devel-announce mailing list -- devel-annou...@lists.fedoraproject.org To unsubscribe send an email to devel-announce-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-annou...@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue ___ 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
Inactive packager check for F38
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 systems checked for activity, so commenting on your ticket that you're still around will prevent you from showing up in the second round.) If you have suggestions for improvement, look for the open feature issues[3] and file an issue in the find-inactive-packagers repo[4] if it's not there already. 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 year. ### ### Found 812 users which show also no activity in mailing lists over the last year. ### ### Found 812 users which also show no activity in Bugzilla over the last year. ### As we approach [1] https://docs.fedoraproject.org/en-US/fesco/Policy_for_inactive_packagers/ [2] https://pagure.io/find-inactive-packagers/issues?tags=inactive_packager=Open [3] https://pagure.io/find-inactive-packagers/issues?tags=feature [4] https://pagure.io/find-inactive-packagers/new_issue -- Ben Cotton He / Him / His Fedora Program Manager Red Hat TZ=America/Indiana/Indianapolis ___ devel-announce mailing list -- devel-announce@lists.fedoraproject.org To unsubscribe send an email to devel-announce-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-announce@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
