This guideline aim to avoid stopping the project by human bottlenecks.

For an overview and usage instructions, please visit https://maintenance-guidelines-for-organization.github.io

You might have seen the deprecated message like "This project is no longer maintained". You can fork the project, but you can not publish the pacakge to registry like npm with the same name. Because, you have not the ownership of the project.

To share ownership of the project, make you and original maintainer better. The ownership is that access to the repository and access to the registry.

In popular library, no longer maintained project is increased. Because, most popular library has plugin system that structure a ecosystem. As a result, number of project is increased and stopped project is also incresed.

To share ownership of the ecosystem, the library should have an organization.

This guideline show procedures for adding packages, adding new member to the oranization.

Related lesson:

• Share ownership of your project
• The Pull Request Hack - Felix Geisendörfer

Please feel free to submit pull requests or open issues to improve this project.

Translation and Pull Request welcome!

For more details, see CONTRIBUTING.md

This Guideline is available under Creative Commons Attribution 4.0 International Public License(CC BY 4.0).

This guideline is based on browserify/admin and Contributor Covenant.