hmm... It's true that a core CPL can help to get translation patch merged in time, more conveniently than a non-core CPL.
But if there is non-core i18n CPL who can - understand project release schedule very well - understand project i18n status and technologies - manage to get translation patch merged in time I agree core is not a required condition. Best regards Ying Chun Guo (Daisy) Sylvain Bauza <[email protected]> wrote on 03/04/2016 07:36:50 PM: > From: Sylvain Bauza <[email protected]> > To: "OpenStack Development Mailing List (not for usage questions)" > <[email protected]> > Date: 03/04/2016 07:40 PM > Subject: Re: [openstack-dev] [all][i18n] Liaisons for I18n > > > Le 04/03/2016 12:24, Ihar Hrachyshka a écrit : > Tony Breeds <[email protected]> wrote: > On Mon, Feb 29, 2016 at 05:26:44PM +0800, Ying Chun Guo wrote: > If you are interested to be a liaison and help translators, > input your information here: > https://wiki.openstack.org/wiki/CrossProjectLiaisons#I18n . > > So https://wiki.openstack.org/wiki/CrossProjectLiaisons#I18n > > says the CPL needs to be a core. That reduces the potential pool ofpeople to > those that are already busy. Is there a good reason for that? > > I'd suspect all that's required is a good working relationship with > the project > cores. > > Yes. I believe it’s fair to say that most liaison positions do not > require coreship (which is strictly about review participation and > not the only indicator of person’s involvement in the project). > > I don't see much of interest of asking people to be cores and that's > even counter-productive. > We should rather welcome any contributor willing to help the > projects so that their could flourish nicely. > > On a practical PoV, only the Zanata translation patches are really > needing approval rights, but that's something a i18n non-core CPL > could manage just by raising the priority to the core team whenever needed. > > -Sylvain > Ihar > > __________________________________________________________________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: [email protected]?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > __________________________________________________________________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: [email protected]?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: [email protected]?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
