You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cocoon.apache.org by Stefano Mazzocchi <st...@apache.org> on 2003/03/11 13:00:34 UTC
are we ready to move to cocoon.apache.org?
Things to do will be:
1) move the existing docs to the cocoon.apache.org virtualhost (please
note that the copyright year on the web site is old!)
2) create permanent redirects from the old location to the new one (so
that no links are broken)
anything else?
Stefano.
Re: [VOTE] cocoon.apache.org URLs (Re: are we ready to move to cocoon.apache.org?)
Posted by Vadim Gritsenko <va...@verizon.net>.
Jeff Turner wrote:
>(changing the topic so people notice its a vote)
>
>If I understand correctly, the proposed URL structure is:
>
>http://cocoon.apache.org/v1.x/
>http://cocoon.apache.org/v2.0/
>http://cocoon.apache.org/v2.1/
>http://cocoon.apache.org/ ->
> http://cocoon.apache.org/v2.0 (whatever's the current version)
>
>+1, looks nice.
>
>
+1
Vadim
>(mild preference for leaving out the '.x' in '1.x')
>
>--Jeff
>
Re: [VOTE] cocoon.apache.org URLs (Re: are we ready to move to cocoon.apache.org?)
Posted by Steven Noels <st...@outerthought.org>.
Steven Noels wrote:
> So when Lenya ever exits from the (DOA) incubator, where should it be
^^^^ ^^^^^
Sorry about these nasty remarks - I should remember to live up to my own
mail guidelines posted only hours ago.
Duh. My bad.
</Steven>
--
Steven Noels http://outerthought.org/
Outerthought - Open Source, Java & XML Competence Support Center
Read my weblog at http://blogs.cocoondev.org/stevenn/
stevenn at outerthought.org stevenn at apache.org
Re: [VOTE] cocoon.apache.org URLs (Re: are we ready to move to cocoon.apache.org?)
Posted by Michael Wechner <mi...@wyona.org>.
Steven Noels wrote:
> Stefano Mazzocchi wrote:
>
>>> Since we are a top level project, we are going to provide (url-) space
>>> for subprojects.
>>
>>
>>
>> Hmmm, that would be against the indications of the ASF that wants
>> each PMC to control one and only one codebase, just like HTTPD has
>> always done and works very well.
>>
>>> So, we should add a "cocoon/" or something else
>>> ("base", "core", "whatever") e.g. cocoon.apache.org/cocoon/v2.1
>>>
>>> Apart from that, go ahead +1
>>
>>
>>
>> I would be slightly -0.5 on this.... for affiliated projects the
>> incubator is the place to be.
>
>
> So when Lenya ever exits from the (DOA) incubator, where should it be
> hosted then?
yeah, what about http://cocoon.apache.org/lenya/ ?
Thanks
Michael
>
>
> </Steven>
Re: [VOTE] cocoon.apache.org URLs (Re: are we ready to move to cocoon.apache.org?)
Posted by Steven Noels <st...@outerthought.org>.
Stefano Mazzocchi wrote:
>> Since we are a top level project, we are going to provide (url-) space
>> for subprojects.
>
>
> Hmmm, that would be against the indications of the ASF that wants each
> PMC to control one and only one codebase, just like HTTPD has always
> done and works very well.
>
>> So, we should add a "cocoon/" or something else
>> ("base", "core", "whatever") e.g. cocoon.apache.org/cocoon/v2.1
>>
>> Apart from that, go ahead +1
>
>
> I would be slightly -0.5 on this.... for affiliated projects the
> incubator is the place to be.
So when Lenya ever exits from the (DOA) incubator, where should it be
hosted then?
</Steven>
--
Steven Noels http://outerthought.org/
Outerthought - Open Source, Java & XML Competence Support Center
Read my weblog at http://blogs.cocoondev.org/stevenn/
stevenn at outerthought.org stevenn at apache.org
Re: [VOTE] cocoon.apache.org URLs (Re: are we ready to move to cocoon.apache.org?)
Posted by Stefano Mazzocchi <st...@apache.org>.
Christian Haul wrote:
> On 12.Mar.2003 -- 12:54 AM, Jeff Turner wrote:
>
>>(changing the topic so people notice its a vote)
>>
>>If I understand correctly, the proposed URL structure is:
>>
>>http://cocoon.apache.org/v1.x/
>>http://cocoon.apache.org/v2.0/
>>http://cocoon.apache.org/v2.1/
>>http://cocoon.apache.org/ ->
>> http://cocoon.apache.org/v2.0 (whatever's the current version)
>
>
> Since we are a top level project, we are going to provide (url-) space
> for subprojects.
Hmmm, that would be against the indications of the ASF that wants each
PMC to control one and only one codebase, just like HTTPD has always
done and works very well.
> So, we should add a "cocoon/" or something else
> ("base", "core", "whatever") e.g. cocoon.apache.org/cocoon/v2.1
>
> Apart from that, go ahead +1
I would be slightly -0.5 on this.... for affiliated projects the
incubator is the place to be.
What do others thing?
Re: [VOTE] cocoon.apache.org URLs (Re: are we ready to move to cocoon.apache.org?)
Posted by Christian Haul <ha...@dvs1.informatik.tu-darmstadt.de>.
On 12.Mar.2003 -- 12:54 AM, Jeff Turner wrote:
> (changing the topic so people notice its a vote)
>
> If I understand correctly, the proposed URL structure is:
>
> http://cocoon.apache.org/v1.x/
> http://cocoon.apache.org/v2.0/
> http://cocoon.apache.org/v2.1/
> http://cocoon.apache.org/ ->
> http://cocoon.apache.org/v2.0 (whatever's the current version)
Since we are a top level project, we are going to provide (url-) space
for subprojects. So, we should add a "cocoon/" or something else
("base", "core", "whatever") e.g. cocoon.apache.org/cocoon/v2.1
Apart from that, go ahead +1
> (mild preference for leaving out the '.x' in '1.x')
Dito.
Chris.
--
C h r i s t i a n H a u l
haul@informatik.tu-darmstadt.de
fingerprint: 99B0 1D9D 7919 644A 4837 7D73 FEF9 6856 335A 9E08
[VOTE] cocoon.apache.org URLs (Re: are we ready to move to cocoon.apache.org?)
Posted by Jeff Turner <je...@apache.org>.
(changing the topic so people notice its a vote)
If I understand correctly, the proposed URL structure is:
http://cocoon.apache.org/v1.x/
http://cocoon.apache.org/v2.0/
http://cocoon.apache.org/v2.1/
http://cocoon.apache.org/ ->
http://cocoon.apache.org/v2.0 (whatever's the current version)
+1, looks nice.
(mild preference for leaving out the '.x' in '1.x')
--Jeff
[leaving original email in for context]
On Tue, Mar 11, 2003 at 02:01:16PM +0100, Stefano Mazzocchi wrote:
> Pier Fumagalli wrote:
> >"Stefano Mazzocchi" <st...@apache.org> wrote:
> >
> >
> >>Things to do will be:
> >>
> >>1) move the existing docs to the cocoon.apache.org virtualhost (please
> >>note that the copyright year on the web site is old!)
> >>
> >>2) create permanent redirects from the old location to the new one (so
> >>that no links are broken)
> >>
> >>anything else?
> >
> >
> >I would move it in a slightly different way, that will help us to be more
> >flexible wih the new/updated documentation for v2.1 comes out:
> >
> >1) move /www/xml.apache.org/cocoon1/ to /www/cocoon.apache.org/v1.x/
> >
> >2) setup permanent redirect from http://xml.apache.org/cocoon1/** to
> > http://cocoon.apache.org/v1.x/{1}
> >
> >3) move /www/xml.apache.org/cocoon/ to /www/cocoon.apache.org/v2.0/
> >
> >4) setup permanent redirect from http://xml.apache.org/cocoon/** to
> > http://cocoon.apache.org/v2.0/{1}
> >
> >5) setup temporary redirect from http://cocoon.apache.org/ to
> > http://cocoon.apache.org/v2.0/ (this will be changed to redirect to
> > http://cocoon.apache.org/v2.1/ when we want to put live a new 2.1 based
> > website)
> > note that this redirect doesn't "redirect" the entire subtree (no ** and
> > no {1} in this one).
> >
> >6) move the mirror.cgi and mirror.html fies to /www/cocoon.apache.org/ and
> > keep them as generic as possible for all our downloads (1.x, 2.x, ...)
> >
> >This should not break any link right now, and at the same time, it will
> >allow us to grow beyond 2.0 (whilst keeping the old doccos on line and
> >without having to move them as we did with 1.x)...
> >
> >And it will only take a few minutes to set up... Let me know if I should
> >shoot for it...
>
> I like it. But since URL space planning is a *very* serious issue, we
> should do a real vote around this.
>
> so, please, guys, place your vote.
>
> NOTE: the vote reflects the URL space only, not how the documentation is
> created/generate/updated, that will be discussed in a separate email
> coming up next.
>
> Stefano.
>
Re: are we ready to move to cocoon.apache.org?
Posted by Torsten Curdt <tc...@dff.st>.
> -0 I abstain
>
> Very minor point, I am not happy with the 'v' in the URL, it is
> unnecessary IMHO.
Same here :)
But not very important. So let's say +0 ;)
> But I don't want to get in the way of your good works .... ;)
ditto
--
Torsten
Re: are we ready to move to cocoon.apache.org?
Posted by Stefano Mazzocchi <st...@apache.org>.
Jeremy Quinn wrote:
> Very minor point, I am not happy with the 'v' in the URL, it is
> unnecessary IMHO.
>
> But I don't want to get in the way of your good works .... ;)
No, you're right, the 'v' doesn't really add any useful information.
I agree to remove it.
Stefano.
Re: are we ready to move to cocoon.apache.org?
Posted by Jeremy Quinn <je...@media.demon.co.uk>.
On Tuesday, March 11, 2003, at 01:01 PM, Stefano Mazzocchi wrote:
> Pier Fumagalli wrote:
>> "Stefano Mazzocchi" <st...@apache.org> wrote:
>>> Things to do will be:
>>>
>>> 1) move the existing docs to the cocoon.apache.org virtualhost
>>> (please
>>> note that the copyright year on the web site is old!)
>>>
>>> 2) create permanent redirects from the old location to the new one
>>> (so
>>> that no links are broken)
>>>
>>> anything else?
>> I would move it in a slightly different way, that will help us to be
>> more
>> flexible wih the new/updated documentation for v2.1 comes out:
>> 1) move /www/xml.apache.org/cocoon1/ to /www/cocoon.apache.org/v1.x/
>> 2) setup permanent redirect from http://xml.apache.org/cocoon1/** to
>> http://cocoon.apache.org/v1.x/{1}
>> 3) move /www/xml.apache.org/cocoon/ to /www/cocoon.apache.org/v2.0/
>> 4) setup permanent redirect from http://xml.apache.org/cocoon/** to
>> http://cocoon.apache.org/v2.0/{1}
>> 5) setup temporary redirect from http://cocoon.apache.org/ to
>> http://cocoon.apache.org/v2.0/ (this will be changed to redirect to
>> http://cocoon.apache.org/v2.1/ when we want to put live a new 2.1
>> based
>> website)
>> note that this redirect doesn't "redirect" the entire subtree (no
>> ** and
>> no {1} in this one).
>> 6) move the mirror.cgi and mirror.html fies to
>> /www/cocoon.apache.org/ and
>> keep them as generic as possible for all our downloads (1.x, 2.x,
>> ...)
>> This should not break any link right now, and at the same time, it
>> will
>> allow us to grow beyond 2.0 (whilst keeping the old doccos on line and
>> without having to move them as we did with 1.x)...
>> And it will only take a few minutes to set up... Let me know if I
>> should
>> shoot for it...
>
> I like it. But since URL space planning is a *very* serious issue, we
> should do a real vote around this.
>
> so, please, guys, place your vote.
-0 I abstain
Very minor point, I am not happy with the 'v' in the URL, it is
unnecessary IMHO.
But I don't want to get in the way of your good works .... ;)
regards Jeremy
Re: are we ready to move to cocoon.apache.org?
Posted by Stefano Mazzocchi <st...@apache.org>.
Pier Fumagalli wrote:
> "Stefano Mazzocchi" <st...@apache.org> wrote:
>
>
>>Things to do will be:
>>
>>1) move the existing docs to the cocoon.apache.org virtualhost (please
>>note that the copyright year on the web site is old!)
>>
>>2) create permanent redirects from the old location to the new one (so
>>that no links are broken)
>>
>>anything else?
>
>
> I would move it in a slightly different way, that will help us to be more
> flexible wih the new/updated documentation for v2.1 comes out:
>
> 1) move /www/xml.apache.org/cocoon1/ to /www/cocoon.apache.org/v1.x/
>
> 2) setup permanent redirect from http://xml.apache.org/cocoon1/** to
> http://cocoon.apache.org/v1.x/{1}
>
> 3) move /www/xml.apache.org/cocoon/ to /www/cocoon.apache.org/v2.0/
>
> 4) setup permanent redirect from http://xml.apache.org/cocoon/** to
> http://cocoon.apache.org/v2.0/{1}
>
> 5) setup temporary redirect from http://cocoon.apache.org/ to
> http://cocoon.apache.org/v2.0/ (this will be changed to redirect to
> http://cocoon.apache.org/v2.1/ when we want to put live a new 2.1 based
> website)
> note that this redirect doesn't "redirect" the entire subtree (no ** and
> no {1} in this one).
>
> 6) move the mirror.cgi and mirror.html fies to /www/cocoon.apache.org/ and
> keep them as generic as possible for all our downloads (1.x, 2.x, ...)
>
> This should not break any link right now, and at the same time, it will
> allow us to grow beyond 2.0 (whilst keeping the old doccos on line and
> without having to move them as we did with 1.x)...
>
> And it will only take a few minutes to set up... Let me know if I should
> shoot for it...
I like it. But since URL space planning is a *very* serious issue, we
should do a real vote around this.
so, please, guys, place your vote.
NOTE: the vote reflects the URL space only, not how the documentation is
created/generate/updated, that will be discussed in a separate email
coming up next.
Stefano.
Re: are we ready to move to cocoon.apache.org?
Posted by Diana Shannon <sh...@apache.org>.
On Tuesday, March 11, 2003, at 07:30 AM, Pier Fumagalli wrote:
> I would move it in a slightly different way, that will help us to be
> more
> flexible wih the new/updated documentation for v2.1 comes out:
Why not have this now for alpha/beta docs? It would save some tedious
manual synching. There's probably ways to speed up cvs live site
update/commits with some directory reorganization. For example, for the
latest update, I didn't even touch the api docs. But their top-level
position, intermingled with all other docs, made updates and commits
have to inspect the hundreds of files therein.
Diana
Re: are we ready to move to cocoon.apache.org?
Posted by Stefano Mazzocchi <st...@apache.org>.
Pier Fumagalli wrote:
> We're relying on the "xml-site" module to make the CVS updates, we'd have to
> create our own "cocoon-site" CVS repository to be in line with all other
> repositories...
>
> But I'm thinking as well about the tediousness in rebuilding the site that
> Diana outlined... It would be probably better to address all those issues
> before moving to the new location...
I agree.
> The other possible option would be to have the cocoon site served by Cocoon
> itself (I did setup a "trial" site on Nagoya some weeks ago), but probably
> right now that would be aiming a little bit too high...
See my next email.
Re: are we ready to move to cocoon.apache.org?
Posted by Pier Fumagalli <pi...@betaversion.org>.
We're relying on the "xml-site" module to make the CVS updates, we'd have to
create our own "cocoon-site" CVS repository to be in line with all other
repositories...
But I'm thinking as well about the tediousness in rebuilding the site that
Diana outlined... It would be probably better to address all those issues
before moving to the new location...
The other possible option would be to have the cocoon site served by Cocoon
itself (I did setup a "trial" site on Nagoya some weeks ago), but probably
right now that would be aiming a little bit too high...
Pier
"Carsten Ziegeler" <cz...@s-und-n.de> wrote:
> Is updating the docs then the same procedure than before
> (updating from cvs)?
>
> Carsten
>
>> -----Original Message-----
>> From: Pier Fumagalli [mailto:pier@betaversion.org]
>> Sent: Tuesday, March 11, 2003 1:30 PM
>> To: cocoon-dev@xml.apache.org
>> Subject: Re: are we ready to move to cocoon.apache.org?
>>
>>
>> "Stefano Mazzocchi" <st...@apache.org> wrote:
>>
>>> Things to do will be:
>>>
>>> 1) move the existing docs to the cocoon.apache.org virtualhost (please
>>> note that the copyright year on the web site is old!)
>>>
>>> 2) create permanent redirects from the old location to the new one (so
>>> that no links are broken)
>>>
>>> anything else?
>>
>> I would move it in a slightly different way, that will help us to be more
>> flexible wih the new/updated documentation for v2.1 comes out:
>>
>> 1) move /www/xml.apache.org/cocoon1/ to /www/cocoon.apache.org/v1.x/
>>
>> 2) setup permanent redirect from http://xml.apache.org/cocoon1/** to
>> http://cocoon.apache.org/v1.x/{1}
>>
>> 3) move /www/xml.apache.org/cocoon/ to /www/cocoon.apache.org/v2.0/
>>
>> 4) setup permanent redirect from http://xml.apache.org/cocoon/** to
>> http://cocoon.apache.org/v2.0/{1}
>>
>> 5) setup temporary redirect from http://cocoon.apache.org/ to
>> http://cocoon.apache.org/v2.0/ (this will be changed to redirect to
>> http://cocoon.apache.org/v2.1/ when we want to put live a new 2.1 based
>> website)
>> note that this redirect doesn't "redirect" the entire subtree
>> (no ** and
>> no {1} in this one).
>>
>> 6) move the mirror.cgi and mirror.html fies to /www/cocoon.apache.org/ and
>> keep them as generic as possible for all our downloads (1.x, 2.x, ...)
>>
>> This should not break any link right now, and at the same time, it will
>> allow us to grow beyond 2.0 (whilst keeping the old doccos on line and
>> without having to move them as we did with 1.x)...
>>
>> And it will only take a few minutes to set up... Let me know if I should
>> shoot for it...
>>
>> Pier
>>
>
>
>
RE: are we ready to move to cocoon.apache.org?
Posted by Carsten Ziegeler <cz...@s-und-n.de>.
Is updating the docs then the same procedure than before
(updating from cvs)?
Carsten
> -----Original Message-----
> From: Pier Fumagalli [mailto:pier@betaversion.org]
> Sent: Tuesday, March 11, 2003 1:30 PM
> To: cocoon-dev@xml.apache.org
> Subject: Re: are we ready to move to cocoon.apache.org?
>
>
> "Stefano Mazzocchi" <st...@apache.org> wrote:
>
> > Things to do will be:
> >
> > 1) move the existing docs to the cocoon.apache.org virtualhost (please
> > note that the copyright year on the web site is old!)
> >
> > 2) create permanent redirects from the old location to the new one (so
> > that no links are broken)
> >
> > anything else?
>
> I would move it in a slightly different way, that will help us to be more
> flexible wih the new/updated documentation for v2.1 comes out:
>
> 1) move /www/xml.apache.org/cocoon1/ to /www/cocoon.apache.org/v1.x/
>
> 2) setup permanent redirect from http://xml.apache.org/cocoon1/** to
> http://cocoon.apache.org/v1.x/{1}
>
> 3) move /www/xml.apache.org/cocoon/ to /www/cocoon.apache.org/v2.0/
>
> 4) setup permanent redirect from http://xml.apache.org/cocoon/** to
> http://cocoon.apache.org/v2.0/{1}
>
> 5) setup temporary redirect from http://cocoon.apache.org/ to
> http://cocoon.apache.org/v2.0/ (this will be changed to redirect to
> http://cocoon.apache.org/v2.1/ when we want to put live a new 2.1 based
> website)
> note that this redirect doesn't "redirect" the entire subtree
> (no ** and
> no {1} in this one).
>
> 6) move the mirror.cgi and mirror.html fies to /www/cocoon.apache.org/ and
> keep them as generic as possible for all our downloads (1.x, 2.x, ...)
>
> This should not break any link right now, and at the same time, it will
> allow us to grow beyond 2.0 (whilst keeping the old doccos on line and
> without having to move them as we did with 1.x)...
>
> And it will only take a few minutes to set up... Let me know if I should
> shoot for it...
>
> Pier
>
Re: are we ready to move to cocoon.apache.org?
Posted by Pier Fumagalli <pi...@betaversion.org>.
"Stefano Mazzocchi" <st...@apache.org> wrote:
> Things to do will be:
>
> 1) move the existing docs to the cocoon.apache.org virtualhost (please
> note that the copyright year on the web site is old!)
>
> 2) create permanent redirects from the old location to the new one (so
> that no links are broken)
>
> anything else?
I would move it in a slightly different way, that will help us to be more
flexible wih the new/updated documentation for v2.1 comes out:
1) move /www/xml.apache.org/cocoon1/ to /www/cocoon.apache.org/v1.x/
2) setup permanent redirect from http://xml.apache.org/cocoon1/** to
http://cocoon.apache.org/v1.x/{1}
3) move /www/xml.apache.org/cocoon/ to /www/cocoon.apache.org/v2.0/
4) setup permanent redirect from http://xml.apache.org/cocoon/** to
http://cocoon.apache.org/v2.0/{1}
5) setup temporary redirect from http://cocoon.apache.org/ to
http://cocoon.apache.org/v2.0/ (this will be changed to redirect to
http://cocoon.apache.org/v2.1/ when we want to put live a new 2.1 based
website)
note that this redirect doesn't "redirect" the entire subtree (no ** and
no {1} in this one).
6) move the mirror.cgi and mirror.html fies to /www/cocoon.apache.org/ and
keep them as generic as possible for all our downloads (1.x, 2.x, ...)
This should not break any link right now, and at the same time, it will
allow us to grow beyond 2.0 (whilst keeping the old doccos on line and
without having to move them as we did with 1.x)...
And it will only take a few minutes to set up... Let me know if I should
shoot for it...
Pier