Skip to content
This repository has been archived by the owner on Apr 22, 2023. It is now read-only.

i18n WG Meeting - Feb 14 #209

Closed
maddhruv opened this issue Feb 4, 2020 · 28 comments
Closed

i18n WG Meeting - Feb 14 #209

maddhruv opened this issue Feb 4, 2020 · 28 comments
Labels
wg-meeting Working Group Meeting

Comments

@maddhruv
Copy link
Contributor

maddhruv commented Feb 4, 2020 •
edited by obensource
Loading

Date & Time

  • 5:00 pm GMT on Feb 14, 2020

Links

Agenda

Invited Members

  • @nodejs/i18n
  • @nodejs/website-redesign
  • @nodejs/community-committee
  • @nodejs/tsc
  • @nodejs/website
@maddhruv maddhruv added the wg-meeting Working Group Meeting label Feb 4, 2020
@nschonni
Copy link
Member

nschonni commented Feb 4, 2020

Should the regular website team also be invited? They're impacted by the first agenda item

@maddhruv
Copy link
Contributor Author

maddhruv commented Feb 4, 2020

Sure, included 👍

@obensource
Copy link
Member

obensource commented Feb 4, 2020 •
edited
Loading

@maddhruv @nschonni imo, we should overlap soon – but for this next i18n WG meeting, there's going to be enough logistics to cover to get the i18n WG back in sync, etc, that it would probably be better time spent joining us at the next WG meeting with website i18n on the agenda. Y'all should join if you'd like and might get something out of it, but just fyi (this is kind of a 'regroup' meeting since a bit of time has passed since we last met).

@obensource
Copy link
Member

@zeke! If you're able, come join us! 🙌🎉🍻

@obensource
Copy link
Member

@srl295 if you're able, please join us! It would be awesome to have your amazing wizardry with us to help push things forward! 🧙‍♂️

research

@zeke
Copy link
Contributor

zeke commented Feb 4, 2020

Thanks for the ping. I doodled.

@RichardLitt
Copy link
Contributor

So, we have our dates, but we didn't decide on a process for dealing with times for when there is no consensus. I'm leaning towards the February the 14th time, if only because I know that @zeke has been instrumental. @TiagoDanin Is there any way you can make that time?

@RichardLitt
Copy link
Contributor

Looks like I also failed to set an end-date. Thanks for filling this out, Aymen. At the moment, it seems that the 14th is the best day for the most people. Shall we go with that time, everyone?

@obensource
Copy link
Member

@RichardLitt sounds great, looks like that's what works best for everyone – let's do it! 🎉

Thanks for wrangling us together via doodle! 🙏

@TiagoDanin
Copy link
Contributor

@TiagoDanin Is there any way you can make that time?

I'll do my best, but I’m not promising anything 😃

@maddhruv maddhruv changed the title i18n WG Meeting - (Date- TBD) i18n WG Meeting - Feb 14 Feb 11, 2020
@RichardLitt
Copy link
Contributor

Awesome. See you all there!

Does anyone have a paid Zoom account? Mine would cap us at 40 minutes, which might be a good idea anyway.

@obensource
Copy link
Member

@RichardLitt Wahoo! See you there! 🙌

@bnb – can we use the node.js zoom account? Would be fun to capture & stream if possible. 😄

@bnb
Copy link

bnb commented Feb 13, 2020

@obensource yes. Currently on a train but ping me on Slack so I can get you the credentials.

@obensource
Copy link
Member

@bnb RAD will do! Thanks a million! 🙏

@maddhruv
Copy link
Contributor Author

Literally forgot to create a calendar event, added now - calendar event

@obensource
Copy link
Member

Haven't been able to receive the node zoom credentials yet, not a big deal if not – I'll share a zoom link shortly before the meeting regardless, record the meeting, and post it on our YT channel in post if needed. 👍

cc @bnb (thanks for your help! 🙏)

@obensource
Copy link
Member

Got the creds from @bnb, getting YT access for streaming now as well – will share the link shortly. 👍

@RichardLitt
Copy link
Contributor

Fantastic. Thanks @bnb.

@obensource
Copy link
Member

obensource commented Feb 14, 2020 •
edited
Loading

Zoom link unlocked! Here it is! 🎉Got streaming set up as well, we're gtg.👍

Also fyi, I can change it at any point, but I set this as a weekly reoccurring zoom call at this time for now (I can revive the issue about meeting time/frequency to land on the optimal time) – I'm going to plan on making myself available at this time weekly so we can pick up momentum with this initiative.

@obensource
Copy link
Member

@maddhruv I noticed that the permissions on the minutes doc weren't set (read only), so I made a new one with edit access for everyone and updated the link in the issue description. 👍

@maddhruv
Copy link
Contributor Author

maddhruv commented Feb 14, 2020 •
edited
Loading

I am very sorry, could't attend the meeting, got stuck into something unavoidable. 😣😣

I'll best follow up on minutes and the recording

@alexandrtovmach
Copy link
Contributor

alexandrtovmach commented Feb 14, 2020 •
edited
Loading

Hello guys,
Unfortunately, I haven't time to join but I'm really interested in questions that you discussed. So I've checked report and just want to let you know, I'd like to help with translations process.
I'd like to share my vision of steps:

  1. As you mentioned, we already had a lot of translated stuff on Crowdin side, but it's not correctly connected to nodejs repos, and that's the first step before we move forward. We can talk more about that here Unblock translation process nodejs.org#2906. I just need this API keys to fix Nodejs<->Crowdin connection.

  2. Second thing, is awesome to give a bit more info about "how to contribute for translators", but I think we need to brainstorm one more time, because we can have different ideas how it's should be. Somewhere in 2019 I tried to handle all translation flow (but faced with blockers), so I have some not realized plan like: "all translations should be on Crowdin side, and automated by hooks, PR and CI/CD".

  3. We still haven't configured CI/CD to build website, docs on different languages

Sorry for the randomness and errors, writing from phone (I'm testing github android app =)). Hope to break the current stalemate, and see you soon on next meeting

@zeke
Copy link
Contributor

zeke commented Feb 19, 2020

Eek! Sorry I missed this meeting, y'all.

I would love to attend the next one. Unfortunately, I don't think I can make it to that 10:30pm Pacific time slot. I'm usually offline (and asleep!) by that time. If it's possible to do another doodle that would make my chances of attendance much higher.

@obensource
Copy link
Member

@zeke oh, sorry if there's been a miscommunication! We're meeting weekly on Fridays at 10am PT (6pm UTC) at the moment. 👍

@obensource
Copy link
Member

We'll likely need to do a bi-monthly or monthly meeting at a time that's ideal globally like that as well in order to make this group accessible to everyone.

@obensource
Copy link
Member

I'll get a reoccurring calendar invite going for everyone asap. 🙌

@obensource
Copy link
Member

obensource commented Feb 19, 2020 •
edited
Loading

Accidentally closed this issue (on mobile), however the meeting has passed so I guess it's ok.

@alexandrtovmach so excited to get things moving with your and very thankful for your continued help! 🙌

@zeke
Copy link
Contributor

zeke commented Feb 19, 2020

We're meeting weekly on Fridays at 10am PT

Nice! I have a conflict this week, but that's generally a good time slot for me. 👍

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
wg-meeting Working Group Meeting
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
8 participants
@zeke @bnb @RichardLitt @nschonni @obensource @TiagoDanin @maddhruv @alexandrtovmach