Core Internet Stack Components

• CometBFT
• Cosmos SDK
• CosmJS
• CosmWasm
• ibc-go
• Hermes
• Wasmd
• Go Relayer | |

• @jonathanpberger to spike ~1-2hrs on a Rails version
• @olliegilbey to spike ~1-2 hrs on a rust CLI or python version

We believe the Interchain dev community
has a problem tracking dependencies across projects
and we can solve it w/ a Information Radiator showing the status of epics across the Core Dev repos
We'll know we're right if time-we're-blocked-by-external-teams goes down
And we'll know we're right if foreign PRs go up (bc it's easy to see where it'll be quicker just to patch a blocker yrself)

As ToT
We want CosmosSDK epics to come through to the IPW board
Because it's our Proof-of-concept

When the cron runs
Then all the CosmosSDK epics get added to IPW
And status should come through
And it should be idempotent

Todo

• pull a "story type: Epic" story from Cosmos SDK into memory
• push Epic into IPW Epics On The Interchain
• sync Status field of foreign stories from a single repo (Cosmos SDK)
• do it all for a 2nd (3rd, 4th, etc) repo
• pull all Epics from Cosmos SDK into IPW Epics On The Interchain
• make it a cron job

How To

Pull story status from CosmosSDK

• brew install gh-cli
• gh auth login
• gh project list --owner cosmos --limit 11 (need explicit limit or get a pagination error from the API)

// Pull epics from foreign project
gh project item-list 26 --owner cosmos --format json -q '.items[] | select(.["story Type"] == "👑 Epic") | {title: .title, status: .status, storyType: .["story Type"], url: .content.url}'

// add single epic to IPW
gh project item-add 3 --owner interchainio --url https://github.com/cosmos/cosmos-sdk/issues/9958

assign "👑 Epic" status to Issue Story Type field in IPW

// get Issue ID
gh project item-list 3 --owner interchainio --limit 200 --format json | jq -r '.items[] | select(.content.url == "cosmos/cosmos-sdk#9958") | .id' # PVTI_lADOAsuzxc4AkKP5zgQ9Oxg

// get IPW Story Type field id

➜  dot-rot git:(master) ✗ gh project field-list --owner interchainio
? Which project would you like to use? Interchain Public Works (#3)
NAME                  DATA TYPE                   ID
Title                 ProjectV2Field              PVTF_lADOAsuzxc4AkKP5zgcaQn0
Assignees             ProjectV2Field              PVTF_lADOAsuzxc4AkKP5zgcaQn4
Status                ProjectV2SingleSelectField  PVTSSF_lADOAsuzxc4AkKP5zgcaQn8
Labels                ProjectV2Field              PVTF_lADOAsuzxc4AkKP5zgcaQoA
Linked pull requests  ProjectV2Field              PVTF_lADOAsuzxc4AkKP5zgcaQoE
Milestone             ProjectV2Field              PVTF_lADOAsuzxc4AkKP5zgcaQoI
Repository            ProjectV2Field              PVTF_lADOAsuzxc4AkKP5zgcaQoM
Reviewers             ProjectV2Field              PVTF_lADOAsuzxc4AkKP5zgcaQoc
Story Type            ProjectV2SingleSelectField  PVTSSF_lADOAsuzxc4AkKP5zgcaQoo

// get the project id

➜  dot-rot git:(master) ✗ gh project list --owner interchainio
NUMBER  TITLE                    STATE  ID
3       Interchain Public Works  open   PVT_kwDOAsuzxc4AkKP5

// get the IPW field value:

 dot-rot git:(master) ✗ gh project field-list 3 --owner interchainio --format json -q ".fields[]" | jq -r '. | select(.name == "Story Type").id'

PVTSSF_lADOAsuzxc4AkKP5zgcaQoo

// get the id of the single-select via --format json --single-select-option-id string

 dot-rot git:(master) ✗ gh project field-list 3 --owner interchainio --format json -q ".fields[]" | jq -r '. | select(.name == "Story Type").options[] | select(.name == "👑 Epic").id'

282f80fd

// assign "👑 Epic" status to Issue Story Type field in IPW

gh project item-edit --project-id PVT_kwDOAsuzxc4AkKP5 --id PVTI_lADOAsuzxc4AkKP5zgQ9Oxg --field-id PVTSSF_lADOAsuzxc4AkKP5zgcaQoo --single-select-option-id string 282f80fd

THIS SEEMS TO HAVE WORKED!!

➜  dot-rot git:(master) ✗ gh project field-list 3 --owner interchainio --format json -q ".fields[]" | jq -r '. | select(.name == "Story Type").id'

PVTSSF_lADOAsuzxc4AkKP5zgcaQoo
➜  dot-rot git:(master) ✗ gh project field-list 3 --owner interchainio --format json -q ".fields[]" | jq -r '. | select(.name == "Story Type").options[] | "\(.name): \(.id)"'

⭐️ User story: 9c507ef2
🐞 Bug: 9b62bd3f
⚙️ Chore: 5b9ce27f
👑 Epic: 282f80fd
🏁 Release Marker: bd1610fc
➜  dot-rot git:(master) ✗ gh project item-edit --project-id PVT_kwDOAsuzxc4AkKP5 --id PVTI_lADOAsuzxc4AkKP5zgQ9Oxg --field-id PVTSSF_lADOAsuzxc4AkKP5zgcaQoo --single-select-option-id 282f80fd

Edited item "EPIC: Separate x/auth and vesting"
➜  dot-rot git:(master) ✗

Tasks

• get Ollie to create public interchain/interchain_public_works repo https://github.com/interchainio/interchain_public_works
• move this ticket to IPW and add Nico and Ollie
• create interchainio/interchain_public_works gh project
• #3
• ⚡️ articulate what "backlog interop" means (blog post?): story types, statuses, board automation, etc
• make projects (see list below) Backlog-Interop compliant
• #12
• socialize it (PHEELblog)
• put out a call to ToT: who's in next?
• create Backlog Interop Wiki

Projects to onboard to Backlog Interop

• Cosmos-SDK
• IBC-wasm
• cosmos/IBC-apps
• strangelove-ventures/horcrux
• strangelove-ventures/interchaintest,
• abstract.money
• some informal?
• some IG?
• some other ToT?

Interchain Stack Components

pilots

• #5 Interchain Test
• #6 Spawn CLI
• Cosmos Kit

secondary priority

• comet bft docs
• cosmjs docs
• cosmos docs
• cosmwasm docs
• ibc docs
• Chain Registry
• npm Module
• CometBFT DB
• Telescope
• Ignite CLI
• Academy
• ibc-rs
• Starship |
• Utilities |
• TS Codegen
• cw-multi-test |
• Client |
• Create Cosmos App |
• Interchain UI | |
• Rust Crate |
• TS Relayer | |

• clean up spawn backlog
• import into IPW

• add a workflow action to auto-add Interchain stories (just epics?) to the IPW Project

## Todo
- [ ] figure out the minimum number of seats needed for now
- [ ] upgrade the plan

As Interchain
We need to upgrade the Interchainio GH plan
Bc we need privs to auto-add stories from all major repos

When I go to https://github.com/orgs/interchainio/projects/3/workflows
Then I should be able to create an "Auto Add" workflow for at least one auto-add workflow for each major Cosmos repo, about ~28 repos at current count

As the Interchain community
We want a Canonical Source of Truth to memorialize any Decisions, Plans, Hypotheses, Experiments, Explorations or Learnings
Because as a community, we need institutional memory and
Because it makes onboarding easier

When I go to the blog (<https://interchainio.github.io/interchain_public_works_pheelblog>?)
Then I should see our PHEELblog