Another change I'm considering is doing away with the current documentation system in favour of using wiki.tmda.net for everything. The current system uses the ht2html.py template processor to generate static .html files that are packaged in the tarball and uploaded to www.tmda.net. The problem with this is that the templates are kept in CVS which make them a pain to update, because not just anyone can do it, so the end result is that the docs never get updated. I'd like to see a more community oriented approach to maintaining the documentation. In a few months I might have even less time to devote to this project (hard to believe, eh?) so a self-maintaining system seems like the way to go.
So unless there are objections, I'll work on stuffing the current documentation into wiki.tmda.net and then it can evolve from there. I'll remove the htdocs/ files from the distribution and so the wiki will then become the definitive source for TMDA documentation. The one thing this new system would lack is the mirroring system, since a wiki can't be mirrored like a set of .html files can. But I don't really think this is a problem - it's not like the TMDA site sees that much traffic anyway. I will probably separate the tarballs out from the wiki so that the code can be mirrored, but the documentation will no longer be. Thoughts, questions, objections? _________________________________________________ tmda-workers mailing list ([email protected]) http://tmda.net/lists/listinfo/tmda-workers
