On Wed, 2008-01-16 at 14:35 +0100, Jörn Nettingsmeier wrote: ... > thorsten, i'm not too familiar with apache.org's security policy - would > the following be acceptable?: > > a lenya server runs on zones. every doc contributor gets access. to > reduce headache and discourage jokesters, ssl is mandatory. > > a cronjob on another machine will wget -r the live area of the zones > server every hour or so and copy the stuff into a local svn sandbox > (some minor wizardry would be needed to correctly "svn add" and "delete" > files, but it shouldn't be too hard). > when the wget is done, it either "svn commit"s the stuff automatically, > or a local webserver makes the repo visible as a web site that can be > inspected by a committer who then triggers a manual update (maybe after > discussion on the mailing list).
I just finished a rewrite of Apache Droids a labs project http://labs.apache.org/labs.html that can do all of the above for us. Regarding the architecture that meets the policy of the ASF AFAIK. However the problem of local vs. public editing described by Andreas remains. > > alternatively, the content could be wgotten locally and rsync'ed to the > other machine (i.e. manual push instead of pull at regular intervals) > IMO having the zones server as our docu server with a real case test of lenya 2.0 is preferable to local editing of our docu till we find a solution. > i can offer a virtual server for that job. the scripts, documentation > and configuration would be stored in our svn so that someone else can > take over easily if i go missing or get hit by a bus. every committer > who takes an interest gets sufficient sudo rights, and the root password > is given to the pmc chair. > > wdyt? I like the idea. wdot? salu2 -- Thorsten Scherler thorsten.at.apache.org Open Source Java consulting, training and solutions --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
