Summit Topic: Node.js i18n, l10n, and ECMA 402 #164
Comments
|
@obensource wont be in town. if i can do anything remote i would. |
|
@srl295 sounds good! Would really love your presence there if you can so we'll plan on getting you (and any other folks who can join remotely) in on the convo via zoom or hangouts at the very least! I'll be in touch – thanks a million Steven! Really looking forward to it! 🙌 |
|
We're actively looking into making remote participation viable this year. Please voice your need on #151. Equipment estimates are not cheap but being vocal about it will strengthen the case for a larger budget allocation. |
|
@obensource 👋 excited to see you in Germany. |
|
@obensource ignore my last msg - have the information now :)
…On Thu, May 9, 2019 at 2:40 PM Benjamin E. Coe ***@***.***> wrote:
@obensource <https://github.com/obensource> 👋 excited to see you in
Germany.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#164 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AKYQ3QIDCR2TNAKULBLCMQ3PUSK5RANCNFSM4HL5DHVQ>
.
--
Eva Howe
This Dot Labs
eva@thisdot.co
|
|
Awesome @evahowe! Please let me know if you need anything from me to make this official – really appreciate it! 👏👏👏 |
|
@bcoe!!! Wahoo! 👋 Couldn't be more stoked to hang with you in Berlin too! 🎉🎉🎉 |
obensource
changed the title
|
@obensource - nope you are all set! :) |
|
Not gonna make it to Berlin for this, but I'd be happy to join remotely if that ends up happening. ☎️ |
|
@zeke awesome! 🎉🎉🎉 Wouldn't be the same without you – very stoked you'll be able to join by ☎️! |
|
I'd be very interested to join this session. For context, I maintain |
|
Excited to see you all there, and happy to facilitate the ECMA-402 part. |
|
@eemeli is also the first, pioneering, outside contributor to CLDR since it moved to git! |
|
is this the right time for the proposed session? https://time.is/1700_30_May_2019_in_Berlin/California?i18n Time zones and DST, always tricky for me. Go figure. |
|
@obensource ping ^ ? i have the above timeslot marked out.. |
|
I don't see it on the schedule, remind me what the name of the talk is?
…On Tue, May 28, 2019 at 11:25 PM Steven R. Loomis ***@***.***> wrote:
@obensource <https://github.com/obensource> ping ^ ? i have the above
timeslot marked out..
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#164>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AKYQ3QKVXX4GVFIR5MQIA23PXWWOPANCNFSM4HL5DHVQ>
.
--
Eva Howe
This Dot Labs
eva@thisdot.co
|
Howdy y'all! 🙌@srl295 @evahowe @zeke @eemeli @littledan apologies for the delay (travel mania) – our official timeslot is located here in the agenda. Session TimeThat would make the official time 14:00 CEST (12pm UTC, 5pm PST) – Steven: here's the updated countdown. ⏰ Let us know if there is a hard blocker for you at that time, I'd bet we can swap times with another session if needed. 👍 Remote participationFrom what I gather, we will have all remote participants on zoom call with us, we will be sure to facilitate the conversation in a way that democratizes it as much as possible. Y'all's participate is of utmost value in this! So stoked to connect and push this rad initiative forward with you! 🙌 |
|
@littledan very stoked to have you facilitate the ECMA-402 part of our session (thanks for offering)! 🙌 @eemeli – we're thrilled to have you with us! Can't wait! 👏👏👏 |
|
@obensource looking… i think you mean 5AM :) edit I will plan in calling in at 5AM PT…will I get the callin info? edit emailed you, so you have my contact info… |
|
@obensource @srl295 would love to join you all remotely :) |
|
This is 5am my time and I won't be able to make it. If you're able to record the call I'd love to catch up on the discussion later. |
|
We are currently talking about moving that later in the day.
Il giorno gio 30 mag 2019 alle 07:07 Zeke Sikelianos <
notifications@github.com> ha scritto:
… This is 5am my time and I won't be able to make it. If you're able to
record the call I'd love to catch up on the discussion later.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#164>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAAMXY7JG37GAGJVF2ILWD3PX5OHRANCNFSM4HL5DHVQ>
.
|
|
Time: CEST Thu 30-May-2019 14:00 (02:00 PM) |
This comment has been minimized.
This comment has been minimized.
|
@zeke @littledan @srl295 @ryzokuken @evahowe @eemeli @trivikr et al: after conferring with all the folks who've expressed interest in joining, we're going to have to keep the original time 14:00 CEST / 5am PST to maximize participation. Apologize to everyone in PST that this inconveniences. We will be recording and share that out asap. Thanks all! 🙌 |
Official Time & Place👉 Today's session with be at: 12pm UTC / 14:00 CEST / 5am PST. cc @zeke @littledan @srl295 @ryzokuken @evahowe @eemeli @trivikr |
|
@zeke I think we should snowball from here and boot up regular @nodejs/i18n WG meetings again. I'll get the video to you and connect asap! Super stoked! 🙌 |
|
Here's the agenda! nodejs/i18n#197 – please feel free to add items! |
|
Going to close since this is now past 👍 |
Topic
i18n: Moving forward with the i18n WG, Node.js Intl, and ECMA 402.
Description
A breakout session for members of the i18n WG to cover how we can continue to push forward efforts like:
Facilitators
tc39 / ECMA 402 Delegates Welcome!
Members of tc39 who will be in town early for JSConfEU have been invited to this summit, and any members of Node.js and/or tc39 are more than welcome to join us in this session! Ideally we'd love to see both delegates from ECMA 402 and @nodejs/i18n engage in an awesome, lively, and forward thinking conversation about all things i18n in JS! 🙌
The text was updated successfully, but these errors were encountered: