search

nix-community / infra

nix-community infrastructure [maintainer=@zowoq]
https://nix-community.org
MIT License
114 stars 75 forks source link

Require build-box users to be in a shared space #1147

Open zimbatm opened 6 months ago

zimbatm commented 6 months ago

We should set up a shared space where they can talk, like a Matrix channel, and enforce it. This could also be a good entry point for users to request access to the builders.

What do you think?

zowoq commented 6 months ago

Good idea.

Are you proposing a separate matrix channel or using #nix-community:nixos.org?

Matrix channel may also be a better alternative to https://github.com/nix-community/infra/issues/604, trying to get all of our members/collaborators into a github team.

zimbatm commented 6 months ago

Ok, yeah, we could add #nix-community-builders:nixos.org, for example. This would be a subset of #604 right?

zowoq commented 6 months ago

Existing #nix-community channel isn't really high traffic, I guess we could use that, might be simpler? Don't feel strongly either way.

This would be a subset of https://github.com/nix-community/infra/issues/604 right?

Similar idea of having a communication channel but for different groups, that issue I was only really thinking of the github side of the org, repo maintainers, etc.

Mic92 commented 6 months ago

I also think #nix-community is enough. I already have too many channels to read. If it becomes too busy there, we can relocate this. If people don't react to matrix messages / github, we can still temporary block their ssh access and leave a notification what happendd in the log.

nbraud commented 1 week ago

We should set up a shared space where they can talk, like a Matrix channel, and enforce it. This could also be a good entry point for users to request access to the builders.

What do you think?

FWIW, I'm (still) not on Matrix, though it's likely something I will have to do as more and more Nix development moves over. I just haven't had the energy to deal with Yet Another platform, setting up a home server, etc. :3

From that perspective, reaching out to users on whatever channel is available, and suspending access if there's an ongoing issue and they are unreachable, seems like the best solution.

It would make sense then to have metadata defining how to reach users, rather than leave admins (or other users) scrambling to find out who a given login name maps to and how to reach them. It should presumably wait for #813 though.