Communitshift would give a bit more flexibility, for example in adding
machine translation - Pontoon is well suited to the Mozilla workflow
because they can actively modify it. Am not a member of infrastructure
group, but am happy to help.
On 8/15/19 1:06 PM, Jean-Baptiste wrote:
> Well, using community shift is an option if some people are OK with assuming the
maintenance of the tool (without the infrastructure team support) for the coming years.
>
> This is a responsibility I personally won't assume.
>
> I opened a request to the council to make it hosted by the Weblate company, so we
have a sustainable hosting with upstream support.
> We should only focus on the tool management (adding a project, a component, managing
groups...) a no sysadmin tasks.
>
>
> -------- Courriel d’origine --------
> De : Michal Konecny <michal.konecny(a)packetseekers.eu>
> Envoyé : 15 août 2019 11:39:35 GMT+03:00
> À : Fedora Translation Project List <trans(a)lists.fedoraproject.org>
> Objet : Re: Translation platform migration: status update
>
> I recommend to use Communishift for hosting our own Weblate. See
https://fedoraproject.org/wiki/Infrastructue/Communishift
>
> It's an Openshift instance for community hosted by Fedora Infrastructure team.
>
> Best regards,
> zlopez
> _______________________________________________
> trans mailing list -- trans(a)lists.fedoraproject.org
> To unsubscribe send an email to trans-leave(a)lists.fedoraproject.org
> Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines:
https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
https://lists.fedoraproject.org/archives/list/trans@lists.fedoraproject.org