nix-community infrastructure [maintainer=@zowoq]

Find a file

zowoq fde3b61530 .sops.yaml: remove github_actions		2023-03-17 11:35:25 +10:00
.github	.github/workflows/hound.yml: various	2023-03-15 13:09:01 +10:00
build01	sops: replace my GPG key with AGE	2023-01-21 10:51:00 +01:00
build02	sops: replace my GPG key with AGE	2023-01-21 10:51:00 +01:00
build03	build03: remove outdated secrets	2023-02-15 12:59:10 +10:00
build04	build04: switch to systemd-boot	2023-03-09 09:09:04 +01:00
docs	docs: various	2023-03-15 10:47:14 +10:00
roles	roles/hercules-ci: fix formatting of secrets	2023-03-14 12:52:20 +10:00
services	hound: update repos 2023-03-15	2023-03-15 03:16:17 +00:00
terraform	.sops.yaml: remove github_actions	2023-03-17 11:35:25 +10:00
users	users: remove admins after quorum changes	2023-02-03 17:10:58 +10:00
.envrc	direnv: also reload on shell.nix and treefmt.nix changes	2023-01-21 10:39:02 +01:00
.gitignore	.sops.yaml: format	2023-03-17 11:34:12 +10:00
.sops.yaml	.sops.yaml: remove github_actions	2023-03-17 11:35:25 +10:00
bors.toml	move terraform-deploy to hercules-ci-effects	2023-03-11 10:33:17 +10:00
ci.nix	move terraform-deploy to hercules-ci-effects	2023-03-11 10:33:17 +10:00
flake.lock	Merge #468	2023-03-14 17:23:43 +00:00
flake.nix	move terraform-deploy to hercules-ci-effects	2023-03-11 10:33:17 +10:00
HOSTS.md	deploy -> inv	2023-01-10 06:47:06 +10:00
inv	deploy -> inv	2023-01-10 06:47:06 +10:00
LICENSE	Create LICENSE	2023-01-22 13:44:41 +10:00
pyproject.toml	apply treefmt to codebase	2022-12-31 07:27:07 +01:00
README.md	docs: various	2023-03-15 10:47:14 +10:00
secrets.yaml	sops: replace my GPG key with AGE	2023-01-21 10:51:00 +01:00
shell.nix	tasks.py: merge update-hound.py script	2023-03-13 07:21:26 +10:00
tasks.py	tasks.py: skip empty repos when updating hound	2023-03-17 11:33:19 +10:00
treefmt.nix	treefmt: enable prettier	2023-03-13 13:23:57 +10:00

README.md

nix-community infrastructure

Welcome to the Nix Community infrastructure project. This project holds all the NixOS and Terraform configuration for this organization.

Services

`Community builder` - build01.nix-community.org

We provide an x86 build machine as a public remote builder for the nix community, this machine also has an aarch64 machine configured as its own remote builder.

See here for more information.

`Continuous integration`

We provide x86 and aarch64 linux CI via these systems:

Hercules - https://hercules-ci.com/github/nix-community
- To enable hercules builds go to https://hercules-ci.com/github/nix-community/$REPO and click "Build this repository".
Hydra - https://hydra.nix-community.org
- To enable hydra builds add a new project in this file.

`Cache` - https://nix-community.cachix.org/

All of the above CI builds are pushed to the cache.

Thanks to Cachix for sponsoring our binary cache!

`Search` - https://search.nix-community.org

Hound code search for NixOS and nix-community GitHub organisations.

`nix-community.org DNS`

DNS is managed by terraform in this file.

`ryantm-updater bot`

Docs: https://ryantm.github.io/nixpkgs-update
Logs: https://r.ryantm.com/log/

`nur-update`

Support

For urgent matters, create an issue here: New Issue.

For repo additions, service requests and general conversation about governance and direction of the project, use the Discussion forum.

For casual chat, come join us in the nix-community room.

Pull requests from forks

As PRs from forks don't have automatic CI checks, admins can test PRs by posting a comment on the PR instead.

bors try - check if the PR builds.
bors merge - same as bors try but will also merge the PR if it builds successfully.
https://bors.tech/documentation/

nix-community administrators

@Mic92
@adisbladis
@ryantm
@zimbatm
@zowoq

Role

The role of the administrators is to support the members of the org, and the Nix project in general.

Responsibilities

The administrators are responsible for serving the community to the best of their ability and availability.

They provide services such as:

keep the systems updated and patched
reply to user requests
host new services that could help the project
on-board new projects
resolve conflict

The administrators are the only "owners" of the github organization.

Quorum of 5 rule

To reduce the attack surface on the project, the administrative team size is limited to 5 people.

Hosts

See HOSTS.md, this file also contains deployment details.