Redirects are easy once the live-site is our site and it can be figured out how 
to add HTML <head> meta tags that the Apache CMS allows.  Also, there is always 
the good old .htaccess scripting of a redirect (again, working around the CMS I 
suppose).

It should be done on at least on ooo-site even if it has no effect until 
cut-over.

There is no reason to break a link on speculation when it is easy to avoid 
breaking it, or having the break be temporary until cut-over.  (I'd bet the 
page has been search-indexed and the "your download is starting, thank you for 
downloading" pages link to donation/contribution points.)

Finally, it is my understanding that cut-over of the static site is now at our 
option and the AOOo has reasonable discretion with regard to timing.  It seems 
that cut-over can be done as soon as ooo-site is ready enough to be the new 
live site.  And the subdomains don't all have to cut over together and 
everything will still work.  A progressive, rolling cut-over might even be in 
the cards.

 - Dennis

-----Original Message-----
From: Rob Weir [mailto:[email protected]] 
Sent: Sunday, November 27, 2011 10:11
To: [email protected]
Subject: Re: [WWW][Policy] Participate! - Rewriting contributing.openoffice.org

On Fri, Nov 25, 2011 at 6:16 PM, Kay Schenk <[email protected]> wrote:
>[ ... ]

> How about if we don't hear any major objections by say, Dec. 1, I'll go
> ahead and make this change (redirect contributing/index.html to this).
> Nothing is in concrete, we can always go back or do something else.
>

I don't know if we need to do an actual HTTP-level redirect.    I
don't think there are many external links to the OOo contributing
page.  It would be sufficient if we just change the link to point to
the project contributing page.


> --
> ----------------------------------------------------------------------------------------
> MzK
>
> "The greatness of a nation and its moral progress can be judged
>  by the way its animals are treated."
>                              -- Mohandas Gandhi
>

Reply via email to