Skip to content

statement of need in package documentation #75

@corybrunson

Description

@corybrunson

JOSS expects the package documentation itself to include a statement of need. Based on previous conversations, this need not be a full section as in the manuscript but could be a sentence or two in Getting Started. Maybe it's already there in another section; if so, please point me to it and accept my apology!

Part of this JOSS review.

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