Let's say... it's a race! I'm the snail and you've swung the starting flag. 'll start crawling, and if a tortoise or a hare jump in too, I won't mind.
It's doable for me, just don't have much experience: in my long programming career, I have uploaded exactly one module to CPAN. And it is much smaller then Padre! At some point in the next couple of weeks I'll figure out what has to be done for fixing up and packaging up Padre. I imagine I'll have to fork the github project, put in some pull requests. Does packaging a CPAN release mean I'll also need to get co-maintainership from Pause? Not exactly what I want to take responsibility for, but I will if need be... the thing is I'm not at all familiar with Padre, just wanted to prevent duplication of effort at install time, and if I become listed as a maintainer then folks may expect much more than I can provide! _______________________________________________ Padre-dev mailing list Padre-dev@perlide.org http://mail.perlide.org/mailman/listinfo/padre-dev
