Ovid wrote:
Hi all,
No names, but if you happen to be sitting on a module which other people
depend on and you're not going to fix bugs, give up the module, offer someone
co-maintainership or figure out *something* which gives users a way out. I
realize that not everyone has a pile of
On Sep 7, 2006, at 9:08 AM, Mark Stosberg wrote:
I say: If you are care about a module's maintenance, start acting like
you own it, being considering that others, especially the current
maintainer, may feel the same way.
Nice. Worthy of a use.perl.org post so others can see it. Maybe
Title: RE: Take back your modules! (was: Re: Give up your modules!)
On Sep 7, 2006, at 9:08 AM, Mark Stosberg wrote:
I say: If you are care about a module's maintenance, start
acting like
you own it, being considering that others, especially the current
maintainer, may feel
Andy Lester wrote:
On Sep 7, 2006, at 9:08 AM, Mark Stosberg wrote:
I say: If you are care about a module's maintenance, start acting like
you own it, being considering that others, especially the current
maintainer, may feel the same way.
Nice. Worthy of a use.perl.org post so others can
Agreed. JFDI. It puts everyone (users, you, the real maintainer) in
a tough position when you just take over someone's module without
having provided any code. Maybe you want to work on it, but after you
realize what that actually entails you'll become a bad maintainter
too. That doesn't solve
* Jonathan Rockway [EMAIL PROTECTED] [2006-09-07 20:55]:
Maybe you want to work on it, but after you realize what that
actually entails you'll become a bad maintainter too. That
doesn't solve any problems.
/me hides in shame
Regards,
--
Aristotle Pagaltzis // http://plasmasturm.org/
David Landgren wrote:
Andy Lester wrote:
On Sep 7, 2006, at 9:08 AM, Mark Stosberg wrote:
I say: If you are care about a module's maintenance, start acting like
you own it, being considering that others, especially the current
maintainer, may feel the same way.
Nice. Worthy of a
