As Matt said, “Until then, POD is it." I just had to call the project something and mdoc.io was the first thing that came to mind, and hadn’t gotten Matt’s reply yet.
What I’ve got for reference for the pod format is: http://perldoc.perl.org/perlpodspec.html and possible extensions via: ftp://ftp.ora.com/pub/labs/pseudopod.html is this what you guys have been using? I just want to make sure we’re all on the same page. It was also suggested that a source based system would be better, like doxygen. I’m not very familiar with doxygen’s capabilities, so will it be able to handle features and changes which affect multiple documents or give more lengthy discussions and examples for people using openssl apps? and as I’m tinkering more with the demo I’m making, I’m starting to see possibilities. The people using the documentation should be helping to improve it. Either actively or passively. Active = going through and submitting patches, flagging areas that need attention Passive = browsing/using documentation, so we can tell what people are most interested in so that we can use real data to target areas most in need of improvement. On May 9, 2014 at 2:33:38 PM, Salz, Rich ([email protected](mailto:[email protected])) wrote: > Please, not mdoc. It doesn't offer any particular feature it's just different. > > > -- > Principal Security Engineer > Akamai Technologies, Cambridge, MA > IM: [email protected]; Twitter: RichSalz > > ?zt?,????-??i??0Š^??%??z�????X??????^??%u??????Z+???f?y???????f???h??)z{,?? ______________________________________________________________________ OpenSSL Project http://www.openssl.org Development Mailing List [email protected] Automated List Manager [email protected]
