Remove inactive members 25-09-19

[galargh]

Summary

Why do you need this?

What else do we need to know?

DRI: myself

Reviewer's Checklist

• It is clear where the request is coming from (if unsure, ask)
• All the automated checks passed
• The YAML changes reflect the summary of the request
• The Terraform plan posted as a comment reflects the summary of the request

[github-actions]

The following access changes will be introduced as a result of applying the plan:

Access Changes

User 0x5459:
  - will lose maintain permission to venus
  - will lose maintain permission to venus-docs
User 4l8ee:
  - will lose push permission to filecoin-solidity
User aakoshh:
  - will lose maintain permission to tla-f3
User aarshkshah1992:
  - will lose admin permission to actors-private
  - will lose admin permission to actors-utils
  - will lose push permission to boost
  - will have the permission to builtin-actor-priv change from admin to pull
  - will have the permission to builtin-actors change from admin to maintain
  - will lose admin permission to builtin-actors-bundler
  - will lose admin permission to ent
  - will lose push permission to filecoin-pin
  - will lose push permission to filoz-infra
  - will lose admin permission to fvm-workbench
  - will lose admin permission to go-amt-ipld
  - will lose admin permission to go-bitfield
  - will lose admin permission to go-fil-markets
  - will lose admin permission to go-hamt-ipld
  - will have the permission to go-state-types change from admin to maintain
  - will lose maintain permission to lassie
  - will lose maintain permission to motion-s3-connector
  - will lose maintain permission to retrieval-load-testing
User abelsoares:
  - will lose admin permission to filecoin-retrieval-market-website
User abominablesnowman730:
  - will lose push permission to system-test-matrix
User achalvs:
  - will lose maintain permission to slate
User adlrocha:
  - will lose push permission to go-legs
  - will lose maintain permission to tla-f3
User akuokojnr:
  - will lose maintain permission to slate
User alanshaw:
  - will lose pull permission to sentinel
  - will lose admin permission to website-security.filecoin.io
User aleksatoljic:
  - will lose push permission to system-test-matrix
User alexandrumatei36:
  - will lose admin permission to starling
User alexey-n-chernyshov:
  - will lose push permission to cpp-filecoin
User alexmcon:
  - will lose admin permission to filecoin-plus-falcon
  - will lose admin permission to filplus-backend
  - will lose admin permission to filplus-registry
  - will lose admin permission to filplus-ssa-bot
  - will lose admin permission to filplus-tooling-backend-test
  - will lose admin permission to filplus-utils
User alexxnica:
  - will lose maintain permission to data
User alexytsu:
  - will lose push permission to actors-utils
  - will lose push permission to fvm-workbench
User ameanasad:
  - will lose maintain permission to lassie
User aminejvm:
  - will lose admin permission to slate
User andrejrakic:
  - will lose push permission to filecoin-solidity
User andrestorresgl:
  - will lose push permission to helm-charts
User andyschwab:
  - will lose admin permission to filecoin-docs
  - will lose admin permission to website-security.filecoin.io
User angelo-gh3990:
  - will lose push permission to filecoin-docs
User anjor:
  - will lose admin permission to data-prep-tools
User anomalroil:
  - will lose pull permission to ff-bounties
User anorth:
  - will lose push permission to filecoin-explorer
  - will lose admin permission to go-f3
  - will lose admin permission to go-fil-markets
  - will lose admin permission to research-private
  - will lose maintain permission to specs
User arajasek:
  - will lose push permission to builtin-actors
  - will lose pull permission to cmc-circulating-supply-fil-addresses
  - will lose push permission to community
  - will lose maintain permission to dealbot
  - will lose push permission to devgrants
  - will lose push permission to fevm-hardhat-kit
  - will lose push permission to ff-bounties
  - will lose push permission to ffi-stub
  - will lose push permission to filecoin-explorer
  - will lose push permission to filecoin-solidity
  - will lose pull permission to filecoin.io
  - will lose maintain permission to fuzzing-fvm
  - will lose maintain permission to fvm-pm
  - will lose maintain permission to fvm-starter-kit-deal-making
  - will lose push permission to fvm-test-vectors
  - will lose maintain permission to fvm-wasm-instrument
  - will lose push permission to fvm-website
  - will lose admin permission to gfm-priv
  - will lose push permission to go-data-transfer
  - will lose push permission to go-fil-markets
  - will lose maintain permission to go-legs
  - will lose push permission to lightning-planning
  - will lose push permission to lotus-docs
  - will lose admin permission to lotus-infra-dev
  - will lose triage permission to mercury-fil
  - will lose admin permission to ref-fvm-fuzz-corpora
  - will lose push permission to retrieval-market-spec
  - will lose push permission to sentinel-tick
  - will lose admin permission to specs
  - will lose maintain permission to venus
  - will lose admin permission to venus-docs
  - will lose pull permission to venus-wallet
User art-gor:
  - will lose push permission to cpp-filecoin
User aschmahmann:
  - will lose push permission to boost
  - will lose push permission to filecoin-pin
  - will lose maintain permission to go-fil-commcid-priv
User ashwanth-eth:
  - will lose admin permission to ecodash
User avivash:
  - will lose maintain permission to filsnap
User bajtos:
  - will lose push permission to filecoin-pin
  - will lose pull permission to retrieval-market
  - will lose pull permission to retrieval-market-spec
User biglep:
  - will have the permission to dealbot change from maintain to push
  - will have the permission to ff-bounties change from admin to push
  - will lose maintain permission to go-legs
  - will have the permission to lotus-infra-dev change from admin to maintain
  - will lose admin permission to specs
User birdychang:
  - will lose admin permission to docker-hub-exporter
  - will lose admin permission to filcryo
  - will lose push permission to filecoin-chain-archiver
  - will lose admin permission to filet
  - will lose admin permission to github-exporter
  - will lose admin permission to helm-charts
  - will lose admin permission to homebrew-exporter
  - will lose admin permission to lily
  - will lose admin permission to lily-archiver
  - will lose admin permission to lotus-infra-dev
  - will lose admin permission to mercury-api
  - will lose admin permission to mercury-fil
  - will lose admin permission to release-metrics-gitops
  - will lose admin permission to sentinel
  - will lose admin permission to sentinel-backfill
  - will lose admin permission to sentinel-infra
  - will lose admin permission to sentinel-tick
  - will lose admin permission to snapcraft-exporter
  - will lose push permission to venus
User blocksonachain:
  - will lose maintain permission to dealbot
  - will lose admin permission to devgrants
  - will lose admin permission to filecoin-solidity
  - will lose admin permission to fuzzing-fvm
  - will lose admin permission to fvm-pm
  - will lose maintain permission to go-legs
  - will lose admin permission to lotus-infra-dev
  - will lose admin permission to specs
  - will lose admin permission to system-test-matrix
User bobdubois:
  - will lose maintain permission to filecoin-docs
  - will lose admin permission to sp-automation
User bokimilinkovic:
  - will lose push permission to system-test-matrix
User brdji:
  - will lose admin permission to system-test-matrix
User brendalee:
  - will lose maintain permission to boost
  - will lose maintain permission to boost-docs
  - will lose maintain permission to boost-gfm
  - will lose maintain permission to boost-graphsync
  - will lose push permission to filecoin-docs
  - will lose maintain permission to lid-benchmarks
  - will lose push permission to sp-automation
User bulatsaif:
  - will lose push permission to cpp-filecoin
User claudiorodr:
  - will lose maintain permission to filecoin-retrieval-market-website
User clriesco:
  - will lose admin permission to filecoin-plus-falcon
  - will lose admin permission to filplus-backend
  - will lose admin permission to filplus-registry
  - will lose admin permission to filplus-ssa-bot
  - will lose admin permission to filplus-tooling-backend-test
  - will lose admin permission to filplus-utils
User codewarriorr:
  - will lose push permission to filplus-backend
User cre-ed:
  - will lose push permission to cpp-filecoin
User cryptoatwill:
  - will lose maintain permission to tla-f3
User d3as8a:
  - will lose maintain permission to ecodash
  - will lose push permission to green.filecoin.io
User dannyob:
  - will lose maintain permission to core-devs
  - will lose admin permission to on-chain-voting
User data-programs:
  - will lose push permission to filecoin-plus-falcon
  - will lose push permission to filplus-tooling-backend-test
User davidd8:
  - will lose admin permission to boost
  - will lose maintain permission to boost-docs
  - will lose maintain permission to boost-gfm
  - will lose maintain permission to boost-graphsync
  - will lose push permission to dagstore
  - will lose maintain permission to dealbot
  - will lose push permission to filecoin-docs
  - will lose maintain permission to go-fil-markets
  - will lose maintain permission to lassie
  - will lose maintain permission to lid-benchmarks
  - will lose admin permission to lightning-planning
  - will lose maintain permission to motion-s3-connector
  - will lose maintain permission to retrieval-load-testing
User daviddias:
  - will lose admin permission to client-growth-analytics
  - will lose pull permission to retrieval-market
  - will lose pull permission to retrieval-market-spec
  - will lose admin permission to sentinel
  - will lose admin permission to website-security.filecoin.io
User dkkapur:
  - will lose admin permission to client-growth-analytics
  - will lose push permission to community
  - will lose maintain permission to data
  - will lose maintain permission to dealbot
  - will lose admin permission to filecoin-plus-application-json-restructure
  - will lose admin permission to filecoin-plus-leaderboard-data
  - will lose admin permission to filecoin-plus-roadmap
  - will lose pull permission to filecoin-retrieval-market-website
  - will lose push permission to filecoin.io
  - will lose admin permission to filplus-backend
  - will lose admin permission to filplus-registry
  - will lose admin permission to filplus-ssa-bot
  - will lose admin permission to filplus-tooling-backend-test
  - will lose admin permission to filplus-utils
  - will lose triage permission to go-data-transfer
  - will lose triage permission to go-fil-markets
  - will lose admin permission to green.filecoin.io
  - will lose admin permission to hackathons-forestry-legacy
  - will lose admin permission to notary-governance
  - will lose admin permission to orbit.filecoin.io
  - will lose admin permission to website-security.filecoin.io
User dnkolegov:
  - will lose maintain permission to tla-f3
User dr-bizz:
  - will lose admin permission to green.filecoin.io
  - will lose admin permission to orbit.filecoin.io
User dzmitrykliapkou:
  - will lose admin permission to cmc-circulating-supply-fil-addresses
User ec2:
  - will lose push permission to builtin-actors
  - will lose triage permission to community
  - will lose push permission to fvm-test-vectors
User elestrias:
  - will lose push permission to cpp-filecoin
User elijaharita:
  - will lose push permission to dagstore
  - will lose maintain permission to go-fil-markets
  - will lose maintain permission to lassie
  - will lose maintain permission to motion-s3-connector
  - will lose push permission to motion-sp-test
  - will lose maintain permission to retrieval-load-testing
User elvin-du:
  - will lose admin permission to venus
  - will lose admin permission to venus-docs
  - will lose admin permission to venus-wallet
User emilymariahh:
  - will lose triage permission to green.filecoin.io
User eshon:
  - will lose admin permission to cmc-circulating-supply-fil-addresses
  - will lose maintain permission to community
  - will lose push permission to filecoin-explorer
  - will lose maintain permission to fvm-pm
  - will lose push permission to fvm-spacewarp
  - will lose push permission to fvm-website
  - will lose push permission to specs
  - will lose admin permission to venus-docs
  - will lose admin permission to website-security.filecoin.io
User expede:
  - will lose admin permission to filsnap
User fabriziogianni7:
  - will lose admin permission to filecoin-plus-application-json-restructure
  - will lose admin permission to notary-governance
User figureouter:
  - will lose maintain permission to devgrants
User filecoin-ci:
  - will lose pull permission to venus
User filecoin-governance:
  - will lose triage permission to fips
User filipagr:
  - will lose pull permission to on-chain-voting
User filozzy:
  - will lose admin permission to bellperson
  - will lose admin permission to bls-signatures
  - will lose admin permission to blstrs
  - will lose admin permission to ec-gpu
  - will lose admin permission to fil-rustacuda
  - will lose admin permission to filecoin-phase2
  - will lose push permission to lotus
  - will lose admin permission to merkletree
  - will lose admin permission to powersoftau
  - will lose admin permission to rust-fil-logger
  - will lose admin permission to rust-fil-proofs
  - will lose admin permission to rust-filecoin-proofs-api
  - will lose admin permission to rust-gpu-tools
  - will lose admin permission to taupipp
User fridrik01:
  - will lose push permission to builtin-actors
  - will lose push permission to dagstore
  - will lose push permission to dealbot
  - will lose push permission to ff-bounties
  - will lose push permission to ffi-stub
  - will lose push permission to filecoin-solidity
  - will lose maintain permission to fvm-starter-kit-deal-making
  - will lose push permission to fvm-test-vectors
  - will lose push permission to go-bitfield
  - will lose push permission to go-commp-utils
  - will lose push permission to go-data-segment
  - will lose push permission to go-data-transfer
  - will lose push permission to go-ds-versioning
  - will lose push permission to go-fil-commcid
  - will lose push permission to go-fil-commp-hashhash
  - will lose push permission to go-fil-markets
  - will lose push permission to go-state-types
  - will lose push permission to go-statemachine
  - will lose push permission to lotus
  - will lose push permission to lotus-docs
  - will lose push permission to lotus-infra-dev
  - will lose push permission to ref-fvm
  - will lose push permission to sentinel-tick
User frm:
  - will lose push permission to filecoin-datasets-discovery-ui
User frrist:
  - will lose push permission to filecoin-explorer
  - will lose push permission to specs
  - will lose pull permission to venus
User galen-mcandrew:
  - will lose admin permission to filecoin-plus-application-json-restructure
User gammazero:
  - will lose push permission to boost
  - will lose push permission to dagstore
  - will lose maintain permission to dealbot
  - will lose maintain permission to go-fil-markets
  - will lose admin permission to go-legs
  - will lose maintain permission to lassie
  - will lose maintain permission to motion-s3-connector
  - will lose push permission to motion-sp-test
  - will lose maintain permission to retrieval-load-testing
User george-haddad:
  - will lose admin permission to starling
User glacierwalrus:
  - will lose push permission to builtin-actors
  - will lose push permission to dagstore
  - will lose push permission to dealbot
  - will lose admin permission to docker-hub-exporter
  - will lose push permission to ff-bounties
  - will lose push permission to ffi-stub
  - will lose push permission to filecoin-chain-archiver
  - will lose push permission to fvm-test-vectors
  - will lose admin permission to github-exporter
  - will lose push permission to go-bitfield
  - will lose push permission to go-commp-utils
  - will lose push permission to go-data-segment
  - will lose push permission to go-data-transfer
  - will lose push permission to go-ds-versioning
  - will lose push permission to go-fil-commcid
  - will lose push permission to go-fil-commp-hashhash
  - will lose push permission to go-fil-markets
  - will lose push permission to go-state-types
  - will lose push permission to go-statemachine
  - will lose admin permission to helm-charts
  - will lose admin permission to homebrew-exporter
  - will lose push permission to lotus
  - will lose push permission to lotus-docs
  - will lose admin permission to lotus-infra-dev
  - will lose push permission to ref-fvm
  - will lose admin permission to release-metrics-gitops
  - will lose maintain permission to sentinel-backfill
  - will lose admin permission to sentinel-infra
  - will lose push permission to sentinel-tick
  - will lose admin permission to snapcraft-exporter
  - will lose push permission to venus
User gndclouds:
  - will lose pull permission to slate
User guy-goren:
  - will lose maintain permission to tla-f3
User hammertoe:
  - will lose push permission to community
  - will lose maintain permission to fevm-data-dao-kit
  - will lose admin permission to fevm-hardhat-kit
  - will lose push permission to filecoin-docs
  - will lose admin permission to filecoin-fvm-localnet
  - will lose push permission to filecoin-solidity
  - will lose admin permission to filecoinverymagic
  - will lose maintain permission to fvm-starter-kit-deal-making
User hannahhoward:
  - will lose admin permission to boost
  - will lose push permission to boost-gfm
  - will lose push permission to boost-graphsync
  - will lose admin permission to data-transfer-benchmark
  - will have the permission to go-data-transfer change from admin to push
  - will have the permission to go-fil-markets change from admin to push
  - will lose maintain permission to go-legs
  - will lose admin permission to go-retrieval-types
  - will lose admin permission to lassie
  - will lose admin permission to lightning-planning
  - will lose admin permission to motion-s3-connector
  - will lose admin permission to retrieval-load-testing
  - will lose admin permission to retrieval-market-spec
  - will lose admin permission to rhea-load-testing
User haochizzle:
  - will lose triage permission to community
User harisbutt:
  - will lose maintain permission to slate
User harrm:
  - will lose push permission to cpp-filecoin
User hugomrdias:
  - will lose push permission to filecoin-pin
User hunjixin:
  - will lose admin permission to venus-docs
User ialberquilla:
  - will lose admin permission to notary-governance
User ianconsolata:
  - will lose admin permission to docker-hub-exporter
  - will lose admin permission to filsnap
  - will lose push permission to fvm-pm
  - will lose admin permission to github-exporter
  - will lose admin permission to homebrew-exporter
  - will lose admin permission to release-metrics-gitops
  - will lose maintain permission to slackcident
  - will lose admin permission to snapcraft-exporter
User igor-egorov:
  - will lose push permission to cpp-filecoin
User irenegia:
  - will lose push permission to lotus-infra-dev
  - will lose push permission to research-private
User isabellabcj:
  - will lose pull permission to filecoin.io
User ischasny:
  - will lose push permission to boost
  - will lose maintain permission to boost-docs
  - will lose maintain permission to boost-gfm
  - will lose maintain permission to boost-graphsync
  - will lose push permission to filecoin-docs
  - will lose maintain permission to lid-benchmarks
User ivanka:
  - will lose push permission to filecoin-docs
User jacarte:
  - will lose admin permission to fuzzing-fvm
  - will lose push permission to fvm-wasm-instrument
  - will lose push permission to ref-fvm-fuzz-corpora
  - will lose push permission to wasm-tools
User jadtermsani:
  - will lose admin permission to starling
User jbenet:
  - will lose admin permission to cmc-circulating-supply-fil-addresses
  - will lose push permission to filecoin-explorer
  - will lose triage permission to filecoin.io
  - will lose push permission to fips
  - will lose pull permission to sentinel
  - will lose maintain permission to specs
User jbesraa:
  - will lose admin permission to filecoin-plus-application-json-restructure
  - will lose admin permission to filecoin-plus-falcon
  - will lose admin permission to filplus-tooling-backend-test
  - will lose admin permission to filplus-utils
User jennijuju:
  - will lose admin permission to bellperson
  - will lose admin permission to benchmarks
  - will lose admin permission to bls-signatures
  - will lose admin permission to blstrs
  - will lose admin permission to boost
  - will lose admin permission to cmc-circulating-supply-fil-addresses
  - will lose admin permission to community
  - will lose admin permission to core-devs
  - will have the permission to dealbot change from maintain to push
  - will lose admin permission to ec-gpu
  - will have the permission to ff-bounties change from admin to push
  - will lose admin permission to fil-rustacuda
  - will lose admin permission to filecoin-phase2
  - will lose push permission to filecoin-solidity
  - will lose push permission to fvm-spacewarp
  - will lose push permission to fvm-website
  - will lose maintain permission to go-legs
  - will have the permission to lotus-docs change from admin to maintain
  - will have the permission to lotus-infra-dev change from admin to maintain
  - will lose admin permission to merkletree
  - will lose admin permission to powersoftau
  - will lose admin permission to rust-fil-logger
  - will lose admin permission to rust-fil-proofs
  - will lose admin permission to rust-filecoin-proofs-api
  - will lose admin permission to rust-gpu-tools
  - will lose admin permission to specs
  - will lose admin permission to taupipp
  - will lose admin permission to venus-docs
User jimpick:
  - will lose pull permission to sentinel
User jnthnvctr:
  - will lose admin permission to filecoin-datasets-discovery-ui
  - will lose push permission to filecoin-explorer
  - will lose pull permission to filecoin-retrieval-market-website
  - will lose push permission to filecoin.io
  - will lose admin permission to green.filecoin.io
  - will lose admin permission to hackathons-forestry-legacy
  - will lose admin permission to notary-governance
  - will lose admin permission to orbit.filecoin.io
  - will lose push permission to specs
  - will lose pull permission to venus
User joannaong:
  - will lose push permission to green.filecoin.io
User joaosa:
  - will lose pull permission to retrieval-market
  - will lose pull permission to retrieval-market-spec
  - will lose push permission to sp-automation
User johannes-jp:
  - will lose push permission to slate
User jordattebayo:
  - will lose push permission to slate
User joss-hua:
  - will lose maintain permission to venus-docs
User jsoares:
  - will lose push permission to fvm-pm
  - will lose admin permission to tla-f3
User juliangruber:
  - will lose push permission to filecoin-pin
  - will lose pull permission to retrieval-market
  - will lose pull permission to retrieval-market-spec
User kacperzuk-neti:
  - will lose admin permission to filplus-ssa-bot
User kaitlin-beegle:
  - will lose admin permission to on-chain-voting
User kalambet:
  - will lose push permission to builtin-actors
  - will lose push permission to f3-activation-contract
  - will lose push permission to fips
  - will lose push permission to fvm-test-vectors
  - will lose maintain permission to ref-fvm
User katarinaketi:
  - will lose pull permission to system-test-matrix
User kevzak:
  - will lose maintain permission to filecoin-plus-roadmap
  - will lose maintain permission to notary-governance
User kkarrancsu:
  - will lose push permission to builtin-actors
User kokal33:
  - will lose admin permission to filecoin-plus-falcon
  - will lose admin permission to filplus-tooling-backend-test
  - will lose admin permission to filplus-utils
User kubuxu:
  - will lose push permission to filecoin-explorer
  - will lose push permission to specs
User lanebloxico:
  - will lose pull permission to system-test-matrix
User laurenspiegel:
  - will lose maintain permission to boost
  - will lose push permission to fvm-pm
  - will lose admin permission to lily
  - will lose maintain permission to motion-s3-connector
User laurentsenta:
  - will lose push permission to homebrew-lotus
User lesnyrumcajs:
  - will lose admin permission to awesome-filecoin
  - will lose pull permission to lotus-infra
User lexluthr:
  - will have the permission to boost-gfm change from admin to maintain
  - will have the permission to boost-graphsync change from admin to maintain
  - will have the permission to go-fil-markets change from maintain to push
  - will lose maintain permission to lassie
  - will have the permission to lid-benchmarks change from admin to maintain
  - will lose maintain permission to motion-s3-connector
  - will lose maintain permission to retrieval-load-testing
  - will lose push permission to sp-automation
User lidel:
  - will lose push permission to filecoin-pin
User lksbrssr:
  - will lose push permission to community
  - will lose push permission to ecodash
  - will lose push permission to filecoin-docs
  - will lose admin permission to fvm-pm
  - will lose push permission to fvm-spacewarp
  - will lose push permission to fvm-website
  - will lose admin permission to hackathons-forestry-legacy
User longfeiwan9:
  - will lose maintain permission to fvm-pm
User lucaniz:
  - will lose push permission to research-private
User lukasz-wal:
  - will lose push permission to filplus-ssa-bot
User maciejwitowski:
  - will lose push permission to builtin-actors
  - will lose push permission to dagstore
  - will lose push permission to dealbot
  - will lose push permission to ff-bounties
  - will lose push permission to ffi-stub
  - will lose admin permission to filsnap
  - will lose push permission to fvm-test-vectors
  - will lose push permission to go-bitfield
  - will lose push permission to go-commp-utils
  - will lose push permission to go-data-segment
  - will lose push permission to go-data-transfer
  - will lose push permission to go-ds-versioning
  - will lose push permission to go-fil-commcid
  - will lose push permission to go-fil-commp-hashhash
  - will lose push permission to go-fil-markets
  - will lose push permission to go-state-types
  - will lose push permission to go-statemachine
  - will lose push permission to lotus
  - will lose push permission to lotus-docs
  - will lose push permission to lotus-infra-dev
  - will lose push permission to ref-fvm
  - will lose push permission to sentinel-tick
User macro-ss:
  - will lose push permission to builtin-actors
User magik6k:
  - will lose maintain permission to dealbot
  - will lose push permission to filecoin-explorer
  - will lose push permission to filecoin-solidity
  - will lose admin permission to go-fil-markets
  - will lose maintain permission to go-legs
  - will have the permission to lid-benchmarks change from admin to maintain
  - will have the permission to lotus-infra-dev change from admin to maintain
  - will lose admin permission to specs
User marco-storswift:
  - will lose push permission to builtin-actors
User markuu-s:
  - will lose push permission to cpp-filecoin
User martinalong:
  - will lose maintain permission to slate
User masterjedy:
  - will lose push permission to cpp-filecoin
User matejpavlovic:
  - will lose maintain permission to tla-f3
User meandavejustice:
  - will lose maintain permission to filsnap
User milos1731:
  - will lose push permission to filecoin-solidity
User milosmarkoni:
  - will lose push permission to system-test-matrix
User mingela:
  - will lose push permission to cpp-filecoin
User mirhamasala:
  - will lose push permission to fvm-website
User mishmosh:
  - will lose push permission to community
  - will lose admin permission to ecodash
  - will lose push permission to filecoin-docs
  - will lose pull permission to filecoin-retrieval-market-website
  - will lose push permission to filecoin.io
  - will lose push permission to go-data-transfer
  - will lose admin permission to go-fil-markets
  - will lose admin permission to green.filecoin.io
  - will lose admin permission to hackathons-forestry-legacy
  - will lose admin permission to orbit.filecoin.io
  - will lose maintain permission to specs
  - will lose admin permission to starling
  - will lose admin permission to venus-docs
User momack2:
  - will lose admin permission to community
  - will lose admin permission to core-devs
  - will lose admin permission to ff-bounties
  - will lose push permission to fvm-website
  - will lose admin permission to retrieval-market-spec
  - will lose admin permission to roadmap
  - will lose pull permission to sentinel
  - will lose maintain permission to specs
User mstojanovicbloxico:
  - will lose push permission to system-test-matrix
User nicola:
  - will lose push permission to bellperson
  - will lose push permission to bls-signatures
  - will lose maintain permission to blstrs
  - will lose maintain permission to ec-gpu
  - will lose push permission to fil-rustacuda
  - will lose admin permission to filecoin-ffi
  - will lose admin permission to filecoin-ffi-private
  - will lose push permission to filecoin-pin
  - will lose pull permission to filecoin-retrieval-market-website
  - will lose push permission to filecoin.io
  - will lose push permission to filoz-infra
  - will lose push permission to fips
  - will lose push permission to go-paramfetch
  - will lose admin permission to green.filecoin.io
  - will lose admin permission to hackathons-forestry-legacy
  - will lose push permission to merkletree
  - will lose admin permission to orbit.filecoin.io
  - will lose push permission to powersoftau
  - will lose admin permission to research-private
  - will lose maintain permission to rust-fil-logger
  - will lose push permission to rust-fil-proofs
  - will lose maintain permission to rust-filecoin-proofs-api
  - will lose push permission to rust-gpu-tools
  - will lose pull permission to sentinel
  - will lose maintain permission to specs
  - will lose pull permission to taupipp
User nicole-code:
  - will lose push permission to green.filecoin.io
User ninitrava:
  - will lose triage permission to filecoin.io
  - will lose push permission to fips
  - will lose pull permission to sentinel
  - will lose triage permission to specs
User nonsense:
  - will lose admin permission to boost
  - will lose maintain permission to boost-docs
  - will lose admin permission to boost-gfm
  - will lose admin permission to boost-graphsync
  - will lose push permission to builtin-actors
  - will lose push permission to dagstore
  - will lose admin permission to dealbot
  - will lose push permission to ff-bounties
  - will lose push permission to ffi-stub
  - will lose push permission to filecoin-docs
  - will lose push permission to fvm-test-vectors
  - will lose push permission to go-bitfield
  - will lose push permission to go-commp-utils
  - will lose push permission to go-data-segment
  - will lose push permission to go-data-transfer
  - will lose push permission to go-ds-versioning
  - will lose push permission to go-fil-commcid
  - will lose push permission to go-fil-commp-hashhash
  - will lose admin permission to go-fil-markets
  - will lose push permission to go-state-types
  - will lose push permission to go-statemachine
  - will lose maintain permission to lassie
  - will lose admin permission to lid-benchmarks
  - will lose push permission to lotus
  - will lose push permission to lotus-docs
  - will lose push permission to lotus-infra-dev
  - will lose maintain permission to motion-s3-connector
  - will lose push permission to ref-fvm
  - will lose maintain permission to retrieval-load-testing
  - will lose pull permission to sentinel
  - will lose push permission to sentinel-tick
  - will lose admin permission to sp-automation
  - will lose maintain permission to specs
User ns4plabs:
  - will lose admin permission to docker-hub-exporter
  - will lose push permission to filecoin-chain-archiver
  - will lose admin permission to github-exporter
  - will lose admin permission to helm-charts
  - will lose admin permission to homebrew-exporter
  - will lose admin permission to lotus-infra-dev
  - will lose admin permission to release-metrics-gitops
  - will lose maintain permission to sentinel-backfill
  - will lose admin permission to sentinel-infra
  - will lose push permission to sentinel-tick
  - will lose admin permission to snapcraft-exporter
  - will lose push permission to venus
User ognots:
  - will lose admin permission to docker-hub-exporter
  - will lose push permission to filecoin-chain-archiver
  - will lose push permission to filecoin-explorer
  - will lose admin permission to github-exporter
  - will lose admin permission to helm-charts
  - will lose admin permission to homebrew-exporter
  - will lose maintain permission to lily-archiver
  - will lose admin permission to lotus-infra-dev
  - will lose admin permission to release-metrics-gitops
  - will lose maintain permission to sentinel-backfill
  - will lose admin permission to sentinel-infra
  - will lose push permission to sentinel-tick
  - will lose admin permission to snapcraft-exporter
  - will lose push permission to specs
  - will lose push permission to venus
User olizilla:
  - will lose pull permission to sentinel
  - will lose admin permission to specs
  - will lose admin permission to website-security.filecoin.io
User onkar-san:
  - will lose push permission to community
User openworklabbot:
  - will lose push permission to cmc-circulating-supply-fil-addresses
User ortyomka:
  - will lose push permission to cpp-filecoin
User orvn:
  - will lose admin permission to ecodash
  - will lose push permission to filecoin-plus-falcon
  - will lose push permission to filplus-backend
  - will lose admin permission to filplus-tooling-backend-test
  - will lose admin permission to green.filecoin.io
User panges2:
  - will lose admin permission to filecoin-plus-falcon
  - will lose admin permission to filplus-backend
  - will lose admin permission to filplus-tooling-backend-test
  - will lose maintain permission to notary-governance
User pap1ll0n:
  - will lose push permission to devgrants
User parthpathakweb3:
  - will lose push permission to filecoin-solidity
  - will lose maintain permission to fvm-starter-kit-deal-making
User parthshah1:
  - will lose admin permission to ff-bounties
  - will lose maintain permission to slackcident
  - will lose admin permission to website-security.filecoin.io
User patrickwoodhead:
  - will lose push permission to filecoin-pin
  - will lose admin permission to filecoin-retrieval-market-website
  - will lose admin permission to retrieval-market
  - will lose admin permission to retrieval-market-spec
User philippbanhardt:
  - will lose maintain permission to devgrants
User pingwindyktator:
  - will lose push permission to filplus-backend
  - will lose push permission to filplus-registry
User pk-controller:
  - will lose pull permission to cmc-circulating-supply-fil-addresses
User protocolin:
  - will lose admin permission to cmc-circulating-supply-fil-addresses
  - will lose pull permission to filecoin-retrieval-market-website
  - will lose push permission to filecoin.io
  - will lose push permission to fips
  - will lose admin permission to green.filecoin.io
  - will lose admin permission to hackathons-forestry-legacy
  - will lose admin permission to orbit.filecoin.io
User pyropy:
  - will lose push permission to filecoin-pin
User raghavrmadya:
  - will lose maintain permission to filecoin-plus-roadmap
  - will lose admin permission to notary-governance
User raulk:
  - will lose push permission to builtin-actors-bundler
  - will have the permission to dealbot change from admin to push
  - will lose push permission to fevm-contract-tests
  - will lose admin permission to filecoin-docs
  - will lose push permission to filecoin-solidity
  - will lose maintain permission to fuzzing-fvm
  - will lose maintain permission to fvm-pm
  - will lose admin permission to fvm-spacewarp
  - will lose maintain permission to fvm-starter-kit-deal-making
  - will lose admin permission to fvm-website
  - will lose pull permission to sentinel
  - will lose admin permission to system-test-matrix
User ravish1729:
  - will lose push permission to raas-starter-kit
User redransil:
  - will lose push permission to green.filecoin.io
User reiers:
  - will lose push permission to boost
  - will lose maintain permission to boost-docs
  - will lose maintain permission to boost-gfm
  - will lose maintain permission to boost-graphsync
  - will lose push permission to filecoin-docs
  - will lose maintain permission to lid-benchmarks
  - will lose push permission to lotus-docs
User relotnek:
  - will lose admin permission to core-devs
  - will lose admin permission to ff-bounties
User ribasushi:
  - will lose admin permission to client-growth-analytics
  - will lose admin permission to go-dagaggregator-unixfs
  - will lose maintain permission to go-fil-commcid-priv
  - will lose push permission to lotus-infra-dev
User rjan90:
  - will lose admin permission to community
  - will lose push permission to lid-benchmarks
User rk-rishikesh:
  - will lose push permission to fvm-pm
User robertagora:
  - will lose admin permission to filecoin-solidity
  - will lose push permission to fvm-pm
  - will lose maintain permission to specs
User rvagg:
  - will lose push permission to boost-graphsync
  - will have the permission to dealbot change from maintain to push
  - will have the permission to go-data-transfer change from admin to maintain
  - will lose admin permission to motion-sp-test
User schreck23:
  - will lose push permission to sp-automation
User schwartz10:
  - will lose push permission to go-crypto
User scotthconner:
  - will lose admin permission to filecoin-solidity
  - will lose push permission to lotus-infra-dev
User seedingtrees:
  - will lose push permission to devgrants
User sergkaprovich:
  - will lose push permission to cpp-filecoin
User simonkim0515:
  - will lose admin permission to filecoin-plus-falcon
  - will lose admin permission to filecoin-plus-roadmap
  - will lose maintain permission to notary-governance
User smooth-operator:
  - will lose admin permission to starling
User snadrus:
  - will lose maintain permission to lotus
  - will lose push permission to lotus-docs
User snissn:
  - will lose maintain permission to fvm-pm
User splumms:
  - will lose push permission to ecodash
  - will lose maintain permission to green.filecoin.io
User ssallam:
  - will lose admin permission to filecoin-plus-application-json-restructure
User starboard-devops:
  - will lose admin permission to lily
  - will lose admin permission to sentinel
User stebalien:
  - will lose push permission to filecoin-solidity
User stefangajic:
  - will lose push permission to system-test-matrix
  - will lose push permission to venus
User steven004:
  - will lose push permission to builtin-actors
  - will lose push permission to f3-activation-contract
  - will lose push permission to fips
  - will lose push permission to fvm-test-vectors
  - will lose admin permission to venus
  - will lose admin permission to venus-docs
  - will lose pull permission to venus-wallet
User suzannaaltman:
  - will lose admin permission to hackathons-forestry-legacy
  - will lose admin permission to orbit.filecoin.io
User svvimming:
  - will lose maintain permission to ecodash
  - will lose admin permission to green.filecoin.io
User tanisha-fil:
  - will lose admin permission to community
User tarafanlin:
  - will lose push permission to slate
User terryhung:
  - will lose admin permission to docker-hub-exporter
  - will lose push permission to filecoin-chain-archiver
  - will lose admin permission to filet
  - will lose admin permission to github-exporter
  - will lose admin permission to helm-charts
  - will lose admin permission to homebrew-exporter
  - will lose admin permission to lotus-infra-dev
  - will lose admin permission to release-metrics-gitops
  - will lose admin permission to snapcraft-exporter
  - will lose push permission to venus
User thedivic:
  - will lose pull permission to system-test-matrix
User tiago258:
  - will lose maintain permission to filecoin-retrieval-market-website
User tikagan:
  - will lose maintain permission to ecodash
User timelytree:
  - will lose admin permission to ecodash
  - will lose admin permission to filecoin-plus-falcon
  - will lose push permission to filplus-backend
  - will lose admin permission to filplus-tooling-backend-test
  - will lose admin permission to green.filecoin.io
User timguo-ipfs:
  - will lose triage permission to community
User tippyflitsuk:
  - will lose push permission to filecoin.io
User tjsmck:
  - will lose push permission to ecodash
User tmaciej-neti:
  - will lose push permission to filplus-backend
  - will lose push permission to filplus-registry
User tmytrn:
  - will lose pull permission to slate
User trruckerfling:
  - will have the permission to community change from maintain to push
  - will lose maintain permission to fevm-data-dao-kit
  - will lose admin permission to fvm-pm
  - will lose push permission to fvm-spacewarp
  - will lose push permission to fvm-website
User turinglabsorg:
  - will lose pull permission to lotus-infra-dev
User turuslan:
  - will lose push permission to cpp-filecoin
User uonai:
  - will lose pull permission to slate
User vaniiiii:
  - will lose push permission to filecoin-solidity
User vesahc:
  - will lose admin permission to ecodash
  - will lose pull permission to filecoin-retrieval-market-website
  - will lose push permission to filecoin-solidity
  - will lose push permission to filecoin.io
  - will lose admin permission to green.filecoin.io
  - will lose admin permission to hackathons-forestry-legacy
  - will lose admin permission to orbit.filecoin.io
User vnessasgrt:
  - will lose push permission to community
  - will lose push permission to devgrants
User vojimirovich:
  - will lose push permission to system-test-matrix
User vonum:
  - will lose push permission to filecoin-solidity
User vukolic:
  - will lose maintain permission to tla-f3
User vvkio:
  - will lose admin permission to hackathons-forestry-legacy
User web3-bot:
  - will lose push permission to builtin-actors
User wer1st:
  - will lose push permission to cpp-filecoin
User wertikalk:
  - will lose push permission to filecoin-solidity
User whiteflamingo:
  - will lose pull permission to fvm-pm
User whyrusleeping:
  - will lose push permission to builtin-actors
  - will lose push permission to dagstore
  - will lose push permission to dealbot
  - will lose push permission to ff-bounties
  - will lose push permission to ffi-stub
  - will lose push permission to filecoin-explorer
  - will lose push permission to fvm-test-vectors
  - will lose push permission to go-bitfield
  - will lose push permission to go-commp-utils
  - will lose push permission to go-data-segment
  - will lose push permission to go-data-transfer
  - will lose push permission to go-ds-versioning
  - will lose push permission to go-fil-commcid
  - will lose push permission to go-fil-commp-hashhash
  - will lose push permission to go-fil-markets
  - will lose push permission to go-state-types
  - will lose push permission to go-statemachine
  - will lose push permission to lotus
  - will lose push permission to lotus-docs
  - will lose push permission to lotus-infra-dev
  - will lose push permission to ref-fvm
  - will lose pull permission to sentinel
  - will lose push permission to sentinel-tick
  - will lose maintain permission to specs
User willscott:
  - will lose admin permission to boost
  - will lose admin permission to data-prep-tools
  - will have the permission to dealbot change from admin to push
  - will lose maintain permission to filecoin-plus-application-json-restructure
  - will lose maintain permission to filecoin-plus-leaderboard-data
  - will lose maintain permission to filecoin-plus-roadmap
  - will lose admin permission to filplus-backend
  - will lose admin permission to filplus-ssa-bot
  - will lose admin permission to filplus-tooling-backend-test
  - will lose triage permission to github-mgmt
  - will lose admin permission to go-legs
  - will have the permission to motion-s3-connector change from admin to maintain
  - will lose push permission to retrieval-market-spec
  - will lose pull permission to sentinel
User wjmelements:
  - will lose push permission to filecoin-pin
  - will lose push permission to filoz-infra
User xbalbinus:
  - will lose push permission to fvm-pm
User xinaxu:
  - will lose admin permission to motion-s3-connector
  - will lose push permission to motion-sp-test
User xmcai2016:
  - will lose push permission to notary-governance
User xors-eng:
  - will lose push permission to fvm-pm
User yiannisbot:
  - will lose triage permission to filecoin.io
  - will lose push permission to fips
  - will lose pull permission to sentinel
  - will lose admin permission to specs
User zamith:
  - will lose push permission to filecoin-datasets-discovery-ui
User zenground0:
  - will lose admin permission to bellperson
  - will lose admin permission to bls-signatures
  - will lose admin permission to blstrs
  - will lose maintain permission to dealbot
  - will lose admin permission to ec-gpu
  - will lose admin permission to fil-rustacuda
  - will lose push permission to filecoin-explorer
  - will lose admin permission to filecoin-phase2
  - will lose maintain permission to go-legs
  - will have the permission to lotus-infra-dev change from admin to maintain
  - will lose admin permission to merkletree
  - will lose admin permission to powersoftau
  - will lose admin permission to rust-fil-logger
  - will lose admin permission to rust-fil-proofs
  - will lose admin permission to rust-filecoin-proofs-api
  - will lose admin permission to rust-gpu-tools
  - will lose admin permission to specs
  - will lose admin permission to taupipp
User zepedroresende:
  - will lose push permission to filecoin-datasets-discovery-ui
User zixuanzh:
  - will lose push permission to filecoin-explorer
  - will lose push permission to fips
  - will lose pull permission to sentinel
  - will lose maintain permission to specs
User zorlin:
  - will lose push permission to sp-automation
User zuiris:
  - will lose admin permission to cpp-filecoin

[galargh]

@BigLep We could convert Alumni team members to external collaborators. The new members added in this PR haven't been active in 12 months. Where activity is defined as follows - https://github.com/filecoin-project/github-mgmt/blob/master/scripts/src/actions/remove-inactive-members.ts#L25

[github-actions]

Before merge, verify that all the following plans are correct. They will be applied as-is after the merge.

Terraform plans

Terraform plans are too long to post as a comment. Please inspect Plan > Comment > Show terraform plans instead.

[BigLep]

A few things coming to mind here:

1. Can "outside collaborators" be managed in github-mgmt so we can do that under source control?

2. I don't think we can just blindly convert the current Alumni team to outside collaborators because the act of converting to "outside collaborator" will cause them to be removed from all teams and any private repos. I would want to make sure that anyone we convert to "outside collaborator" actually isn't part of any teams or private repos of consequence.

   • It would be awesome if github-mgmt would have a check for when converting to outside collaborator that it would share the change of permission that will happen (or that it requires in the PR also removw them from team and private repos in order for the CI check to pass).

3. If we are to go with this approach that you have right now, there are definitely some KEEPs I'll need to add in before we merge.

4. If we go with this approach, for auditing, it would be really useful to add more to the "access change summary". I also want to see what team changes are being applied. The user focused view is great, but it's harder to reason about without also knowing the team changes. For example, I would want to see something like:

User Smith:
  - will lose maintain permission to awesome-repo because of removal from team X
  - will lose maintain permission to cool-repo because of direct repo removal

OR

User Smith:
  - will lose member permission to team builders
  - will lose maintain permission to awesome-repo

5. I wonder if an area of lower-hanging fruit is to go through all members.member and look to see who hasn't had any PR/issue/discussion creation/commenting in the last X months. As an approximination, if these queries come up empty, someone should become an external collaborator:

• https://github.com/search?q=org%3Afilecoin-project+updated%3A%3E2024-09-19+biglep&type=issues&ref=advsearch
• https://github.com/search?q=org%3Afilecoin-project+updated%3A%3E2024-09-19+biglep&type=pullrequests&ref=advsearch
• https://github.com/search?q=org%3Afilecoin-project+updated%3A%3E2024-09-19+biglep&type=discussions&ref=advsearch

[BigLep]

it would be really useful to add more to the "access change summary". I also want to see what team changes are being applied.

For cross linking, this idea was brought up in ipdxco/github-as-code#113

[galargh]

1. Can "outside collaborators" be managed in github-mgmt so we can do that under source control?

To some extent, yes. There is no notion of conversion from member to outside collaborator in github-mgmt. We could definitely script it (there is no such thing in the provider). The missing piece is - "on membership destroy, create all missing direct collaboration links".

Also, when a member is already an outside collaborator (or was converted to one through UI), they can be managed through github-mgmt just fine.

2. I don't think we can just blindly convert the current Alumni team to outside collaborators because the act of converting to "outside collaborator" will cause them to be removed from all teams and any private repos. I would want to make sure that anyone we convert to "outside collaborator" actually isn't part of any teams or private repos of consequence.

The invariant that should hold is if someone's in the Alumni team, then they are not in any other team and they are not direct collaborators of any repositories.

3. If we are to go with this approach that you have right now, there are definitely some KEEPs I'll need to add in before we merge.

I just want to clarify, by putting together this PR, my intention was to see which users haven't been "active" in the org in the past 12 months (those removed from any other repositories/teams and moved to the Alumni team by the cleanup script).

If we wanted to carry on with the cleanup, then, as you mentioned, we should definitely clean up this PR because it certainly was a little too eager. One thing that is pretty obviously wrong is that it moved some bot accounts to the Alumni team. That's because they don't have any activity that the script looks for.

4. If we go with this approach, for auditing, it would be really useful to add more to the "access change summary". I also want to see what team changes are being applied. The user focused view is great, but it's harder to reason about without also knowing the team changes.

Thank you for creating an issue for this 🙇 I think that's a really good idea.

5. I wonder if an area of lower-hanging fruit is to go through all members.member and look to see who hasn't had any PR/issue/discussion creation/commenting in the last X months. As an approximination, if these queries come up empty, someone should become an external collaborator:

So that's exactly what being moved to the Alumni team means. That's why I mentioned these users might be good candidates for turning into outside collaborators. As well as the current members of the Alumni team.

[rvagg]

A bunch of these look like some kind of cleanup or dedupe, not removing active members? are diffs creating changes or reflecting an existing reality or just deduping individuals who already have access as a team, e.g. this one snadrus should be in Curio team which has admin?

This is good, but it does make it slightly harder to review. No strong opinion on whether it should be split off to a separate PR, just noting this fact.

[rvagg]

Well as I read more, I'm not really sure what I would be reviewing by looking at this! So yes, a change summary of "X will lose access to Y" would certainly help.

[galargh]

It was indeed never intended for any review and this PR will be closed without being merged - it was only supposed to serve as a suggestion for which users might be up for turning into outside collaborators.

[BigLep]

Thanks @galargh. I've been thinking about your responses and about how outside collaborators work.

The invariant that should hold is if someone's in the Alumni team, then they are not in any other team and they are not direct collaborators of any repositories.

I like this invariant. The problem I see though is that in order to be part of an organization team like filecoin-project/Alumni, you need to be a member of the organization, not an outside collaborator. ("Outside collaborators cannot be added to a team, team membership is restricted to members of the organization.")

I agree that the users that are identified as inactive from https://github.com/filecoin-project/github-mgmt/blob/master/scripts/src/actions/remove-inactive-members.ts are good candidates to make outside collaborators. When they are made outside collaborators, they lose private repo and filecoin-project team access. It would be ideal to see what that translates to for each user, but in practice, if they haven't been active in any way for over a year, I think we're fine to blindly make them outside collaborators and let them lose the corresponding permissions. They can always be readded if needed.

So it seems like the sequence of events is:

1. Get a list of usernames that we want to make outside collaborats. This is a combination of users that are already Alumni and that get flagged by remove-inactive-members.t, with some exceptions like bots.
2. Pass that list of usernames to a script which converts them to outside collaborators using PUT /orgs/{org}/outside_collaborators/{username}. (I'd ideally like to do that in a PR given this is a destructive action but it could just be done in an issue where we get a couple of people to check the list and sign off.)
3. Run github-mgmt sync to pull in the reduced 1) members.member list 2) private repo acces and 3) fileocin-project team memberships

Does that seem right?

I assume with Claude I can create the script easily, but if this is something you have thoughts around @galargh and want to take, that is great too. I would also want to document this process for the future. I can at least handle the documentation part if the approach seems right.

[galargh]

I like this invariant. The problem I see though is that in order to be part of an organization team like filecoin-project/Alumni, you need to be a member of the organization, not an outside collaborator. ("Outside collaborators cannot be added to a team, team membership is restricted to members of the organization.")

Yes, that's correct. I was only trying to suggest that the users who are now in the Alumni team would not loose any access if you were to turn them into outside collaborators. In fact, for them, turning into outside collaborators and outright removing them from an organization should really be equivalent.

I agree that the users that are identified as inactive from https://github.com/filecoin-project/github-mgmt/blob/master/scripts/src/actions/remove-inactive-members.ts are good candidates to make outside collaborators. When they are made outside collaborators, they lose private repo and filecoin-project team access. It would be ideal to see what that translates to for each user, but in practice, if they haven't been active in any way for over a year, I think we're fine to blindly make them outside collaborators and let them lose the corresponding permissions. They can always be readded if needed.

Exactly! That's why I thought putting this together could be helpful to you in the short term.

So it seems like the sequence of events is:

Get a list of usernames that we want to make outside collaborats. This is a combination of users that are already Alumni and that get flagged by remove-inactive-members.t, with some exceptions like bots.
Pass that list of usernames to a script which converts them to outside collaborators using PUT /orgs/{org}/outside_collaborators/{username}. (I'd ideally like to do that in a PR given this is a destructive action but it could just be done in an issue where we get a couple of people to check the list and sign off.)
Run github-mgmt sync to pull in the reduced 1) members.member list 2) private repo acces and 3) fileocin-project team memberships

Does that seem right?

Yeah, that sounds about right. However, I would definitely advise a human step between getting a list of usernames and calling the API.

I assume with Claude I can create the script easily, but if this is something you have thoughts around @galargh and want to take, that is great too. I would also want to document this process for the future. I can at least handle the documentation part if the approach seems right.

Nothing off the top of my head, but maybe something could come up in the process of making it. I can create it for you or you can have a go, just let me know :)