> From: Diana Shannon [mailto:[EMAIL PROTECTED]]
> On Friday, May 24, 2002, at 08:49 AM, Matthew Langham wrote: > > > The current Cocoon website documentation contained in CVS contains a > > structure that includes links to books, trainings etc. This sort of > > information (including links to Cocoon consultants, use-cases, best > > practices etc.) is getting more important as Cocoon becomes > more widely > > used. > > > > What about updating xml.apache.org/cocoon to reflect this? > > Sure. It's my understanding, from Carsten, that any committer > can update > the live site. If someone can provide instructions, I'd be > happy to do > this for links now (and soon for lots of other docs in process). Then > I'll write a committer how-to to clarify the process for other/future > committers. Dia~a, Most committers have (as you have) also commit access to the xml-site module on CVS, which is regularly published to xml.apache.org (where most *don't* have acces to). The idea is that xml-site/targets/cocoon/ is updated (using CVS) by the project committers and Sam's cron job moves this to the live site. So yes, you can update the site if you commit changes to that site to the xml-site module. Be warned however that this module is quite large (100+ MB), getting the module can take a long time - you might as well only retrieve the cocoon directory from it. Furthermore, xml-site is a mess, part of it presumably is still maintained using the stylebook stuff, half of the xml-site/sources dirs are empty (as Cocoon's for instance) since those don't use stylebook anymore, etc etc. Fingers itching to get this solved ;-) HTH, </Steven> ps: while I understand this setup in terms of security etc, I'd prefer scp for Forrest's publication process, so that we can simply send a tarball and expand it in-place on xml.apache.org. That means of course we don't keep a CVS history of the website anymore, and loose the comment facility inherent to that. Anyone any comments on this over here? --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
