Skip to content
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

TSC meeting July 13 #291

Closed
mhdawson opened this issue Jul 6, 2017 · 11 comments
Closed

TSC meeting July 13 #291

mhdawson opened this issue Jul 6, 2017 · 11 comments

Comments

@mhdawson
Copy link
Member

mhdawson commented Jul 6, 2017

We had agreed on monthly, but unfortunately the next meeting would then conflict with Node Summit.

I would move 1 week back/forth but that would conflict with the CommComm meeting and there are some overlapping members.

I've therefore updated the Node.js calendar to show the next meeting Thursday the 13th, and then every 4 weeks after that.

Time

UTC Thu 13-Jul-Apr-2017 20:00 (08:00 PM):

Timezone Date/Time
US / Pacific Thu 13-Jul-2017 13:00 (01:00 PM)
US / Mountain Thu 13-Jul-2017 14:00 (02:00 PM)
US / Central Thu 13-Jul-2017 15:00 (03:00 PM)
US / Eastern Thu 13-Jul-2017 16:00 (04:00 PM)
Amsterdam Thu 13-Jul-2017 22:00 (10:00 PM)
Moscow Thu 13-Jul-2017 23:00 (11:00 PM)
Chennai Thu 13-Jul-2017 01:30 (01:30 AM)
Tokyo Thu 13-Jul-2017 05:00 (05:00 AM)
Sydney Thu 13-Jul-2017 06:00 (06:00 AM)

Or in your local time:

Links

Agenda

Extracted from tsc-agenda labelled issues and pull requests from the nodejs org prior to the meeting.

nodejs/TSC

  • Candidate "areas" for TSC and Community Committee #278
  • Request: Additional 2017 Travel Fund Allocation #250
  • Copyright Date #195
  • Regular roll-up reporting for active working groups #109

tsc-review

For awareness, please review comment on these issues marked tsc-review:

nodejs/TSC

  • Candidate "areas" for TSC and Community Committee #278
  • Approval to move node-heapdump into foundation #257
  • Define Travel Fund approval requirements #254
  • Add quorum rules #253
  • Request: Asset audit report #249
  • Nominating @MylesBorins to the TSC #247
  • create public nodejs/collaborators repo #243
  • Rotating meeting times #198

Invited

Notes

The agenda comes from issues labelled with tsc-agenda across all of the repositories in the nodejs org. Please label any additional issues that should be on the agenda before the meeting starts.

Joining the meeting

NOTE As agreed in the last meeting with be help using hangouts this week:

For those who want to watch:
Link for participants:
Events link: https://www.youtube.com/my_live_events

@addaleax
Copy link
Member

addaleax commented Jul 6, 2017

Just a single data point, but I’ll be on my way to JSConf.CN one week from now, so I won’t be there.

@mhdawson
Copy link
Member Author

Looking at the items on the agenda and the later notice I might suggest that we just cancel and do it 4 weeks from now, but I believe @hackygolucky might have a high priority one to add related to the travel fund ?

@jennwrites
Copy link

You can drop me from the invite list and future ones @mhdawson.
@kbarnard10 is taking over the newsletter duties. ☺️

@jasnell
Copy link
Member

jasnell commented Jul 10, 2017

Unfortunately I'll be on a flight from NYC back to Fresno during this scheduled time so, if it's not cancelled, I won't be able to attend.

@mhdawson
Copy link
Member Author

@renrutnnej thanks for the FYI, updated.

@mhdawson
Copy link
Member Author

Just waiting to hear from @hackygolucky. If we don't hear by tomorrow my plan would be to cancel.

@mhdawson
Copy link
Member Author

This is the issue #294 (review)

@nodejs/TSC if people can comment review/there by tomorrow morning we can likely cancel the meeting.

@mhdawson
Copy link
Member Author

@nodejs/TSC for those who can make the meeting can you

  1. comment here if you can make it or not.
  2. Indicate if you have questions about Coordinate travel fund across project committees #294 that we might be able to move quickly resolve on a call versus continued discussion in github.

@MylesBorins
Copy link
Contributor

I'm planning to attend, will be at a dinner that may run late. I've approved #294 with a tiny nit.

@nebrius
Copy link
Contributor

nebrius commented Jul 13, 2017

I'm available and can attend

@mhdawson
Copy link
Member Author

So I think that the only people who have responded that they can make it have already approved #294 so I think we should cancel, push #294 forward in the github issue and then meet at the next regular scheduled time where we can get more attendees.

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

No branches or pull requests

6 participants