<html>
  <head>
    <meta content="text/html; charset=windows-1252"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <div class="moz-cite-prefix">Thank you Akihiro and Doug!<br>
      <br>
      Please see my comment inline.<br>
      <br>
      <br>
      Doug Hellmann wrote on 10/8/2016 11:35 PM:<br>
    </div>
    <blockquote
      cite="mid:D3C9A6F7-DF91-40AF-B464-3F88AB1C4093@doughellmann.com"
      type="cite">
      <meta http-equiv="Content-Type" content="text/html;
        charset=windows-1252">
      <br class="">
      <div>
        <blockquote type="cite" class="">
          <div class="">On Oct 8, 2016, at 5:55 AM, Akihiro Motoki <<a
              moz-do-not-send="true" href="mailto:amotoki@gmail.com"
              class="">amotoki@gmail.com</a>> wrote:</div>
          <br class="Apple-interchange-newline">
          <div class="">
            <div dir="ltr" class="">
              <div class="">Hi i18n team,</div>
              <div class="">CC: Doug from the release team.</div>
              <div class=""><br class="">
              </div>
              <div class="">We are now preparing translated version of
                release notes.</div>
              <div class="">I would like to discuss the import criteria
                of release notes translation.</div>
              <div class="">If there is a better way, it would be great.</div>
              <div class=""><br class="">
              </div>
              <div class="">== Problem ==</div>
              <div class=""><br class="">
              </div>
              <div class="">Release notes translation is imported when
                75% of a PO file is translated.<br class="">
              </div>
              <div class="">75% is calculated as a whole.</div>
              <div class=""><br class="">
              </div>
              <div class="">If a language team wants to translate
                release notes of a specific release,<br class="">
              </div>
              <div class="">the team needs to translate release notes of
                other releases.</div>
              <div class="">This comes from the fact that the
                translation percentage is calculated as a whole.</div>
              <div class=""><br class="">
              </div>
              <div class="">The development teams started to use reno
                for translation at the beginning of Mitaka cycle</div>
              <div class="">and Liberty release notes are converted into
                reno-based release notes.</div>
              <div class="">This mean if we want to publish Newton
                release notes translation, we need to translate</div>
              <div class="">release notes for Liberty and Mitaka at the
                same time.</div>
              <div class=""><br class="">
              </div>
              <div class="">== Proposal ==</div>
              <div class=""><br class="">
              </div>
              <div class="">I hope we can publish translated release
                notes per release.</div>
              <div class="">If Newton release notes translation
                completes, I want to publish Newton release notes.</div>
              <div class="">My proposal is to change the import criteria
                for release notes translation</div>
              <div class="">to 75% at least for a specific release.</div>
            </div>
          </div>
        </blockquote>
        <div><br class="">
        </div>
        <div>I agree that it makes sense to translate by release, if we
          can make the tool changes needed. I don’t have an opinion
          about what percent of the text needs to be translated for it
          to be useful — I’m sure all of you have more insight into that
          than I do.</div>
        <br class="">
      </div>
    </blockquote>
    I just thought that we needed to take care of all releases since
    Zanata has 'only' master branch for releasenotes,<br>
    and so I have not thought 'translate by release' concept.<br>
    It will be great for translation by release.<br>
    <br>
    Thank you Akihiro-san for 'translate by release' idea with
    implementation commit request.<br>
    <br>
    IMO upper percent value is fine, since the values are the same in
    common_translate_update.sh [3].<br>
    <br>
    [3]
<a class="moz-txt-link-freetext" href="http://git.openstack.org/cgit/openstack-infra/project-config/tree/jenkins/scripts/common_translation_update.sh#n563">http://git.openstack.org/cgit/openstack-infra/project-config/tree/jenkins/scripts/common_translation_update.sh#n563</a><br>
    <br>
    <br>
    <blockquote
      cite="mid:D3C9A6F7-DF91-40AF-B464-3F88AB1C4093@doughellmann.com"
      type="cite">
      <div>
        <blockquote type="cite" class="">
          <div class="">
            <div dir="ltr" class="">
              <div class=""><br class="">
              </div>
              <div class="">If translation progress of release notes are
                less than 40% for all releases,</div>
              <div class="">a corresponding PO file will be removed from
                the repo.<br class="">
              </div>
              <div class=""><br class="">
              </div>
              <div class="">I proposed an infra scirpt change to
                implement the above.<br class="">
              </div>
              <div class=""><a moz-do-not-send="true"
                  href="https://review.openstack.org/#/c/383622/"
                  class="">https://review.openstack.org/#/c/383622/</a><br
                  class="">
              </div>
              <div class="">Proposed threshold 75% and 40% might need to
                be revisited.<br class="">
              </div>
            </div>
          </div>
        </blockquote>
      </div>
    </blockquote>
    By the way, I think we need to discuss the value minimum: 40%, since
    the value has been changed from previous 20% (actually 8% in
    script).<br>
    <br>
    I have updated [4] about several months ago. At that time I just
    referred Wiki documentation [5].<br>
    On March, the value was still 20% [6].<br>
    <br>
    IMO Andreas temporally changed the value from 20% to 30% [7] and 40%
    [8] for cleaning up purposes.<br>
    So which minimum percent value would be appropriate for I18n team?<br>
    <br>
    <br>
    [4]
    <a class="moz-txt-link-freetext" href="http://docs.openstack.org/developer/i18n/infra.html#translation-jobs">http://docs.openstack.org/developer/i18n/infra.html#translation-jobs</a><br>
    [5]
<a class="moz-txt-link-freetext" href="https://wiki.openstack.org/wiki/Translations/Infrastructure#Translation_percentage_changes">https://wiki.openstack.org/wiki/Translations/Infrastructure#Translation_percentage_changes</a><br>
    [6]
<a class="moz-txt-link-freetext" href="http://lists.openstack.org/pipermail/openstack-i18n/2016-March/001993.html">http://lists.openstack.org/pipermail/openstack-i18n/2016-March/001993.html</a><br>
    [7] <a class="moz-txt-link-freetext" href="https://review.openstack.org/#/c/372141/">https://review.openstack.org/#/c/372141/</a><br>
    [8] <a class="moz-txt-link-freetext" href="https://review.openstack.org/#/c/375285/">https://review.openstack.org/#/c/375285/</a><br>
    <blockquote
      cite="mid:D3C9A6F7-DF91-40AF-B464-3F88AB1C4093@doughellmann.com"
      type="cite">
      <div>
        <blockquote type="cite" class="">
          <div class="">
            <div dir="ltr" class="">
              <div class=""><br class="">
              </div>
              <div class="">== Open question ==<br class="">
              </div>
              <div class=""><br class="">
              </div>
              <div class="">Do we publish translated release notes for a
                release with <75% progress?</div>
              <div class="">This is about publishing rendered release
                notes.<br class="">
              </div>
              <div class=""><br class="">
              </div>
              <div class="">For example, assume my lang team have
                translated release notes<br class="">
              </div>
              <div class="">90% for Newton, 10% for Mitaka and Liberty.
                In this case, which is better</div>
              <div class="">not to publish Mitaka and Liberty release
                notes translation or to publish all?</div>
              <div class=""><br class="">
              </div>
              <div class="">My vote is not to publish less-translated
                version of release notes.</div>
            </div>
          </div>
        </blockquote>
      </div>
    </blockquote>
    +1<br>
    <br>
    Also I have a question.<br>
    So the criteria "for release notes translation to 75% at least for a
    specific release" means<br>
    for all the project repositories, or for one project repository?<br>
    <br>
    For example, if one language team is interested mainly in Nova
    Newton release, the team<br>
    translated only releasenotes strings for Newton release in
    openstack/nova repository, then would it be published?<br>
    <br>
    I am not currently sure how translated releasenotes landing page
    will be built and/or organized,<br>
    but I think it is not a good idea to add just a link to Newton
    horizon releasenotes page in docs.o.o/[language]/index.html page.<br>
    <br>
    <blockquote
      cite="mid:D3C9A6F7-DF91-40AF-B464-3F88AB1C4093@doughellmann.com"
      type="cite">
      <div>
        <blockquote type="cite" class="">
          <div class="">
            <div dir="ltr" class="">
              <div class=""><br class="">
              </div>
              <div class="">== Note ==</div>
              <div class=""><br class="">
              </div>
              <div class="">Question from Ian on the gerrit review.</div>
              <div class=""><span style="font-family: sans-serif; white-space: pre-wrap;" class="">By the way, is it possible to see only Newton release note strings in Zanata?</span><br
                  class="">
              </div>
              <div class=""><span style="font-family: sans-serif; white-space: pre-wrap;" class="">Answer: The current Zanata version we use does not support filtering by an original filename.</span><br
                  class="">
              </div>
              <div class=""><span style="font-family: sans-serif; white-space: pre-wrap;" class="">You need to check English release notes like [1] or [2] and search strings on Zanata.</span></div>
              <div class=""><font class="" face="sans-serif"><span style="white-space:pre-wrap" class="">[1] <a moz-do-not-send="true" href="https://releases.openstack.org/newton/index.html" class="">https://releases.openstack.org/newton/index.html</a></span></font></div>
              <div class=""><font class="" face="sans-serif"><span style="white-space:pre-wrap" class="">[2] </span></font><span style="white-space: pre-wrap; font-family: sans-serif;" class=""><a moz-do-not-send="true" href="http://docs.openstack.org/releasenotes/horizon/" class="">http://docs.openstack.org/releasenotes/horizon/</a></span></div>
              <div class=""><br class="">
              </div>
            </div>
          </div>
        </blockquote>
      </div>
    </blockquote>
    Oh I have not thought such methods: using two web browser windows,
    one is for English release notes and and the other is for string
    search in Zanata :)<br>
    <br>
    <br>
    With many thanks,<br>
    <br>
    /Ian
    <blockquote
      cite="mid:D3C9A6F7-DF91-40AF-B464-3F88AB1C4093@doughellmann.com"
      type="cite">
      <div>
        <blockquote type="cite" class="">
          <div class="">
            <div dir="ltr" class="">
              <div class="">Akihiro</div>
              <div class=""><br class="">
              </div>
            </div>
          </div>
        </blockquote>
      </div>
      <br class="">
      <br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <br>
      <pre wrap="">_______________________________________________
OpenStack-I18n mailing list
<a class="moz-txt-link-abbreviated" href="mailto:OpenStack-I18n@lists.openstack.org">OpenStack-I18n@lists.openstack.org</a>
<a class="moz-txt-link-freetext" href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n</a>
</pre>
    </blockquote>
    <p><br>
    </p>
  </body>
</html>