docs: add request for maintainership md file

[charleenfei]

Description

As the Cosmos ecosystem has expanded and flourished, it has become increasingly apparent that along with ecosystem growth, there has been the growth of great development teams working on IBC applications and features. We recognise that having these applications in the ibc-go repo can be valuable for ease of discoverability, "officialness", and of course assurance of seamless performance as updates to the repo continue to be pushed by our team and collaborators.

We've spent a lot of time working on processes to handle inbound requests for maintaining important IBC applications which may be valuable for the entire Interchain ecosystem but developed outside of our engineering team. This document seeks to articulate this process (as well as our our own internal process of developing any new feature).

---

Before we can merge this PR, please make sure that all the following items have been
checked off. If any of the checklist items are not applicable, please leave them but
write a little note why.

• Targeted PR against correct branch (see CONTRIBUTING.md)
• Linked to Github issue with discussion and accepted design OR link to spec that describes this work.
• Code follows the module structure standards.
• Wrote unit and integration tests
• Updated relevant documentation (docs/) or specification (x/<module>/spec/)
• Added relevant godoc comments.
• Added a relevant changelog entry to the Unreleased section in CHANGELOG.md
• Re-reviewed Files changed in the Github PR explorer
• Review Codecov Report in the comment section below once CI passes

[colin-axner]

Thanks @charleenfei :) Left some initial thoughts. Very open to differing opinions

[colin-axner]

One question about the image, if there isn't an ICS spec, there should be right? Or is it supposed to imply an ICS spec won't always be necessary?

[charleenfei]

some cases (specified in the spec section below) will not require an ics spec -- we can update the image to add the spec process as a dotted box perhaps to suggest it's not always necessary

[colin-axner]

"Is there an ICS spec?" I think can be "Is an ICS spec required?" ?

[colin-axner]

Thanks @charleenfei :) Everything looks good to me. We can always make modifications as we try this process out

[colin-axner]

"Is there an ICS spec?" I think can be "Is an ICS spec required?" ?

[chatton]

Content looks great, I left a few small suggestions and some tiny nits! Great work 🥇!

[chatton]

should we include an email address for the specification team as we need for product?

[charleenfei]

good question. @AdityaSripal do you have a preference here?

[chatton]

Suggested change

	Once the spec has been given initial approval, `ibc-go` engineering will coordinate a code walkthrough in preparation for taking the module into the repo. Any requested changes from the `ibc-go` engineering team after the code walkthrough should be discussed and/or addressd in a timely manner.
	Once the spec has been given initial approval, `ibc-go` engineering will coordinate a code walkthrough in preparation for taking the module into the repo. Any requested changes from the `ibc-go` engineering team after the code walkthrough should be discussed and/or addressed in a timely manner.

[chatton]

[nit] we are using walkthrough and walk through, we should use one to stay consistent.
[mega-nit] we should keep punctuation consistent (missing full stop)

[chatton]

Maybe we can link to the E2E Readme here

[chatton]

Suggested change

	Please indicate the expected contribution of your team maintainership, if any. This contribution should also include ideas about devrels support and support for product on social media
	Please indicate the expected contribution of your team maintainership, if any. This contribution should also include ideas about devrels support and support for product on social media.

[damiannolan]

🙏

[crodriguezvega]

Thank you, @charleenfei. I just left a couple of nits.

[crodriguezvega]

In the rest of the docs in the repo we write ibc-go in normal text.

Suggested change

	This document details the acceptance process for requests from external contributors who require for the `ibc-go` core team to take over **maintainership** of a complex block of code (ie: an application module or a light client implementation). It is the process we also follow internally for features that we develop which will go into the `ibc-go` codebase.
	This document details the acceptance process for requests from external contributors who require for the ibc-go core team to take over **maintainership** of a complex block of code (ie: an application module or a light client implementation). It is the process we also follow internally for features that we develop which will go into the `ibc-go` codebase.

[crodriguezvega]

I would just write this in normal text as an unordered list.