-
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 2016-03-03 #57
Comments
fine by me |
As per nodejs/inclusivity#78 the Inclusivity WG has both @hg and @nebrius interested in joining. I suggest we add them both as observers for a week or two to get a better feel for who might want to be the rep long-term and then have the WG finalize it. cc @nodejs/tsc ^^ |
@Fishrock123 It's not a great precedent for the TSC to pick and choose the rep from WGs or projects. I don't see a huge problem with adding people as observers for a while but I would recommend kicking the final decision for which one of them is given voting privileges to the Inclusivity WG. |
@mikeal Yes, agreed, I don't think I implied anything else but it's possible that I did. I.e. we shouldn't vote on which, this is for them to be more informed. |
Yes, my understanding is that the WG will decide. @hg and I are interested in observing to get a better feel for the process, and help the group come to a consensus on who we want to nominate (we'd like to avoid needing to do a vote, if possible). |
My bad, i missread the comment :) |
UPDATE: We are going to use Uberconference instead. Participants should have the link. |
This is what I'm going to propose as a starting point for discussion about mission of the Foundation. I'd like us to back up from the dirty detail about process, questions for applications, structure and all of that and make sure we get alignment between the board and the TSC on what we are trying to achieve together. Then everything else should be able to flow from there and we can argue on the basis of a shared position and our understanding of how that works.
|
Partial recording on youtube at https://youtu.be/-vf23GsR6vk |
Any chance there can be more lead time on these meetings? Maybe watching this repo for issues isn't the best way to get informed? ...I would have loved to contribute to that "watching now" number ;) |
@williamkapke They're weekly, same time slot every Thursday. |
Awesome- thank you. Where is this posted? I'm sure it is- but somehow I didn't find it. Probably something really obvious too! |
I've removed the tsc-agenda tags from pending applications while we are on pause from considering new ones. |
Time
UTC Thu 03-Mar-2016 20:00:
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/TSC
nil
We will likely be discussing foundational Foundation things, see some of recent open pull requests on this repo for that theme.
Invited
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.The text was updated successfully, but these errors were encountered: