-
Notifications
You must be signed in to change notification settings - Fork 8
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
Initiative needs a champion #13
Comments
Tweet went out after last TSC meeting thanks @joyeecheung, but still not volunteer to be the champion. |
We agreed to remove the initiative for now from the list since we've not had a volunteer to champion. I looked after the meeting and Mary already moved it when she moved to emeritus so there is nothing to do. Going to close this issue. If we get a champion we can re-add/re-start the initiative. |
Not sure if #11 should get closed too. Not sure if it got posted on hacker news or something, but there has been a bunch of comments there in the last week of people saying their intersted, but it's probably a moot point without a champion |
Yes, it got posted on twitter in https://twitter.com/nodejs/status/1520176973984591872. I would be +1 about closing if there are no objections because forming a team probably wouldn't help if we don't have a champion. |
There is no champion for the strategic initiative around next-gen toolchain for Node.js. (It was @mmarchini, but she is stepping away from the project for a while.) This could use a champion. @nodejs/tsc @nodejs/build
Refs: nodejs/node#42750
Adding a
tsc-agenda
label to see if anyone is interested or has ideas for who might be a good person to pick it up. But it can be removed if there is discussion and no candidate emerges.The text was updated successfully, but these errors were encountered: