search

jupyterlab / frontends-team-compass

A repository for team interaction, syncing, and handling meeting notes across the JupyterLab ecosystem.
https://jupyterlab-team-compass.readthedocs.io/en/latest/
BSD 3-Clause "New" or "Revised" License
59 stars 30 forks source link

Add policy for membership #206

Closed fcollonval closed 12 months ago

fcollonval commented 1 year ago

Fix #204

As the discussion has stopped implying informal consensus, I call for a vote on this proposal as mentioned yesterday at the weekly call.

The question to vote on: do you agree with the new membership policy?

The vote will be closed on September 21st at midnight anywhere on earth (or as soon as we reach majority).

The vote:

fcollonval commented 1 year ago

Thanks @ellisonbg for bringing your suggestions. I agree that removing the inactive status of JupyterLab council membership makes sense.

I want to highlight that in this comment for others to voice for or against it.

Happy to get it removed in this proposal.

isabela-pf commented 1 year ago

Thanks to @fcollonval being insistent about bringing this up during JupyterLab calls; this kept getting moved to the bottom of my list. I appreciate the reminders.

Most of this is roughly what I expected based on prior discussions, but I do have questions about what happens with removed council members. I assume they are removed from the GitHub organization and the mailing list and the like. Does being removed do anything else? Like disqualify them from rejoining again after or in the future? Please let me know if these are out of scope and/or detailed elsewhere.

fcollonval commented 1 year ago

Thanks for the questions @isabela-pf

Most of this is roughly what I expected based on prior discussions, but I do have questions about what happens with removed council members. I assume they are removed from the GitHub organization and the mailing list and the like.

If a JupyterLab council member steps down (or is assumed too by lack of response when solicited), indeed it will be remove from the GitHub organization team and the mailing list.

Does being removed do anything else?

No (except if the member was also part of the smaller sub group with additional rights on PyPI and NPM for example).

Like disqualify them from rejoining again after or in the future?

No, they can ask to rejoin at any time. But the new application will go trough a vote like any new members.

Please let me know if these are out of scope and/or detailed elsewhere.

I can clarify that point in the document. I don't recall seeing that any where else.

ivanov commented 1 year ago

I pushed up some typo fixes, :+1:

fcollonval commented 12 months ago

Thanks a lot for all comments and for voting.

The changes have passed with 18 Yes and 3 unexpressed vote.

welcome[bot] commented 12 months ago

Congrats on your first merged pull request in this project! :tada: congrats Thank you for contributing, we are very proud of you! :heart: