jupyter / jupyter/security

Electing a new Security Representative to the SSC

Open
#86 11 comments 0 reactions 0 assignees View on GitHub
Dominant language
Jupyter Notebook
Stars
27
Forks
12
Avg merge
3d 5h
Merged PRs (30d)
3

Description

By now you likely saw the email from Zach Sailer announcing the results of the latest Executive Council election, and thank you to everyone who took the time to vote. Because I’ve been elected to the EC, I can no longer serve as the Security representative to the SSC and we’ll need to elect a new one.

During the bootstrapping phase of the new Jupyter governance model our election of an SSC rep was very informal. I was nominated, agreed I would serve, and then we voted during one of our calls. Since we’re still small group a similar process may work again. I would like to ensure that the process is open, although I also support voting being private if that what any one of us prefers.

We can discuss this during our upcoming meetings, or we can work through the process here.

At the moment, the Security Council is (the easy way to tag you all on this issue):
- Matthias Bussonnier @Carreau
- Jason Grout @jasongrout
- Rollin Thomas @rcthomas
- Rick Wagner @rpwagner
- David L. Qiu @dlqqq
- Joe Lucas @josephtlucas
- Rosio Reyes @RRosio
- Yann Pellegriny @Yann-P

If there is someone else we would like to invite to participate (such as @krassowski), this could be good time.

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.