Beefy Boxes and Bandwidth Generously Provided by pair Networks
Clear questions and runnable code
get the best and fastest answer

Taking over broken subroutines??

by astaines (Curate)
on Aug 15, 2006 at 18:54 UTC ( #567538=note: print w/replies, xml ) Need Help??

in reply to Re^2: Upgrade-proofing overridden subroutines
in thread Upgrade-proofing overridden subroutines

There is an important issue which goes beyond Ovid's elegant solution. There should be a way to take over deceased modules. Text::CSV comes to mind. Is there any group who would be willing to arbitrate here? -- I would propose that a module could only be taken if the original developer does not reply for a certain period, say three months or six months. Is this a runner or are there insuperable copyright issues?

-- Anthony Staines

Replies are listed 'Best First'.
Re: Taking over broken subroutines??
by adamk (Chaplain) on Aug 16, 2006 at 14:13 UTC
    The team (mainly Brian Foy, Andreas and myself) have been handling this for years.

    Module takeover is handled on a case by case basis, with the general standard being "A number of contact methods tried a number of times over a number of weeks".

    You'll then be given co-maintainership.

    If the original author returns, they retain control.

    Often, they'll just hand you primary if you show an interest.

    But this is a solved problem.

Log In?

What's my password?
Create A New User
Node Status?
node history
Node Type: note [id://567538]
and all is quiet...

How do I use this? | Other CB clients
Other Users?
Others about the Monastery: (7)
As of 2018-03-23 01:44 GMT
Find Nodes?
    Voting Booth?
    When I think of a mole I think of:

    Results (287 votes). Check out past polls.