Node.js Foundation Technical Steering Committee (TSC) Meeting 2018-10-31 #618
Comments
|
I’m unlikely to make it, but I think our onboarding rules want some kind of announcement for collaborator nominations – currently open are nodejs/node#23849, nodejs/node#23850 and https://github.com/nodejs/node/issues/23955… maybe somebody could make sure that these are mentioned? :) |
|
nodejs/node#23433 is not added to the agenda. I propose moving that to a vote. |
|
I won't be able to make the meeting next week as I'll be at NodeConfEU. Any volunteers to chair? It is at 4EST. |
|
I'd like to know whether Athens time (GMT +2, 18:00) can be added to the time chart. |
|
It's going to be hard to vote on nodejs/node#23433 because there are 5 options. There is no reason to vote in the meeting, and in fact, we should avoid meeting votes in my opinion. (Our governance doc even says so, or used to. Not seeing it now.) We should initiate the vote in the issue tracker. I'm not sure how you want to handle it with 5 options, though. I suggest someone (preferably @thefourtheye) champion a single option (maybe based on feedback in the issue) and we have an up-or-down vote on that one single option. |
You could raise a pull request/issue against https://github.com/nodejs/make-node-meeting: |
|
👍 Will do, its October so another PR cannot hurt |
|
@Trott I am willing to champion this. The reason why I moved for a vote is that, in the future the same issue might come back to life. If the TSC makes a decision now, we can settle this once and for all. As of now, Option 1 is the popular one. |
|
@cfanoulis to add another time you would need to PR a change into node-meeting-agenda or make-node-meeting which are modules used by https://github.com/nodejs/create-node-meeting-artifacts to create the items for the meetings. EDIT, I see that was already answered. |
|
Do note that there are already two links below the chart for getting the meeting time in your local time zone. I won't stop someone from adding a time zone but if it were left up to me, I'd prefer we remove time zones rather than add them. A comprehensive list of times across the globe isn't going to happen. In the past, it listed just time zones that had TSC members living in them. The table is long and a bit unwieldy, and there are those links I just mentioned. Based on the locations of TSC members, I'm guessing we could do fine without Mountain, Central, London, and Tokyo. |
I believe the tool is not TSC specific and uses the same list of time zones for any meeting it creates. At least the London timezone was added for CommComm (nodejs/make-node-meeting#20). |
Good point and something that had escaped my notice... |
|
@nodejs/tsc There is a table in nodejs/node#23433, which we can use to vote for it. Abstainers can just add an empty row with their name. As the options are not binary, this could be used as an alternative to the formal voting. |
|
@Trott replying to your comment: By Athens, I mean the GMT +2 (UTC +3) timezone, which seems to be absent, or actually skipped. I will agree with your comment that there may be a few too many timezones, but since GMT +1/3/4 exist, I would say that it could not be that bad to add a timezone. |
|
I'll actually have to miss this meeting because of the DST shift :( |
|
Once the TZ's settle I was planning on asking everybody to update the sheet so we can take another look.,= |
|
@mhdawson, I'm be planning on adding automatic TZ support :-). A bit later, though. |
|
PR for minutes: #619 |
|
Moderation Team Updates:
@nodejs/tsc @nodejs/community-committee @nodejs/moderation |
Time
UTC Wed 31-Oct-2018 16:00 (04: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
nodejs/TSC
Invited
Observers/Guests
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
Zoom link: https://zoom.us/j/611357642
Regular password
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.
Invitees
Please use the following emoji reactions in this post to indicate your
availability.
The text was updated successfully, but these errors were encountered: