maintenance tiers

Not all projects are treated equal. Some are in active development, others are finished, others are deprecated, etc.

The purpose of this page is to show what does each tier mean. Some projects may not adhere to the descriptions here, any deviation from this page should be documented in the project itself.

active development

Recommendation: feel free to use the project.

• The project is not finished yet and new features will arrive in the future.
• The response time to issues and pull requests is good.
• New features are welcome after some public discussion.

finished

Recommendation: feel free to use the project.

• The project serves its purpose and does not need any more features.
• The response time to issues and pull requests is good, but those related to new features may be rejected.
• Any unexpected behaviour will be fixed by myself (unless a pull request is sent by someone else).

low maintenance

Recommendation: feel free to use the project.

• The project serves its purpose and does not need any more features, but its relevance has decreased.
• The response time to issues and pull requests can be worse.
  • Pull requests related to new features will be rejected.
• I will not work on any non-security issues, but will review and merge pull requests.
• Anyone can become a maintainer after contacting me.

deprecated

Recommendation: switch to an alternative or start maintaining your own fork.

• The project is not actively maintained anymore.
• I will not work on any issues, but I will review and merge pull requests related to security issues.
• Feel free to maintain your own fork.

decommissioned/archived

Recommendation: switch to an alternative or start maintaining your own fork as soon as possible.

• The project is not maintained at all.
• I will not work on any issues.
• Pull requests will not be reviewed nor merged.
• Feel free to maintain your own fork.