Skip to content

document "how to become a maintainer" and "how to be a good maintainer" #2986

@boneskull

Description

@boneskull

This probably exists in a "project" somewhere, but we need to formalize contribution guidelines, decision-making process, etc. I like what ESLint has done.

UPDATE: I forgot that I already wrote up CONTRIBUTING.md, and I can live with that for now. What we're missing is "how to become a maintainer" and "how to be a good maintainer once you are one", etc.

I'll tackle "governance" in another issue.

Metadata

Metadata

Assignees

No one assigned

    Labels

    area: repository toolingconcerning ease of contributionsemver-patchimplementation requires increase of "patch" version number; "bug fixes"status: accepting prsMocha can use your help with this one!

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions