http://qs1969.pair.com?node_id=660869

This is a public notice to the maintainer of the Text::Markdown module on CPAN. I have tried to contact you via email and rt.cpan.org as I would like to suggest merging this module with the code I have for Text::MultiMarkdown.

Text::MultiMarkdown passes the latest Markdown test suite (which Text::Markdown doesn't) and has also solved the bugs reported in Text::Markdown on rt.cpan.org.

Therefore I'd like to be able to maintain (and at some point merge) Text::Markdown.

Please get in contact with me via email / CPAN / here etc so that we can discuss this.

Replies are listed 'Best First'.
Re: Text::Markdown - unmaintained.
by sri (Vicar) on Jan 09, 2008 at 03:53 UTC
    You're now co-maint of Text::Markdown, feel free to merge the modules.
[reply]
      I know it's kind of off-topic, but I think this thread has everything that should make a Perl hacker feel good about the world.
      1. Someone who wants to contribute to and improve existing code
      2. Someone who wrote code in the past that was good enough to elicit interest from another who wants to help maintain and improve it
      3. An earnest, honest, respectful process for seeking this responsibility and privilege
      4. The new code passes the old code's own unit tests!
      5. An appeal to the community, who gladly offers it's help and advice
      6. The old hacker is found, and apprentices the new hacker
      OK, it's an embellishment, but I'm a believer in Perl (the community) even on the days when nothing seems to be working.

      I laughed, I cried... It moved me, Bob. :^D
[reply]
        a once nervous nelly is regular once more :)
[reply]
Re: Text::Markdown - unmaintained.
by castaway (Parson) on Jan 08, 2008 at 10:18 UTC
    You're better off contacting the module-authors list, who will, given sufficient proof of attempts to contact, and eveidence of patches etc, hand over maintenance of modules to worthy persons ;)

    http://www.nntp.perl.org/group/perl.module-authors/ (hmm, theres a way to send it an email somewhere.. but where?)

    C.

[reply]

      As far as I know, module-authors is generally intended for advice and discussion on CPAN modules (naming, etc.).

      Administrative issues should most certainly go to the modules at perl dot org mailing list instead. I suppose some of the PAUSE admins also read module-authors, though. The original poster has contacted the PAUSE admins by now.

      The usual way of dealing with such requests is that we demand some proof that some effort has been put into contacting the original author by various means. That certainly includes trying mail, google, and possibly the module's mailing list and may include a perlmonks or use.perl.org post. Once some time has passed without a reaction from the module author, we hand over co-maintenance permissions. This procedure is to make sure no CPAN authors are rid of their modules just because they went on a longer vacation or are moving house or somesuch.

      Cheers,
      Steffen

[reply]
[reply]

      I think bobtfish did that and his posting here is a *proof of attempts.* Sebastian Riedel is a known monk (sri) but looks like he's gone offline -- even his public website (oook.de) is offline.

      -derby
[reply]
        I'm not really offline, just very busy with other stuff atm.
        Also make sure to mention the word "Perl" in mails when trying to contact me, otherwise the chance it gets buried with the 1000 daily spam mails i get is quite high. ;)
[reply]

Back to Meditations