Skip to content
This repository has been archived by the owner on Nov 9, 2017. It is now read-only.

Emeritus status for CTC #92

Closed
Trott opened this issue Apr 2, 2017 · 8 comments
Closed

Emeritus status for CTC #92

Trott opened this issue Apr 2, 2017 · 8 comments

Comments

@Trott
Copy link
Member

Trott commented Apr 2, 2017

I found out recently that Ember.js has an emeritus status for core team members who are no longer active. Maybe it's an informal thing as a quick web search didn't turn much up. But the point is it got me thinking...

Perhaps having an emeritus status for CTC (and maybe TSC too?) would help with situations where people are inactive. Right now, we don't have anyone whose activity is so low that I'd want to suggest we use this. But that makes it the perfect time to discuss it, because it's not about any particular individual; it's about our process.

Someone who was emeritus would be listed as such in the README. But otherwise, they would be indistinguishable from any other Collaborator. This is mostly about psychology and appearances, but I do think that it might ease the process of coming to terms with leaving. And it seems like it's just a nice and respectful thing to do.

One potential issue is whether or not someone who rage-quits under tense circumstances should be granted emeritus or not. But those details can be worked out once we have agreement that this overall is A Good Idea or that it is Not A Good Idea.

@nodejs/ctc

@bnoordhuis
Copy link
Member

Sounds like A Good Idea to me.

@jasnell
Copy link
Member

jasnell commented Apr 3, 2017

The only question I would have on this is what happens when an Emeritus member does return to become more active again? Is their voting position on the CTC/TSC restored or are they simply Collaborators still or ...?

@bnoordhuis
Copy link
Member

Seems only fair they need to be voted in again at the CTC's discretion.

@Trott
Copy link
Member Author

Trott commented Apr 3, 2017

Yeah, what @bnoordhuis said. I don't think anyone who leaves active CTC should be guaranteed anything in the future, but I suspect that anyone who leaves under relatively uncontroversial circumstances is likely (but again, not guaranteed) to be welcomed back if they find themselves getting active again and wanting back on. On the other hand, someone who leaves under a cloud of some kind may find it more challenging, but it's ultimately up to the CTC to decide its own membership. I don't think there should be any rules (at least not related to Emeritus status) that curtail that self-determination.

@mhdawson
Copy link
Member

mhdawson commented Apr 3, 2017

Sounds reasonable to me as well based on the discussion so far. Emeritus status would mostly be a "thank you" for the work done without any special privileges attached except that you can say that you have it.

@cjihrig
Copy link

cjihrig commented Apr 4, 2017

We should use some of the Foundation's money to set them up with a pension. Also this idea, SGTM.

@Trott
Copy link
Member Author

Trott commented Apr 11, 2017

I guess I'll also add that if we don't like "emeritus", we can also use "alumnus". /shrug

@Trott Trott removed the ctc-review label May 2, 2017
Trott added a commit to Trott/io.js that referenced this issue May 26, 2017
Trott added a commit to Trott/io.js that referenced this issue May 29, 2017
PR-URL: nodejs#13232
Ref: nodejs/CTC#92
Reviewed-By: Anna Henningsen <[email protected]>
Reviewed-By: Daniel Bevenius <[email protected]>
Reviewed-By: Ben Noordhuis <[email protected]>
Reviewed-By: Michaël Zasso <[email protected]>
Reviewed-By: Colin Ihrig <[email protected]>
Reviewed-By: Michael Dawson <[email protected]>
@Trott
Copy link
Member Author

Trott commented May 29, 2017

Closed by nodejs/node#13232

@Trott Trott closed this as completed May 29, 2017
jasnell pushed a commit to nodejs/node that referenced this issue May 29, 2017
PR-URL: #13232
Ref: nodejs/CTC#92
Reviewed-By: Anna Henningsen <[email protected]>
Reviewed-By: Daniel Bevenius <[email protected]>
Reviewed-By: Ben Noordhuis <[email protected]>
Reviewed-By: Michaël Zasso <[email protected]>
Reviewed-By: Colin Ihrig <[email protected]>
Reviewed-By: Michael Dawson <[email protected]>
MylesBorins pushed a commit to nodejs/node that referenced this issue Jul 17, 2017
PR-URL: #13232
Ref: nodejs/CTC#92
Reviewed-By: Anna Henningsen <[email protected]>
Reviewed-By: Daniel Bevenius <[email protected]>
Reviewed-By: Ben Noordhuis <[email protected]>
Reviewed-By: Michaël Zasso <[email protected]>
Reviewed-By: Colin Ihrig <[email protected]>
Reviewed-By: Michael Dawson <[email protected]>
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants