We don't have maintainer documentation

[mfisher87]

521 proposed a maintainer doc, but that would be an addition, not a refactor. This ticket is for the new documentation.

Related: #529 , #573

• How to become a maintainer or triager?
  • Need better text, but something along the lines of be involved in our community and ask if you're interested.
  • Also, if you're interested in helping managing issues with labels and interacting with incoming requests, you can have a "triager" role!
• What is required of maintainers?
  • No time obligation, we understand our ability to commit can fluctuate, but communicate openly.
  • Yes obligation to team culture (e.g. link to Openscapes team culture page, and recorded psychological safety talk)
  • More???
• What processes do maintainers follow beyond regular contributing processes?
  • Labeling. Specifically call out "good first issue"
  • Creating welcoming environment when communicating with contributors (issue / PR / discussion posters).
  • Reviewing and merging.
  • Releasing (documented in contributor guide already, we should move in to the maintainer guide).
• ???

[Sherwin-14]

Hey are we looking at something similar to this https://www.pygmt.org/dev/maintenance.html?

[mfisher87]

That looks amazing. In addition to answering the questions above (I'll add a bit of prose to the issue description), that maintainer guide includes the policy we're considering adopting in #573 , so we could knock both issues down at once here.

[chuckwondo]

That looks amazing. In addition to answering the questions above (I'll add a bit of prose to the issue description), that maintainer guide includes the policy we're considering adopting in #573 , so we could knock both issues down at once here.

They even have a more detailed page regarding Minimum Supported Versions

[mfisher87]

We now have a maintainer doc thanks to @Sherwin-14's amazing work! :tada: