On 08/07/05 13:53 -0500, [EMAIL PROTECTED] wrote: > > > > -----Original Message----- > > From: nadim [mailto:[EMAIL PROTECTED] > > Sent: Friday, July 08, 2005 3:44 PM > > To: inline@perl.org > > Subject: Re: Inline at OSCON > > > > Hi, > > > > IMHO, the best you can do it give up ownership of this module > > to someone who will have time for it. This might sound > > drastic but I believe it would be best for an excellent module.
There is really not a need for me to turn over the module to any one person. I can't really think who that person would be. Better to open it up to everyone who can possibly contribute. I think would rather take a more "Larry" position of Inline Designer, and let a group of porters do most of the work. I still do have a vision for Inline. > I'm not sure it needs to be that drastic - a middle ground would be to > put the code repository somewhere accessible and open things up to a > couple more committers and releasers. Brian can still maintain > "blessing" authority if he wants to IMO. I think that will be the resultant course of action. I'll put the code on a FreePAN svn server, handout some commit bits, and start up a wiki for planning. For the time being I'll act as a CPAN release manager but later on I can share that role with someone else. Cheers, Brian BTW, I could possibly envision a test first rewrite of Inline that basically brings the module to where it is today with a few use cases made nicer. Inline was my first module, and it kind of does too much in some ways. That's not necessarily bad, but i would like some annotated test coverage for all that cruft.
