Under the new governance, we've facilitated one new Maintainer nomination/appointment so far (@domdomegg). This PR adds some rough guidelines as to the process folks can follow to nominate new maintainers.

Motivation and Context

Without these guidelines, it is unclear how to actually put forward and process a nomination. The alternative is to basically DM David and ask him to explain the desired process :)

The intent here is to provide an easy, well-paved way for folks to push forward nominations and expand Maintainer capacity. It does not introduce any new bureaucracy.

How Has This Been Tested?

npm run serve:docs:

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Documentation update

Checklist

• I have read the MCP Documentation
• My code follows the repository's style guidelines
• New and existing tests pass locally
• I have added appropriate error handling
• I have added or updated documentation as needed

Additional context

Don't feel strongly on the wording and content if anyone wants to suggest changes; feel free to nitpick.