---
# System prepended metadata

title: Repo Management Proposal From IG

---

# Repo Management Proposal From IG

### Problem

- ibc-go is agnostic with respect to apps/light clients. Thus there is no default app/light client when importing ibc
- This is good for as a protocol, but for the ecosystem, each app/light client must convince chains to add them into the chain binary
- We want to provide a default wiring for chains to adopt to bootstrap the IBC app and light client ecosystem

### Proposed Solution

- ibc-go team maintains a canonical app.go file that will wire all recommended apps and light clients.
- This allows apps/light clients to exist in whichever repos they want and managed by whomever they want. All IBC chains can use them by default by simply following the recommended app.go from the ibc-go team
- ibc-go team DOES NOT want to be the ultimate authority on what goes into this recommended file and what does not as this is inherently political. Instead this authority will ultimately reside with the TAB, though it is expected that they rely on product and technical expertise from the core teams when making the decision.
- Coordination of product between the core IBC teams is a key piece here, since the coordinating body can decide on which apps/light clients get recommended on the TAB's behalf.
- If the TAB (or product council) needs technical input from a team (e.g. audit) this should be requested along with an expected delivery time, the core team in question can plan into their work and bill the audit to TAB separately.