-
Notifications
You must be signed in to change notification settings - Fork 30.2k
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
io.js TC Meeting 2015-04-08 #1369
Comments
I consulted @indutny on the time change and he's fine with it because it'll be 10pm where he is. The old time pushes to 5am for me and 6am is hard enough. However, since this is pretty much unilateral and very late, if there is objection to the time change by other participants then I'm more than happy for the meeting to go ahead at UTC 19:00 rather than 20:00 like I'm proposing. Please discuss that here and make sure that anyone watching this issue is aware of it any change that happens (I'll be asleep!) |
I'd also like one of the participants to volunteer to minute the meeting this time, perhaps @domenic or @Fishrock123? |
Another potential topic, and I don't want to labour on reconciliation too much, but @mikeal locked #1336 because he felt it had come to and end, was just collecting trolls and wasn't focused on constructive discussion. I believe this is the first issue that's been locked in this repo (there may have been others in node-forward) and it might be worth discussing TC thoughts on this course of action. It wasn't long ago that I was criticising issue closing to shut down discussion on joyent/node but now we're doing it here. |
@rvagg While he locked it, he did offer other avenues to continue discussion. The current thread had turned into trolling and spreading FUD. |
4:00 Eastern is a little late for me, I have prior obligations at 5:15 every Wednesday, which I need to have a bit to eat before and drive to. However, that's not much is comparison to 5am. If we start relatively on-time it won't be too much of an issue.
I think @domenic already does, I'll try to help, but I'm not really good at taking notes so I wouldn't trust myself with doing most of it. |
Has the workers implementation PR already been discussed? #1159 I couldn't find mention of that in recent meetings and it seems like one of the more significant new features. |
Maybe the The options are to either keep it as is, revert (#1358) or workaround (#1363). My vote would be to keep as is, as the workaround did turn out quite ugly and because |
@silverwind agreed that it should probably be |
Let's add an agenda item to talk about https://github.com/jasnell/dev-policy |
New TC meeting link: https://plus.google.com/events/c1c3234uog6svplgrapqucb557k?authkey=COurnuPFwbaefg |
Meeting minutes merged, this can be closed now |
UTC Wed 08-Apr-15 20:00:
Note this time has shifted forward by one hour UTC from previous meetings
Or in your local time:
Please allow time for cat-herding before broadcast starts.
Public YouTube feed: http://www.youtube.com/watch?v=w67JGaYJ8CM
Google Plus Event page: https://plus.google.com/events/c1fiaslmj03eqfs7jjicl86an9k
Invited: @bnoordhuis (TC), @piscisaureus (TC), @indutny (TC), @isaacs (TC), @trevnorris (TC), @chrisdickinson (TC, streams), @mikeal (website), @rvagg (TC), @domenic (observer), @Fishrock123 (observer)
Agenda and minutes doc, editable by TC, commentable by everyone else: https://docs.google.com/document/d/1EsDjfRGpVKFABH4LcNXNxsAsBTnHsU-i5cehmAcp1A8 (written in markdown so we can put it straight into the repo)
Agenda so far: lifted from issues marked with _tc-agenda_, please label, or ask to have issues labelled if they need to be elevated to TC discussion.
tls
option to triggerhttps
module functionalityThe text was updated successfully, but these errors were encountered: