Define the role and organization of the foundation #32
Conversation
|
This pull request has been mentioned on NixOS Discourse. There might be relevant details there: https://discourse.nixos.org/t/tweag-nix-dev-update-43/25185/1 |
thufschmitt
changed the title
Dirty commit after some discussions with @zimbatm . Will need to be refined later
Keep the README short and focused
thufschmitt
force-pushed
the
expand-foundation-role
branch
from
d13cdd3
to
69988a3
Compare
|
@NixOS/foundation (and anyone interested), I've reshaped this quite a bit to make it clearer and more concise. Reviews welcome |
- Clarify the distinction between the Foundation and the board - Restructure and shrink the part about the responsibilities of the Foundation
role_and_responsibilities.md
Outdated
|
|
||
| _Empower the community and stay out of the way_ | ||
|
|
||
| The role of the board is to support the day-to-day operations of the community, help to structure it, and serve as a last-resort backup when things go wrong. |
There was a problem hiding this comment.
| The role of the board is to support the day-to-day operations of the community, help to structure it, and serve as a last-resort backup when things go wrong. | |
| The role of the board is to provide operational and organizational support to the NixOS project and community. | |
| The board is not responsible for technical leadership, as this is left to the individual community teams. |
I would like it if it was a bit more explicit that the board doesn't provide technical leadership, so that members can turn to the right people when looking to participate in the ecosystem.
There was a problem hiding this comment.
I would even expand that to make it clear that -> The board is not responsible for technical leadership, decisions or direction
There was a problem hiding this comment.
Indeed. I've made that more explicit in ad5a6a779084159eb27d83fb6482357e434af667
| - Fund community events and efforts | ||
| - Unblock things that would be stuck otherwise | ||
| - Arbiter in case of conflicts | ||
| - Serve as a backup for critical tasks when needed |
There was a problem hiding this comment.
What's missing here is handing out permissions and credentials. Someone has to hold and manage the keys.
There was a problem hiding this comment.
Added in 4b6d915 (although I'm not entirely sure I've put it in the best possible place)
There was a problem hiding this comment.
Ideally, the Foundation members do not hold any critical security tokens, but have a good working relationship with and can delegate those tasks to the Infra team. Otherwise, it will be difficult for the infra team to guarantee the security of the infrastructure as a whole.
There was a problem hiding this comment.
@zimbatm I would argue that the infra team needs in practice to have access to most systems, but it shouldn't have the responsibility of delegating the access to other teams. Maybe that shouldn't be the foundation board either though, but then we don't have anybody in a good position for it.
There was a problem hiding this comment.
The board would still hold the power to instruct the infra team to delegate access, either directly, or by delegating some of that access further down to the community. For example by setting up an election system.
But this is more of a future statement. The current infra team needs more people and a better interface.
| - Organize or support Nix events (NixCon, Summer of Nix, hackathons, …) | ||
| - Maintain the community in a healthy state | ||
| - Enforce some needed rules to keep the community an open and welcoming place (with or without a code of conduct) | ||
| - Run regular community surveys to take the pulse of the community and share back the results |
There was a problem hiding this comment.
| - Run regular community surveys to take the pulse of the community and share back the results |
This is the marketing team's job.
There was a problem hiding this comment.
Of course, but everything here is some team's job. But that doesn't mean that it's can't ultimately be the Foundation's responsibility (the same way that running the infrastructure is the infra team's job, but the Foundation is accountable for it).
There was a problem hiding this comment.
Maybe put it a bit more generally: gather data to take the pulse of the community and communicate the results.
There was a problem hiding this comment.
We'll keep having conversations and updating the document. This doesn't need to be set in stone.
| - Provide the necessary human infrastructure | ||
| - Host and empower the community teams | ||
| - Provide a conflict moderation and resolution path |
There was a problem hiding this comment.
This doesn't exactly match the rest of the mission statement. The foundation cannot provide human resources, but support and arrange for people to get together. Conflict moderation is the moderation team's job, and you already covered the escalation capacity (which would be part of the board's job) at the bottom.
There was a problem hiding this comment.
I agree, I think we mean more about an escalation route if all other recommended/defined channels fails
There was a problem hiding this comment.
The foundation cannot provide human resources, but support and arrange for people to get together.
Yes, but it can (and I believe should) give the moderation team legitimity to do so. Would
| - Provide the necessary human infrastructure | |
| - Host and empower the community teams | |
| - Provide a conflict moderation and resolution path | |
| - Provide the necessary human infrastructure | |
| - Host and empower the community teams | |
| - Ensure the existence of a conflict moderation and resolution path |
be better?
|
That may sound pedantic, but the documentation team converged on using British English some time ago, so that may be a consideration for this document as well. |
|
This pull request has been mentioned on NixOS Discourse. There might be relevant details there: https://discourse.nixos.org/t/tweag-nix-dev-update-46/26872/1 |
|
|
||
| - Handle the administrative, legal and financial tasks of the Foundation | ||
| - Serve as an interface between the community and the corporate/governmental world | ||
| - Handle sponsoring and donations |
There was a problem hiding this comment.
- Build and maintain beneficial and collaborative relationships (an example here would be Github and maybe other foundations for collaboration)
Co-authored-by: Ron Efroni <44145468+refroni@users.noreply.github.com> Co-authored-by: Valentin Gagarin <valentin.gagarin@tweag.io>
Co-authored-by: Ron Efroni <44145468+refroni@users.noreply.github.com> Co-authored-by: Jonas Chevalier <zimbatm@zimbatm.com>
Co-authored-by: Ron Efroni <44145468+refroni@users.noreply.github.com>
Should probably go to nixos.org once committed, but let's discuss it here for now