Maintainer's handbook

[svrnm]

How to promote people to approvers, and eventually, maintainer

• Best practices!
• What to look for
• What not to do
  • Be clear about expectations around PRs, issues…
  • Give feedback when you say no
• How to ask for help
• What docs to have about this in each repository

How to distribute this, so that individual SIGs can customize their sections?

Maintainer responsibilities

• “Day in the life of a maintainer”
• It's not just about being able to write quality code
• You are responsible for the health of your SIG

Resources available (internships, machines, help from other SIGs, …)

“what do I need to know?”

How to determine what's a good balance?

Which resources can we share with them?

• Books?
• Presentations?

[codefromthecrypt]

package naming guidance makes sense here, too

[svrnm]

https://github.com/open-telemetry/community/pull/2051 -- @austinlparker already created this initial proposal before the SIG was started, please take a look