incubator-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "chen chen" <>
Subject Re: Help!
Date Sat, 12 Jul 2008 08:08:07 GMT
Thanks for your help! But I still have some problems.

2008/7/12 Robert Burrell Donkin <>:

> On 7/11/08, chen chen <> wrote:
> > I want to ask some questions about "Updating the the top-level Incubator
> > website".
> Cool
> >
> > a. Is it that every page of Incubator website(
> > and Official website(
> > must be *.xml?
> Control of the space is delegated
> to the bluesky podling. Bluesky is free to create the content however
> they like.
> The Incubator public site above bluesky is generated from XML

Firstly, the websites must be *.XML, but I have uploaded the  Official
website being *.html. Should I re-upload the website with *.xml?

> > (Why not *.html?)
> Most Apache projects choose to generate their sites often from XML.
> This allows common elements (for example sidebars) to be easily
> included. Apache is a high volume site running on modest hardware. So,
> as many pages as possible are statically served.
> > b. How can I update the Incubator and Official websites?

Secondly, I look through the page(
I think there is three steps to update the website:
a, "svn co http://....", get the documents from server to my computer.
b, do the work of change, and "svn status","svn add". After achieving, "svn
ci http://.." with username and password
c, shh to the server ,  and "svn update" in my project .

Is it right? Is it to update the  Incubator website or the Official website?


> Anyone with bluesky karma should be able to upload changes. The
> recommended approach is to create content in subversion then checkout.
> As the mentors for more details.
> Karma for the main site is mostly limited to the PMC. If you have any
> suggestions for improvements, please submit a patch in JIRA and we'll
> take a look at it.
> Robert
> >
> > Thanks!
> >
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message