Closed codebytere closed 3 years ago
Sounds good. Would be happy to be in the team if it is created.
I'd like to be in the team too.
Pinging all other folks who have individual write access to this repo (just in case): @tniessen @Tiriel @refack @priyank-p @jasnell @apapirovski @addaleax
I don't need it, but thank you! Great idea
+1, also I guess we could complete https://github.com/nodejs/admin/issues/488 after the new team is created.
EDIT: I'd like to be in the team as well :)
I guess I'd like to be in team as well!
I plan to make the initial team tomorrow if that sounds ok to you all!
Done here: https://github.com/orgs/nodejs/teams/node-core-utils/members
Should we leave this open or close it out? Perhaps leave it open until we've cleaned up old automation team items?
leave it open until the cleanup sounds good
This issue is stale because it has been open many days with no activity. It will be closed soon unless the stale label is removed or a comment is made.
Closing since we've done the clean up.
As mentioned by @mmarchini in an earlier PR, as there is a small consistent group of folks who review/open PRs on this repo I think it would simplify and streamline
@mentions
to create a@nodejs/node-core-utils
team . What do you all think? I don't believe we need to follow any other protocol to make one once it's been determined who it would include, though I may be wrong!cc'ing folks who may be interested: @mmarchini @targos @joyeecheung @richardlau @BridgeAR
People slated for initial team (so far):