Skip to content

Timing of TSC member addition / resignation #817

Closed

Description

@tniessen

If @BridgeAR isn't added to the TSC (#811) before @Fishrock123 leaves the TSC (nodejs/node#31725), and if I am not mistaken about the number of IBM employees on the TSC, this clause will come into effect:

If removal or resignation of a TSC member, or a change of employment by a TSC member, creates a situation where more than one-fourth of the TSC membership shares an employer, then the situation must be immediately remedied by the resignation or removal of one or more TSC members affiliated with the over-represented employer(s).

It might be too early to add @BridgeAR, given that he hasn't had a chance to attend any meetings yet. We can avoid this clause from coming into effect if @Fishrock123 is okay with delaying his resignation for a while, but I understand if he is not, and we should in no way prevent him from stepping down.

cc @nodejs/tsc

Activity

  1. mhdawson commented on Feb 12, 2020

    @mhdawson
    Member

    @tniessen thanks for opening, just catching up on latest events.

    @Fishrock123 just let me know what your feeling is on this. If you don't want to delay I'll get started on figuring out who drops out on the IBM side.

  2. changed the title [-]Timing of TSC member addition / removal[/-] [+]Timing of TSC member addition / resignation[/+] on Feb 12, 2020
  3. Fishrock123 commented on Feb 12, 2020

    @Fishrock123
    Contributor

    I think that is rather a question for the TSC.

    Sure, I could still vote on anything important if it was sent to me directly, but I am not involved by any real meaningful sense of the term, and am also likely to forget about the regular meetings.

    Does asking me to stay on then reflect poorly on the integrity of the TSC? I don't know, we are basically asking philosophical questions.

    If it makes it easier I can stay for a few more weeks but don't expect me to... well, be particularly involved.

  4. mhdawson commented on Feb 12, 2020

    @mhdawson
    Member

    @nodejs/tsc please chime in on what you think is best.

  5. cjihrig commented on Feb 12, 2020

    @cjihrig
    Contributor

    Does asking me to stay on then reflect poorly on the integrity of the TSC?

    I think so. If any collaborator were to merge nodejs/node#31725, would that mean @Fishrock123 is officially off of the TSC at that moment? That seems kind of silly. What if someone else on the TSC also resigned (for legitimate reasons, or just to watch the TSC squirm)?

  6. jasnell commented on Feb 12, 2020

    @jasnell
    Member

    If @BridgeAR's nomination (or any new nomination) wasn't already in progress I would say that the rule would apply. But since there is an active nomination in the works and it's not likely to take too long, we can likely assume a safe grace period for the IBMers. Alternatively, one of the IBMers could temporarily and voluntarily move to emeritus status while the nomination is still open. I highly doubt anyone would object to them coming back off emeritus once @BridgeAR's nomination is finalized.

  7. sam-github commented on Feb 12, 2020

    @sam-github
    Contributor

    I wouldn't want it to look like IBM isn't following the membership rules. I'll resign from the TSC if membership ends up over quota.

  8. mhdawson commented on Feb 12, 2020

    @mhdawson
    Member

    @sam-github thanks for jumping in with the offer.

  9. jasnell commented on Feb 12, 2020

    @jasnell
    Member

    @sam-github ... I don't think a full resignation is required. Moving temporarily to emeritus should work also.

  10. sam-github commented on Feb 13, 2020

    @sam-github
    Contributor

    Ok, will do when I need to. I think that is after nodejs/node#31725 lands, but someone tell me if its needed earlier.

  11. Fishrock123 commented on Feb 13, 2020

    @Fishrock123
    Contributor

    After, yes. I'll land that soon.

  12. gireeshpunathil commented on Feb 13, 2020

    @gireeshpunathil
    Member

    I had word with @sam-github . I will go emeritus to address the situation. The WIP PR is in, just waiting for nodejs/node#31725 to be landed.

  13. mcollina commented on Feb 13, 2020

    @mcollina
    SponsorMember

    In case, I would like nominate @gireeshpunathil immediately to the TSC to join together with @BridgeAR. It's a little bit of a dance but within the rules.

  14. mhdawson commented on Feb 14, 2020

    @mhdawson
    Member

    @gireeshpunathil thanks for doing that.

  15. mhdawson commented on Feb 21, 2020

    @mhdawson
    Member

    I think this can be close, let me know if closing was not the right thing to do. @mcollina maybe you could open an issue with your nomination to bring @gireeshpunathil back on the CPC when @BridgeAR is confirmed. I think it would be good to capture that in it's own issue along with the +1s

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions

      Sponsor
      SponsoredKunjungi sekarang
      Promo