Re: String Freeze milestone timing

2.09.2017 16:56 Piotr Drąg <[email protected]> wrote:
>
>
> 2017-09-02 15:29 GMT+02:00 Jan Kurik <[email protected]>:
> > As far as I understand the scope of translation we (as Fedora
> > community) provide, the String Freeze should apply only to packages in
> > Zanata. Projects which are not translated by our (Fedora) community
> > might have independent cycle and the String Freeze does not apply on
> > these.
> >
> > Hopefully someone more senior in this area might answer these
> > questions, if I am wrong :-)
> >
>
> In theory, the string freeze is about projects in the “main” group, as
> opposed to the “upstream” group:
>
> https://fedora.zanata.org/version-group/list
>
> In practice, we have no way to enforce it and we rely exclusively on
> good will of the developers.

True, this does not apply to the projects where Fedora only pulls
whatever source code is released by upstreams, including translations
already, and rebuilds and packages it.

But even if a translation of a project is hosted in Zanata we
have no power to enforce their release cycle. Therefore I think
we should change the perspective and instead of talking about projects
translated in Zanata we should talk about projects where Fedora acts
as an upstream as well. That means, the projects hosted at pagure.io.
While eventually "being hosted at pagure.io" should mean the same as
"being translated in Zanata". That means that projects are encouraged
to be both translated in Zanata and hosted at pagure.io. But as long
as exceptions exist we must accept that some projects will want to
be translated in Zanata but will not follow our release cycle.
We are encouraging other projects to join Zanata but we are not telling
them "OK, you agreed so now you must follow our release cycle" or
"either you decide to follow or you are removed from Zanata".
If the projects don't follow the release cycle the consequence is that
their translations may be incomplete or delayed and then it's their
problem if they accept it or not, also it's our problem if we as
packagers accept the upstream source code with some l10n issues.

Shortly, my point is that if we change perspective from Zanata to
pagure.io it defines the area where we have power to control the
upstream release cycle because we are the upstream.

Regards,

Rafal
_______________________________________________
trans mailing list -- [email protected]
To unsubscribe send an email to [email protected]