Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Governance: identify consensus on non-participation and write documentation #15408

Open
lucasgonze opened this issue Apr 10, 2024 · 5 comments
Open

Comments

@lucasgonze
Copy link
Contributor

lucasgonze commented Apr 10, 2024

We need to think about how to get a quorum when TSC members go inactive. It should be a quorum of active voters. So many voters have stopped responding to calls for votes that we are unable to finish them.

The activity on the meetings of TSC or any other committee is considered contribution. The person who has attended meeting had contributed his time, and that is no different from any other contribution.

Use https://gist.github.com/lucasgonze/0be5db9dee45e9fd85fbe7d062d0f83f for drafting

See #15347

@lucasgonze
Copy link
Contributor Author

Breaking it down:

  • Eligible participation types to be considered active
  • Time threshold to be considered inactive
  • What to do if we fall below the threshold
  • Minimize size for project viability

@lucasgonze
Copy link
Contributor Author

#15375

@lucasgonze
Copy link
Contributor Author

@lucasgonze
Copy link
Contributor Author

@lucasgonze
Copy link
Contributor Author

Call for vote:

  • Ready to forward upwards to other parties as a proposed proposal, but not for final approval
  • If they ask for changes, they will be made before acceptance
  • Whether or not they make changes, there will be a later vote on final acceptance
  • Vote +1: Jordan, Jim, Yogesh, Som, Lucas (unanimous)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant