2015-07-15 15:26:51 +02:00
|
|
|
# Contributions
|
|
|
|
|
|
|
|
## Pull Requests
|
2015-09-06 17:54:18 +02:00
|
|
|
We welcome any contribution to improve Lynis. Contributions to the Lynis project can
|
|
|
|
be submitted as a pull request. The upstream project can be found in our [GitHub repository](https://github.com/CISOfy/lynis).
|
2015-07-15 15:26:51 +02:00
|
|
|
|
|
|
|
By submitting a [Pull Request](https://help.github.com/articles/using-pull-requests/)
|
|
|
|
to this repository, you agree that you:
|
|
|
|
|
2015-07-15 20:02:15 +02:00
|
|
|
1. Own the contribution that you are providing or have obtained permission from
|
2015-07-15 15:26:51 +02:00
|
|
|
the contribution owner
|
|
|
|
|
|
|
|
2. Allow your contribution to be licensed under the license of the target
|
|
|
|
project (GPLv3)
|
|
|
|
|
|
|
|
3. Allow your contribution to be freely distributed to the Lynis community
|
|
|
|
|
|
|
|
4. Allow the project the [Unlimited Rights](#Unlimited-Rights) to your contribution
|
|
|
|
|
2015-09-06 17:54:18 +02:00
|
|
|
If you have questions regarding development, send us an e-mail at [lynis-dev](mailto:lynis-dev@cisofy.com)
|
2015-07-15 15:26:51 +02:00
|
|
|
|
|
|
|
## Unlimited Rights
|
|
|
|
Our project is licensed under GPLv3. By providing a contribution to the project, it
|
|
|
|
will be used for the purpose of the project. Unlimited rights includes the rights to
|
|
|
|
use, modify, reproduce, release, perform, display, or disclose computer software or
|
|
|
|
computer software documentation in whole or in part, in any manner and for any
|
|
|
|
purpose whatsoever, and to have or authorize others to do so.
|
|
|
|
|
|
|
|
If you want to be named in as a contributor in the CONTRIBUTOR file, then include
|
2015-07-15 20:02:15 +02:00
|
|
|
this notition in your pull request. Preferred format: Full Name, with optional the
|
|
|
|
company name and/or your e-mail address).
|
2015-07-15 15:26:51 +02:00
|
|
|
|
2015-09-06 17:54:18 +02:00
|
|
|
## Developer Guidelines
|
|
|
|
|
|
|
|
To ensure all pull requests can be easily checked and merged, here are some tips:
|
|
|
|
* Your code should work on other platforms running the bourne shell (/bin/sh), not just BASH.
|
|
|
|
* Properly document your code where needed. Besides the 'what', focus on explaining the 'why'.
|
|
|
|
* Check the log information (lynis.log) of your new test or changed code, so that it provides helpful details for others.
|