Join forces with Diagnostics WG

[mhdawson]

The diagnostics wg (https://github.com/nodejs/Diagnostics) is restarting regular meetings and I think we share some common interests with that group.

I'd like to suggest that we join forces by using the same meeting to discuss post-mortem and other diagnostics issues. The orgnanizer of the meeting and the group in the last meeting was open to this suggestion.

I've added the diag-agenda label to this repo and we'd just have to add that to any issues we wanted on the agenda.

I'm also planning to set up an in person Diagnostics Summit and I think it should cover both post-mortem and other Diagnostics topics.

@nodejs/post-mortem what do you think ?

@nodejs/diagnostics FYI

[cjihrig]

Makes sense to me.

[richardlau]

We used to do this -- nodejs/post-mortem members were cc'd and invited to the diagnostics WG meetings (e.g. nodejs/diagnostics#79).

[Qard]

At the time post-mortem was starting the tracing working group had not yet expanded to cover general diagnostics, so it made sense for them to be separate. The groups probably should have merged when the switch to diagnostics happened though.

[mhdawson]

Ok seems like there is general agreement with the approach. It would be great if the @nodejs/diagnostics team members could joing the next scheduled meeting for the Diagnostics group which is set for: 3-4 EST on Wed Nov 29th.

@mike-kaufman can you make sure to include any items tagged with the diagnostics-agenda Label are included in the agenda.

[richardlau]

I agree with @Qard that the groups should have been merged. If post-mortem needs to be kept as a team it should be under the diagnostics WG.

Any objections from @nodejs/post-mortem and/or @nodejs/diagnostics?

[mhdawson]

+1 from me. I think we should look at migrating open issues over to the Diagnostics repo and making post-mortem a sub-team.

[mmarchini]

Are there any objections here? I want to start migrating open issues to nodejs/diagnostics next week.

[joyeecheung]

+1

[mhdawson]

I think that this has been open long enough that we likely would have heard objections if there were going to be any.

There was agreement of all those at the diagnostic session at the summit last week as well.

@mmarchini I think if you don't hear any objections by next week you should be good to go.

[mmarchini]

Quick question: should I close issues here after migrating them to nodejs/diagnostics?

[mike-kaufman]

should I close issues here after migrating them to nodejs/diagnostics?

Yeah, I think that makes sense - we ideally want a single copy of each issue where we concentrate discussion/decisions, vs having multiple copies.

[mhdawson]

+1 for closing here once there is something equivalent in the Diagnostics repo

[mmarchini]

@joyeecheung @mhdawson I don't have permission to close issues here :(

Shouldn't nodejs/post-mortem be a subteam of nodejs/diagnostics?