Deoren Moor
Deoren Moor
## Short version Please setup an experimental branch and a corresponding build script on the main site to allow submitting PRs against that branch which build within a scheduled short...
## Problem The content in the `Statement Types` section is a near duplicate of what is now in the `source/configuration/conf_formats.rst` file. Either it needs to be updated to match the...
The intention is to provide a set of guidelines to be used when creating new documentation or refreshing older content. ## Task list - [ ] module doc formatting (use...
This came up in a recent conversation with @rgerhards. As we go about pruning the older obsolete format content from the documentation it is important that we have a cross-reference...
Since the Adiscon package was updated to match what CentOS 7 has, we should update the `imjournal` doc to remove that statement or mention somewhere that the official Adiscon package...
@rgerhards The discussion on rsyslog/rsyslog#2367 brought up an interesting quandry: 1. The current project philosophy is to touch the legacy codebase as little as possible (presumably to reduce effort spent...
See rsyslog/rsyslog#2418 for details. The mailinglist threads linked from that entry are good source material. Currently there is some coverage of rsyslog history in the docs. Perhaps this belongs there...
While working on some module docs recently I noted that the header level syntax was inconsistent between at least two of them. If two, then likely more. ## Task list...
Example change: ```diff -see our** `troubleshooting guide `_ **to get started.** +see our** :doc:`troubleshooting guide ` **to get started.** ```
1. Create a doc of removed modules 1. Note when each module was last in the source tree Examples: rsyslog/rsyslog#2103, rsyslog/rsyslog#2105