Have just updated myself as a murano liaison. Would be happy to help with i18n’ing murano-dashboard!
-- Kirill Zaitsev Murano team Software Engineer Mirantis, Inc On 29 February 2016 at 12:29:15, Ying Chun Guo (guoyi...@cn.ibm.com) wrote: Just noticed the previous mail is not in good format. Send again for your reading easily. Sorry for the inconveniency. --- Hello, Mitaka translation will start soon, from this week. In Mitaka translation, IBM full time translators will join the translation team and work with community translators. With their help, I18n team is able to cover more projects. So I need liaisons from dev projects who can help I18n team to work compatibly with development team in the release cycle. I especially need liaisons in below projects, which are in Mitaka translation plan: nova, glance, keystone, cinder, swift, neutron, heat, horizon, ceilometer. I also need liaisons from Horizon plugin projects, which are ready in translation website: trove-dashboard, sahara-dashboard,designate-dasbhard, magnum-ui, monasca-ui, murano-dashboard and senlin-dashboard. I need liaisons tell us whether they are ready for translation from project view. As to other projects, liaisons are welcomed too. Here are the descriptions of I18n liaisons: - The liaison should be a core reviewer for the project and understand the i18n status of this project. - The liaison should understand project release schedule very well. - The liaison should notify I18n team happens of important moments in the project release in time. For example, happen of soft string freeze, happen of hard string freeze, and happen of RC1 cutting. - The liaison should take care of translation patches to the project, and make sure the patches are successfully merged to the final release version. When the translation patch is failed, the liaison should notify I18n team. If you are interested to be a liaison and help translators, input your information here: https://wiki.openstack.org/wiki/CrossProjectLiaisons#I18n . Best regards Ying Chun Guo (Daisy) __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
__________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
