-
Notifications
You must be signed in to change notification settings - Fork 134
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
Node.js Foundation Technical Steering Committee (TSC) Meeting 2018-02-28 #496
Comments
Again, I won’t be able to make it to this meeting due to a scheduling conflict. |
Added update from @mrhinkle to the agenda |
Note that nodejs/node#18990 is an alternative to nodejs/node#18158 so they can effectively be treated as a single issue. nodejs/node#18990 has multiple approvals and no rejections. It's also only been open for 22 hours. I don't think there's anything for the TSC to do there. nodejs/node#18158 was on the agenda last week but we didn't really discuss it much. That PR is opposed by @TimothyGu, @jasnell, and @BridgeAR. It was put on the agenda by @mcollina so that there could be a vote and the thing either lands or gets closed. I don't think there's much left to say as the discussion seems to have run its course in that issue. And we're unlikely to get @TimothyGu in here for the conversation unless we wait many weeks or choose to meet at a different time. (The conversation is better to have asynchronously in GitHub anyway, IMO. People who can't make a particular meeting time should not be excluded from an important part of the conversation.) I'm inclined to start recording TSC votes, if no one else objects to that approach. |
I've removed tsc-agenda from both nodejs/node#18990 and nodejs/node#18158. nodejs/node#18990 is less contentious and it's probably going to land instead. |
OK, that leaves #479 as the only non-recurring TSC agenda item this time (other than @mrhinkle telling us about Foundation stuff). It seems to me that @rvagg put #479 on the agenda mostly for awareness and to expedite it. So far, it has no TSC approvals, although some have reviewed it. Personal opinion only but my short list of people I'd like to see give it a 👍 so it can land is probably any three of @mhdawson @jasnell @MylesBorins and @ofrobots. Not sure there's much to discuss at the meeting other than saying "Hey, we need to land this or modify it or reject it sooner rather than later, so please go review it." |
Oh, @danbev is probably a good choice too, if they have time to do it. |
And @mcollina approved it just now! 🎉 |
Added nodejs/node#15346 to the agenda. Here's my relevant comment from that PR copy/pasted: I'm adding The TSC has approved runtime-deprecating Buffer constructor in 10.0.0 😱 but also 🤘 but also 😱... That's not necessarily an approval of this specific implementation. People still need to review and approve this specifically. But there is no need for this to be held up due to concerns about whether or not we want to implement a runtime deprecation. We do, at least for now. (We can always revert if it lands on master, goes out in a nightly or release candidate, and wreaks havoc.) |
(In case I'm not at the meeting: We need to talk about how to land it as soon as we can and get the word out as effectively as we can. Also, if there's things we need to do to help prepare the ecosystem, let's talk about what those things are.) |
Link for the meeting, will send password separately: https://zoom.us/j/349243116 |
Updated invite list, was out of office last week and have not yet updated template. Should be able to do that before next week. |
Prosed Agenda for my part (about 10 minutes) How can I help you?
How our legal committee works
Q&A |
I'm going to have to skip tonights meeting....got a bad cold and need to sleep. |
Same here 🤧 🤧 |
I hope y’all feel better! |
I probably won't be able to participate today (as documented in the spreadsheet 😉), need to get up early tomorrow… |
The emailed out password does not appear to be working for me |
Worked for me and some others? |
I see james is in now |
Link for those who want to watch https://www.youtube.com/watch?v=R2aZin_5tiY |
I can't find the link to join. |
Moderation Team update for this week: Indefinitely blocked one user, see moderation repo issue 177 for details. Other than that, no activity. |
@nodejs/community-committee Pinging for the Moderation Team update above. Rather than having someone else make the same report to CommComm, I thought maybe I'd just @-mention CommComm here. |
PR for minutes: #499 |
Time
UTC Wed 28-Feb-2018 22:00 (10:00 PM):
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/node
process: doc-only deprecate non-string env value #18990src: delete process.env values set to undefined #18158nodejs/TSC
Invited
Observers
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
Uberconference; participants should have the link & numbers, contact me if you don't.
Public participation
We stream our conference call straight to YouTube so anyone can listen to it live, it should start playing at https://www.youtube.com/c/nodejs+foundation/live when we turn it on. There's usually a short cat-herding time at the start of the meeting and then occasionally we have some quick private business to attend to before we can start recording & streaming. So be patient and it should show up.
Many of us will be on IRC in #node-dev on Freenode if you'd like to interact, we have a Q/A session scheduled at the end of the meeting if you'd like us to discuss anything in particular. @nodejs/collaborators in particular if there's anything you need from the TSC that's not worth putting on as a separate agenda item, this is a good place for that
The text was updated successfully, but these errors were encountered: