#1553 i7z - nonresponsive maintainer
Closed None Opened 8 years ago by raphgro.

= phenomenon =
The maintainer of i7z is nonresponsive. I asked several times for response without succes, in a FTBFS bug¹ depending on other requests, as well per devel mailing list ². There's 1 open abrt bug³. Last real commit is 2013-08-06, afterwards mass rebuilds happens only. Last build is 2013-08-06 17:36:16 for f20, besides 2015-01-13 07:43:58 for epel7 with failure.

> python2 fedora_active_user.py --user fantom
FAS password for raphgro: 
Last login in FAS:
   fantom 2015-11-09
Last action on koji:
   Wed, 24 Feb 2016 package list entry created: xinput_calibrator in f25 by pkgdb [still active]
Last package update on bodhi:
   2015-05-08 21:36:54 on package poezio-0.9-0.1.dfd6042.fc21
Last actions performed according to fedmsg:
  - fantom updated the rules on a fmn irc filter on 2016-02-18 18:48:08 ()
  - fantom updated the rules on a fmn email filter on 2016-02-18 18:48:08 ()
  - fantom updated their email filters on 2016-02-18 17:01:08 ()
  - fantom updated their irc filters on 2016-02-18 17:00:40 ()
  - fantom's poezio-0.9-0.1.dfd6042.fc23 was deleted on 2015-12-11 14:05:07 ()
  - fantom's poezio-0.9-0.1.dfd6042.fc23 untagged from trashcan by oscar on 2015-12-11 14:05:06 ()
  - fantom posted "Le jour d'après" on 2015-12-05 17:20:45 ()
  - fantom updated the rules on a fmn irc filter on 2015-11-16 23:07:49 ()
  - fantom updated the rules on a fmn email filter on 2015-11-16 23:07:48 ()
  - fantom posted "Dockerized" on 2015-11-15 21:02:10 ()

= reason =
nonresponsive maintainer

= recommendation =
Please orphan i7z.

¹ https://bugzilla.redhat.com/show_bug.cgi?id=1263459
² https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/PDGVC32JDZDM32B56AZDRFGDQVA3PH62/
³ https://bugzilla.redhat.com/show_bug.cgi?id=1279250


[20:37:03] <RaphGro> whoowns i7z
[20:37:03] <zodbot> fantom
[20:37:07] <RaphGro> fasinfo fantom
[20:37:08] <zodbot> User: fantom, Name: Matthieu Saulnier, email: casper@casperlefantom.net, Creation: 2010-10-06, IRC Nick: Casper_v2, Timezone: Europe/Paris, Locale: fr, GPG key ID: 83288189, Status: active
[20:37:11] <zodbot> Approved Groups: gitspin-kickstarts packager fedorabugs cla_fpca cla_done cla_fedora ambassadors
[20:37:19] <RaphGro> seen #fedora-devel Casper_v2
[20:37:20] <zodbot> Casper_v2 was last seen in #fedora-devel 2 years, 13 weeks, 5 days, 19 hours, 38 minutes, and 14 seconds ago: <Casper_v2> nirik, it works perfectly

Just to be clear, there is actually no requirement at all that anyone be active on IRC. ;)

That said, they do appear inactive and so if they don't respond by the next fesco meeting, I would be +1 to orphan their packages.

(Note that the updated rules entries above are a false positive, we were updating everyone's filters then for some new rules and the script that does so incorrectly appears to be the user instead of an automated process. This is being fixed).

Replying to [comment:3 kevin]:

Just to be clear, there is actually no requirement at all that anyone be active on IRC. ;)

I know. But I want to provide all information that I could get so far. Guidelines say to try everything possible to reach the maintainer, before filing a FeSCo ticket. I try to do possible prework for you. ;)

That said, they do appear inactive and so if they don't respond by the next fesco meeting, I would be +1 to orphan their packages.

Their? Which packages else than i7z only? Please notice that the active user script gave activities in nearest past about other things done for Fedora community.

(Note that the updated rules entries above are a false positive, we were updating everyone's filters then for some new rules and the script that does so incorrectly appears to be the user instead of an automated process. This is being fixed).

I do not understand what that means.

Replying to [comment:4 raphgro]:

Replying to [comment:3 kevin]:

(Note that the updated rules entries above are a false positive, we were updating everyone's filters then for some new rules and the script that does so incorrectly appears to be the user instead of an automated process. This is being fixed).

I do not understand what that means.

This mean that the fedora_active_user.py output lines you pasted which contains "fantom updated the rules on a fmn" for date 2016-02-18 are false positive. They mean the user has not actually updated the filters but some script has updated every FAS user's filters on that day. So we should not count that fantom user was active recently.

Well, I heard from Matthieu 2 weeks ago on #fedora-devel-fr. I'll try to ping him afk.
+1 to switch PoC for i7z and 7kaa to raphgro right now, but orphaning all of his packages seems a bit extreme for now.

Replying to [comment:6 hguemar]:

Well, I heard from Matthieu 2 weeks ago on #fedora-devel-fr. I'll try to ping him afk.
+1 to switch PoC for i7z and 7kaa to raphgro right now, but orphaning all of his packages seems a bit extreme for now.

i7z: I can do an hotfix to close still open bugs, after the package got properly orphaned. There's an user waiting in the main bug. But I do not have interest to keep that package as maintainer after bugs got fixed.

7kaa: There was a pong in one bug from the maintainer and he promised to fix soonish (next week lately). I'm already co-maintainer for this package.

Dear Maintainers, Fedora Developpers.

I'm sorry to informe you that I have no time anymore to take care of my packages for the Fedora Projet. I orphan i7z following the process, and I will find a solution for my other packages.

Fedora was for me a great experience and I wish come back when I will have more time.

Best regards

Replying to [comment:8 fantom]:

Dear Maintainers, Fedora Developpers.

I'm sorry to informe you that I have no time anymore to take care of my packages for the Fedora Projet. I orphan i7z following the process, and I will find a solution for my other packages.

Hi,
thanks for your feedback. It's always sad to see maintainers as leaving.

As promised, I'll do at least the hotfix to close all open bugs for the i7z package. This ticket can be closed, please feel free to reopen if there's still an issue.

Login to comment on this ticket.

Metadata