Got this from infrastructure trac - https://fedorahosted.org/fedora-infrastructure/ticket/938
CC'ing reporter, we should consider this at the next meeting
Isn't this covered by the Nonresponsive Maintainer(1) policy? Or am I missing something?
http://fedoraproject.org/wiki/PackageMaintainers/Policy/NonResponsiveMaintainers
Gah, I should have done more research. AWOL has already been declared (by spot) at http://www.redhat.com/archives/fedora-devel-list/2007-November/msg02343.html. We just need someone to mass-orphan his packages (some of which are important perl packages). I'll ping kevin about that.
Replying to [comment:2 jstanley]:
It's probably worthwhile to discuss what we should do with awol contributors accounts after they had their packages orphaned. I think in the past we've removed privileges in some cases (I remember when ignacio went awol we removed his sponsor status, and he had to apply for it again when he came back), but I don't think we've ever put forth any official policy on how to handle that.
He shouldn't own anything anymore, I took all his packages which no one else wanted. What does he still own?
He is listed on InitialCC for some fedora packages still. (Don't know if that matters at all).
He is owner on a number of EPEL branches of packages:
Fedora EPEL|perl-DBD-SQLite|Self Contained RDBMS in a DBI Driver|jpo||perl-sig,wtogami Fedora EPEL|perl-Error|Error/exception handling in an OO-ish way|jpo||perl-sig Fedora EPEL|perl-ExtUtils-CBuilder|Compile and link C code for Perl modules|jpo||perl-sig Fedora EPEL|perl-ExtUtils-ParseXS|Module and a script for converting Perl XS code into C code|jpo||perl-sig Fedora EPEL|perl-GD|Perl interface to the GD graphics library|jpo||perl-sig Fedora EPEL|perl-GDGraph|Graph generation package for Perl|jpo||perl-sig Fedora EPEL|perl-GDTextUtil|Text utilities for use with GD|jpo||perl-sig Fedora EPEL|perl-MLDBM|Store multi-level hash structure in single level tied hash|jpo|| Fedora EPEL|perl-Pod-Coverage|Checks if the documentation of a module is comprehensive|jp o||perl-sig Fedora EPEL|perl-Pod-Escapes|Perl module for resolving POD escape sequences|jpo||perl-sig Fedora EPEL|perl-Pod-Simple|Framework for parsing POD documentation|jpo||perl-sig Fedora EPEL|perl-Test-Builder-Tester|Test runner for Test::Builder testsuites|jpo||perl-s ig Fedora EPEL|perl-Test-Pod|Perl module for checking for POD errors in files|jpo||perl-sig Fedora EPEL|perl-Test-Pod-Coverage|Check for pod coverage in your distribution|jpo||perl- sig Fedora EPEL|perl-Text-Template|Expand template text with embedded Perl|jpo||perl-sig Fedora EPEL|perl-pmtools|A suite of small programs to help manage Perl modules|jpo||perl- sig
Did these get orphaned, or assigned to the Perl SIG?
They haven't yet.
I can ask the perl sig if anyone there wants them. Failing that we can bring up the matter in the next EPEL meeting and see if we can get them all taken care of.
Spot has agreed to take all these. Moved ownership to him. Closing this now..
Log in to comment on this ticket.