Skip to content

[JOSS-REVIEW] Contributor outline needed in developer guide #27

@PennyHow

Description

@PennyHow

Specifically relating to documentation and JOSS' requirements, there needs to be clear guidelines on:

  1. How to contribute to the software
  2. How to report issues or problems with the software
  3. How to seek support

Currently, the outline of the package architecture and rules are very clear and succinct. However, in order to meet JOSS' requirements, you also need to include these additional guidelines.

I would suggest referring to readily available on how to contribute to github repos (e.g. Github's own documentation here, and taking inspiration from other packages with good contributor guidelines (e.g. pandas)

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