#861 Cleanup of maintainers with bugzilla account issues
Closed None Opened 7 years ago by kevin.

Fedora uses our pkgdb to keep track of package ownership and initialcc information.

This information is then synced with bugzilla.redhat.com to make sure components have the right owner emails and initialcc's on bugs.

Currently we have 25 maintainers listed in pkgdb as either owner or initialcc on packages where they do not have a bugzilla email account. This causes currently 120 packages to error out setting these things, likely meaning maintainers don't see bugs from them as much as they should.

This state could have happened any of the following ways:

  • They changed their FAS account email, but didn't change their bugzilla email.

  • They changed their bugzilla email so it no longer matches their FAS email.

  • They removed their bugzilla account.

I mailed all users in this state on 2012-06-04 and one user (with 23 of the packages) on 2012-05-24

I'd like to ask FESCo to ok my removing those users from owner (and thus orphaning some packages) and initialcc where they appear until they can fix these issues.


FESCO agreed that Kevin will re-contact users, and we will address this after giving them one more week.

Affected maintainers:

{{{

bernie@codewiz.org
braoru@gmail.com
caillon+fedoraproject@gmail.com
caniszczyk@gmail.com
choeger@umpa-net.de
christian@eide-itc.no
cmaiolino@redhat.com
deadbabylon@googlemail.com
deleteme@mailinator.com
fedora@mostafadaneshvar.com
gareth.l.john@gmail.com
gspurgeon@dageek.co.uk
imlinux+fedora@gmail.com
jfch@jagda.eu
metamel@gmail.com
peter@peterscheie.com
pnasrat@gmail.com
pzhukov@ru.ibm.com
rui.he@oracle.com
viji@linux.com
zack@cerza.org
}}}

I just mailed them all again and said action would be taken 2012-06-18.

Packages that will be orphaned:

{{{
bernie devtodo
bernie monkeysphere
braoru jboss-ejb3-ext-api
caillon drwright
caillon fedora-bookmarks
caillon gnome-hearts
caillon gnuchess
caillon iso-codes
caillon mozilla-filesystem
caillon xboard
caillon xchat
choeger offlineimap
gljohn gtkmm-utils
gljohn paperbox
landgraf aunit
landgraf florist
landgraf gnatcoll
landgraf gprbuild
landgraf jbig2dec
landgraf matreshka
landgraf mupdf
landgraf sdcv
landgraf xmlada
landgraf zeromq-ada
landgraf zyGrib
mchua education-bookmarks
mmcgrath ytalk
peterscheie k12linux-quick-start-guide
svahl devilspie
svahl kcoloredit
svahl kgrab
svahl kiconedit
svahl konq-plugins
svahl koverartist
svahl ksig
svahl libzip
svahl polyester
svahl polyester3
svahl stalonetray
zmc dogtail
}}}

than in the kde sig has already agreed to take ownership of the kde related packages.

It seems to me that if you want packages orphaned then the non-responsive maintainer procedure should be followed. You're planning to take people's packages away from them after two emails and 14 days. According to http://fedoraproject.org/wiki/Policy_for_nonresponsive_package_maintainers it normally takes at least four emails to the maintainer (through Bugzilla), one email to the devel list, and 24 days in total before packages are orphaned. Is this problem really so severe that the packages need to be orphaned faster than that?

Well, I have actually mailed them 4 times (and one maintainer 5).

The problem is bad in my opinion because:

  • Any bugs filed by our users on these packages are currently going to old/possibly inactive email addresses. So, no one is listening at all on them.

  • Any issues requiring maintainer coordination are likely going unanswered.

  • This script runs every hour and all the failures have actually been noted by the bugzilla.redhat.com maintainers. It would be nice for them to clean these up. Also, it mails out these failures to me and Toshio every hour.

FYI, the list for owners of packages is down to:

{{{
braoru
gljohn
landgraf
mchua
mmcgrath
svahl
zmc
}}}

Oh, as a side note, in the past we had this script mail everyone who had issues in it... but we got a few complaints about that, and a number of these folks not fixing things. So, a number of these may have seen many emails on this subject and still not fixed it.

I'm not sure when we changed it from mailing everyone to just mailing admins, but I can check.

Having the script send a mail to the person who can actually fix the problem seems like a good idea. The only reason I can see why somebody would complain about that would be if they actually wanted the addresses to be different. Wouldn't the best solution be to allow that for everyone, given that it's apparently allowed for some people?

Well, sending it to the folks that are broken hasn't caused them to fix it in the last year or two. :(

I suspect some of them it hits there spam filter, or they decide they don't want to deal with it and just drop those emails, or their fas email is now invalid and they don't get it, or...

Everyone could have a different address, but currently the process is MANUAL. They have to request it and we have to update a lookup table. Some discussion has happened around adding a field to the account system for bugzilla account, but so far no one has stepped up to implement it.

Well, I haven't seen what those emails looked like. Perhaps some people thought it wasn't really a problem, and they wanted the addresses to be different? Has it been more than two weeks since you first threatened to orphan their packages?

Following the non-responsive maintainer policy would amount to posting to the devel list tomorrow and waiting ten more days. Is that really too much to ask?

By the way, I will pick up at least some of Pavel Zhukov's (Landgraf's) packages if they are orphaned, but I'd prefer to give him the prescribed 24 days to respond first.

We could surely wait longer, I just don't feel it's worth it in this case as these issues have been ongoing for a long time.

Do you mean that all of the remaining packagers have had this problem for a long time? It's not possible that some of them changed their addresses recently? Some time after the script stopped sending mail to them perhaps?

Replying to [comment:10 rombobeorn]:

Do you mean that all of the remaining packagers have had this problem for a long time?

Yes, I think thats the case. I'll try and find info on when that email was going directly to them.

It's not possible that some of them changed their addresses recently?

Sure, but if they no longer use or check the one in the Fedora account system, how can we get a hold of them?
Note that their address would have been vaild in the last 8 months, because they would have had to change their password/ssh keys when we asked them to do this.

Some time after the script stopped sending mail to them perhaps?

Sure. It could be. It could also be that they closed the account they have listed in fas and no longer use it.
They might have moved to a cabin in the woods. We can't know. :)

All that we know now is that their email in fas doesn't match up to any existing bugzilla account, and that for most of these, the problem has been happening a long time. (I will try and get you more exact info).

Anyhow, I don't know that we are adding much here, so I will stop and FESCo can discuss tomorrow.

Replying to [comment:11 kevin]:

Sure, but if they no longer use or check the one in the Fedora account system, how can we get a hold of them?

According to the non-responsive maintainer policy you should post to the devel list and ask if anyone knows how to contact them. Someone might know another address. Someone might know a phone number. They might even be subscribed to the list themselves with a working address (but might not be interested in reading FESCo meeting schedules or minutes, and therefore not have noticed that this is going on).

I happen to know that Pavel Zhukov's Bugzilla account is pavel in the zhukoff domain with a top-level domain of net. That address was valid on 2012-04-08, as he replied to an email I sent that day. He wrote a comment in Bugzilla on 2012-05-20. He hasn't yet reacted to an email I sent to alert him to this issue, but that was only a week ago. Sure, he might have disappeared in the last four weeks, but he might also return from that cabin in the woods tomorrow and start to catch up on email.

AGREED: nirik will mail a list of affected maintainers to the devel
list asking for anyone to contact them. nirik will mail them
directly to their fas account again today. Then we wait and process
any that didn't fix things by july 2nd on july 2nd

Mailed affected users fas accounts again.
Mailed devel list.

Current affected users and packages:

fas name / real-name (if public) / email:

{{{
aleksey2005 'Popkov Aleksey' aleksey@oscada.org.ua
bernie 'Bernie Innocenti' bernie@codewiz.org
caillon 'Christopher Aillon' caillon+fedoraproject@gmail.com
caniszczyk 'Chris Aniszczyk' caniszczyk@gmail.com
choeger 'Christoph Höger' choeger@umpa-net.de
chreide 'Christian Eide' christian@eide-itc.no
cmaiolino '' cmaiolino@redhat.com
svahl 'Sebastian Vahl' deadbabylon@googlemail.com
arbiter '' deleteme@mailinator.com
lashar 'Mostafa Daneshvar' fedora@mostafadaneshvar.com
gljohn 'Gareth John' Gareth.L.John@gmail.com
dageek 'Gavin Spurgeon' gspurgeon@dageek.co.uk
mmcgrath 'Mike McGrath' imlinux+fedora@gmail.com
jfch2222 'Jan F. Chadima' jfch@jagda.eu
mchua 'Mel Chua' metamel@gmail.com
peterscheie 'Peter Scheie' peter@peterscheie.com
pnasrat 'Paul Nasrat' pnasrat@gmail.com
rhe 'Rui He' rui.he@oracle.com
viji 'Viji V Nair' viji@linux.com
zmc '' zack@cerza.org
}}}

We will be orphaning packages owned by people in this state on
2012-07-02, so if you know of a way to contact them, please do so
before then.

Packages with owners in the above list that will be orphaned:

{{{
aleksey2005 lightsquid
aleksey2005 openscada
bernie devtodo
bernie monkeysphere
caillon drwright
caillon fedora-bookmarks
caillon gnome-hearts
caillon gnuchess
caillon iso-codes
caillon mozilla-filesystem
caillon xboard
caillon xchat
choeger offlineimap
svahl devilspie
svahl kcoloredit
svahl kgrab
svahl kiconedit
svahl konq-plugins
svahl koverartist
svahl ksig
svahl libzip
svahl polyester
svahl polyester3
svahl stalonetray
gljohn gtkmm-utils
gljohn paperbox
mmcgrath ytalk
mchua education-bookmarks
peterscheie k12linux-quick-start-guide
zmc dogtail
}}}

Chris Aillon left RH some time ago, he may not maintain those packages. fedora-bookmarks and mozilla-filesystem can go to mozilla team (gecko-bugs-nobody@fedoraproject.org).

This appears not to have occurred. I'd be willing to pick up some of them if needed.

Yeah, I miscalculated and didn't realize that I would still be on vacation on the 2nd. ;)

I'll send a final plea today and orphan things/remove people monday.

Cool, I'll have a look at the list when I get back and grab what I care about that's not claimed. Thanks!

Mailed privately everyone still on the list as of today again.

Mailed devel list with a list of pending users and packages that will be orphaned monday.

kevin, please close the ticket when you orphan the packages.

This is done. SQL for doing this in case someone other than me needs to do it next time:
{{{

-- Find non-EOL collections
select id from collection where statuscode != 9

(8, 13, 24, 27, 28)

-- owner (check and then orphan)
select p.name, pl.* from packagelisting as pl, package as p where p.id = pl.packageid and owner = 'peterscheie' and collectionid in (8, 13, 24, 27, 28) order by name, collectionid;

update packagelisting set owner = 'orphan', statuscode = 14 where id in (select pl.id from packagelisting as pl where pl.owner = 'peterscheie' and pl.collectionid in (8, 13, 24, 27, 28));

-- acls (check for and then remove wathbugzilla)
select * from personpackagelistingacl where id in (select id from personpackagelistingacl where personpackagelistingid in (select id from personpackagelisting where username = 'peterscheie') and statuscode = 3 and acl = 'watchbugzilla');

update personpackagelistingacl set statuscode = 13 where id in (select id from personpackagelistingacl where personpackagelistingid in (select id from personpackagelisting where username = 'peterscheie') and statuscode = 3 and acl = 'watchbugzilla');
}}}

The following packages were orphaned by this:

  • devilspie
  • dogtail
  • gtkmm-utils
  • k12linux-quick-start-guide
  • kcoloredit
  • kgrab
  • kiconedit
  • koverartist
  • ksig
  • libzip
  • polyester
  • polyester3
  • python-djblets
  • python-flask
  • python-werkzeug
  • stalonetray
  • tasks

Login to comment on this ticket.

Metadata