On 8/14/06, James E Keenan <[EMAIL PROTECTED]> wrote:
In the subsequent discussion, people suggested that we need the following: 1. Place for current module authors/maintainers who wish to transfer maintenance of certain modules to so indicate. 2. Place for people who are willing to take over maintenance of CPAN modules to so indicate. 3. (And this is the delicate part ...) A way to encourage authors/maintainers whose code needs transfer to a new maintainer to effect that. My hunch is that if we get (1) and (2) up and working, it will be easier to accomplish (3). jimk
Is not this mailing list both 1 and 2? Without some kind of centralized subscription service its difficult to come up with a business case for setting up systems to satisfy the mandate of 3. OTOH, a centralized subscription service that guarantees maintenance and support of modules downloaded therefrom may or may not fly. I don't think it would work; at least not any better than activestate's vetting of what becomes a PPM. -- David L Nicol all your grammar nit are belong to us
