-
Notifications
You must be signed in to change notification settings - Fork 39
i18n WG Meeting - Feb 28 #217
Comments
@obensource seems busy, so I took the responsibility of creating this issue. Please mention any issues/points to discuss today. |
I won't be able to join even this time, stuck in some other meetings |
@alexandrtovmach thanks for creating this issue, I really appreciate it! 🙏 @nodejs/i18n – on that note, I hope everyone feels like they can pitch in anywhere (like @alexandrtovmach, and @maddhruv a couple weeks ago) if something needs to be done. We're all in this together! In this case, it would be nice to automate opening and closing our WG meeting issues – which we can definitely do with create-meeting-artifacts (the tool most folks use in Node.js for this). I'll post more info for the meeting in about 1/2 an hour. See y'all soon! 🍻 |
I was wondering if it would make sense to remove (or possibly hide) from crowdin the directories of old documentation like v6.x or v8.x to help avoid confusion for incoming members of the Spanish translation group. @alexandrtovmach is that possible? |
@a0viedo as a quick solution added mark "Low priority": I can permanently remove original files, but I'm not sure that's the good idea. Let me research a bit |
Low priority would also help, deleting might be irreversible...if there was an alternative similar to hiding those directories I think it would be the best option. |
Hey y'all! I am hoping to make it to this week's meeting on March 6. Do we use the same zoom URL for each weekly meeting? |
@zeke we do! Setting things up for tomorrow's meeting issue/minutes now. Would you mind sending me the email address you use for calendar invites via keybase or your preferred messaging method so I can invite you to the recurring event? Thanks a million! 🍻 |
Date & Time
Links
Agenda
l10n
i18n
Intl
Note: Please feel free to add any issues you'd like to discuss today.
Invited Members
The text was updated successfully, but these errors were encountered: