-
Notifications
You must be signed in to change notification settings - Fork 30.1k
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-22 #1502
Comments
Can we do the TC nominations first, to get them out of the way? |
If it's possible I'd like to update everyone on the results of the v1.8.0 release, and what I'd like to do for the upcoming v2.0.0 release. |
@chrisdickinson Please do. I suspect the "Ready to upgrade to V8 4.2?" will be about that in part. |
Sorry, I didn't mean for them to be voted on at this meeting, I just included them to explain why they are there. The suggestion was that they would join the TC meetings for a few weeks like @Fishrock123 did and then we vote at a later meeting. |
@shigeki by the way, how did you find understanding the meeting? Was our english we clear enough? |
@Fishrock123 Thanks for taking care of me. Everyone speaks very clear. But sometime I could not follow conversations because of my lack of understanding of agenda. It was very helpful for me that Rod takes notes simultaneously during the meeting. I'm sure I can catch up by reading minutes later. |
@shigeki Honestly I also had some trouble following today too, the agenda was a little back-and-forth. No worries. :) |
as per nodejs#1502 PR-URL: nodejs#1507 Reviewed-By: Chris Dickinson <christopher.s.dickinson@gmail.com> Reviewed-By: Ben Noordhuis <info@bnoordhuis.nl>
@Fishrock123 how can we improve on the back-and-forth that you're seeing? |
Was mostly just this meeting, but we jumped ahead or something at some point after the TC nominations and I got lost in the schedule when trying to take notes. Was generally like "wait where are we at?" a couple times. |
Whenever I'm in a meeting and am feeling like that then I like to call for some clarification or a back-up to figure it out. Anyone in these meetings should feel free to ask for a temporary halt if anything's unclear so we can make sure we proceed with everyone on the same page. This goes particularly for anyone trying to take notes! |
UTC Wed 22-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=s7LIMsTFaps
Google Plus Event page: https://plus.google.com/events/co7i7pv2a51270jat7jvkfcue64
Google Doc for minutes: https://docs.google.com/document/d/1G4aJ2OwiW2WphW7Vz2OW56VRot8xRBFitluKsuYPxk0 (written in markdown so we can put it straight into the repo)
Invited: @bnoordhuis (TC), @piscisaureus (TC), @indutny (TC), @isaacs (TC), @trevnorris (TC), @chrisdickinson (TC, streams), @mikeal (website), @rvagg (TC), @domenic (observer), @Fishrock123 (observer)
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.
The first few of these are duplicates from the last meeting but I think they might still be relevant.
Note: There will be time at the end of the meeting for interactive QA with people in the #io.js channel on Freenode.
The text was updated successfully, but these errors were encountered: