Project

General

Profile

Actions

Task #3343

open

tracking: developer documentation

Added by Victor Julien about 5 years ago. Updated over 1 year ago.

Status:
Assigned
Priority:
Normal
Assignee:
Target version:
Effort:
Difficulty:
Label:

Description

Goal is to create a developer guide similar to the user guide. So it will also live in the git repo and will using sphinx for the higher level guides.

For low level, we will continue to use doxygen.
In addition, for the Rust and Python components we need to support other low level frameworks as well like rustdoc.

Provisional TOC (will update as needed)

TOC

working with the codebase
- contributing
  = process (github)
  = quality requirements
- style
- debugging
- performance
  = concepts
  = analysis and tooling

internals
- packet pipeline
- threading
- common data structures

extending
- capture methods
- packet decoders
- app-layer protocols
- detection
- outputs

Existing documentation can be found here https://redmine.openinfosecfoundation.org/projects/suricata/wiki/Suricata_Developers_Guide. Much of this is outdated, so we shouldn't just copy it over. But it may be a good starting point for some of the new docs.


Subtasks 4 (1 open3 closed)

Task #3344: devguide: setup sphinxClosedShivani BhardwajActions
Task #3363: devguide: set up rustdoc to generate low level rust docsClosedJason IshActions
Task #3365: Research: can we use doxygen to validate completeness of low level docsNewOISF DevActions
Task #4909: devguide: move into userguide as last chapterClosedJuliana Fajardini ReichowActions

Related issues 1 (1 open0 closed)

Related to Suricata - Documentation #7150: devguide: document adding a logging pluginNewOISF DevActions
Actions

Also available in: Atom PDF