syslog-ng / syslog-ng/syslog-ng.github.io
Update outdated summary, instructions, etc. pages
Open
Nobody has claimed this yet.
documentation
enhancement
- Dominant language
- JavaScript
- Stars
- 6
- Forks
- 15
- Avg merge
- 4h 32m
- Merged PRs (30d)
- 5
Description
- https://syslog-ng.github.io/admin-guide/010_Introduction_to_syslog-ng/000_What_syslog-ng_is
- https://syslog-ng.github.io/admin-guide/030_Installing_syslog-ng/001_Compiling_options
- https://syslog-ng.github.io/admin-guide/030_Installing_syslog-ng/000_Compiling_syslog-ng_from_source
- Manual pages https://syslog-ng.github.io/admin-guide/190_The_syslog-ng_manual_pages/README
- especially of the supported parameters of syslog-ng itself https://syslog-ng.github.io/admin-guide/190_The_syslog-ng_manual_pages/005_syslog-ng_manual
- or, the tools like syslog-ng-ctl https://syslog-ng.github.io/admin-guide/190_The_syslog-ng_manual_pages/007_syslog-ng_control_tool_manual
- etc.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the linked Introduction, installation, compilation, and manual-page entries, especially the syslog-ng and syslog-ng-ctl pages. Compare their summaries, instructions, and supported parameters with the current project information; done means the outdated documentation across the listed pages has been updated.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100