Skip to content
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

Tracing WG Meeting 2015-10-07 #24

Closed
pmuellr opened this issue Sep 28, 2015 · 23 comments
Closed

Tracing WG Meeting 2015-10-07 #24

pmuellr opened this issue Sep 28, 2015 · 23 comments

Comments

@pmuellr
Copy link
Contributor

pmuellr commented Sep 28, 2015

Date/Time: Wed, 2015-10-07, 1PM eastern - world time

Agenda and minutes can be collected in here and copied into this repo later:
https://docs.google.com/document/d/1KWFRzRrJJY8zx1rofZqLSh9KCWR77cV3OBZ7jTtffYw/edit?usp=sharing

Previous minutes: https://github.com/nodejs/tracing-wg/blob/master/wg-meetings/2015-09-25.md

Hangout on air for active participants: https://plus.google.com/hangouts/_/hoaevent/AP36tYdhLhQViZjmEr4eZPbuYRavosv7p1Djlx-dn7mEPVN1cXcWoQ?hl=en

YouTube movie for observers and saved recording: http://www.youtube.com/watch?v=LsO8eLGN7XA

Hangout on air event for more details: https://plus.google.com/u/1/events/cq00d0smhgb1lv0m6r3s94f71mg

Agenda discussion can happen in this thread.

(format copied from nodejs/Release#38)

(instructions for creating Hangouts On Air on the nodejs/node wiki)

@pmuellr
Copy link
Contributor Author

pmuellr commented Sep 28, 2015

So, funny thing happened when I brought up the question of having monthly calls, in the video at 5:10. @ofrobots responds with "Monthly sounds good to me ...". And then @natduca appears, and what I now identify as an echo of something I said 45 seconds early plays, instead of Nat talking. Where I mention "I think we should be talking more frequently than that". The context was from earlier, as in "more frequently than every seven months".

At the time, I thought it was Nat talking, asking for meetings more frequent than every month.

So weird.

Anyway, even though no one complained about meeting twice a month, I'm guessing once a month will be fine.

Thinking of targeting the end of October, which would put us at once a month. @matthewloring had created a doodle for an Oct 5 meeting. Matt, wanna create for more end of the month?

Discussion in this issue. The agenda/minutes for for the next meeting is live, in this issue's description above.

@ofrobots
Copy link
Contributor

Actually I am going to change my own opinion. Given that there is some momentum behind the discussion on trace-event, it might make sense to meet on Oct 5 after all while the knowledge about it is still fresh. Two weeks is long enough for people to digest the information and not too long to forget it.

@natduca
Copy link

natduca commented Sep 28, 2015

Agh, no opinions from me. I'd look to @ofrobots to be point on this from goog/chrome side and he can loop me in as needed on specific calls.

@Qard
Copy link
Member

Qard commented Sep 28, 2015

I'd say generally monthly, but scale up to every two weeks as-needed.

It seems like there's more to discuss on the trace-event stuff, and we didn't really get anywhere with async_wrap, due to Trevor's absence. It might be good to run another hangout sooner rather than later.

@pmuellr
Copy link
Contributor Author

pmuellr commented Sep 29, 2015

Allrighty, let's try for week of Oct 5, with Matt Loring's doodle:

Contact me or Matt if you need the admin bit of the doodle.

Folks, start you're doodling!

@AndreasMadsen @Qard @wraithan @bnoordhuis @brycebaril @chiniforooshan
@dberesford @domenic @fmeawad @groundwater @hayes @lucamaraschi @lykkin
@matthewloring @mikeal @ofrobots @othiym23 @paulirish @piscisaureus @pmuellr
@rmg @rvagg @sam-github @thekemkid @thlorenz @trevnorris @yunong @yury-s

@Qard
Copy link
Member

Qard commented Sep 29, 2015

You can also just mention @nodejs/tracing to catch everyone in the team. :)

@yunong
Copy link
Member

yunong commented Sep 30, 2015

@pmuellr Would you mind adding me to the README?

@pmuellr
Copy link
Contributor Author

pmuellr commented Oct 1, 2015

@yunong I would, but really you should be added to the Tracing team as well. And I can't do that, or don't know how to.

Suggest you do an edit right from the GH page for the README, create a pull request from that, and add a comment that you want to be added to the Tracing team.

@Qard
Copy link
Member

Qard commented Oct 1, 2015

You can request to be added to the team here: https://github.com/orgs/nodejs/teams/tracing

You'll have to ping someone in there with the owner bit to approve you.

@pmuellr
Copy link
Contributor Author

pmuellr commented Oct 2, 2015

Looking at the doodle, we have 9 folks who have responded, and there are 2 times that have 7 check marks (the most check marks). Those are:

@rvagg and @Qard can't make the Wednesday time
@rvagg and @lucamaraschi can't make the Thursday time

@rvagg / @Qard / @lucamaraschi, thoughts?

Given no other info, guess I'd opt for Wed, it's first.

@pmuellr
Copy link
Contributor Author

pmuellr commented Oct 2, 2015

Also need to work on the agenda.

Presumably @trevnorris could give us an update on AsyncWrap, and @ofrobots on v8-trace.

Would be nice to have the docs section of the wiki fleshed out. If you know something, write something (or whatever :-) )

@AndreasMadsen
Copy link
Member

I filled in the doodle. Sorry for the late response.

@pmuellr you should add the doodle link to the overview, I missed it in the comments.

@ofrobots ofrobots closed this as completed Oct 2, 2015
@pmuellr pmuellr reopened this Oct 2, 2015
@rvagg
Copy link
Member

rvagg commented Oct 3, 2015

please don't let this hinge on me in any way, I'll make it if it lines up with my availability (I probably shouldn't have filled out the doodle!)

@Qard
Copy link
Member

Qard commented Oct 3, 2015

Wednesday at 1PM EST is not great for me, but I can make it work, if necessary. I'll have to cut out by 2PM though.

@pmuellr
Copy link
Contributor Author

pmuellr commented Oct 5, 2015

OK, looks like Wed 1PM is the date - much thanks to @Qard for squeezing it in. I'll set up the HoA, update dates/links in the issue description, etc.

Still need agenda bits - see comment from 3 days ago

@pmuellr pmuellr changed the title Tracing WG Meeting 2015-10-xx Tracing WG Meeting 2015-10-07 Oct 5, 2015
@pmuellr
Copy link
Contributor Author

pmuellr commented Oct 5, 2015

Looks like everyone on the Doodle (incl Rod, for completeness) has been sent an invite to the hangout.

Except @fmeawad, since I don't have, or misplaced, his email address.

@yunong
Copy link
Member

yunong commented Oct 5, 2015

@pmuellr I did not get the invite :(

@lucamaraschi
Copy link

@pmuellr me neither

@pmuellr
Copy link
Contributor Author

pmuellr commented Oct 5, 2015

Hmmm, maybe I forgot to click something to actually send an invite. Please check the event page and make sure you're listed on the invite list; I see: Patrick Mueller, Fadi Meawad, Yunong Xiao, Matt Loring, Ali Sheikh, Andreas Madsen, Stephen Belanger, Luca Maraschi, Rod Vagg, Trevor Norris.

@pmuellr
Copy link
Contributor Author

pmuellr commented Oct 6, 2015

I've given up on trying to use the Hangouts invite system, for now, and have curated a list of emails for folks in the tracing team, and other folks who have expressed an interest in the tracing wg. If you are reading this, and didn't get an email from my gmail account titled "Node.js Tracing WG Meeting 2015-10-07", send me your email offline, to [email protected].

@AndreasMadsen
Copy link
Member

@Qard
Copy link
Member

Qard commented Oct 7, 2015

Thanks all for participating in the meeting today! I feel like we made some great progress on finally establishing a direction for the tracing work.

I'm going to close this and we can continue discussion in the other new issues. 😄

@Qard Qard closed this as completed Oct 7, 2015
@pmuellr
Copy link
Contributor Author

pmuellr commented Oct 12, 2015

I've added minutes for this meeting here - https://github.com/nodejs/tracing-wg/blob/master/wg-meetings/2015-10-07.md

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

8 participants