On 12 Jan 2007, at 15:06, Smylers wrote:
If your hunch turns out to be correct then your service (or whatever)
will turn out to be more useful than the existing one. People will
start using it. At that point in can be blessed with more 'official'
status. For example, consider JJ's Perldoc project: it's something
that
he did, and is now running 'officially' as perldoc.perl.org.
Sure - I'm not suggesting anyone else should do this - just floating
an idea.
I guess there are essentially three categories of module
1 active, maintained
2 actively used, abandoned
3 not used, not maintained
It'd be nice to be able to weed out some of the modules in category 3
and identify cat 2 modules with a view to flagging them as abandoned
so that when/if a new maintainer came along the takeover processes
could be fast tracked.
Because in your experience of the past week or so the current
process is
too slow?
Because it's possible I guess. The process of identifying abandoned
modules could start before there was a volunteer to take over.
I'm not entirely sure what problem you're trying to solve here. But
that's largely irrelevant -- because however good your idea is,
there's
bound to be somebody in the Perl community questioning it or objecting
to it! So don't wait for approval: just do it, whatever "it" is, then
show folks.
Good luck!
Thanks :)
--
Andy Armstrong, hexten.net
