Skip to content
This repository has been archived by the owner on Sep 2, 2023. It is now read-only.

Membership requirements #43

Closed
MylesBorins opened this issue Feb 28, 2018 · 4 comments
Closed

Membership requirements #43

MylesBorins opened this issue Feb 28, 2018 · 4 comments

Comments

@MylesBorins
Copy link
Member

In the most recent meeting we decided to waive an earlier decision to create membership requirements that would have moved about 20% of the members of the group to Observer status. We agreed to discuss what types of requirements we would like to have, and how the process would be handled in a transparent and fair way.

Some examples of requirements that we could measure:

  • Meeting Attendance
  • Participation in the nodejs/modules repo (issues / prs)
  • Participation in votes
  • Code review / participation in nodejs/node in regards to ESM

It is worth mentioning that coming to something actionable here is going to be difficult, and getting it right will be even harder. That being said, I think coming up with clear expectations up front will make this group overall healthier.

@MylesBorins MylesBorins added this to discussion in Governance Feb 28, 2018
@weswigham
Copy link
Contributor

How about:

All members always retain their ability to voice objections and vote, however if a member is absent for more than 3 consecutive meetings, they may be removed from the 'Quorum' list with a non-quorum vote at a meeting, at which point they are no longer counted towards the total required to achieve quorum in a meeting. All new members initially start on the 'Quorum' list, and any member who attends a meeting will be added to the 'Quorum' list if they are not already on it.

?
That would at least take care of the progress concerns, I think, since if people drop away the remainder can vote to simply not count their attendance towards quorum, while also making it trivial to get back into things after a sabbatical (just show up). The effect is that even though we use quorum to pass things, if you go away for a long time your votes effectively default to "yes" by not attending after awhile instead of "no". It also prevents us from absolutely needing to move anyone or do anything until it actually becomes an issue (ie, we have a meeting without quorum, during which we'd be forced to move eligible individuals off of the quorum list in order to get work done).

@MylesBorins
Copy link
Member Author

@weswigham I don't think that really works. The default should be to seek quorum, in the perfect world we would never be voting. If one isn't participating in quorum they are not active in the decision making process. TLDR; I don't think it makes sense to have a difference between quorum and non quorum members. We should have active members and observers, and make it easy to move between the two groups.

@weswigham
Copy link
Contributor

weswigham commented Mar 6, 2018

@MylesBorins Mentally rename "Quorum" to "Members" and "Non-quorum" to "Observers" and it's the same effect. I'm just avoiding implying one group isn't actually a member (by calling the group "Members"), since that seemed to have been triggering people.

@MylesBorins
Copy link
Member Author

This is now defined 🎉

@MylesBorins MylesBorins moved this from discussion to done in Governance Apr 24, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
No open projects
Development

No branches or pull requests

2 participants