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

Volunteers to run TSC meeting Nov 8 and 15 #409

Closed
mhdawson opened this issue Nov 1, 2017 · 9 comments
Closed

Volunteers to run TSC meeting Nov 8 and 15 #409

mhdawson opened this issue Nov 1, 2017 · 9 comments

Comments

@mhdawson
Copy link
Member

mhdawson commented Nov 1, 2017

I'm going to be at NodeConfEU on the 8th and on holiday on the 15th.

Any volunteers to chair the meeting one or both or those dates ?

@nodejs/tsc

@Fishrock123
Copy link
Contributor

Fishrock123 commented Nov 2, 2017

I could "chair" the meetings if someone can create the issues / documents

(I could never get rod's issue tool thing to work properly..) (I understand that is part of chairing them haha)

@joshgav
Copy link
Contributor

joshgav commented Nov 2, 2017

@Fishrock123 I'll help with issues and docs if you run the stream and keep the meeting on track.

Glad neither of these is the early time :)

@mhdawson
Copy link
Member Author

mhdawson commented Nov 3, 2017

I can create the issue on Saturday for the first meeting if that helps, for the second I won't have access to the machine were my automation is.

@Fishrock123 thanks for volunteering to chair.

@Trott
Copy link
Member

Trott commented Nov 7, 2017

I can create the issue on Saturday for the first meeting

It looks like maybe this hasn't happened yet? (Perhaps because no one said "Yes, please do!")

We should see if a bot can open these for us.

@mhdawson
Copy link
Member Author

mhdawson commented Nov 7, 2017

I missed creating it before I left. I just tried remoting into my home network but I can't get in right now for some reason. I'll try again later but if its not up by tomorrow then you'll probably have to create manually.

As for the bot/automation, that is what I'm working towards. I have the scripts to do the generation automatically now creating the issues and github docs, but want to test it out a few more times before I set it up as a cron job as a first step. At that point if the automation team can set up a bot to do it at a scheduled time that would be great.

@mhdawson
Copy link
Member Author

mhdawson commented Nov 8, 2017

Sorry looks like my vpn is down for some reason and I'm not going to be able to get in so you'll have to create the issue manually like we've being doing up until a week or two ago. @Trott I'm hoping you are still setup to do that.

@mhdawson
Copy link
Member Author

mhdawson commented Nov 8, 2017

These are the issues currently tagged for the agenda:

nodejs/node

  • Support both OpenSSL 1.1.0 and 1.0.2 #16130
  • stream: move prefixed files into internal/streams. #11957

nodejs/TSC

  • doc: initial version of strategic initiatives #399
  • Proposal to form a Governance Working Group #383

nodejs/admin

  • meta: fix case of extensions on internal docs and move CoC to admin repo #25

@Trott
Copy link
Member

Trott commented Nov 8, 2017

I've reassembled my old setup for the CTC meetings and will have an issue opened for the meeting shortly.

@MylesBorins
Copy link
Contributor

Closing as it seems we have volunteers set up to do this

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

5 participants