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

i18n WG Meeting - March 13th #223

Closed
obensource opened this issue Mar 13, 2020 · 8 comments
Closed

i18n WG Meeting - March 13th #223

obensource opened this issue Mar 13, 2020 · 8 comments

Comments

@obensource
Copy link
Member

Date & Time

  • 6:00pm UTC on March 6, 2020

Links

Agenda

Please feel free to add or subtract issues as is relevant. 👍

l10n

i18n

Intl

  • Onboarding new Intl contributors (not yet an issue)
    • What kind of help is needed the most in Intl right now?

Note: Please feel free to add any issues you'd like to discuss today.

Invited Members

  • @nodejs/i18n
  • @nodejs/website-redesign
  • @nodejs/community-committee
  • @nodejs/tsc
  • @nodejs/website
@obensource
Copy link
Member Author

Unfortunately, I'm currently experiencing a family health emergency and won't be able to facilitate or attend today's meeting.

If anyone is willing to facilitate – I can likely hop on to start the youtube stream. If there's no attendance, no problem. We can reconvene next week. :)

Thanks all! 🙏

@maddhruv
Copy link
Contributor

@obensource take care in this prime time, I hope everyone is healthy

Also, I also wont be able to attend

@srl295
Copy link
Member

srl295 commented Mar 13, 2020

I'm going to have to drop out this time. But I am getting some things moved forward on the locale data building front. Also ICU 66.1 shipped

@nodejs-crowdin-zz
Copy link
Contributor

I'm @zeke masquerading as @nodejs-crowdin 👋

I generated a new token with the following scopes: https://github.com/settings/tokens/new?scopes=repo,user,admin:repo_hook&description=Crowdin%20integration

...and added it to the https://crowdin.com/project/nodejs GitHub integration.

cc @alexandrtovmach

@JohnTitor
Copy link
Member

It seems @nodejs-crowdin triggers many CI builds?

@zeke
Copy link
Contributor

zeke commented Mar 13, 2020

Hi @JohnTitor what are you referring to? Can you share more details?

@JohnTitor
Copy link
Member

JohnTitor commented Mar 13, 2020

@zeke See here: https://travis-ci.com/github/nodejs/i18n/builds
Currently, travis receives every branch commits. I think we don't have to check every commit but check at once or so?

@zeke
Copy link
Contributor

zeke commented Mar 13, 2020

Yeah maybe there's a way to use Travis cron jobs for this, instead of running on every commit. Or we could use GitHub Actions. Can you open a separate issue to look into this?

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

7 participants