# Strangelove as IBC Repository Maintainer Coordinator **URL:** \ **Category:** Hub Proposals\ **Created:** [March 4, 2023, 5:23am UTC](https://forum.cosmos.network/t/strangelove-as-ibc-repository-maintainer-coordinator/10044 "2023-03-04T05:23:49Z")\ **Posts on this page:** 1\ **Showing post:** 2
**Author:** ![jacobgadikian](https://yyz1.discourse-cdn.com/flex031/user_avatar/forum.cosmos.network/jacobgadikian/32/6994_2.png) [@jacobgadikian](https://forum.cosmos.network/u/jacobgadikian)\ **Post date:** [March 4, 2023, 12:18pm UTC](https://forum.cosmos.network/t/strangelove-as-ibc-repository-maintainer-coordinator/10044/2 "2023-03-04T12:18:42Z")
Hey so I just wanted to add a little detail to this, here is where I first discussed this concept: > [@Use governance for software development processes](https://forum.cosmos.network/t/use-governance-for-software-development-processes/9877): > > Hi slight_smile So this is a thought on software development processes, and governance, and where they intersect. Github is currently a hard dependency, more or less Github permissioning limits the decentralization of this work Permissioning could be related to VotePower of validators or to a governance proposal Imagine a governance proposal to determine the contents of this file: How could we make it such that Gaia chooses her own maintainers? gov props that choose CODEOWNERS all val… I think that it is very important that: Repositories be grouped by function like: - No one uses IAVL, ledger-cosmos-go, and cosmos-db without the SDK, therefore put all of them in the SDK - No one uses cometbft-db without cometbft, therefore put cometbft-db in cometbft - The vast majority of IBC enabled chains built using the cosmos SDK will want packet forward middleware, ICQ, and WASM clients, therefore those tools should go directly into the IBC go repository **Benefits of this approach** - Faster onboarding - This approach saves time and money because developers are not needing to visit many different repositories in order to do their work and they don’t need to know where those repositories are because everything is where they need it. - Easier maintenance - In all of the cases mentioned above, maintenance is made much faster by removing the separate software components and placing them into the larger repository so that they can be maintained and tested alongside it. - Better integration testing - Historically one of the areas where we are weak is software integration testing. When more of the components are in the same repository it is much easier to use the continuous integration system to run tests both on them and between them. This leads to better security. --- _[View the full topic](https://forum.cosmos.network/t/strangelove-as-ibc-repository-maintainer-coordinator/10044)._