Skip to content

Conversation

@2color
Copy link
Member

@2color 2color commented Dec 16, 2025

Summary

I have started as an advocate with the IPFS foundation and will be active again.

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

@2color 2color requested a review from a team as a code owner December 16, 2025 20:08
@github-actions
Copy link
Contributor

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

Access Changes
User 2color:
  - will have the permission to community change from triage to maintain
  - will have the permission to in-web-browsers change from pull to push
  - will have the permission to ipfs change from pull to triage
  - will have the permission to js-kubo-rpc-client change from pull to push
  - will have the permission to kubo change from pull to push
  - will have the permission to roadmap change from pull to push
  - will gain push permission to 2019.ipfs.camp
  - will gain push permission to aegir
  - will gain push permission to benchmarks
  - will gain push permission to boxo
  - will gain push permission to camp
  - will gain push permission to distributions
  - will gain push permission to eslint-config-ipfs
  - will gain push permission to fs-repo-migrations
  - will gain push permission to go-bitfield
  - will gain push permission to go-block-format
  - will gain push permission to go-bs-sqlite3
  - will gain push permission to go-cid
  - will gain push permission to go-cidutil
  - will gain push permission to go-datastore
  - will gain push permission to go-detect-race
  - will gain push permission to go-dnslink
  - will gain push permission to go-ds-badger
  - will gain push permission to go-ds-crdt
  - will gain push permission to go-ds-flatfs
  - will gain push permission to go-ds-leveldb
  - will gain push permission to go-ds-measure
  - will gain push permission to go-ds-redis
  - will gain push permission to go-ds-s3
  - will gain push permission to go-ds-sql
  - will gain push permission to go-ds-swift
  - will gain push permission to go-fs-lock
  - will gain push permission to go-graphsync
  - will gain push permission to go-ipfs-archived
  - will gain push permission to go-ipfs-blocksutil
  - will gain push permission to go-ipfs-cmds
  - will gain push permission to go-ipfs-delay
  - will gain push permission to go-ipfs-example-plugin
  - will gain push permission to go-ipfs-pq
  - will gain push permission to go-ipld-cbor
  - will gain push permission to go-ipld-eth-import
  - will gain push permission to go-ipld-format
  - will gain push permission to go-ipld-git
  - will gain push permission to go-ipld-legacy
  - will gain push permission to go-ipld-zcash
  - will gain push permission to go-libipfs-rapide
  - will gain push permission to go-log
  - will gain push permission to go-merkledag
  - will gain push permission to go-metrics-interface
  - will gain push permission to go-metrics-prometheus
  - will gain push permission to go-peertaskqueue
  - will gain pull permission to go-qringbuf
  - will gain push permission to go-todocounter
  - will gain push permission to go-unixfsnode
  - will gain push permission to hang-fds
  - will gain push permission to helia
  - will gain push permission to helia-cli
  - will gain push permission to helia-delegated-routing-v1-http-api
  - will gain push permission to helia-verified-fetch
  - will gain pull permission to ipfs-companion
  - will gain push permission to ipfs-desktop
  - will gain push permission to ipfs-ds-postgres
  - will gain admin permission to ipfs-gui
  - will gain push permission to ipfs-update
  - will gain push permission to ipfs-webui
  - will gain push permission to ipget
  - will gain push permission to ipld-explorer-components
  - will gain push permission to iptb
  - will gain push permission to iptb-plugins
  - will gain push permission to js-dag-service
  - will gain push permission to js-datastore-pubsub
  - will gain push permission to js-fs-pull-blob-store
  - will gain pull permission to js-hamt-sharding
  - will gain push permission to js-idb-pull-blob-store
  - will gain push permission to js-ipfs-bitswap
  - will gain push permission to js-ipfs-merkle-dag
  - will gain push permission to js-ipfs-repo
  - will gain push permission to js-ipfs-unixfs
  - will gain push permission to js-ipfs-utils
  - will gain push permission to js-ipfsd-ctl
  - will gain push permission to js-ipns
  - will gain push permission to js-level-pull-blob-store
  - will gain push permission to protons
  - will gain push permission to public-gateway-checker
  - will gain push permission to specs

@github-actions
Copy link
Contributor

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

Terraform plans

ipfs

Terraform used the selected providers to generate the following execution
plan. Resource actions are indicated with the following symbols:
  + create

Terraform will perform the following actions:

  # github_team_membership.this["community:2color"] will be created
  + resource "github_team_membership" "this" {
      + etag     = (known after apply)
      + id       = (known after apply)
      + role     = "maintainer"
      + team_id  = "5082620"
      + username = "2color"
    }

  # github_team_membership.this["repos - go:2color"] will be created
  + resource "github_team_membership" "this" {
      + etag     = (known after apply)
      + id       = (known after apply)
      + role     = "member"
      + team_id  = "3232508"
      + username = "2color"
    }

  # github_team_membership.this["repos - javascript:2color"] will be created
  + resource "github_team_membership" "this" {
      + etag     = (known after apply)
      + id       = (known after apply)
      + role     = "member"
      + team_id  = "1433120"
      + username = "2color"
    }

  # github_team_membership.this["wg gui/ux:2color"] will be created
  + resource "github_team_membership" "this" {
      + etag     = (known after apply)
      + id       = (known after apply)
      + role     = "member"
      + team_id  = "2825335"
      + username = "2color"
    }

Plan: 4 to add, 0 to change, 0 to destroy.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant