Hi Randy

Pls see inline. I might be responding slow due to my paid work, but I hope this is not too late yet.

On Thu, Oct 5, 2017 at 5:42 AM, Jean-Baptiste Holcroft <jean-baptiste@holcroft.fr> wrote:
Le 25/09/2017 à 21:18, Randy Barlow a écrit :

During Friday's FESCo meeting[0] we were asked to approve a change to
the release schedule to accommodate translation string freeze deadlines
that somehow got left out of the new "no-alphas" schedule.

Several participants pointed out that Fedora has not enforced the
"string freeze" in many years, despite it being on the schedule until
now. Thus, we would like to revisit the string freeze policy to
determine if it is still valuable, and if so, how can/should it be enforced?

We'd like to explore a couple of questions:

* What exact things are frozen? Things like comps make sense to follow
   Fedora freezes, but do things like anaconda? or system-config-printer?

* Can we automate some way of enforcing or at least detecting when
   something changes a string in the freeze?

This ticket tracks the issue:

Hi Randy,

well, I think this was discussed already twice.

First, the link you already had for your meeting: https://lists.fedoraproject.org/archives/list/trans@lists.fedoraproject.org/thread/XVX4YQCN4MVCHBSSNXMAWOFGMNSUAUTR/
Second, in our last meeting: https://lists.fedoraproject.org/archives/list/trans@lists.fedoraproject.org/message/L52XG2XKGVSGORL5GRBHCETOOWBXP224/

* First question: "What exact things are frozen? Things like comps make sense to follow Fedora freezes, but do things like anaconda? or system-config-printer?"

     * My suggestion would be to get some help from Fesco to make our translator list (priority package from Zanata) an distribution-wide list.
     * As we know, there is no way to force this, only communicate and convince upstream that it's a benefit for everyone.

 +1, to Jean-Baptiste
Let me add a bit of what exactly would be helpful for us.

I strongly hope, many of packages should be able to follow the software string freeze just being implemented recently by Jan. Could you confirm this works on your side? In case not, we have to discuss further.

I understand that you are pointing some specific packages which likely need changes after the deadline, such as comps, anaconda, etc. For these, most likely and hystorically, translation team could/can accommodate late change, if a developer explicitly inform us. 

So one step up, let me propose/ask my idea if it works;
Can you of FESCO (and developers) coordinate/collect the information of which packages need to get translation update after the deadline (aka last minute change) from the developers, and inform us with the break list with the date by when the developers would like to receive the translation update?

 * Second question: "Can we automate some way of enforcing or at least detecting when something changes a string in the freeze?"

     * We are doing a proof of concept with transtats for F28, if this works, it should answer the question

For this, I think, a developer knows a change cz he makes a change (aka accountable). As above, some coordination and communication would help here a lot, I believe. Btw, it would be nice to have an automate tool.

Thanks for reading me.


I don't think we can go any further for now, the subject is wide, and the solution is not trivial.
Our next meeting is Monday (October 9th), if no more reaction either here or in https://pagure.io/g11n/issue/42 I think we should use this as work hypotheses for the 1st question, and reopen the automation subject after our proof of concept.

Have a nice day,

Jean-Baptiste Holcroft

trans mailing list -- trans@lists.fedoraproject.org
To unsubscribe send an email to trans-leave@lists.fedoraproject.org