Software Steering representative: term length

[fcollonval]

At the weekly call, the question of the term duration for the Software Steering representative was raised.

The security council for example decided for a year term.

What do you think would be a good duration for the JupyterLab representative?

[isabela-pf]

Reading the Software Steering Council responsibilities, I think a year sounds like a good balance of time between reasonable commitment for representatives, enough time for representatives to get acquainted to processes, and being responsive to the potential changes in the JupyterLab council.

Correct me if I'm wrong, but I don't think we have other representative processes sorted out that might impact people's thoughts on what a good term length is. For example, is there a cap on the number of terms for an individual? Can representatives serve multiple terms in a row? Can the council members take any action if they believe their representative has been neglecting duties? Those sorts of things.

If this derails the discussion from the original issue, I'm happy to move it to another issue.

[ellisonbg]

I think a year is a good starting point. I was talking to Ana about this same question for the DEI standing committee and our initial thought was also a year.

…

On Wed, Sep 14, 2022 at 11:24 AM Isabela Presedo-Floyd < ***@***.***> wrote: Reading the Software Steering Council responsibilities <https://jupyter.org/governance/software_steering_council.html#responsibilities>, I think a year sounds like a good balance of time between reasonable commitment for representatives, enough time for representatives to get acquainted to processes, and being responsive to the potential changes in the JupyterLab council. Correct me if I'm wrong, but I don't think we have other representative processes sorted out that might impact people's thoughts on what a good term length is. For example, is there a cap on the number of terms for an individual? Can representatives serve multiple terms in a row? Can the council members take any action if they believe their representative has been neglecting duties? Those sorts of things. If this derails the discussion from the original issue, I'm happy to move it to another issue. — Reply to this email directly, view it on GitHub <#162 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAAGXUDZ5HC5ZKJDL5KXSLTV6IJ7DANCNFSM6AAAAAAQMSOX3A> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

-- Brian E. Granger Senior Principal Technologist, AWS AI/ML ***@***.***) On Leave - Professor of Physics and Data Science, Cal Poly @ellisonbg on GitHub

[damianavila]

Yep, 1 year seems a sensible length.

[afshin]

It seems like there wasn't any real disagreement here and the consensus is for a one-year term. Closing this issue as resolved. We can revisit the question 11 months after the first SSC meeting or some similar time frame if necessary. Cheers, all!