Nino's suggestion is much better than mine. I guess I should file a
ticket to have this done, unless someone else has already opened a
ticket about the problem. (I can never find anything in any
bugtracking system, and indeed have never attempted to use ours.)
---------- Forwarded message ----------
From: Nino Novak <firstname.lastname@example.org>
Date: Fri, Sep 7, 2012 at 12:08 AM
Subject: Re: Alfresco (by PM)
To: Jean Weber <email@example.com>
I'd suggest to not redirect automatically (as people normally don't realize such
a redirect and might be surprised to end up somewhere different) but to leave
the subdomain active and put a static index.html page there which explains that
Alfresco is not used at the moment but work on LibreOffice Documentation
primarily happens at odfauthors (and, of course provide a link to odfauthors
and the Doc Wiki).
Am 06.09.2012 08:53 schrieb Jean Weber:
I'd like to thank the Board for agreeing to host the LO Alfresco site
on TDF infrastructure if the Docs team wanted to use it.
I don't know if David Nelson has informed you that he has taken down
his LO Alfresco site after the Docs team failed to choose it as our
How should LO deal with the error messages (site not found; page not
found) that people will get if they go to
http://alfresco.libreoffice.org/ or http://media.libreoffice.org/ ?
Can we redirect those addresses to the main LO page?
I am deleting references to those sites from the wiki and the LO
website and other places as I find them, but no doubt there are links
from other places, blogs, etc.
Impressum (Legal Info)
: Unless otherwise specified, all text and images
on this website are licensed under the
Creative Commons Attribution-Share Alike 3.0 License
This does not include the source code of LibreOffice, which is
licensed under the Mozilla Public License (MPLv2
"LibreOffice" and "The Document Foundation" are
registered trademarks of their corresponding registered owners or are
in actual use as trademarks in one or more countries. Their respective
logos and icons are also subject to international copyright laws. Use
thereof is explained in our trademark policy