On Tue, 3 Apr 2001, Vincent Massol wrote:
>
> ----- Original Message -----
> From: "Craig R. McClanahan" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Monday, April 02, 2001 11:47 PM
> Subject: Re: Re : Repost: [Cactus] What remains to do ...
>
> [snip]
> > > >I can help with that. I assume that we will adopt the standard Jakarta
> site
> > > >format to integrate with the rest of jakarta. We would need to do the
> main
> > > >commons site (someone is already working on that?), which I assume we
> model
> > > >after Taglibs.
> > > >
> >
> > The rational place for the Cactus-specific stuff would be:
> >
> > http://jakarta.apache.org/commons/cactus
> >
> > which translates to directory "/www/jakarta.apache.org/commons/cactus" on
> > the server.
> >
>
> Fine.
> Who has access to this directory ? Who should I hand the zip file of the
> Cactus to ?
To expand on previous answers a little:
* Everyone Jakarta committer (i.e. members of the "jakarta" group on the
server) have read/write access to the web site directories. However,
you should ensure that your umask is set to 002 so that all files you
create have group write access.
* Much/most of the site is automatically generated (using Anakia) from
CVS module "jakarta-site2" -- if you want to help maintain that part
of the website (such as updating the news page for releases), contact
me for appropriate CVS karma. There's a detailed README in the top
level directory that describes the steps.
* Subprojects are pretty much free to use whatever technology they want
for their corresponding subdirectories, although we should all strive
for the same look-and-feel. In practice this ranges from hand-edited
HTML to using XSLT with Ant's <style> tag to interlinked with Anakia.
Craig
