Hi Oli, Oliver Welter wrote:
I have now prepared to move the documentation to the new module as announced 2 weeks ago.I am unconsious about one thing:The "Guide" consisits of the XML Sources and the compiled pdf/html/ps version. What should we put into the "doc" module ? Only the sources or the final docs also ?My personal suggestion is:Guide: src only, compiled versions (pdf, html, chunked html) will move to the website, (in real and in cvs)HowTos: kept in cvs and copied to the website on checkout as already done
I would prefer to put all final docs into the doc/ area or all final docs on the website. If the final howtos are in doc/ then I would like to see the pdf/ps/html guide in the doc/ area too. One rule for all content.
Otherwise a chunked html version of the guide makes only sense for a web site so perhaps we should put all final content to the webserver - including the howtos.
So this means the docs module must only be checkedout from cvs by people who contribute to the docs. An UpToDate version of the guide is always available at the webpage
I think the major issue is to make the maintenance of a webserver as easy as possible. The most service outages in the last months were from wrong cronjobs. So perhaps it is the best idea to put all final content on the website. If a howto has no real "source code" (and all of our howtos have no source code today) then we should put them on www.openca.org/. doc/ would only contain the source and perhaps some makefiles (with some special targets).
To make it clear. I don't think so much about the generation of the guide. I think majorly about my webserver ;)
Michael -- _______________________________________________________________ Michael Bell Humboldt-Universitaet zu Berlin Tel.: +49 (0)30-2093 2482 ZE Computer- und Medienservice Fax: +49 (0)30-2093 2704 Unter den Linden 6 [EMAIL PROTECTED] D-10099 Berlin _______________________________________________________________
smime.p7s
Description: S/MIME Cryptographic Signature
