-
Notifications
You must be signed in to change notification settings - Fork 30k
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
doc: add CTC meeting minutes 2016-02-17 #5410
Conversation
rvagg
commented
Feb 24, 2016
- Audio Recording: https://soundcloud.com/node-foundation/ctc-meeting-2016-02-17
- GitHub Issue: Node.js Foundation Core Technical Committee (CTC) Meeting 2016-02-17 #5274
- Minutes Google Doc: https://docs.google.com/document/d/1Y9p8EopccPOj1v4gDbnor2kvlHvkbHxankWuRKHssyo
LGTM. Condenses the promises discussion very well. :-) |
LGTM |
LGTM |
PR-URL: #5410 Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Ben Noordhuis <info@bnoordhuis.nl> Reviewed-By: James M Snell <jasnell@gmail.com>
@rvagg ... would it actually be possible to start putting these into the nodejs/tsc repository? |
PR-URL: #5410 Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Ben Noordhuis <info@bnoordhuis.nl> Reviewed-By: James M Snell <jasnell@gmail.com>
To me it makes sense that they stay with "core" but perhaps that doesn't mean that they should go into the core repo, the TSC repo seems like the wrong place, maybe it's time to start a CTC repo for meta & core business stuff that doesn't stray far enough into TSC territory? We could use it for announcing and managing CTC meetings, for collecting and organising onboarding of new collaborators. Or is repo-proliferation a problem? |
If a CTC repo is created & these move there, I just ask that there is an announcement made here to let others know. Side note: Whatever the Promises discussion was- the summary maybe should just say "Lengthly conversation: refer to audio". Maybe it wasn't lengthy? I'm not sure unless I listen to the audio. :( |
Closing because this landed already. |