[SAC] Weblate self-hosting proposal

[Sandro Santilli]

I've contacted Michal Čihař who's responsible for the weblate
hosting solutions documented here: https://weblate.org/en/hosting/#self

Like we did for website, we could also get help from Weblate
developers to provide translation infrastructure to OSGeo projects
(translate.osgeo.org?). A contract of 500EUR/year would give us
initial installation (with LDAP support) and an upgrade every 6
months.

I'd love to have the option to move PostGIS translation from transifex
(discontinued from being open-source) to OSGeo-hosted Weblate (GPLv3+),
what would you think about it ?

Micheal mail follows.

--strk;


----- Forwarded message from Michal Čihař <michal at cihar.com> -----

Date: Tue, 24 Oct 2017 16:21:07 +0200
From: Michal Čihař <michal at cihar.com>
To: Sandro Santilli <strk at kbt.io>
Subject: Re: Weblate self-hosting
X-Mailer: Evolution 3.26.1-1
In-Reply-To: <20171024105838.3krf4p5cxr4qxtt5 at liz>
X-Spam-Level: 

Hello

Thanks for your interest in using Weblate.

The self-hosted packages are not limited in size (in the end it's using
your infrastructure), only in amount of support and upgrades you will
get. So it's really up to you how many projects you will host - you
will have access to the admin interface and manage projects on your
own.

As for LDAP authentication it's supported, I don't think there is easy
way to map LDAP groups to Weblate ones, what probably could be done is
limiting access to Weblate to certain group.

Best regards
-- 
	Michal Čihař | https://cihar.com/ | https://weblate.org/


On Tue, 2017-10-24 at 12:58 +0200, Sandro Santilli wrote:
> Hi, I'm evaluating the cost of setting up a translation
> service on osgeo.org infrastructure to serve all the
> projects under the open source foundation umbrella.
> 
> Is this something your "Minimal support for self hosted Weblate"
> would allow or is it to be considered a setup for a single project ?
> 
> You'd have close cooperation with admins, backend of choice
> would probably be PostgreSQL and current frontend we use
> is mostly Apache (but we could evaluate a dockerization or
> VM just for the new service).
> 
> Thank you for making a free software alternative to Transifex
> alive !
> 
> --strk; 

----- End forwarded message -----