Node.js Foundation Technical Steering Committee (TSC) Meeting 2017-02-23 #213
Comments
|
I have an overlapping personal conflict today that will limit my participation. I should be able to listen in but I won't be able to talk much for at least part of the call. If a vote is called, I am +1 on adding @joshgav to the TSC. On the copyright date issue and license update issues I'll have to defer to any update that @rvagg may have from the legal committee discussions. And on the revised membership rules, we need people to vote. The only alternative will be to go ahead and take it to the board and ask them to approve the change in lieu of a vote (I'm thinking that a major reason we're not getting enough votes for this changes is that we need to be enforcing these exact kind of participation rules) |
|
I am also unable to make it.
And, like James, I am in favor of Josh becoming a TSC member.
- Bert
…On Thu, 23 Feb 2017 at 19:31, James M Snell ***@***.***> wrote:
I have an overlapping personal conflict today that will limit my
participation. I should be able to listen in but I won't be able to talk
much for at least part of the call.
If a vote is called, I am +1 on adding @joshgav
<https://github.com/joshgav> to the TSC.
On the copyright date issue and license update issues I'll have to defer
to any update that @rvagg <https://github.com/rvagg> may have from the
legal committee discussions.
And on the revised membership rules, we need people to vote. The only
alternative will be to go ahead and take it to the board and ask them to
approve the change in lieu of a vote (I'm thinking that a major reason
we're not getting enough votes for this changes is that we *need* to be
enforcing these exact kind of participation rules)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#213 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AANUkbpNM1ftjImlUenD5R9SHUFlSpssks5rfdCEgaJpZM4MJ5kT>
.
|
|
I will most likely be late as well, and may not be able to make it either (I'm in the middle of moving, and have an move-out inspection sometime between now and 1). If a vote is called, I'm also +1 on adding @joshgav to the TSC. I voted in the membership rules thread, but just to reiterate, I vote +1 on it as well. |
|
Notes: #215 Thanks for the votes :) |
Time
UTC Thu 23-Feb-2017 20:00 (08: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/summit
nodejs/TSC
Invited
Notes
The agenda comes from issues labelled with
tsc-agendaacross 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.
A standing invitation exists for all @nodejs/CTC members who are not also TSC members to attend in observer capacity.
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 it.
The text was updated successfully, but these errors were encountered: