-
-
Notifications
You must be signed in to change notification settings - Fork 119
Document team structure #646
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
base: main
Are you sure you want to change the base?
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.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Wondering if this is the best place to document this. Alternatives could be nixos/org for example.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
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.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
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.
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.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
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! |
3b25603
to
f13229c
Compare
Document the team structure a bit, so people know how we work and how to interface with us.