How about converting the document to something like Docbook, allowing public svn access to the repository directory tree where the documentation is kept, and using a Subversion hook to require an approver to accept any changes?
This is what the Subversion project is using for their documentation, and IMO it works extremely well. People can choose between the daily build of the PDF version or the daily build of the HTML version. It also allows people to correct some of the more egregious errors quickly. As Docbook is just plain text, it's pretty quick and easy for anyone to edit. BTW, there's a thread in zenoss-dev about this too: http://community.zenoss.com/forums/viewtopic.php?t=2692 simon wrote: > Hi Roger, > > actually there is currently no ideal way to contribute to the documentation. > We are certainly open for suggestions, what would you like to see ideally for > you to contribute to the docu? > A HTML based commenting system is in the works and should be available in the > near future. Until then it would be great if you would submit your changes > into the ticketing system to be found under > http://dev.zenoss.com/trac/newticket (user: zenoss password: zenoss) you can > actually just submit all of it into one ticket. If you want more info on how > to create a ticket please see http://dev.zenoss.com/trac/wiki/HowToAddTicket > > bye, > Simon -------------------- m2f -------------------- Read this topic online here: http://community.zenoss.com/forums/viewtopic.php?p=9447#9447 -------------------- m2f -------------------- _______________________________________________ zenoss-users mailing list [email protected] http://lists.zenoss.org/mailman/listinfo/zenoss-users
