incubator-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Rana Bhattacharyya <>
Subject Re: ftpserver has broken svn directory on webserver
Date Fri, 21 Oct 2005 07:55:26 GMT

   I am terribly sorry and thank you all for helping
me out. Now I am trying to write what I have
understood so that I won't mess-up again. Please do
write your comments.

1. The source repository :

   The generated document for the project website :

2. The new project site will be
To update the site, first we have to login into and then do a svn update at
/www/ directory. The
cron job will publish these pages later.

cd /www/
svn update

3. The generated javadoc will not be in SVN. Instead
an empty directory will be there in SVN. The javadocs
will be copied manually somewhere under
/www/ directory in

4. STATUS (or status.xml) file has to be added in SVN.
The location should be
This file is used by PMC. It is not used in any way to
update any page.

5. One thing is NOT clear to me. Who can update the
Or how does it get generated?
I can see the wiki page :

Now release related issue:

Podlings are, by definition, not yet fully accepted as
part of the Apache Software Foundation. Podling web
sites MUST include a clear disclaimer on their website
and in all documentation stating that they are in

Podlings SHOULD use the following text for all
disclaimers :

<project name> is an effort undergoing incubation at
the Apache Software Foundation (ASF), sponsored by the
<name of sponsor>. Incubation is required of all newly
accepted projects until a further review indicates
that the infrastructure, communications, and decision
making process have stabilized in a manner consistent
with other successful ASF projects. While incubation
status is not necessarily a reflection of the
completeness or stability of the code, it does
indicate that the project has yet to be fully endorsed
by the ASF. 

As podlings are not yet fully accepted as part of the
Apache Software Foundation, any software releases
(including code held in publically available CVS) made
by Podlings will not be endorsed by the ASF.

Podlings in Incubation SHALL NOT perform any releases
of software without the explicit approval of the
Incubator PMC. Such approval SHALL be given only after
the Incubator PMC has followed the process detailed in
(Reference to Charter), and SHALL NOT occur until all
source has been legally transferred to the ASF.

So the bottom-line is projects in Incubation cannot
release without permission from PMC. In case of a
release, the filename should contain "incubating"

Rana Bhattacharyya

--- David Crossley <> wrote:

> Sorry if i sound frustrated today. 
> When ftpserver sprang back to life recently
> we started getting svn commit mails coming to
> the general@ list. This was a sign that an old
> project was not configured the same way that the
> newer ones are.
> After one of my messages to general, Rana contacted
> me offlist and i explained what need to happen with
> the website side of things. Not sure about their
> mail lists.
> I also requested not to do offlist email, because
> now i cannot refer back to that effort. Will try
> again:
> The instructions are at
> (Yes they need to be improved. I will try that
> after this message.)
> The source documents for your project website:
> The generated documents for your project website:
> Make sure that your subversion client is properly
> configured. This vastly reduces the amount of
> traffic
> on the svn email commits, e.g. *.pdf
> ssh
> cd /www/
> svn update
> Rana Bhattacharyya wrote:
> > 
> >     It is true that I have not checked-in the
> latest
> > generated project pages in SVN. The reasons are as
> > follows:
> > 
> > 1. The website has javadocs. So do we need to
> commit
> > those things in SVN?
> A lot of projects don't put javadocs in their SVN,
> just manually add them to the webserver each time
> that
> you regenerate them. Just have an empty directory
> in your site svn.
> (If committers want to help with better ways to
> generate and maintain javadocs et al, then come to
> the site-dev mailing list.)
> > I got few mails to minimize the
> > SVN footprint. So I did not commit the generated
> docs
> > in SVN. If I commit everything in SVN, slowly the
> > size would be huge and it might be difficult to
> > maintain.
> Why would it be difficult?
> > 2. The site can be generated anytime from the
> source
> > code. Do we really need to put the generated doc
> in
> > SVN?
> Yes. It is then a lot easier for people who
> are unfamiliar with your project or website,
> to help fix it, like we needed to do today.
> > 3. According to
> >
> > the project site would be
> >
> So
> > the path should be
> > /www/
> Nope, that is old. See above.
> > Please let me know the proper way to update site.
> Hope that helps.
> -David
> To unsubscribe, e-mail:
> For additional commands, e-mail:

Yahoo! FareChase: Search multiple travel sites in one click.

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message