Learn from other communities

[Widdershin]

For example, the rackt community has an excellent set of principles. If you haven't read it, I highly recommend it.

I think we have a different goal as a community, more centered around collaboration and creativity, but maintenance and ownership are definitely things to consider.

Does anyone else know of similar documents we can absorb and discuss?

[SteveALee]

I agree the Rackt principles are good - but not all inclusive.

• A very mature set of guidelines is The Apache way.
• here's one of our articles about how to contribute to a OSS project
• Mozilla's community guidelines
• there are plenty of 'code of conduct' style guides eg twitter's

[TylorS]

A big :+1: For this converstion

I like the rackt set of principles. Its easy to read and makes sense. I think we could touch it up to make it a little less intense and more friendly though

[Widdershin]

Another excellent set of pricinciples from Homebrew: https://github.com/Homebrew/brew/blob/master/docs/Maintainers-Avoiding-Burnout.md

I've been thinking a lot about the maintainer role recently.

How can we avoid maintainer burnout? How can we attract and upskill new maintainers? All ideas and feedback welcome.