Beefy Boxes and Bandwidth Generously Provided by pair Networks
Don't ask to ask, just ask
 
PerlMonks  

Re: Howto abandon rights to a cpan module and stop getting bug reports for it?

by Corion (Pope)
on Apr 06, 2012 at 08:55 UTC ( #963793=note: print w/ replies, xml ) Need Help??


in reply to Howto abandon rights to a cpan module and stop getting bug reports for it?

The good way would be to find one of these bug-reporting users (as they, obviously, care about the module more than you do), and make them into the maintainer.

The bad way would be to simply delete the distribution from CPAN.

Update: It seems that RubyKat already has given maintainership to someone else and removed the file from CPAN. Then I'd release an updated version of the module that does not contain my email address, to obscure my authorship.


Comment on Re: Howto abandon rights to a cpan module and stop getting bug reports for it?
Re^2: Howto abandon rights to a cpan module and stop getting bug reports for it?
by Anonymous Monk on Apr 06, 2012 at 09:21 UTC

    What about pure unadulterated abandonment aka the Baby Moses option?

      The issue is that until a new version is uploaded, or the existing version deleted, your email address will appear in the POD and META.* files. I think deleting it is the least effective option (ignoring the social issues for a moment). Because if you just delete, existing users will never upgrade, and thus will always have your email as their contact point. Backpan would always have your version as the latest too.

      One option would be to post to the modules@perl.org mailing list asking someone to step up. If that produces nothing, try the following steps:

      The more socially conscious (and probably more effective) solution (assuming you are unable to find a new maintainer) would be to upload a new version. In the AUTHOR section or bugs reporting section place a note that the module is currently no longer being maintained nor supported, that support requests will go unanswered, and that if there is someone wishing to take over maintainership to please follow the steps outlined in the "TAKING OVER" section of the PAUSE documentation, with the understanding that you are granting your explicit permission for full priviliges to be transfered.

      If you know of a module that is a better solution you may point to it as well, and as final steps, mangle your email address to username-no-support-requests-please@cpan.org, and post another message to modules@perl.org announcing your resignation, so to speak, and your explicit intent to allow the transfer of authority on the module to the first person who asks for it.

      I'm no authority on PAUSE, but these steps seem like they would be socially acceptible, effective, and would possibly result in the module finding a new life with another maintainer.


      Dave

        I'm no authority on PAUSE, but these steps seem like they would be socially acceptible, effective, and would possibly result in the module finding a new life with another maintainer.

        They also seem an awful lot like work :)

        Seems like PAUSE should have an abandon distribution button, that stops forwarding rt.cpan.org bug reports to your @CPAN adress, removes you as maintainer, deletes the release from your CPAN directory, and moves it to A/AB/ABANDONED , and maybe adds a README-ABANDONED.txt

        If there is a PAUSE Custodial Account there could be a PAUSE Abandoned Modules Account (or Modules In Need Of Support, PAUSE MINOS )

Log In?
Username:
Password:

What's my password?
Create A New User
Node Status?
node history
Node Type: note [id://963793]
help
Chatterbox?
and the web crawler heard nothing...

How do I use this? | Other CB clients
Other Users?
Others perusing the Monastery: (18)
As of 2014-09-19 18:08 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    How do you remember the number of days in each month?











    Results (144 votes), past polls