Update permissions in light of Elliptic Research 202505 dissolution

[BigLep]

At the end of 202505, Elliptic Research, the maintainers of the "proofs" repos will be be dissolving. This issue is tracking the related permissions work including:

1. Ensuring new maintainers (e.g., FilOz for the time being) have relevant permissions.
2. Previously active Elliptic Research team members have their permissions reduced.

Desired Repo Status

2025-05-22: this is currently a @BigLep guess. It needs sign-off/update from Elliptic Research team members (e.g., @cryptonemo, @vmx)

https://docs.google.com/spreadsheets/d/1Jk-f9DgEcaiXqWiX3ZeMQdY5De559_u-N_S2lw92Fgg/edit?gid=711134418

Note: Doing this in a google sheet so it's easier to collaborate since not everyone involved as the ability to update this issue description.

Tasks

• Get authoritative answer from the proofs team on the "desired repo status" table above
• Migrate CI for the relevant repos: Update "proofs" repos' CI to use self-hosted runners that will function in 2025H2+ rust-fil-proofs#1775
• Archive the repos above: Adjusting "proofs" repos to rely solely on teams and archive some repos #133
• For all of the repos above: Adjusting "proofs" repos to rely solely on teams and archive some repos #133
  1. remove direct collaborators
  2. reduce permissions generally to

      admin:
        - proofs-crate-owners
      push:
        - proofs

• Adjust membership of the "proofs" team: Update permissions of the "proofs" team from PL Inc / Elliptic Research days #134
• Remove cases where Elliptic Research team members (or previous "PL Inc Proofs team" members) have direct access (and instead rely on team access where appropriate). This includes @cryptonemo, @vmx, @DrPeterVanNostrand, @porcuquine: Update permissions of the "proofs" team from PL Inc / Elliptic Research days #134
• (nice to have) Rename the "proofs" team to be "proofs-contributors": Rename proofs team to proofs-contributors #139

Notes

1. It's expected that multiple PRs will be needed to pull this off.
2. Rust crate ownership was handled in Rust crate ownership (and possibly release automation) #104

[BigLep]

@cryptonemo @vmx: I took first pass at enumerating all the "proofs" related repos and my understanding on what should be done. I'd appreciate your review here. Please also take on updating #133

[vmx]

My view:

Repo	Should migrate CI to FilOz self hosted runners?	Should archive?
fil_pasta_curves	no	yes
fil-rustacuda	no	no
fil-sppark	no	yes
filecoin-phase2	no	no
halo2	no	yes
merkletree	no (revert filecoin-project/merkletree@f2fb713)	no
pc2_cuda	no	yes
halo2	no	yes
phase2-attestations	no	no
powersoftau	no	no
proofs-buildbot	no	yes
rust-fil-logger	no	no
taupipp	no	yes

I think I've filled in all the blanks. @cryptonemo please correct or ack.

[BigLep]

@vmx: I'm realizing you probably didn't have the ability to edit the table inline. Lets use https://docs.google.com/spreadsheets/d/1Jk-f9DgEcaiXqWiX3ZeMQdY5De559_u-N_S2lw92Fgg/edit?gid=711134418 for now. I ideally want to stay out of the middle of this and let you guys specify what needs to get done and drive it.

[vmx]

Lets use https://docs.google.com/spreadsheets/d/1Jk-f9DgEcaiXqWiX3ZeMQdY5De559_u-N_S2lw92Fgg/edit?gid=711134418 for now.

@cryptonemo I've filled that out, please check if it's OK and change or ack.

[galargh]

To switch to FilOz self-hosted runners, we need to:

1. Get the repos off of self-hosted runner; here are the PRs:

• Use hosted runners merkletree#132
• Revert "feat: test out self hosted runner" rust-filecoin-proofs-api#107
• Revert "Switch over to self hosted CI" rust-fil-proofs#1776 (has some failures; at the time of writing, not all jobs finished yet)
• Revert "Switch to self hosted CI" bellperson#330

2. Deregister the self-hosted runners from those repos.
3. Register FilOz self-hosted with the repos that need it (rust-filecoin-proofs-api, rust-fil-proofs, bellperson + rust-gpu-tools which didn't have self-hosted runners before)
4. Put the jobs that need it (mainly the GPU dependent ones) on self-hosted runners.
5. Fix any new errors in jobs running on FilOz self-hosted runners (e.g. parameters files setup might be a common thing that will need adding).