-
-
Notifications
You must be signed in to change notification settings - Fork 69
doc: self nomination to diagnostics WG #363
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Added to diag-agenda as Governance says changes to membership should be posted on the WG agenda, once the next meeting complete this can land. |
PR-URL: #363 Reviewed-By: Stephen Belanger <admin@stephenbelanger.com> Reviewed-By: Matheus Marchini <mat@mmarchini.me> Reviewed-By: Gireesh Punathil <gpunathi@in.ibm.com> Reviewed-By: Michael Dawson <Michael_Dawson@ca.ibm.com> Reviewed-By: Gerhard Stöbich <deb2001-github@yahoo.de>
landed in bedab34 , welcome to the working group! |
I believe someone with admin access needs to invite @legendecas to @nodejs/diagnostics. |
looks like I don't have it, @mhdawson ? |
I just added @legendecas to the diagnostics team. |
Hello everyone, as a Node.js core collaborator, I'd like to nominate myself to diagnostics WG to show my interests on pushing Node.js user diagnostics experience forward :)