Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
@Santymax98 If you want to write this paper with me, here are a few guidelines. Leveraging from the readme, and adding references from our own biliographies, this should not take us more than two to three hours to write.
Take a look here : https://joss.readthedocs.io/en/latest/submitting.html for the details on what to write.
Basically we should include importnat references of the field (Nelsen 2006, Joe 2014, Durante 2017 for the books), and maybe McNeil & Neshlehova, the reerence to the R package, etc.. the bigger the number of references the better.
The summary section should be about 20 lines describing what the paper is about.
You can [@cite_something] from paper.bib, and you should do it a lot, after filling the papeR.bib of course.
The whole paper should only be a few pages, maximum 4 or 5, not much more.
The most important part is the statement of need, where the goal is to justify the existance of the package. basically, you can leverage what is written on the readme (the easiest way to do it) and