-
Notifications
You must be signed in to change notification settings - Fork 78
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
WG Meeting Week of February 19th on trace_event
#4
Comments
I'm happy to watch the feed :) |
I don't think I have anything to offer on this one, and I can always feed my input through @sam-github or @piscisaureus if I hear something on the youtube stream. |
I'll watch the feed. :) |
I'll try to join but I'm moving next week and I may not have a working internet connection on the 19th yet. |
Happy to join. |
We should get Ali from Google (don't remember his last name or github handle) into the discussion as well as he has expressed interest in helping us adopt the v8 tracing format. I myself would be available any day of the week and early Friday for a meeting. |
Also linking in @natduca's very detailed notes regarding tracing in chromium since I believe that some points in there should become part of the discussion. |
I'll be happy to join. (Hi Thorsten!) On Fri, Feb 13, 2015 at 9:09 AM, Thorsten Lorenz [email protected]
Ali |
Awesome @ofrobots, glad to have you :) |
That sounds a bit strange to me since AsyncWrap and tracing aren't really related. Potentially you're thinking about replacing @trevnorris' tracing support? |
@piscisaureus I think @piscisaureus and @ofrobots can probably explain it better. |
I'd like to be involved, I'm working on these areas for StrongLoop ATM. |
Also, is there a target day? Later in the week would work better for me, morning would probably help cross time zones from North American pacific coast through Europe. |
Hi, I would like to join this WG as well. I am working with Sam on the same areas within StrongLoop. Thanks |
Doodle for finding the best time on Thursday. http://doodle.com/yds5u6ns86t85tuu |
You can't just replace |
replace was probably the wrong way to put it, it was more like "feed asyncwrap events in to trace_event" |
I put myself up for any time, though I might just lurk in IRC if it gets too full. I'm not sure how much I have to contribute to the conversation anyway. I've only just recently started digging into tracing the native side. |
Doodle is closed, Thu 2/19/15 2:00 PM – 3:00 PM PST. |
Participation link for WG meeting today: https://plus.google.com/hangouts/_/hoaevent/AP36tYfCdqP069ksasAoWqzK5gGpvS7T0BVhOWoCJxS9Ay8wtiKEJw?authuser=0&eid=101986715696875566237&hl=en-GB Event link for people watching: https://plus.google.com/b/101986715696875566237/events/c791vkvvdldnvf14t08vcfa8hv4 Agenda and Notes Please add things to the Agenda, it is very slim right now. |
We should have a working group meeting this week, there's a lot to discuss but because we have so many people I think that we're going to have to limit the meeting in scope and ask that people unfamiliar with the topic watch the feed rather than get on the hangout since space on hangouts-on-air is limited.
I think we should discuss v8/chrome's
trace_event
and how this can be leveraged byiojs
. In particular, I've heard people wondering if we might actually be able to replaceAsyncWrap
with trace events which would make it easier to write more unified tooling. If changes to the debugging plan this big are being considered we should shake them out now :)Off the top of my head I think we need @natduca @ofrobots @trevnorris and @thlorenz and probably others.
The text was updated successfully, but these errors were encountered: