Beefy Boxes and Bandwidth Generously Provided by pair Networks
good chemistry is complicated,
and a little bit messy -LW

comment on

( #3333=superdoc: print w/replies, xml ) Need Help??
I think you are free to put your "will" everywhere you like and think it'll be found.

IMHO from a general legal and organizational point of view, it should be somehow like and near the licence information in your module.

Different people will want to handle it differently on a module's basis (competence varies, a DBI expert might not be the best to handle a Tk module) and general schemes would be nice (like hypothetical "in case of longer absence the Saints of PerlMonk should poll" or "the most depending CPAN authors should decide").

BUT from a practical view people are reluctant to talk about their own death, so hiding it in Makefile or Meta sounds more feasible.

In the end it should be somewhere where the CPAN admins can easily retrieve and handle it.


And "absence" should be defined, being 10 years coma or going missing in an Asian land war (freely citing Brian d Foy) are not much better.

Probably all of this is better handled by an institutionalized fork and branch technique... ?

Cheers Rolf
(addicted to the Perl Programming Language :)
Wikisyntax for the Monastery FootballPerl is like chess, only without the dice

PS: In case of my own death, I want all my PM posts to be edited and translated to Japanese Haikus. ;-)

In reply to Re: Delegating responsibility of one's CPAN distributions by LanX
in thread Delegating responsibility of one's CPAN distributions by stevieb

Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post; it's "PerlMonks-approved HTML":

  • Are you posting in the right place? Check out Where do I post X? to know for sure.
  • Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
    <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
  • Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
  • Want more info? How to link or How to display code and escape characters are good places to start.
Log In?

What's my password?
Create A New User
Domain Nodelet?
and the web crawler heard nothing...

How do I use this? | Other CB clients
Other Users?
Others scrutinizing the Monastery: (1)
As of 2023-06-06 06:02 GMT
Find Nodes?
    Voting Booth?
    How often do you go to conferences?

    Results (26 votes). Check out past polls.