As part of a sweeping effort I am doing to reduce outdated package count, begin regularly enforcing maintainership file inclusion in old(er) repos, and increase the likelihood of a package having a maintainer (should it be required, outside of those being handled by Core Team and Global Maintainers), this task is being created to effectively "notify" the current maintainer of the package that it needs to be updated and ensure it is regularly maintained. In the event there is no specific maintainer, either one may be specified that has regularly updated it in the past, or this task shall also be considered an RFC for a new maintainer.
During the update process, the `MAINTAINERS.md` file should be included if it is not already, and have the following content (replace `REPLACEME` with the correct value):
This file is used to indicate responsibility for the maintenance of this package. Individuals on this list should be the sole modifiers of the package, excluding cases where the Solus Team may need to perform necessary rebuilds, upgrades, or security fixes. This list should not be used for any direct contact usage. If you believe this package requires a package update, follow documentation from https://getsol.us/articles/packaging/request-a-package-update/en/. In the event this package no longer becomes sufficiently maintained, Core Team reserves the right to request a new maintainer or remove this package from the repository.
- REPLACEME FIRST NAME(S) LAST NAME(S)
- IRC: REPLACEME
- Email: REPLACEME
Unless the updating of the package is being blocked by other items in the stack, 30 days shall be provided to update the package. Should the package not see an update by either the maintainer or an individual volunteering to become the maintainer, Core Team reserves the right to remove it from the repository. Please note that simply volunteering for maintainership without providing a patch is not an accepted "solution" to resolving this task or preventing deprecation.