Limiting team/repository access for users inactive for 60 months

[galargh]

Summary

This PR cleans up user access by removing users who have been inactive for over 60 months (5 years) from teams and repositories.

A user is deemed inactive if they haven't performed any of the following actions in the past 60 months in a repository in question or in any of the repositories the team in question grants access to:

• created an issue or a pull request
• commented on an issue or a pull request
• reviewed a pull request
• commented on a commit
• pushed (in particular, force pushed) to a branch
• created a branch
• deleted a branch
• merged a pull request
• added a pull request to a merge queue

Any user who, after the introduction of the above changes, isn't a direct collaborator in any of the repositories and isn't a member of any teams is assigned to the Alumni team.

If a user's access to a repository or team should be restored, the appropriate line change should be reverted, and a comment starting with KEEP: (followed by a reason) should be added directly above that line.

This pertains to the "'archive' inactive users and teams" in https://github.com/ipfs/ipfs/issues/511.

Who is this targeting?

The current PR is what results from a script to identify inactive users in an org.

Why is this being done?

See "Why do we care about periodically cleaning up permissions across the orgs?" in https://github.com/ipfs/ipfs/issues/511

Is this set in stone?

No. This PR was created and being left open for some days to give awareness and incorporate feedback. We're not taking a "ask for permission" approach, as that would require way too much wrangling. Instead, we're giving visibility to what's proposed and inviting folks to comment and influence. A saving grace here is that none of this is a "one-way door". If something got messed up or missed, a follow-up PR can be done to correct it.

Is anyone being removed from the organization?

No. All existing members of the org are staying members. In the most reduced/scoped-down case, someone will still be part of an "Alumni" team in the org to signal their past involvement. Thank you for your past contributions, and we certainly welcome you to play a more active role in the future.

Timeline

2024-02-26: public PR 2024-03-04: notify affected parties with @mention: 2024-03-08: merge this change after incorporating feedback 2024-03-08: clean up empty teams and past IPFS Camp teams

[github-actions[bot]]

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

Access Changes

``` User 1015bit: - will lose triage permission to camp User 2color: - will lose admin permission to areweinterplanetaryyet.org - will lose admin permission to ipfs-camp-2022 User AdamStone: - will lose triage permission to community - will lose push permission to devgrants - will lose pull permission to distributed-wikipedia-mirror - will lose pull permission to go-dag-store - will lose pull permission to in-web-browsers - will lose pull permission to ipfs - will lose pull permission to js-kubo-rpc-client - will lose pull permission to kubo - will lose pull permission to roadmap User BrendanBenshoof: - will lose triage permission to community - will lose push permission to devgrants - will lose pull permission to distributed-wikipedia-mirror - will lose pull permission to go-dag-store - will lose pull permission to in-web-browsers - will lose pull permission to ipfs - will lose pull permission to js-kubo-rpc-client - will lose pull permission to kubo - will lose pull permission to roadmap User DrCatman: - will lose triage permission to camp User JGAntunes: - will lose triage permission to community - will lose push permission to devgrants - will lose pull permission to distributed-wikipedia-mirror - will lose pull permission to go-dag-store - will lose pull permission to in-web-browsers - will lose pull permission to ipfs - will lose pull permission to js-kubo-rpc-client - will lose pull permission to kubo - will lose pull permission to roadmap User JonKrone: - will lose triage permission to community - will lose push permission to devgrants - will lose pull permission to distributed-wikipedia-mirror - will lose pull permission to go-dag-store - will lose pull permission to in-web-browsers - will lose pull permission to ipfs - will lose pull permission to js-kubo-rpc-client - will lose pull permission to kubo - will lose pull permission to roadmap User Kubuxu: - will lose admin permission to go-bitswap-priv - will lose admin permission to gomod - will have the permission to hang-fds change from admin to push User MAkcanca: - will lose triage permission to camp User NeoTeo: - will lose triage permission to community - will lose push permission to devgrants - will lose pull permission to distributed-wikipedia-mirror - will lose pull permission to go-dag-store - will lose pull permission to in-web-browsers - will lose pull permission to ipfs - will lose pull permission to js-kubo-rpc-client - will lose pull permission to kubo - will lose pull permission to roadmap User Robmat05: - will lose triage permission to community - will lose push permission to devgrants - will lose pull permission to distributed-wikipedia-mirror - will lose pull permission to go-dag-store - will lose pull permission to in-web-browsers - will lose pull permission to ipfs - will lose pull permission to js-kubo-rpc-client - will lose pull permission to kubo - will lose pull permission to roadmap User ShishKabab: - will lose triage permission to camp User SidHarder: - will lose triage permission to community - will lose push permission to devgrants - will lose pull permission to distributed-wikipedia-mirror - will lose pull permission to go-dag-store - will lose pull permission to in-web-browsers - will lose pull permission to ipfs - will lose pull permission to js-kubo-rpc-client - will lose pull permission to kubo - will lose pull permission to roadmap User abn: - will lose triage permission to camp User adlrocha: - will lose push permission to aegir - will lose push permission to benchmarks - will lose push permission to eslint-config-ipfs - will lose push permission to go-bitswap-priv - will lose push permission to helia - will lose push permission to helia-cli - will lose push permission to helia-delegated-routing-v1-http-api - will lose push permission to helia-verified-fetch - will have the permission to in-web-browsers change from push to pull - will lose push permission to iptb - will lose push permission to js-dag-service - will lose push permission to js-datastore-pubsub - will lose push permission to js-fs-pull-blob-store - will lose pull permission to js-hamt-sharding - will lose push permission to js-idb-pull-blob-store - will lose push permission to js-ipfs-bitswap - will lose push permission to js-ipfs-merkle-dag - will lose push permission to js-ipfs-repo - will lose push permission to js-ipfs-unixfs - will lose push permission to js-ipfs-utils - will lose push permission to js-ipfsd-ctl - will lose push permission to js-ipns - will lose push permission to js-level-pull-blob-store - will lose push permission to protons - will lose pull permission to public-gateway-checker User akru: - will lose triage permission to camp User akrych: - will lose push permission to 2019.ipfs.camp - will lose push permission to community - will lose push permission to devgrants - will lose pull permission to distributed-wikipedia-mirror - will lose pull permission to go-dag-store - will lose pull permission to in-web-browsers - will lose pull permission to ipfs - will lose pull permission to ipfs-companion - will lose push permission to ipfs-desktop - will lose admin permission to ipfs-gui - will lose push permission to ipfs-webui - will lose push permission to ipld-explorer-components - will lose pull permission to js-kubo-rpc-client - will lose pull permission to kubo - will lose push permission to public-gateway-checker - will lose pull permission to roadmap User alekswn: - will lose triage permission to camp User angiemaguire: - will lose push permission to camp - will lose triage permission to community - will lose push permission to devgrants - will lose pull permission to distributed-wikipedia-mirror - will lose pull permission to go-dag-store - will lose pull permission to in-web-browsers - will lose pull permission to ipfs - will lose pull permission to js-kubo-rpc-client - will lose pull permission to kubo - will lose pull permission to roadmap User apronkin: - will lose triage permission to camp User arcalinea: - will lose push permission to go-ipld-zcash User arsstone: - will lose triage permission to camp User asutula: - will lose push permission to js-dag-service User balupton: - will lose triage permission to camp User cleichner: - will lose triage permission to community - will lose push permission to devgrants - will lose pull permission to distributed-wikipedia-mirror - will lose pull permission to go-dag-store - will lose pull permission to in-web-browsers - will lose pull permission to ipfs - will lose pull permission to js-kubo-rpc-client - will lose pull permission to kubo - will lose pull permission to roadmap User cmk: - will lose triage permission to camp User cwaring: - will lose admin permission to 2022.ipfs.camp User cyborgshead: - will lose triage permission to camp User damedoteth: - will lose maintain permission to ecosystem-directory User dankelleher: - will lose triage permission to camp User darkdh: - will lose triage permission to camp User davidar: - will lose push permission to apps User daviddias: - will lose maintain permission to ecosystem-directory - will lose admin permission to go-bitswap-priv - will lose push permission to ipfs-blog - will lose maintain permission to ipfs-website User dborzov: - will lose triage permission to camp User dchoi27: - will lose push permission to aegir - will lose push permission to benchmarks - will lose maintain permission to boxo - will lose push permission to distributions - will lose push permission to eslint-config-ipfs - will lose push permission to fs-repo-migrations - will lose push permission to go-bitfield - will lose push permission to go-block-format - will lose push permission to go-bs-sqlite3 - will lose push permission to go-cid - will lose push permission to go-cidutil - will lose push permission to go-datastore - will lose push permission to go-detect-race - will lose push permission to go-dnslink - will lose push permission to go-ds-badger - will lose push permission to go-ds-badger2 - will lose push permission to go-ds-crdt - will lose push permission to go-ds-flatfs - will lose push permission to go-ds-leveldb - will lose push permission to go-ds-measure - will lose push permission to go-ds-redis - will lose push permission to go-ds-s3 - will lose push permission to go-ds-sql - will lose push permission to go-ds-swift - will lose push permission to go-fs-lock - will lose push permission to go-graphsync - will lose push permission to go-ipfs-archived - will lose push permission to go-ipfs-blocksutil - will lose push permission to go-ipfs-cmds - will lose push permission to go-ipfs-delay - will lose push permission to go-ipfs-example-plugin - will lose push permission to go-ipfs-pq - will lose push permission to go-ipld-cbor - will lose push permission to go-ipld-eth-import - will lose push permission to go-ipld-format - will lose push permission to go-ipld-git - will lose push permission to go-ipld-legacy - will lose push permission to go-ipld-zcash - will lose push permission to go-libipfs-rapide - will lose push permission to go-log - will lose push permission to go-merkledag - will lose push permission to go-metrics-interface - will lose push permission to go-metrics-prometheus - will lose push permission to go-peertaskqueue - will lose pull permission to go-qringbuf - will lose push permission to go-todocounter - will lose push permission to go-unixfsnode - will lose push permission to hang-fds - will lose push permission to helia - will lose push permission to helia-cli - will lose push permission to helia-delegated-routing-v1-http-api - will lose push permission to helia-verified-fetch - will have the permission to in-web-browsers change from push to pull - will lose push permission to ipfs-ds-convert - will lose push permission to ipfs-ds-postgres - will lose push permission to ipfs-update - will lose push permission to ipget - will lose push permission to iptb - will lose push permission to iptb-plugins - will lose push permission to js-dag-service - will lose push permission to js-datastore-pubsub - will lose push permission to js-fs-pull-blob-store - will lose pull permission to js-hamt-sharding - will lose push permission to js-idb-pull-blob-store - will lose push permission to js-ipfs-bitswap - will lose push permission to js-ipfs-merkle-dag - will lose push permission to js-ipfs-repo - will lose push permission to js-ipfs-unixfs - will lose push permission to js-ipfs-utils - will lose push permission to js-ipfsd-ctl - will lose push permission to js-ipns - will have the permission to js-kubo-rpc-client change from push to pull - will lose push permission to js-level-pull-blob-store - will have the permission to kubo change from push to pull - will lose push permission to protons - will lose pull permission to public-gateway-checker - will lose push permission to specs User deltazxm: - will lose triage permission to camp User dignifiedquire: - will lose admin permission to awesome-ipfs - will lose triage permission to camp - will lose admin permission to js-fs-pull-blob-store - will lose admin permission to js-idb-pull-blob-store - will lose admin permission to js-ipfs-merkle-dag User dongtianyi: - will lose triage permission to camp User dryajov: - will lose triage permission to community - will lose push permission to devgrants - will lose pull permission to distributed-wikipedia-mirror - will lose pull permission to go-dag-store - will lose pull permission to in-web-browsers - will lose pull permission to ipfs - will lose pull permission to js-kubo-rpc-client - will lose pull permission to kubo - will lose pull permission to roadmap User elijaharita: - will lose push permission to go-graphsync User emerick: - will lose triage permission to camp User eminence: - will lose push permission to newsletter User ericronne: - will lose triage permission to camp - will lose push permission to specs User eshon: - will lose triage permission to camp User fbaiodias: - will lose triage permission to community - will lose push permission to devgrants - will lose pull permission to distributed-wikipedia-mirror - will lose pull permission to go-dag-store - will lose pull permission to in-web-browsers - will lose pull permission to ipfs - will lose pull permission to js-kubo-rpc-client - will lose pull permission to kubo - will lose pull permission to roadmap User flyingzumwalt: - will lose admin permission to artwork - will lose triage permission to community - will lose push permission to devgrants - will lose pull permission to distributed-wikipedia-mirror - will lose pull permission to go-dag-store - will lose pull permission to in-web-browsers - will lose pull permission to ipfs - will lose pull permission to js-kubo-rpc-client - will lose pull permission to kubo - will lose pull permission to roadmap User gavinmcdermott: - will lose triage permission to community - will lose push permission to devgrants - will lose pull permission to distributed-wikipedia-mirror - will lose pull permission to go-dag-store - will lose pull permission to in-web-browsers - will lose pull permission to ipfs - will lose pull permission to js-kubo-rpc-client - will lose pull permission to kubo - will lose pull permission to roadmap User gfanton: - will lose triage permission to camp User gmasgras: - will lose push permission to benchmarks - will lose pull permission to go-ipfs-priv - will lose push permission to public-gateway-checker User guillemcordoba: - will lose triage permission to camp User guseggert: - will lose admin permission to go-ipfs-priv User haadcode: - will lose triage permission to community - will lose push permission to devgrants - will lose pull permission to distributed-wikipedia-mirror - will lose pull permission to go-dag-store - will lose pull permission to in-web-browsers - will lose pull permission to ipfs - will lose pull permission to js-kubo-rpc-client - will lose pull permission to kubo - will lose pull permission to roadmap User hannahhoward: - will have the permission to go-dag-store change from admin to pull - will lose admin permission to go-data-transfer-bus - will lose admin permission to stargate User harlantwood: - will lose triage permission to community - will lose push permission to devgrants - will lose pull permission to distributed-wikipedia-mirror - will lose pull permission to go-dag-store - will lose pull permission to in-web-browsers - will lose pull permission to ipfs - will lose pull permission to js-kubo-rpc-client - will lose pull permission to kubo - will lose pull permission to roadmap User hosh: - will lose triage permission to community - will lose push permission to devgrants - will lose pull permission to distributed-wikipedia-mirror - will lose pull permission to go-dag-store - will lose pull permission to in-web-browsers - will lose pull permission to ipfs - will lose pull permission to js-kubo-rpc-client - will lose pull permission to kubo - will lose pull permission to roadmap User hugomrdias: - will lose maintain permission to ecosystem-directory - will lose push permission to ipfs-blog - will lose maintain permission to ipfs-website - will lose triage permission to npm-kubo User ipfs-gui-bot: - will lose push permission to distributions - will lose push permission to in-web-browsers - will lose push permission to ipfs-companion - will lose push permission to ipfs-desktop - will lose push permission to ipfs-gui - will lose push permission to public-gateway-checker User ipfsbot: - will lose push permission to aegir - will lose push permission to awesome-ipfs - will lose push permission to benchmarks - will lose maintain permission to boxo - will lose push permission to distributions - will lose push permission to eslint-config-ipfs - will lose push permission to fs-repo-migrations - will lose push permission to go-bitfield - will lose push permission to go-block-format - will lose push permission to go-bs-sqlite3 - will lose push permission to go-cid - will lose push permission to go-cidutil - will lose push permission to go-datastore - will lose push permission to go-detect-race - will lose push permission to go-dnslink - will lose push permission to go-ds-badger - will lose push permission to go-ds-badger2 - will lose push permission to go-ds-crdt - will lose maintain permission to go-ds-dynamodb - will lose push permission to go-ds-flatfs - will lose push permission to go-ds-leveldb - will lose push permission to go-ds-measure - will lose push permission to go-ds-redis - will lose push permission to go-ds-s3 - will lose push permission to go-ds-sql - will lose push permission to go-ds-swift - will lose push permission to go-fs-lock - will lose push permission to go-graphsync - will lose push permission to go-ipfs-archived - will lose push permission to go-ipfs-blocksutil - will lose push permission to go-ipfs-cmds - will lose push permission to go-ipfs-delay - will lose push permission to go-ipfs-example-plugin - will lose push permission to go-ipfs-pq - will lose push permission to go-ipld-cbor - will lose push permission to go-ipld-eth-import - will lose push permission to go-ipld-format - will lose push permission to go-ipld-git - will lose push permission to go-ipld-legacy - will lose push permission to go-ipld-zcash - will lose push permission to go-libipfs-rapide - will lose push permission to go-log - will lose push permission to go-merkledag - will lose push permission to go-metrics-interface - will lose push permission to go-metrics-prometheus - will lose push permission to go-peertaskqueue - will lose pull permission to go-qringbuf - will lose push permission to go-todocounter - will lose push permission to go-unixfsnode - will lose push permission to hang-fds - will lose push permission to helia - will lose push permission to helia-cli - will lose push permission to helia-delegated-routing-v1-http-api - will lose push permission to helia-verified-fetch - will lose push permission to in-web-browsers - will lose push permission to ipfs-docs - will lose push permission to ipfs-ds-convert - will lose push permission to ipfs-ds-postgres - will lose push permission to ipfs-update - will lose push permission to ipfs-webui - will lose push permission to ipget - will lose push permission to iptb - will lose push permission to iptb-plugins - will lose push permission to js-dag-service - will lose push permission to js-datastore-pubsub - will lose push permission to js-fs-pull-blob-store - will lose pull permission to js-hamt-sharding - will lose push permission to js-idb-pull-blob-store - will lose push permission to js-ipfs-bitswap - will lose push permission to js-ipfs-merkle-dag - will lose push permission to js-ipfs-repo - will lose push permission to js-ipfs-unixfs - will lose push permission to js-ipfs-utils - will lose push permission to js-ipfsd-ctl - will lose push permission to js-ipns - will lose push permission to js-kubo-rpc-client - will lose push permission to js-level-pull-blob-store - will lose push permission to kubo - will lose push permission to protons - will lose pull permission to public-gateway-checker - will lose push permission to specs User jacobheun: - will lose maintain permission to ecosystem-directory - will lose push permission to ipfs-blog - will lose maintain permission to ipfs-website User jamiejn: - will lose push permission to camp User jbenet: - will lose push permission to benchmarks - will lose push permission to helia - will lose push permission to helia-cli - will lose push permission to helia-delegated-routing-v1-http-api - will lose push permission to helia-verified-fetch - will lose push permission to js-dag-service - will lose push permission to js-datastore-pubsub - will have the permission to js-ipfs-utils change from push to pull User jsoares: - will lose triage permission to community - will lose push permission to devgrants - will lose pull permission to distributed-wikipedia-mirror - will lose pull permission to go-dag-store - will lose pull permission to in-web-browsers - will lose pull permission to ipfs - will lose pull permission to js-kubo-rpc-client - will lose pull permission to kubo - will lose pull permission to roadmap User juliaxbow: - will lose triage permission to ipfs-gui User kinu: - will lose triage permission to camp User krl: - will lose triage permission to community - will lose push permission to devgrants - will lose pull permission to distributed-wikipedia-mirror - will lose pull permission to go-dag-store - will lose pull permission to in-web-browsers - will lose pull permission to ipfs - will lose pull permission to js-kubo-rpc-client - will lose pull permission to kubo - will lose pull permission to roadmap User kumavis: - will lose push permission to aegir - will lose push permission to benchmarks - will lose push permission to eslint-config-ipfs - will lose push permission to helia - will lose push permission to helia-cli - will lose push permission to helia-delegated-routing-v1-http-api - will lose push permission to helia-verified-fetch - will lose push permission to in-web-browsers - will lose push permission to iptb - will lose push permission to js-dag-service - will lose push permission to js-datastore-pubsub - will lose push permission to js-fs-pull-blob-store - will lose pull permission to js-hamt-sharding - will lose push permission to js-idb-pull-blob-store - will lose push permission to js-ipfs-bitswap - will lose push permission to js-ipfs-merkle-dag - will lose push permission to js-ipfs-repo - will lose push permission to js-ipfs-unixfs - will lose push permission to js-ipfs-utils - will lose push permission to js-ipfsd-ctl - will lose push permission to js-ipns - will lose push permission to js-level-pull-blob-store - will lose push permission to protons - will lose pull permission to public-gateway-checker User lidel: - will have the permission to go-ipfs-priv change from admin to pull User litzenberger: - will lose triage permission to community - will lose push permission to devgrants - will lose pull permission to distributed-wikipedia-mirror - will lose pull permission to go-dag-store - will lose pull permission to in-web-browsers - will lose pull permission to ipfs - will lose pull permission to js-kubo-rpc-client - will lose pull permission to kubo - will lose pull permission to roadmap User locotorp: - will lose push permission to awesome-ipfs - will lose maintain permission to go-ds-dynamodb - will lose pull permission to go-ds-sql - will lose push permission to ipfs-docs - will lose pull permission to js-hamt-sharding - will lose pull permission to public-gateway-checker User ma82: - will lose triage permission to camp User magik6k: - will lose push permission to aegir - will lose push permission to benchmarks - will lose triage permission to camp - will lose push permission to eslint-config-ipfs - will lose admin permission to go-bitswap-priv - will lose admin permission to go-ds-bitcask - will have the permission to go-ds-swift change from admin to push - will lose push permission to helia - will lose push permission to helia-cli - will lose push permission to helia-delegated-routing-v1-http-api - will lose push permission to helia-verified-fetch - will have the permission to in-web-browsers change from push to pull - will lose push permission to js-dag-service - will have the permission to js-datastore-pubsub change from push to pull - will lose push permission to js-fs-pull-blob-store - will lose pull permission to js-hamt-sharding - will lose push permission to js-idb-pull-blob-store - will lose push permission to js-ipfs-merkle-dag - will lose push permission to js-ipfs-repo - will lose push permission to js-ipfs-unixfs - will lose push permission to js-ipfs-utils - will lose push permission to js-ipfsd-ctl - will lose push permission to js-ipns - will lose push permission to js-level-pull-blob-store - will lose push permission to protons - will lose pull permission to public-gateway-checker User marcooliveira: - will lose triage permission to community - will lose push permission to devgrants - will lose pull permission to distributed-wikipedia-mirror - will lose pull permission to go-dag-store - will lose pull permission to in-web-browsers - will lose pull permission to ipfs - will lose pull permission to js-kubo-rpc-client - will lose pull permission to kubo - will lose pull permission to roadmap User marshall: - will lose push permission to areweinterplanetaryyet.org User mcollina: - will lose triage permission to community - will lose push permission to devgrants - will lose pull permission to distributed-wikipedia-mirror - will lose pull permission to go-dag-store - will lose pull permission to in-web-browsers - will lose pull permission to ipfs - will lose pull permission to js-kubo-rpc-client - will lose pull permission to kubo - will lose pull permission to roadmap User mildred: - will lose triage permission to community - will lose push permission to devgrants - will lose pull permission to distributed-wikipedia-mirror - will lose pull permission to go-dag-store - will lose pull permission to in-web-browsers - will lose pull permission to ipfs - will lose pull permission to js-kubo-rpc-client - will lose pull permission to kubo - will lose pull permission to roadmap User mishmosh: - will have the permission to steering-wg change from admin to pull User moeghashim: - will lose triage permission to camp User momack2: - will lose admin permission to go-ipfs-priv User neogeweb3: - will lose triage permission to camp User nicola: - will lose triage permission to community - will lose push permission to devgrants - will lose pull permission to distributed-wikipedia-mirror - will lose pull permission to go-dag-store - will lose pull permission to in-web-browsers - will lose pull permission to ipfs - will lose pull permission to js-kubo-rpc-client - will lose pull permission to kubo - will lose pull permission to roadmap User nunofmn: - will lose triage permission to community - will lose push permission to devgrants - will lose pull permission to distributed-wikipedia-mirror - will lose pull permission to go-dag-store - will lose pull permission to in-web-browsers - will lose pull permission to ipfs - will lose pull permission to js-kubo-rpc-client - will lose pull permission to kubo - will lose pull permission to roadmap User parkan: - will lose push permission to awesome-ipfs - will have the permission to community change from push to triage User petar: - will lose admin permission to go-ipfs-regression User pooja: - will lose triage permission to camp User ratoshniuk: - will lose triage permission to camp User raulk: - will lose maintain permission to ecosystem-directory - will lose push permission to ipfs-blog - will lose maintain permission to ipfs-website User sanderpick: - will lose push permission to js-dag-service User sericaia: - will lose triage permission to community - will lose push permission to devgrants - will lose pull permission to distributed-wikipedia-mirror - will lose pull permission to go-dag-store - will lose pull permission to in-web-browsers - will lose pull permission to ipfs - will lose pull permission to js-kubo-rpc-client - will lose pull permission to kubo - will lose pull permission to roadmap User smihaylov: - will lose triage permission to camp User stongo: - will lose push permission to benchmarks - will lose push permission to public-gateway-checker User tbenbow: - will lose triage permission to community - will lose push permission to devgrants - will lose pull permission to distributed-wikipedia-mirror - will lose pull permission to go-dag-store - will lose pull permission to in-web-browsers - will lose pull permission to ipfs - will lose pull permission to js-kubo-rpc-client - will lose pull permission to kubo - will lose pull permission to roadmap User teh-f00l: - will lose triage permission to camp User tikagan: - will lose maintain permission to ecosystem-directory User travisperson: - will lose triage permission to community - will lose push permission to devgrants - will lose pull permission to distributed-wikipedia-mirror - will lose pull permission to go-dag-store - will lose pull permission to in-web-browsers - will lose pull permission to ipfs - will lose pull permission to roadmap User vmx: - will lose push permission to go-graphsync User vyzo: - will lose admin permission to go-bitswap-priv User whyrusleeping: - will lose triage permission to camp - will lose admin permission to go-bitswap-priv User yangwao: - will lose triage permission to community - will lose push permission to devgrants - will lose pull permission to distributed-wikipedia-mirror - will lose pull permission to go-dag-store - will lose pull permission to in-web-browsers - will lose pull permission to ipfs - will lose pull permission to js-kubo-rpc-client - will lose pull permission to kubo - will lose pull permission to roadmap User yiannisbot: - will lose push permission to go-bitswap-priv User yunigraham: - will lose triage permission to community - will lose push permission to devgrants - will lose pull permission to distributed-wikipedia-mirror - will lose pull permission to go-dag-store - will lose pull permission to in-web-browsers - will lose pull permission to ipfs - will lose pull permission to js-kubo-rpc-client - will lose pull permission to kubo - will lose pull permission to roadmap User yusefnapora: - will lose triage permission to community - will lose push permission to devgrants - will lose pull permission to distributed-wikipedia-mirror - will lose pull permission to go-dag-store - will lose pull permission to in-web-browsers - will lose pull permission to ipfs - will lose pull permission to js-kubo-rpc-client - will lose pull permission to kubo - will lose pull permission to roadmap User zeckli: - will lose triage permission to camp ```

[github-actions[bot]]

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.

[galargh]

Hi! We're ready to open up the PR for general review 🥳

I'd like to ask you to review the changes affecting you and flag any that should be reverted, are wrong, or need more explanation. You can find the detailed explanation of this PR, the reasoning for introducing the changes and the process itself in the description - https://github.com/ipfs/github-mgmt/pull/193#issue-2153562441

Thank you, and let me know if you have any questions 💁

Tagging all the people whose access changes (https://github.com/ipfs/github-mgmt/pull/193#issuecomment-1963563098) as a result of this PR (no one is being removed from the org):

• [ ] @1015bit
• [ ] @2color
• [ ] @AdamStone
• [ ] @BrendanBenshoof
• [ ] @DrCatman
• [ ] @JGAntunes
• [ ] @JonKrone
• [ ] @Kubuxu
• [ ] @MAkcanca
• [ ] @NeoTeo
• [ ] @Robmat05
• [ ] @ShishKabab
• [ ] @SidHarder
• [ ] @abn
• [ ] @adlrocha
• [ ] @akru
• [ ] @akrych
• [ ] @alekswn
• [ ] @angiemaguire
• [ ] @apronkin
• [ ] @arcalinea
• [ ] @arsstone
• [ ] @asutula
• [ ] @balupton
• [ ] @cleichner
• [ ] @cmk
• [ ] @cwaring
• [ ] @cyborgshead
• [ ] @damedoteth
• [ ] @dankelleher
• [ ] @darkdh
• [ ] @davidar
• [ ] @daviddias
• [ ] @dborzov
• [ ] @dchoi27
• [ ] @deltazxm
• [ ] @dignifiedquire
• [ ] @dongtianyi
• [ ] @dryajov
• [ ] @elijaharita
• [ ] @emerick
• [ ] @eminence
• [ ] @ericronne
• [ ] @eshon
• [ ] @fbaiodias
• [ ] @flyingzumwalt
• [ ] @gavinmcdermott
• [ ] @gfanton
• [ ] @gmasgras
• [ ] @guillemcordoba

1/3

[galargh]

Continuation of https://github.com/ipfs/github-mgmt/pull/193#issuecomment-1977089729

• [ ] @guseggert
• [ ] @haadcode
• [ ] @hannahhoward
• [ ] @harlantwood
• [ ] @hosh
• [ ] @hugomrdias
• [ ] @ipfs-gui-bot
• [ ] @ipfsbot
• [ ] @jacobheun
• [ ] @jamiejn
• [ ] @jbenet
• [ ] @jsoares
• [ ] @juliaxbow
• [ ] @kinu
• [ ] @krl
• [ ] @kumavis
• [ ] @lidel
• [ ] @litzenberger
• [ ] @locotorp
• [ ] @ma82
• [ ] @magik6k
• [ ] @marcooliveira
• [ ] @marshall
• [ ] @mcollina
• [ ] @mildred
• [ ] @mishmosh
• [ ] @moeghashim
• [ ] @momack2
• [ ] @neogeweb3
• [ ] @nicola
• [ ] @nunofmn
• [ ] @parkan
• [ ] @petar
• [ ] @pooja
• [ ] @ratoshniuk
• [ ] @raulk
• [ ] @sanderpick
• [ ] @sericaia
• [ ] @smihaylov
• [ ] @stongo
• [ ] @tbenbow
• [ ] @teh-f00l
• [ ] @tikagan
• [ ] @travisperson
• [ ] @vmx
• [ ] @vyzo
• [ ] @whyrusleeping
• [ ] @yangwao
• [ ] @yiannisbot
• [ ] @yunigraham

2/3

[galargh]

Continuation of https://github.com/ipfs/github-mgmt/pull/193#issuecomment-1977089729

• [ ] @yusefnapora
• [ ] @zeckli

3/3

[vyzo]

Is this for ipfs only? I am still very much involved in libp2p.

[galargh]

Is this for ipfs only? I am still very much involved in libp2p.

For you, as per https://github.com/ipfs/github-mgmt/pull/193#issuecomment-1963563098, this will result in the following change:

User vyzo:
  - will lose admin permission to go-bitswap-priv

[vyzo]

ah, ok. Thanks.

[jsoares]

Understood, no objections from my side. Thanks for the heads-up!

[yangwao]

Nice, will this help prevent recent spam? I've probably contributed to the early days :) Happy being Alumni and if needed I will ask around.