Document team structure #646
Conversation
|
|
||
| In general we try to reach overall consensus on decisions, and the team lead is here to listen and make judgement calls when no clear direction is available. | ||
|
|
||
| The current team lead is @mweinelt (hexa on Matrix). |
There was a problem hiding this comment.
Wondering if this is the best place to document this. Alternatives could be nixos/org for example.
There was a problem hiding this comment.
I think both places are fine. A bit of redundancy doesn't hurt. I would personally not look at the org repository if I would look into infrastructure related topics.
There was a problem hiding this comment.
The org repo is only meant to serve as the entry-point. In https://github.com/NixOS/org/blob/main/doc/governance.md#teams it links to the teams section of the homepage, which is the default place to document team leads. I recommend putting it there and linking to it from this README.
There was a problem hiding this comment.
Updated the role on the team page on the homepge.
README.md
Outdated
|
|
||
| Because the team size and budget is limited, we try to only take on new projects we feel we can manage. | ||
|
|
||
| The best way to join the team, is to start helping out. Ask where you can help and start tackling some tickets. If you're unsure what to work on, you can join or bi-weekly call (see below). |
There was a problem hiding this comment.
| The best way to join the team, is to start helping out. Ask where you can help and start tackling some tickets. If you're unsure what to work on, you can join or bi-weekly call (see below). | |
| The best way to join the team, is to start helping out. Ask where you can help and start tackling some tickets. If you're unsure what to work on, you can join our bi-weekly call (see below). |
|
/format |
Document the team structure a bit, so people know how we work and how to interface with us.
|
✅ Successfully formatted and absorbed changes! |
github-actions
bot
force-pushed
the
team-structure
branch
from
3b25603 to
f13229c
Compare
4 participants
Document the team structure a bit, so people know how we work and how to interface with us.