Repository navigation
Node.js Foundation Technical Steering Committee (TSC) Meeting 2016-01-07 #27
Description
Activity
Unfortunately I'm unlikely to make this one, I really shouldn't be on conference calls while on holiday with the family! Uberconference will record automatically without intervention.
This meeting seems to be mainly needed to help tick off items that are blocking the Inclusivity group from getting ratified, although looking the current state of #24 I'm not sure if that'll be possible this week.
My input on the agenda items fwiw:
- invite prior contributors to the nodejs org #3802: I'm +0 on this, while I recognise the debt we have to all of these people, I'd prefer that we prioritise the project being owned and run according to current merit rather than historical merit or some other measure. Just because you added some fundamental feature back in 2010 doesn't necessarily mean you automatically get a say in what we do with that feature today. When I move on one day, why should the new cohort of collaborators care what I say? I know that we're just talking about foundation membership here and I recognise the potential value in adding a larger pool of members, but membership is not without its benefits—voting rights on community board seat for instance—should contributors who have moved on from this community get a free say in who represents the current community on the board? +0 because this not that big a deal to me, more of a sentiment.
- Add inclusivity@ for inclusivity WG Issues regarding the behavior of certain members #13: +1, this is a blocker because it's referred to in their docs, although this only gives inclusivity@iojs.org, if they want @nodejs.org we'll have to get the LF to redirect.
- email: add lts email alias /dev/null #12: +0, I defer to @jasnell if he thinks this is useful
- doc: add Working Groups document doc: add Working Groups document #24: +1, this looks fine to me but there do appear to be outstanding items in the discussion that have not been resolved and probably should be before moving forward. A bit of meeting bikeshedding required I guess.
Aside: I pulled out https://github.com/rvagg/node-meeting-agenda to a separate repo, it's in npm and can be used to make the agenda list from issue labels.
I also pulled out https://github.com/rvagg/make-node-meeting and made it more generic to make the text of these meeting announcements. I have configs for ctc and tsc, hopefully there are other WGs that may appreciate the leg-up on this tedious task.
I think I may be double-booked tonight. My input in case I can't join:
- invite prior contributors to the nodejs org node#3802 - no opinion
- Add inclusivity@ for inclusivity WG email#13 - seems fine to me
- email: add lts email alias email#12 - ditto
- doc: add Working Groups document #24 - no opinion, not sure what the controversy is
I just withdrew nodejs/email#12 ... it's just a convenience, not critical
It's not clear to me whether this meeting officially happened, the minutes doc hasn't got anything substantive in it and I'm going to just repurpose it for the next meeting. Can someone who attended please let me know whether this happened and whether we need to make record of the proceedings?
Comment here: nodejs/node#3802 (comment) suggests that there was a meeting and decisions were made. No minutes but I'll grab the recording and publish it (perhaps I'll even listen to it and jot some things down!).
Minutes added in #111
Time
UTC Thu 07-Jan-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/node
nodejs/email
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.