2020-05-16 06:59:59 +02:00
|
|
|
|
2015-07-15 15:26:51 +02:00
|
|
|
# Contributions
|
|
|
|
|
2016-10-28 16:38:09 +02:00
|
|
|
## Helping out
|
2015-07-15 15:26:51 +02:00
|
|
|
|
2016-10-28 16:38:09 +02:00
|
|
|
### Run the latest version from GitHub
|
|
|
|
Run the tool in debug mode (use lynis audit system --profile developer.prf) and see if it shows any error.
|
2015-07-15 15:26:51 +02:00
|
|
|
|
2016-10-28 16:38:09 +02:00
|
|
|
### Report bugs
|
2020-05-16 06:59:59 +02:00
|
|
|
Create a GitHub issue on the issue tracker.
|
2015-07-15 15:26:51 +02:00
|
|
|
|
2016-10-28 16:38:09 +02:00
|
|
|
### Suggest changes (pull request)
|
|
|
|
When you find something that can be improved, fork the project and create a pull request.
|
2015-07-15 15:26:51 +02:00
|
|
|
|
2016-10-28 16:38:09 +02:00
|
|
|
### Translations
|
2020-05-16 06:59:59 +02:00
|
|
|
See the db/languages directory.
|
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'.
|
2015-09-06 21:38:56 +02:00
|
|
|
* Check the log information (lynis.log) of your new test or changed code, so that it provides helpful details for others.
|
2016-05-02 17:12:19 +02:00
|
|
|
|
2016-10-28 16:38:09 +02:00
|
|
|
|
2016-05-02 17:12:19 +02:00
|
|
|
## Code Guidelines
|
|
|
|
|
|
|
|
### General
|
2020-11-09 05:16:47 +01:00
|
|
|
Indentation should be 4 spaces (no tab character).
|
2016-05-02 17:12:19 +02:00
|
|
|
|
|
|
|
### Comments
|
|
|
|
Comments: use # sign followed by a space. When needed, create a comment block.
|
2020-05-16 06:59:59 +02:00
|
|
|
Blank lines: allowed, one line maximum.
|
2016-05-02 17:12:19 +02:00
|
|
|
|
|
|
|
### Functions
|
|
|
|
All functions use CamelCase to clearly show a difference between shell built-in commands, or external commands.
|
|
|
|
|
|
|
|
### Variables
|
2020-05-16 06:59:59 +02:00
|
|
|
Variables should be capitalized, with underscore as word separator (e.g. PROCESS_EXISTS=1).
|
2016-10-28 16:38:09 +02:00
|
|
|
|
|
|
|
|
|
|
|
## Pull Requests
|
|
|
|
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).
|
|
|
|
|
|
|
|
By submitting a [Pull Request](https://help.github.com/articles/using-pull-requests/)
|
|
|
|
to this repository, you agree that you:
|
|
|
|
|
|
|
|
1. Own the contribution that you are providing or have obtained permission from
|
|
|
|
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
|
|
|
|
|
2020-05-16 06:59:59 +02:00
|
|
|
If you have questions regarding development, send us an e-mail at [lynis-dev](mailto:lynis-dev@cisofy.com).
|
2016-10-28 16:38:09 +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
|
2020-11-09 05:52:56 +01:00
|
|
|
this notation in your pull request. Preferred format: Full Name, and your e-mail
|
2016-10-28 16:38:09 +02:00
|
|
|
address).
|
|
|
|
|