-
Notifications
You must be signed in to change notification settings - Fork 4
Open
0 / 10 of 1 issue completedMilestone
Description
- The software must be open source as per the OSI definition.
- The software must be hosted at a location where users can browse the source code files, open issues, and propose code changes without manual approval of (or payment for) accounts
- The software must have an obvious research application.
- You must be a major contributor to the software you are submitting, and have a GitHub account to participate in the review process.
- Your paper must not focus on new research results accomplished with the software.
- Your paper (paper.md and BibTeX files, plus any figures) must be hosted in a Git-based repository together with your software.
- The paper may be in a short-lived branch which is never merged with the default, although if you do this, make sure this branch is created from the default so that it also includes the source code of your submission.
- Be stored in a repository that can be cloned without registration.
- Be stored in a repository where the software source files are browsable online without registration.
- Have an issue tracker that is readable without registration.
- Permit individuals to create issues/file tickets against your repository.
As a rule of thumb, JOSS’ minimum allowable contribution should represent not less than three months of work for an individual. Some factors that may be considered by editors and reviewers when judging effort include:
- Age of software (is this a well-established software project) / length of commit history.
- Number of commits.
- Number of authors.
- Total lines of code (LOC). Submissions under 1000 LOC will usually be flagged, those under 300 LOC will be desk rejected.
- Whether the software has already been cited in academic papers.
- Whether a potential user can easily install, understand, and test the software. (If your software is new, please be sure a colleague has tried it.)
- Whether the software is sufficiently useful that it is likely to be cited by your peer group.
Check more details on: https://joss.readthedocs.io/en/latest/submitting.html#submission-requirements
Sub-issues
Metadata
Metadata
Assignees
Labels
No labels