Skip to content

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.

Sign up for GitHub

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

Open
wants to merge 2 commits into
base: main
Choose a base branch
from
Open

Document team structure #646

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
5f9c62a
Update README.md
zimbatm Apr 19, 2025
f13229c
Update README.md
zimbatm Apr 19, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
37 changes: 32 additions & 5 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,10 +1,37 @@
# The NixOS infrastructure configurations
# NixOS infrastructure

This repository contains all the hardware configuration for the nixos project
infrastructure.
This repo is used by the NixOS infrastucture team to hold, manage and document
the server infrastructure needed to run the project.

All the hosts are currently managed using NixOps. Some of the infrastructure is
managed using Terraform. There are still a lot of things configured manually.
This includes things like hydra.nixos.org, the binary cache, CDN, email, etc...

## Team role

The infra team is in service to the rest of the project to keep things up and
running (to the best of our abilities).

If you are a member of the project and need infrastructure, feel free to reach
out by creating a new issue on this repository. Please remember that our
capacity is limited so if you really want to see something happening, the best
way is to ask how you can help, and we'll try to find a way to make you part of
the team.

## How the team functions

Each member is voluntary and taking on part of the infrastructure they want to
work on.

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).
Copy link
Member

@mweinelt mweinelt Apr 23, 2025

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.

Copy link
Member

@Mic92 Mic92 Apr 24, 2025

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.

Copy link
Member

@infinisil infinisil Jun 11, 2025

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.

Copy link
Member

@mweinelt mweinelt Jun 28, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Updated the role on the team page on the homepge.


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).

## Docs

Expand Down