From amotoki at gmail.com Sat Jun 1 10:53:27 2019 From: amotoki at gmail.com (Akihiro Motoki) Date: Sat, 1 Jun 2019 19:53:27 +0900 Subject: [OpenStack-I18n] Stopping Queens stable version translation In-Reply-To: <2e930e4e-ca9e-f9c8-fe23-6d81aa469c46@gmail.com> References: <2e930e4e-ca9e-f9c8-fe23-6d81aa469c46@gmail.com> Message-ID: Sorry late post. This mail hits me a question how the upstream projects should handle translation bugs for stable branches which the translation platform (zanata) no longer supports. Should the upstream projects accept translation fixes which are directly proposed to git repositories, or can they reject them as the translation should happen in translate.openstack.org (though there is no way to fix translation actually)? Akihiro On Wed, May 8, 2019 at 10:58 PM Ian Y. Choi wrote: > > Hello team, > > > Just I would like to share with team members that I18n team will stop > translation for Queens stable version > > due to no translation activities, low demand, and low bandwidth on such > a stable branch. > > > I wanna more share that: > > - If some translators find bugs on latest two releases (Stein, Rocky), > please share via this mailing list or Launchpad. > > - Such decision will start after [1] is merged. > > - Still other bug fixes would be fine for extended maintence purpose > [2]. If someone finds significant translation bugs on such old versions, > > please share via this mailing list so that we can discuss how to deal with. > > > > With many thanks, > > > /Ian > > > [1] https://review.opendev.org/#/c/656047/ > > [2] > https://governance.openstack.org/tc/resolutions/20180301-stable-branch-eol.html > > > _______________________________________________ > OpenStack-I18n mailing list > OpenStack-I18n at lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n From ianyrchoi at gmail.com Tue Jun 4 16:13:05 2019 From: ianyrchoi at gmail.com (Ian Y. Choi) Date: Wed, 5 Jun 2019 01:13:05 +0900 Subject: [OpenStack-I18n] Stopping Queens stable version translation In-Reply-To: References: <2e930e4e-ca9e-f9c8-fe23-6d81aa469c46@gmail.com> Message-ID: <8d10bac8-cd1e-ce67-b339-e8c5c4d42689@gmail.com> Hello Motoki-san, Thank you for rasing such a good point. Can I rephrase like the followings? "translators still can report translation bugs through Launchpad and/or mailing list so that I18n team cores recognize the translation bugs, and I18n team will support for translators to fix in translate.openstack.org by changing from read-only to writable, so that translators can fix translation bugs on translate.openstack.org, and I18n team cores will propose a patch to the upstream project on a target stable branch which is in extended maintenance." With many thanks, /Ian Akihiro Motoki wrote on 6/1/2019 7:53 PM: > Sorry late post. > > This mail hits me a question how the upstream projects should handle > translation bugs for stable branches which the translation platform > (zanata) no longer supports. > Should the upstream projects accept translation fixes which are > directly proposed to git repositories, or can they reject them as the > translation should happen in translate.openstack.org (though there is > no way to fix translation actually)? > > Akihiro > > On Wed, May 8, 2019 at 10:58 PM Ian Y. Choi wrote: >> Hello team, >> >> >> Just I would like to share with team members that I18n team will stop >> translation for Queens stable version >> >> due to no translation activities, low demand, and low bandwidth on such >> a stable branch. >> >> >> I wanna more share that: >> >> - If some translators find bugs on latest two releases (Stein, Rocky), >> please share via this mailing list or Launchpad. >> >> - Such decision will start after [1] is merged. >> >> - Still other bug fixes would be fine for extended maintence purpose >> [2]. If someone finds significant translation bugs on such old versions, >> >> please share via this mailing list so that we can discuss how to deal with. >> >> >> >> With many thanks, >> >> >> /Ian >> >> >> [1] https://review.opendev.org/#/c/656047/ >> >> [2] >> https://governance.openstack.org/tc/resolutions/20180301-stable-branch-eol.html >> >> >> _______________________________________________ >> OpenStack-I18n mailing list >> OpenStack-I18n at lists.openstack.org >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n From ianyrchoi at gmail.com Tue Jun 4 16:13:29 2019 From: ianyrchoi at gmail.com (Ian Y. Choi) Date: Wed, 5 Jun 2019 01:13:29 +0900 Subject: [OpenStack-I18n] Stopping Queens stable version translation In-Reply-To: References: <2e930e4e-ca9e-f9c8-fe23-6d81aa469c46@gmail.com> Message-ID: <4b195c79-2700-1e02-eb35-2c748694cfb6@gmail.com> Hello Motoki-san, Thank you for raising such a good point. Can I rephrase like the followings? "translators still can report translation bugs through Launchpad and/or mailing list so that I18n team cores recognize the translation bugs, and I18n team will support for translators to fix in translate.openstack.org by changing from read-only to writable, so that translators can fix translation bugs on translate.openstack.org, and I18n team cores will propose a patch to the upstream project on a target stable branch which is in extended maintenance." With many thanks, /Ian Akihiro Motoki wrote on 6/1/2019 7:53 PM: > Sorry late post. > > This mail hits me a question how the upstream projects should handle > translation bugs for stable branches which the translation platform > (zanata) no longer supports. > Should the upstream projects accept translation fixes which are > directly proposed to git repositories, or can they reject them as the > translation should happen in translate.openstack.org (though there is > no way to fix translation actually)? > > Akihiro > > On Wed, May 8, 2019 at 10:58 PM Ian Y. Choi wrote: >> Hello team, >> >> >> Just I would like to share with team members that I18n team will stop >> translation for Queens stable version >> >> due to no translation activities, low demand, and low bandwidth on such >> a stable branch. >> >> >> I wanna more share that: >> >> - If some translators find bugs on latest two releases (Stein, Rocky), >> please share via this mailing list or Launchpad. >> >> - Such decision will start after [1] is merged. >> >> - Still other bug fixes would be fine for extended maintence purpose >> [2]. If someone finds significant translation bugs on such old versions, >> >> please share via this mailing list so that we can discuss how to deal with. >> >> >> >> With many thanks, >> >> >> /Ian >> >> >> [1] https://review.opendev.org/#/c/656047/ >> >> [2] >> https://governance.openstack.org/tc/resolutions/20180301-stable-branch-eol.html >> >> >> _______________________________________________ >> OpenStack-I18n mailing list >> OpenStack-I18n at lists.openstack.org >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n From ianyrchoi at gmail.com Sun Jun 9 22:57:16 2019 From: ianyrchoi at gmail.com (Ian Y. Choi) Date: Mon, 10 Jun 2019 07:57:16 +0900 Subject: [OpenStack-I18n] =?utf-8?q?OpenStack_User_Survey_translation_in_2?= =?utf-8?q?019_-_Fwd=3A_It=E2=80=99s_OpenStack_User_Survey_Time!?= In-Reply-To: References: Message-ID: <82ecf67f-febc-8e0f-b356-f934f7454c62@gmail.com> Hello I18n team members, OpenStack user survey translation is available through [1], like previous two years. Translation is synced into [2] regularly (once everyday) but please don't hesitate to share through here if there are some translation or sync issues. With many thanks, /Ian [1] https://translate.openstack.org/iteration/view/openstack-user-survey/openstack-user-survey/documents [2] https://www.openstack.org/user-survey/survey-2019 -------- Original Message -------- Subject: It’s OpenStack User Survey Time! Date: Fri, 17 May 2019 14:29:36 -0500 From: Matt Van Winkle To: openstack-discuss at lists.openstack.org Hi everyone, If you operate OpenStack, it’s time to participate in the annual OpenStack User Survey . This is your opportunity to provide direct feedback to the OpenStack community, so we can better understand your environment and needs. We send all anonymous feedback directly to the project teams who work to improve the software and documentation. The survey will take less than 20 minutes. All participants who complete the OpenStack deployment survey will receive AUC status and discounted registration to the Shanghai Summit. Please let me or any members of the User Committee know if you have any questions. Cheers, VW -- Matt Van Winkle Senior Manager, Software Engineering | Salesforce From haoyang at openstack.org Wed Jun 12 06:07:09 2019 From: haoyang at openstack.org (haoyang at openstack.org) Date: Wed, 12 Jun 2019 14:07:09 +0800 Subject: [OpenStack-I18n] =?utf-8?b?562U5aSNOiAgT3BlblN0YWNrIFVzZXIgU3Vy?= =?utf-8?q?vey_translation_in_2019_-_Fwd=3A_It=E2=80=99s_OpenStack_?= =?utf-8?q?User_Survey_Time!?= In-Reply-To: <82ecf67f-febc-8e0f-b356-f934f7454c62@gmail.com> References: <82ecf67f-febc-8e0f-b356-f934f7454c62@gmail.com> Message-ID: <010f01d520e5$13006410$39012c30$@openstack.org> Hi, Ian and Team, CHS translation of user survey is done, currently I don't see any issue on translation or sync. Let me know if anything doesn't work. Thanks, Horace -----邮件原件----- 发件人: Ian Y. Choi 发送时间: 2019年6月10日 6:57 收件人: Openstack-i18n 主题: [OpenStack-I18n] OpenStack User Survey translation in 2019 - Fwd: It’s OpenStack User Survey Time! Hello I18n team members, OpenStack user survey translation is available through [1], like previous two years. Translation is synced into [2] regularly (once everyday) but please don't hesitate to share through here if there are some translation or sync issues. With many thanks, /Ian [1] https://translate.openstack.org/iteration/view/openstack-user-survey/openstack-user-survey/documents [2] https://www.openstack.org/user-survey/survey-2019 -------- Original Message -------- Subject: It’s OpenStack User Survey Time! Date: Fri, 17 May 2019 14:29:36 -0500 From: Matt Van Winkle To: openstack-discuss at lists.openstack.org Hi everyone, If you operate OpenStack, it’s time to participate in the annual OpenStack User Survey . This is your opportunity to provide direct feedback to the OpenStack community, so we can better understand your environment and needs. We send all anonymous feedback directly to the project teams who work to improve the software and documentation. The survey will take less than 20 minutes. All participants who complete the OpenStack deployment survey will receive AUC status and discounted registration to the Shanghai Summit. Please let me or any members of the User Committee know if you have any questions. Cheers, VW -- Matt Van Winkle Senior Manager, Software Engineering | Salesforce _______________________________________________ OpenStack-I18n mailing list OpenStack-I18n at lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-i18n From robert.simai at suse.com Thu Jun 27 07:36:33 2019 From: robert.simai at suse.com (Robert Simai) Date: Thu, 27 Jun 2019 09:36:33 +0200 Subject: [OpenStack-I18n] Stackalytics for Translations broken Message-ID: Hi, I was just checking Stackalytics and found there are no results when I change the Metric to "Translations" while that used to work reliably in the past. Opened a bug https://bugs.launchpad.net/stackalytics/+bug/1834434 in case anyone has an idea. -- Thanks,    Robert From eumel at arcor.de Fri Jun 28 14:02:20 2019 From: eumel at arcor.de (Frank Kloeker) Date: Fri, 28 Jun 2019 16:02:20 +0200 Subject: [OpenStack-I18n] Stackalytics for Translations broken In-Reply-To: References: Message-ID: Am 2019-06-27 09:36, schrieb Robert Simai: > Hi, > > I was just checking Stackalytics and found there are no results when I > change the Metric to "Translations" while that used to work reliably > in the past. Opened a bug > > https://bugs.launchpad.net/stackalytics/+bug/1834434 > > in case anyone has an idea. Hi Robert, just wondering. For me it's working with Firefox on Win10. Maybe some cached fancy javascript stuff? A screenshot would be good for your trouble or the URL of the empty output. kind regards Frank From robert.simai at suse.com Fri Jun 28 14:28:11 2019 From: robert.simai at suse.com (Robert Simai) Date: Fri, 28 Jun 2019 16:28:11 +0200 Subject: [OpenStack-I18n] Stackalytics for Translations broken In-Reply-To: References: Message-ID: Hi Frank, On 28.06.19 16:02, Frank Kloeker wrote: > Am 2019-06-27 09:36, schrieb Robert Simai: >> Hi, >> >> I was just checking Stackalytics and found there are no results when I >> change the Metric to "Translations" while that used to work reliably >> in the past. Opened a bug >> >> https://bugs.launchpad.net/stackalytics/+bug/1834434 >> >> in case anyone has an idea. > > just wondering. For me it's working with Firefox on Win10. Maybe some > cached fancy javascript stuff? > A screenshot would be good for your trouble or the URL of the empty > output. > Thanks for trying. I checked again and right now it's working for me, too. I didn't delete cache or cookies meanwhile so difficult to tell if that was my browser or on the server side. Indeed, I should have tried with another/clean browser immediately ... Anyway, I'll make a comment to the bug so it can eventually be closed. -- Thanks,    Robert From fungi at yuggoth.org Fri Jun 28 14:38:09 2019 From: fungi at yuggoth.org (Jeremy Stanley) Date: Fri, 28 Jun 2019 14:38:09 +0000 Subject: [OpenStack-I18n] Stackalytics for Translations broken In-Reply-To: References: Message-ID: <20190628143808.iofsm24vkp4yvvk6@yuggoth.org> On 2019-06-28 16:28:11 +0200 (+0200), Robert Simai wrote: > On 28.06.19 16:02, Frank Kloeker wrote: > > Am 2019-06-27 09:36, schrieb Robert Simai: > > > I was just checking Stackalytics and found there are no results when I > > > change the Metric to "Translations" while that used to work reliably > > > in the past. Opened a bug > > > > > > https://bugs.launchpad.net/stackalytics/+bug/1834434 > > > > > > in case anyone has an idea. > > > > just wondering. For me it's working with Firefox on Win10. Maybe some > > cached fancy javascript stuff? > > A screenshot would be good for your trouble or the URL of the empty > > output. > > > Thanks for trying. I checked again and right now it's working for me, too. I > didn't delete cache or cookies meanwhile so difficult to tell if that was my > browser or on the server side. Indeed, I should have tried with > another/clean browser immediately ... > > Anyway, I'll make a comment to the bug so it can eventually be closed. It was very likely related to this: http://lists.openstack.org/pipermail/openstack-discuss/2019-June/007365.html -- Jeremy Stanley -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 963 bytes Desc: not available URL: