Grant nthmost sudo on m3

[nthmost]

Moves nthmost from noisebridge_users to noisebridge_admins on m3.

Deploy

ansible-playbook site.yml --limit m3.noisebridge.net -t access

[nthmost]

is this how this works? 😁

[mcint]

It doesn't auto-deploy.

Nor does the consensus you mentioned seem that salient to your own pursuits.

Can we pick a way to collaborate—then we can stick to it?

Noting the PR—self-approve-merge for others' context: https://github.com/noisebridge/infrastructure/commits/master/?since=2026-03-20&until=2026-03-27

[nthmost]

Honestly not sure how to collaborate, want to suggest ways?

and... I didn't self-approve... i merged. That's generally what's done when a PR is approved, in my experience?

I feel the culture in this group is hard to make sense of.

Where do you, @mcint, want to talk through things? What are the magic words to use that won't make you think everyone's out to get you, specifically? I haven't figured that out.

[mcint]

My mistake, saw the commit log on master but missed the approver only on PR.

My misinterpretation here has informed a chunk of my frustration, in trying or planning to collaborate and how do-ocratically I should expect changes might be pursued.

[nthmost]

For record, @mcint , i didn't believe this PR would work. I wanted to know why it wouldn't work.

[SuperQ]

Probably a key ordering issue. The various files have a loading order that affects how all the variables are merged.

Plus the actual user creation task is a bit funky.