Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

JOSS review - License #10

Closed
craig-willis opened this issue Sep 22, 2022 · 7 comments
Closed

JOSS review - License #10

craig-willis opened this issue Sep 22, 2022 · 7 comments

Comments

@craig-willis
Copy link

craig-willis commented Sep 22, 2022

Review issue: openjournals/joss-reviews#4707
Branch reviewed: release-0.2.4

Problem
JOSS requires that your repository include the full-text of an OSI approved license. See the Software License section of the review criteria. The current LICENSE file does not appear to be an OSI approved license. The DESCRIPTION indicates an MIT license.

If the MIT license has been selected, consider updating the LICENSE file based on the OSI template. (Also, I'm not sure what "MIT + file LICENSE" means in the DESCRIPTION).

@craig-willis craig-willis changed the title JOSS review - license JOSS review - License Sep 22, 2022
@robchallen
Copy link
Contributor

Many thanks for this and other comments which are all very helpful.

I went through a few iterations with the LICENSE files. CRAN have some specific ways they want the files which I now sort of understand, but required me taking out the original. I've added in a LICENCE.md file into this repo for github, which is ignored for CRAN submission. The 2 line LICENSE text file and DESCRIPTION entry "MIT + file LICENSE" is the correct incantation for CRAN.

@craig-willis
Copy link
Author

Ah, that makes sense now. I wasn't aware of the CRAN license requirements but see now that this is a common approach. Did you push your change to Github? I don't see a new commit.

@robchallen
Copy link
Contributor

Not yet.
I'll try and bundle a few things together, so it doesn't come at you piecemeal.
It will probably will take me a few days.
Do you close these issues or do I?

@craig-willis
Copy link
Author

craig-willis commented Sep 23, 2022

Sounds good.

As for closing the issues, I've confirmed with the editor that either of us can close an issue after it's been addressed. I'm happy to review any changes (or explanation of why changes don't need to be made) and close them. You're also welcome to close them and I'll let you know if I have any further concerns.

For JOSS, the main thing is that I communicate any concerns -- particularly that might block acceptance -- via the primary review issue. I don't plan on putting anything there until you've had a chance to respond to the open issues in this repo.

@robchallen
Copy link
Contributor

Hi. I've worked through all your helpful comments. In the end I made quite a few changes which I will describe in the linked issues, and this has been very worthwhile. I've bundled all the changes into a new release (0.2.4.9000) in a new branch which can be found here:

https://github.com/terminological/dtrackr/tree/joss-fixes-0.2.4.9000

On this specific issue I've added a LICENCE.md file.

This now show up on the home page of GitHub also.

(p.s. I'll let you close the issues once reviewed)

@craig-willis
Copy link
Author

Great. I'll complete my review based on that branch.

@craig-willis
Copy link
Author

craig-willis commented Oct 5, 2022

Revised branch: joss-fixes-0.2.4.9000

License looks good.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants