Infrastructure

Muhammet Kara wrote:

Can we have a short url pointing to our pootle (https://translations.documentfoundation.org)?

Our short urls are of the form tdf.io/$KEYWORD so I'd suggest tdf.io/l10n instead. (Compared to a subdomain it's less work for infra :-)

Maybe we should also change the main/actual url from https://translations.documentfoundation.org to https://l10n.documentfoundation.org

This requires consensus, and this ticket isn't the right place for the discussion. Would you mind bringing that up to the projects (and I guess also l10n) list?

Done.

$ curl -so/dev/null -w'%{http_code} %{url_effective} -> %{redirect_url}\n' \
    '{tdf.io/l10n,l10n.tdf.io,l10n.libreoffice.org}'
301 http://tdf.io/l10n -> https://translations.documentfoundation.org
301 http://l10n.tdf.io/ -> https://translations.documentfoundation.org/
301 http://l10n.libreoffice.org/ -> https://translations.documentfoundation.org/

(On second thought I did create the l10n.tdf.io subdomain, since you were asking for l10n.libreoffice.org anyway.)

Note that the X.509 cert was renewed a few days ago (April 30) and while I did configure our system to request certs for l10n.tdf.io and l10n.libreoffice.org, it won't be done before the next renewal (July 30). In practice that means https://l10n.tdf.io and https://l10n.libreoffice.org will fail with an "invalid cert" error for the next 3 months. If that's a problem I can request and new cert and revoke the existing one, of course.

Muhammet Kara wrote:

Maybe we should also change the main/actual url from https://translations.documentfoundation.org to https://l10n.documentfoundation.org

This requires consensus, and this ticket isn't the right place for the discussion. Would you mind bringing that up to the projects (and I guess also l10n) list?

Sure.

Closing this ticket, then. Please file a new one once there is consensus on what the canonical hostname should be.