[openstack-dev] [election][tc]Question for candidates about global reachout
Fred Li
yongle.li at gmail.com
Sun Sep 16 02:50:00 UTC 2018
As a non-native English speaker, it is nice-to-have that some TC or BoD can
stay in the local social media, like wechat group in China. But it is also
very difficult for non-native Chinese speakers to stay find useful
information in ton of Chinese chats.
My thoughts (even I am not a TC candidate) on this is,
1. it is kind of you to stay in the local group.
2. if we know that you are in, we will say English if we want you to notice.
3. since there is local OpenStack operation manager, hope he/she can
identify some information and help to translate, or remind them to
translate.
My one cent.
On Sun, Sep 16, 2018 at 2:21 AM, Zhipeng Huang <zhipengh512 at gmail.com>
wrote:
> Ya I think the whole point here (the question per se )is just to gauge if
> TC Candidates are willing to engage with regional developer in a way that
> is best fitting for that region.
>
> It surly will take other measures to make this entire effort work . On
> that I totally agree with you that there should be ambassadors to help
> facilitate the discussion, and the end goal is always to go to upstream
> instead of the convo ending in local or downstream.
>
>
> On Sat, Sep 15, 2018, 9:52 AM Matt Riedemann <mriedemos at gmail.com> wrote:
>
>> On 9/14/2018 1:52 PM, Zhipeng Huang wrote:
>> > This is a joint question from mnaser and me :)
>> >
>> > For the candidates who are running for tc seats, please reply to this
>> > email to indicate if you are open to use certain social media app in
>> > certain region (like Wechat in China, Line in Japan, etc.), in order to
>> > reach out to the OpenStack developers in that region and help them to
>> > connect to the upstream community as well as answering questions or
>> > other activities that will help. (sorry for the long sentence ... )
>> >
>> > Rico and I already sign up for Wechat communication for sure :)
>>
>> Having had some experience with WeChat, I can't imagine I'd be very
>> useful in a nova channel in WeChat since the majority of people in that
>> group wouldn't be speaking English so I wouldn't be of much help, unless
>> someone directly asked me a question in English. I realize the double
>> standard here with expecting non-native English speakers to show up in
>> the #openstack-nova freenode IRC channel to ask questions. It's
>> definitely a hard problem when people simply can't speak the same
>> language and I don't have a great solution. Probably the best common
>> solution we have is having more people across time zones and language
>> barriers engaging in more discussion in the mailing list (and Gerrit
>> reviews of course). So maybe that means if you're in WeChat and someone
>> is blocked or has a bigger question for a specific project team,
>> encourage them to send an email to the dev ML - but that requires
>> ambassadors to be in WeChat channels to make that suggestion. I think of
>> this like working with product teams within your own company. Lots of
>> those people aren't active upstream contributors and to avoid being the
>> middleman (and thus bottleneck) for all communication between upstream
>> and downstream teams, I've encouraged the downstream folk to send an
>> email upstream to start a discussion.
>>
>> --
>>
>> Thanks,
>>
>> Matt
>>
>> ____________________________________________________________
>> ______________
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe: OpenStack-dev-request at 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-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
--
Regards
Fred Li (李永乐)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20180916/1cabeffc/attachment.html>
More information about the OpenStack-dev
mailing list