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 Anonymous Monk
on Apr 07, 2012 at 22:08 UTC ( #963949=note: print w/ replies, xml ) Need Help??


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

I just installed Statistics::Sequences, and watching the install process I noticed that Math::Cephes is an abandoned module.

When the installation was finished, I went to investigate what was up with Math::Cephes. It was immediately obvious what happened, as I remember when Randy Kobes died I seen news about it. I knew his name as I normally use the CPAN interface at UWinnipeg.

I think it would be nice if someone could at least alter the POD for packages that Randy Kobe "abandoned", to mention that he is no longer with us.


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 BrowserUk (Pope) on Apr 07, 2012 at 23:00 UTC

    Seems like the solution would be to have a timeout on CPAN modules. If the designated owner didn't log-on to CPAN within some time period, an email is sent to their registered PAUSE email account. If no response is received after some period, the module gets flagged as abandoned and the first person to register interest get maintainership.

    For time periods I'd probably go with something like 6-months and one month.


    With the rise and rise of 'Social' network sites: 'Computers are making people easier to use everyday'
    Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
    "Science is about questioning the status quo. Questioning authority".
    In the absence of evidence, opinion is indistinguishable from prejudice.

    The start of some sanity?

      It'd be even better if CPAN even allowed a "default trust" model that has been so successful on the internet. I'd flag all of my modules as "default trust" so anybody who felt like I wasn't doing a good enough job of maintaining my module could upload a new version.

      Add to that various time-outs so if I never respond to new uploads then those who do the work of uploading can get ownership power over the module name(s).

      Heck, let me set the time-outs. How long before a non-author upload becomes official and gets indexed. How long after I upload a new version of a module (or even "refresh" a module as "still up-to-date") before non-author uploads can become official and get fully indexed. How long before a new uploader is automatically declared an authorized maintainer (and thus can set their own time-outs or approve others' uploads).

      If I don't configure a specific time-out for a module, then that time-out wouldn't apply to it (CPAN would behave as it does now -- valuing ownership far above contribution and discouraging collaboration).

      Though, I'd prefer to require a new version be uploaded and not allow an empty declaration of "still up-to-date". But I suspect allowing the latter would be more successful, at least at first.

      - tye        

        I thought anyone can upload a new version. It just gets marked as "UNAUTHORIZED" in red on search.cpan.org

        Besides, there is an existing process for taking over an abandoned module. This is a separate issue from the one brought up by the OP.

        It'd be even better if CPAN even allowed a "default trust" model ...

        I suspect that that would require long and wide-ranging discussions amongst CPAN authors; would probably require the implementation and validation of various checks and balances; and could conceivably have knock-on affects upon corporate views and policies with regard to CPAN. Five years from now you might finally reach a majority consensus, and all that would be left to do is argue about who is going to implement it; and who is going to fund that implementation.

        On the other hand, the timeouts could probably be implemented by one person over a weekend and -- as it only requires authors to log in once every six months; or respond to an email once every six months -- should be sufficiently uncontroversial that it wouldn't raise objections.


        With the rise and rise of 'Social' network sites: 'Computers are making people easier to use everyday'
        Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
        "Science is about questioning the status quo. Questioning authority".
        In the absence of evidence, opinion is indistinguishable from prejudice.

        The start of some sanity?

Log In?
Username:
Password:

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

How do I use this? | Other CB clients
Other Users?
Others studying the Monastery: (6)
As of 2014-07-31 06:41 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    My favorite superfluous repetitious redundant duplicative phrase is:









    Results (245 votes), past polls