Documentation Guide

Here you can find information about how we organize, maintain and create the documentation of syslog-ng.

How to contribute to the documentation

If you do not already have a GitHub account, create one.
Fork the repository on GitHub (preferably, from the master branch)
Create a branch that will store your contribution, for example, git checkout -b my-typo-fixes
Find the part of the source that you want to modify. The easiest thing is to search for a specific text using grep, regexxer, or a similar tool.
If you modify a file in the _includes/doc/ directory, it is probably included to multiple parts of the documentation. Make sure that your changes make sense in each context.
Modify the files as you need (following our markup conventions). For example, you can add new examples, correct typos, and so on.
Validate the files to make sure that the markdown is well-formed.
Commit and sign off your changes. If your changes apply only to syslog-ng OSE, begin the commit message with the ose prefix. If the changes apply only to specific versions, indicate them in the tag, for example, ose 3.35
Push your changes, for example, git push origin my-typo-fixes
Submit a pull request.
Sign the syslog-ng Open Source Edition Documentation Contributor License Agreement when prompted.
We will review your contribution and if accepted, integrate to the master branch of the documentation and publish it.