Skip to content

Commit

Permalink
CONTRIBUTING.md: clearly state foreground requirement of runit services
Browse files Browse the repository at this point in the history 
The fact that runit requires services to run in the foreground
was recently mentioned by a Void member, @ahesford, but
a clear statement of this requirement is lacking in the
appropriate section of CONTRIBUTING.md.

Link: TigerVNC/tigervnc#1649 (comment)
  • Loading branch information
@zmudc
zmudc authored Oct 4, 2023
1 parent 65acf9a commit 2e8737d
Showing 1 changed file with 3 additions and 0 deletions.
3 changes: 3 additions & 0 deletions CONTRIBUTING.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -28,6 +28,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.

Components of upstream projects that consist of services that cannot be configured to meet runit's requirement that services run in the foreground will not be accepted.
Exceptions will be made only for critical system services identified by the core Void Team in which case the Void developers will modify the upstream source so the affected services run in the foreground.

## Creating, updating, and modifying packages in Void by yourself

If you really want to get a new package or package update into Void Linux, we recommend you contribute it yourself.
Expand Down

1 comment on commit 2e8737d

@ahesford
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is not a helpful addition. This is akin to saying "we don't accept broken contributions", which should be implicit in any collaborative endeavor.

Please sign in to comment.