Maintaining something others use.
WHAT TO PROVIDE
A clear description of what it does and does not do A licence Setup and usage documentation Contribution guidance A code of conduct
WHAT CONTRIBUTION GUIDANCE SHOULD STATE
How to set up the project Conventions expected How to propose a change What will and will not be accepted
WHY THAT LAST POINT
It prevents wasted effort and awkward rejections.
WHAT TO AUTOMATE
Checks on contributions, so review addresses substance.
WHAT TO EXPECT
Many more issues than contributions Requests for features you do not want Users depending on behaviour you considered incidental
WHAT TO DECIDE EARLY
The scope, and defend it.
WHY
Projects fail by accumulating everything anyone asked for.
WHAT TO COMMUNICATE
Your capacity, honestly.
WHAT TO AVOID
Silence on issues and proposals Committing to support you cannot provide
WHAT TO PLAN FOR
Not maintaining it forever: additional maintainers, or a clear statement that it is unmaintained.
