-
Notifications
You must be signed in to change notification settings - Fork 39
Translators for our WG Meetings #20
Comments
Thanks, @obensource! For this next call, I think we should wait until it is scheduled, and then field requests for translators from participants. Do you know when the next CommComm meeting is? |
@RichardLitt the next CommComm meeting is tomorrow. I provided the wrong link above, apologies–updated it. :) I'll secure the date of our next meeting on Friday, and then we can see if participants need translation help, definitely. Thank you Richard! 👍 |
Post CommComm-meeting update@ZibbyKeaton gave us the go ahead to ping her when we need help to field & request assistance from translators in our community via the Node.js twitter profile. Thanks Zibby! 🎉🎉🎉 |
I just sign-in the Monday doodle |
Yes, please just ping me with your needs and I can share info on social and also send notes to Node.js Foundation members to see if they can support here too. |
Checking in to see if there's anything needed this week or next in promoting efforts here? If so, just send me an email zkeaton@linuxfoundation.org or comment here, so I can stay up to speed with support. |
Thank you @ZibbyKeaton! 🍻 At present, I believe the goal is to reach out as necessary if anyone expresses a need for translation. That need wasn't expressed for our first meeting yesterday, but I'm sure it will be in future meetings–so we will reach out as it arises. Thanks so much for helping us out in this way and being super awesome! 😎 |
Purpose
We'd like everyone involved in our WG to have the same understanding of what's going on, and be able to have the same opportunity to weigh in on every decision we make–without being held back by a language barrier.
Description
As @RichardLitt brought up in the discussion around our first i18n WG meeting: It would be advantageous to start searching for "on call" translators for our WG calls. This is probably an achievable goal if we reach out to the community via CommComm, Twitter, and our l10n groups.
TODO
The text was updated successfully, but these errors were encountered: