diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 5119ad366100a9..aba4dbe91b7ca5 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -27,6 +27,9 @@ Such forks require heavy patching, maintenance and hours of build time. Software need to be used in version announced by authors as ready to use by the general public - usually called releases. Betas, arbitrary VCS revisions, templates using tip of development branch taken at build time and releases created by the package maintainer won't be accepted. +Software should have an established and mature release history. New projects or those with an excessively frequent release cadence are not good candidates for system packages. + +Packages should be submitted by someone other than the developer of the software, though exceptions can be made for established contributors if the software meets other requirements. ## Creating, updating, and modifying packages in Void by yourself @@ -73,6 +76,9 @@ Templates must have the name `void-packages/srcpkgs//template`, where ` For deeper insights on the contents of template files, please read the [manual](./Manual.md), and be sure to browse the existing template files in the `srcpkgs` directory of this repository for concrete examples. +To ensure packages stay maintained, we prefer that they are submitted by those with a history of contributions to existing packages. +A good way to do this is to work on orphaned packages (those maintained by `orphan@voidlinux.org`) that you use. + ### Updating a template At minimum, a template update will consist of changing `version` and `checksum`, if there was an upstream version change, and/or `revision`, if a template-specific change (e.g. patch, correction, etc.) is needed.