We do not have clear owners or well-defined processes or structures for a lot of important aspects of the Interledger project and community. This makes it hard for newcomers to figure out how to contribute and means that some key pieces of the project are not being properly maintained.
I would propose that we come up with some processes or structures for governing and maintaining:
- Protocol specs (Interledger RFCs repo)
- Hyperledger Quilt (Java implementation)
- Interledger.rs (Rust implementation)
- Community events and calls
A couple of specific problems I would highlight are:
- Without a clear process for proposing new protocols or updating old ones, some Pull Requests go for weeks or months without comment. Also, a few people (probably including @adrianhopebailie, @sharafian, @justmoon, and myself) seem to have an unofficial veto over protocol changes. This may or may not be desirable but either way it should be made explicit
- No one is responsible for Interledger.org and so the documentation is and stays out of date
- We don’t have real moderation guidelines for this forum
- Interledger.js doesn’t have clear maintainers
Each aspect of the project could probably use definition of:
- Who the maintainers are
- What the rights and obligations of the maintainers are
- A schedule for check-ins with the maintainers to see how things are going
- Some dispute resolution guidelines
- A roadmap
- A guide for contributing
What do you think? Ideas, suggestions, or interest in volunteering for a maintainer team?
PS For anyone that hasn’t read this essay before, I would highly recommend reading The Tyranny of Structurelessness.