Repository navigation
Move bcoe to Collaborator emeriti #46682
Description
Activity
Sorry to hear that, and I hope we'll see you around – and that you'll be back as a collaborator in the future 🤞
Do you want to open a PR to move your name from the Collaborators list to the Emeriti one?Lines 287 to 288 in 0cfe4ab
If you prefer, I can open that PR myself if that's easier for you, and you'd only need to approve it.
Also you are part of some other teams in the org:
@nodejs/coverage-admins,@nodejs/testing, and@nodejs/tooling. Would you like to stay member of those teams (if so, which ones?), or would you prefer stepping out of everything for the time being?or would you prefer stepping out of everything for the time being?
I think it would be best to remove me from the teams for now, folks can reach out to me by email or on Twitter if I am needed for anything.
- added a commit that references this issue
on Feb 18, 2023 - added 2 commits that reference this issue
on Feb 18, 2023 - added a commit that references this issue
on Apr 11, 2023
What is the problem this feature will solve?
I have had almost no time for open source over the last 6 months. In the name of good house keeping, I think it's probably best to move me to Collaborator emeriti. The principals of defense in depth suggest that, if I'm not using my access to the Node.js repositories, it's better that I don't have access 😝
In the future I would love to get more involved with the project again, and hopefully it would be possible to move back to being a collaborator.
What is the feature you are proposing to solve the problem?
bcoebeing listed as a collaborator without doing much collaboration.What alternatives have you considered?
Staying as a collaborator, in the hopes that I start making some small contributions to the project again.