Re: PDF::Template needs a new maintainer

If no one else is going to shout "here!", I'd raise my hand.

I've done quite a bit of low level hacking in PDF (as well as its cousin PostScript), so this might be a good fit... (Actually, I've written my own PDF lib in Perl (that was before PDF::API2 was ready for prime time) -- unfortunately, it's proprietary... (paid work)). Also, I have access to virtually all major unix platforms, so I could at least make sure the modules build/work on those.

OTOH, I'm entirely new to maintaining CPAN modules... so I'm wondering, what does it entail beyond hacking at the sources?

Comment on Re: PDF::Template needs a new maintainer

Replies are listed 'Best First'.
Re^2: PDF::Template needs a new maintainer by xdg (Monsignor) on Jan 28, 2007 at 15:23 UTC
You might want to write to jkeenan1, who is leading an effort to mentor people on taking over maintenance of modules. See Phalanx Phoenix: Mentored Maintenance of CPAN Modules. While that is a face-to-face effort, primarily, there is also a mailing list and Jim has given some talks on this topic at YAPC and other places that he might be able to share with you. If you're new to CPAN modules entirely, I suggest reading some of the Tutorials as a good starting point (e.g. How to make a CPAN Module Distribution). Sam Tregar's book Writing Perl Modules for CPAN is another good starting point. -xdg Code written by xdg and posted on PerlMonks is public domain. It is provided as is with no warranties, express or implied, of any kind. Posted code may not have been tested. Use of posted code is at your own risk.	[reply]
Re^2: PDF::Template needs a new maintainer by dragonchild (Archbishop) on Jan 28, 2007 at 18:23 UTC
In addition to xdg's excellent pointers, you might also want to look at my article on the subject. As for what's needed in this specific area, the biggest thing lacking is tests. When I took over PDF::Template 4 years ago, there was no easy way of testing PDFs. One of the reasons I was so interested in converting PDF::Template to use PDF::Writer as its engine is that writing tests for PDF::Template become much simpler (see how I wrote tests for Excel::Template as a good example). In the meantime, Test::PDF has been released to CPAN and would make a very good way to test PDF::Template or PDF::Writer. The most immediate need is to get off of the PDFlib v3 API and either onto PDF::Writer (best solution) or the PDFlib v6 API (better than nothing). After that, there's a number of directions you can go. Build in support for HTML-like tables. (The single-most requested feature). Move off of the XML templating format and to a TT-based format. (Fixes a bunch of design flaws and gets us out of the templating business and into the PDF-generation business) Make a bigger deal of the custom nodes feature. Add the ability to draw (second-most requested feature) As you have low-level PDF experience, this sounds like it might be a good fit. I'll /msg you my email and we can chat further. My criteria for good software: Does it work? Can someone else come in, make a change, and be reasonably certain no bugs were introduced?	[reply]


Perl-Sensitive Sunglasses
	PerlMonks