Create a semi-automated community-sourced roadmap workflow - Githubissues

consensus-shipyard / ipc

🌳 Spawn multi-level trees of customized, scalable, EVM-compatible networks with IPC. L2++ powered by FVM, Wasm, libp2p, IPFS/IPLD, and CometBFT.

https://ipc.space

Apache License 2.0

41 stars 35 forks source link

Create a semi-automated community-sourced roadmap workflow #1026

Open raulk opened 3 months ago

raulk commented 3 months ago

Adopter teams

Key members from adopter teams are grouped into repo teams that can be @'ed in comments and pull requests, e.g. @fluence-dev-team.
Teams are maintained declaratively through a config file, and changes are applied through a GitHub Actions workflow.

Pinging teams for input

When a feature is tagged with adopter input required, a bot pings all adopter teams for input.
It then tracks when input is delivered and replaces the label with adopter input sourced.
It keeps a comment updated at the top of the discussion thread with input status and creates a summary when all teams have provided their input.

Integration with roadmap board

TBD.