How about adding a "nextofkin" attribute to META.yml, say? The value of the nextofkin attribute might be a list of CPAN IDs and/or email addresses of people who have agreed to inherit your module should you die or become inactive. Ideally, at least one of the nextofkin should physically know the module owner, so that, in the event of bouncing emails, an email to the nextofkin will establish what has truly happened to the inactive module author. Not as much fun as "I think not" Descartes jokes, admittedly ;-) http://nntp.x.perl.org/group/perl.module-authors/927
/-\ http://personals.yahoo.com.au - Yahoo! Personals - New people, new possibilities! Try Yahoo! Personals, FREE for a limited period!