Reduce org owners/admins

[BigLep]

Summary

This aligns with the "reduce org owners" step listed in ipfs/ipfs#511.

This is the first step of wider 2024Q1 permissions cleanup.

Why do you need this?

Github org safety. See ipfs/ipfs#511 for more info.

Timeline

• 2024-02-12: public PR
• 2024-02-12: notify affected parties:
• 2024-02-14: merge this change assuming no major pushback

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]

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

Terraform plans

ipfs-examples

Terraform used the selected providers to generate the following execution
plan. Resource actions are indicated with the following symbols:
  ~ update in-place

Terraform will perform the following actions:

  # github_membership.this["aschmahmann"] will be updated in-place
  ~ resource "github_membership" "this" {
        id       = "ipfs-examples:aschmahmann"
      ~ role     = "admin" -> "member"
        # (2 unchanged attributes hidden)
    }

  # github_membership.this["autonome"] will be updated in-place
  ~ resource "github_membership" "this" {
        id       = "ipfs-examples:autonome"
      ~ role     = "admin" -> "member"
        # (2 unchanged attributes hidden)
    }

  # github_membership.this["biglep"] will be updated in-place
  ~ resource "github_membership" "this" {
        id       = "ipfs-examples:BigLep"
      ~ role     = "admin" -> "member"
        # (2 unchanged attributes hidden)
    }

  # github_membership.this["sgtpooki"] will be updated in-place
  ~ resource "github_membership" "this" {
        id       = "ipfs-examples:SgtPooki"
      ~ role     = "admin" -> "member"
        # (2 unchanged attributes hidden)
    }

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

[achingbrain]

Should we just retire this org and move the examples to the main IPFS org?

The js-libp2p equivalent to helia examples lives in the main libp2p org and so far it's co-existence has been drama-free.

[BigLep]

Should we just retire this org and move the examples to the main IPFS org?

Good point @achingbrain . It looks like all the repos within the org are Helia or js-ipfs related.

I assume there was some initial reasons why ipfs-examples was created to begin with and that those conditions aren't holding true anymore?

I don't know who else you need to pull into the conversation and whether it's worth doing now.

Let me know how I can support.

[galargh]

I assume there was some initial reasons why ipfs-examples was created to begin with and that those conditions aren't holding true anymore?

I don't know who else you need to pull into the conversation and whether it's worth doing now.

Let me know how I can support.

I think @2color might be able to weigh in on this.

[2color]

I would suggest we move these examples to the main ipfs org and do away with all the synched fork-and-go repos and just have a single monorepo.

@achingbrain wdyt?

[BigLep]

I'll merge this for now since it isn't doing any harm. I'll leave it to shipyard team to decide/schedule when to do the work of deprecating the ipfs-examples org. I created a tracking item here: #31