-
-
Notifications
You must be signed in to change notification settings - Fork 15
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
Define community constituency #71
Comments
Dupe of #62, closing to keep things tidy |
No, this is not about the foundation board, this is about the community it's supposed to represent. Or maybe the wording in #62 is misleading, because to me "part of the foundation" signals "representative" instead of "constituent". |
Some high-level thinking: We want constituents to have a vested interest in the project's success. Assuming that the constituency is called upon for voting. I would suggest defining that vested interest by a minimum level of contribution. This is a metric that can be gamed, and the foundation reserves the right to reject people who game the system. Another downside is that contribution is mostly measured by code contribution, so we also want a manual mechanism to recognize other types of contributions such as helping to organize events. Contribution should also decay in some form, to avoid zombie members. Members can also explicitly opt out in case they don't want to participate in the project anymore. That would be to enter the outer circle. Then each team would have their own criteria for entry and exit. For example, the infra team has stricter requirements than others due to the sensitive nature of the credentials they are holding. |
The premise here seems the project's impact is limited to its users. As such, I would wonder how we would define project success, and why such measures of success should necessarily be considered both self-evident and uncontroversial. |
If the foundation is to be representative of something at all, this something needs to be defined.
This may be as simple as:
The text was updated successfully, but these errors were encountered: