Skip to content

document policy around use of doxygen #5

@gonsie

Description

@gonsie

I've set up a repo for the user documentation which uses Doxygen to parse the header files and generate documentation. It requires that the header files be documented in a specific way. I need to write this down so that future developers can follow.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions