-
Notifications
You must be signed in to change notification settings - Fork 577
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
LTS Meeting March 13 - 5 EST #185
Comments
thanks for taking the lead @mhdawson I've been pretty buried and really appreciate the help |
I'd like to join this meeting if possible (not sure what the rules are for joining). |
@MylesBorins I saw a comment on another issue about you being out today ? Are you going to be able to make it. I've set the time/date to match what is in the community google calendar. |
@gibfahn, I'd say just join, I don't think there will be any objections. |
I'll plan to post the PR for the minutes in the next day or so. |
PR for minutes: #187 |
LTS Codename? Logical choices seem to be a C from the periodic table, which comes down to:
Carbon seems like the best fit, with a low atomic number, and ends in -on like the 2 other codenames. Chromium, would be too confusing. |
@binoculars codename is being discussed here: #163 |
Minutes landed, closing... |
Present
@nodejs/lts
When
9PM Monday March 13 UTC, or in your local timezone:
https://www.timeanddate.com/worldclock/fixedtime.html?msg=Node.js+LTS+Working+Group+Meeting&iso=20170313T17&p1=179&ah=1
Where
Hangouts on Air:
Agenda
nodejs/LTS
other
Minutes
Should we consider swapping the timeframe for Active LTS and Maitanance lts-agenda [#130 ] (#130)
https://docs.google.com/document/d/1qaloPiXAZd5Pf3H0CtzW7m5kk-ahOKZg622KXAr8ehE/edit
The text was updated successfully, but these errors were encountered: