Suggest taking ownership of your hack...
|Reported by:||markm||Owned by:||Lucas Eisenzimmer|
I saw that you are 'retiring' from this hack - and I would be willing to take it over for a while.
I asked on the mailing list what the process is (see the thread at: https://lists.trac-hacks.org/pipermail/th-users/2009-March/000009.html )
In the thread Michael Renzmann writes:
- Open a ticket for the hack in question, ask about it's maintainership
status and tell the audience that you'd be willing to take over maintainership. Then sit back and wait for at least two weeks, to see if the author of the hack replies.
2a. If the author replies, he is to decide how to proceed. He could deny
your request, ask us to give you read/write permission for the hack in the repository or even pass (maintainer|owner)ship to you.
2b. If the author does not reply within the given time frame, contact one
of the admins. They will check the status quo, probably try again to get in contact with the author, and eventually decide on your request. In most cases you would be granted (maintainer|owner)ship of the hack in question if its development seems stalled and if neither the original author nor any contributor can be contacted in a reasonable timeframe.
One of the things I would like to enable in the hack is integration of python library lxml for working with XSLT rather than using the external applications. Many of the issues seem to be people having problems setting up the dependencies.
Though if you have other ideas for how the plugin should work - feel free to let me know (if you would like me to take it over).