flow_stability

flow_stability copied to clipboard

Closes #16

j-i-l

j-i-l

OSI approved license

2

Software must be open source as per [OSI definition](https://opensource.org/osd)

j-i-l

How to host any paper specific content?

2

> Your paper (`paper.md` and BibTeX files, plus any figures) must be hosted in a Git-based repository together with your software (although they may be in a short-lived branch which...

j-i-l

j-i-l

See the [relevant section in the JOSS review criteria](https://joss.readthedocs.io/en/latest/review_criteria.html#documentation). The following elements are required in an adequate documentation: - `README.md` providing at least - [ ] high level overview -...

j-i-l

See [JOSS GH Action](https://joss.readthedocs.io/en/latest/submitting.html#github-action) section. We might want to directly use the action [provided by Open Journals](https://github.com/marketplace/actions/open-journals-pdf-generator) Given that this task is only relevant in the context of https://github.com/alexbovet/flow_stability/milestone/1 we...

j-i-l

Generally a good idea and relevant for #12 in particular

j-i-l

Get started with the paper.md

1

See the [What should my paper contain](https://joss.readthedocs.io/en/latest/submitting.html#what-should-my-paper-contain) for details about content and structure. Generally, `paper.md` needs to contain the following blocks: - authors - summary - statement of need -...

j-i-l

The minimal requirement this regard consists of instructions to verify the expected behavior of core functionalities. This does not include the automation of tests. To tie the execution of tests...

j-i-l