-
-
Notifications
You must be signed in to change notification settings - Fork 138
self nomination: nominating @ovflowd to the TSC #1707
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
Comments
cc @nodejs/tsc |
The TSC is a subset of the collaborators team, as defined in https://github.com/nodejs/node/blob/df883b0c7234cb44bef3175cd3e6a997c830db05/GOVERNANCE.md#L79 You've recently left the collaborators team, so you can't join the TSC at the moment. |
Right. It doesn't prohibit me from nominating myself... it only means I wouldn't be able to join... I guess? But if you want, I can close this issue then :/ |
We can leave this issue open but yeah, you'll need to be onboarded as a collaborator again in order for any tsc nomination to proceed. So let me ask this: I assume this means you would like to be nominated as a collaborator again? If so, we can likely get that done quickly via a public issue in nodejs/node Assuming that happens, the next step here would be for the tsc to deliberate and reach consensus on the nomination. That is typically done via private discussion. |
I appreciate that; I just don't want to sound disrespectful toward the nomination process. I'd like to at least wait for nodejs/node#57503 to land, that'd make me more comfortable tho :)
Thank you, James 🙇 |
Hey Claudio I'm sure you had your own reason to remove yourself from collaborators but this seem to contraddict
Being part of TSC also means participating in coversation related to collaboration. My suggestion is to take some time to understand if you really want to be involved in these conversation and be a collaborator. |
The sort of conversations I was referring to were the ones regarding nomination processes. It felt weird for me to block/not block a nomination and be a collaborator without certain things being clarified. The PR that James is authoring solves pretty much all my concerns. |
I understand some of my actions might seem contradictory. But they were done based on my own moral compass. I completely understand if the TSC determines Im not fit. |
I'm closing this issue as I seem to be overstepping and I believe some past actions are not providing a good image of myself at the moment. I apologise for the escalatory actions and for causing problems to the project. I appreciate everyone's time. |
Uh oh!
There was an error while loading. Please reload this page.
These nominations are quite uncommon, and I understand that the TSC nomination process might be private. However, the Node.js project charter (https://github.com/nodejs/TSC/blob/main/TSC-Charter.md) does not specify whether self-nominations or nominations from outside the TSC are allowed. Therefore, I am proceeding with this self-nomination, but please feel free to close it if it is unwarranted.
I have been actively contributing to the Node.js project since 2021. My focus has been on the future of Node.js and fostering a more inclusive community for our contributors and the community at large.
Some of my efforts have included continuously enhancing Node.js's public presence, such as improving the website to make it easier for people to download, access, and learn Node.js. The "Learn" section of the website contains excellent material and has been well-received by many. The new website is designed to support and advocate for the rest of the community.
I have revived the website team and established a web infrastructure team, which has been crucial for strategic initiatives, including the development of the Node.js Cloudflare Worker. This project has addressed some long-standing infrastructure issues and is one of the top concerns reported by our community.
I have secured key partnerships with Vercel, Sentry, and other providers that support our infrastructure. I have also collaborated closely with Cloudflare on essential work and contributed to the OpenJS Foundation to acquire resources and eliminate existing limitations on our Node.js Cloudflare account.
Additionally, I have been involved in the Next-10 initiative, working to improve our documentation. I proposed new documentation formats that will enhance developer experience and upgrade our documentation tools with the new
api-docs-tooling
.I have also supported multiple other teams in their initiatives, including the Build Working Group and the Next-10 team.
Recently, I worked to secure a partnership and launch an official Discord server to support our community and strengthen relationships between the Node project and the broader community.
One of my latest initiatives has been developing a better funding program for Node.js in collaboration with @mhdawson; Including how we showcase supporters.
My contributions have significantly benefited the project, and I am eager to continue my stewardship and step up as part of its leadership. I feel I can better share my opinions, advocate for my work, and represent the project more effectively.
Thank you all!
The text was updated successfully, but these errors were encountered: