Hi Oli, Oliver Welter wrote:
new/removed files when we work on the guide - so maintaining this chunk version might get hard - but I dont have a real solution for this, as website and doc are kept in the cvs....
This is not so hard at all: cd doc/guide/ change something compile it cd ../ cvs update -dP guide > erg.txt vi erg.txt --> here you have to do the following with all updated files --> files="..." --> rm $files --> cvs rm $files --> cvs commit $files This is usually really fast.
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).If the cron hangs, you will neither run a simple nor a complex update-script but I agree to keep the sync script as simple as possible - so I would agree with you and say, only sources in the /doc module and all finals in the webserver. But I will handle the HowTos as a src to - they dont need to be compiled but I think we should keep the version in both places, so that ALL documentation is in the doc area....
Ok, you are the maintainer ;) BTW did you check in the new doc area already? 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
