Spoke with Chloe about this privately. I think the original charter of
the base team dillutes the authority necessary for it to be effective in
times of crisis. By outlining a bunch of limitations on the base team,
it gives tools to bad actors to undermine their authority with, and
works against the trust we're supposed to be putting in that team.
This reframes the base team as self-governing, putting how it governs
itself as out of scope for the project-wide governance document, and
updates the project governance docs accordingly to establish the base
team more firmly as the final authority on the project.
However, the information lost is still important. We should find a place
to put a document which establishes the principles to which the base
team holds itself. These include at least:
- Live up to the faith the project has put in you
- Trust the teams and generally avoid intervention
- Have faith in the election process and trust the next base team to
execute the role responsibly
We should use these principles when establishing the initial base team.
As new members cycle in, the veterans should use their first year to
educate them on the principles by which they can be responsible stewards
of the project.
Aside: the first patch is pretty unopinionated. I shoved all of the
opinions into the second patch.
Drew DeVault (2):
Move team structure before team administration
Rework the base team description
modules/Teams/pages/index.adoc | 62 ++++++++++++++++------------------
1 file changed, 29 insertions(+), 33 deletions(-)
Received on Tue Apr 09 2019 - 01:02:08 UTC