-
Notifications
You must be signed in to change notification settings - Fork 30.2k
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
doc: move TSC member from regular to emeritus #55524
Conversation
Signed-off-by: Michael Dawson <midawson@redhat.com>
Not to hijack Ben's issue, but I'm curious what the motivation, and especially the criteria for moving people from regular to emeritus is. The "regular" TSC tier was only created to offboard inactive TSC members who wouldn't step down on their own, so presumably project activity isn't a big deal at that tier. As a "regular" member who has been significantly more active in the project than some of the current "voting" members recently it seems like maybe something hasn't been communicated publicly to the rest of the project. |
I dont think its related to inactivity but more on the interest of the person of still being involved in project. |
IIUC an email was sent to all regular members asking if they would still want to stay as regular TSC members. If they said no or if they have not responded for 2 weeks then they'll be moved to emeritus. If they said yes then they'll stay in the list. Not sure whether Ben said no or whether he didn't reply (Michael sent the email). Though I suppose we can always just ping @bnoordhuis here and double check just in case he didn't get that email. (Not sure where this "hey do you want to stay, if not we'll move you or if you don't respond in 2 weeks we'd take that as no" regular check is documented, I remember it has always been done for TSC and other collaborators, and the motivation probably has been trying to clean up permissions given to non-responsive accounts? That used to be done by tools/find-inactive-tsc.yml workflow, but I guess we resort back to humans sending emails now after nodejs/TSC#1350) |
I got the email and replied I was fine with moving to emeritus. A non-voting TSC member is kind of pointless anyway, right? For posterity: Michael sent the email on October 7 (PDT), I replied on the 8th (CEST) |
I don't think I have any permissions that regular contributors (the non-TSC kind) don't have. |
hmm yeah, after reading nodejs/TSC#1350 again my interpretation is that the role difference between non-TSC collaborator and a TSC (the different tiers of them now) is centered on the participation in votes, and after adding in the regular member tier, the permissions difference between regular v.s. emeritus only comes down to "how easy it is for me to start voting again". If a regular TSC wishes to vote, they can request to move themselves to voting TSC with a PR; If emeritus wishes to vote they'll need to go through nomination again. Though that's just my interpretation, maybe the TSC charter can use some PRs for clarification. On the other hand regular TSC will still get pinged by all TSC meeting issues, whereas emeritus will no longer get the spam. Technically regular TSC also have the permission to just join TSC meetings and stay for e.g. security discussions without prior requests, but with how liberally we grant meeting requests to any collaborator/people who have a reason to come it doesn't seem to matter a lot. My impression is that a regular question about "do you want to be moved to emeritus" is just a practice that has always been done for all kinds of membership in the organization that it has become a habit without need of motivations now. The habit can use more documentation PRs/discussions for sure. (Although #55524 (comment) seemed to be asking about the motivation of this PR itself and the answer is that they said yes to the question). |
Oh, in that case I'd rather stay on the TSC. |
@bnoordhuis would you be interested in participating in TSC activities/meeting/votes? |
Things related to security have my interest, so... a qualified yes? |
@bnoordhuis then a kind reminder that as a regular TSC member you can ask to move to voting member. @cjihrig I have messaged you a while ago inviting you to rejoin the TSC on slack, but I only realized a while later that you've left the OpenJS slack and I couldn't find your phone number from the conference. |
As indicated earlier in the thread, I've been asking people who are regular TSC members every 3-4 months if they are ok moving to emeritus. I ask all regular members, some say they would like to stay which is ok, for others they agree it's time to move to emeritus. I think this makes sense as after some period of time we've seen some regular members agree its time to move to emeritus. @cjihrig should I assume you would like to stay as well? |
Yes, please. |
I'm going to go ahead and close this since after discussion Ben has indicated he'd prefer to stay as a regular member. |
No description provided.