We could always check the packages and update those are not maintained (I do that once in a while but I missed some).
I do not think that this is fit for giving people unmaintained packages really, as it is meant as a summer activity.
I like the OpenDocument idea alot!
A new OpenDoc package would bring up the same problem... Who will maintain it after the summer ends and the cold time of autumn and winter sends bug reports and feature requests?
As another point: I played with the topic already while looking for a docbook2odt converter. I fear, it will be a hard task to write a full-featured OpenDoc package including docs in the given time. An if it is not full-featured, look at the section before...
What to propose instead? What about the request for a Wiki for DocBook? This idea isn't to PEAR-specific, improving the chance to get someone interested and the chance to be accepted by Google.
BTW: By accident, i find such a Wiki implement in Python this week (
http://kvota.net/sarma/list.cgi ). While playing with it, i think the real pain for such a project would be not the wiki2db thing, but designing an usable interface looks like a challenge.
--
Alexander Merz
http://www.alexander-merz.com