Update DOI and LICENSE for CRAN submission#54
Conversation
According CRAN policy, year field in MIT LICENSE should start as `YEAR` not `Year`. Also, DOI prefix should be removed.
|
I'd prefer to keep master clean -- are you OK with waiting with the merge until CRAN accepts it? Just in case there are more changes to do... |
|
Sure. Make sense. Will try second submission now. |
Codecov Report
@@ Coverage Diff @@
## master #54 +/- ##
=======================================
Coverage 88.42% 88.42%
=======================================
Files 3 3
Lines 380 380
=======================================
Hits 336 336
Misses 44 44Continue to review full report at Codecov.
|
|
Finally get reply from CRAN maintainers (normally they will reply in a day): For 1 and 3, it's easy to fix. For the copyrights, it seems that there is no specific one acts as the
What do you think @dmey @DJGosnell ? |
this looks more like a preference than anything else -- In any case, let's try to keep this simple -- I would simply use what's already done at https://github.com/rstudio/rmarkdown/blob/master/DESCRIPTION#L36-L37. Specifically, I would change it to: Then add you as maintainer |
|
That is a feasible way. My only concern is whether ASHARE should be put as an author. |
Co-Authored-By: dmey <dmey@users.noreply.github.com>
OK, how about something like? |
Seems like this did not work. R CMD check directly fails. Probably we could keep the original style and also add ASHRAE? |
|
Can you try simply by adding your email before role under "The PsychroLib Contributors" |
|
No lock. It seems that the first "person" field should always have an non-empty name. |
How about you just add yourself as the first, rest should be fine as is? |
Worked! |
|
@dmey Latest reply from CRAN maintainer: According to Writing R Extensions:
It seems that we have to list all authors like rmarkdown in a separate file and include it in the package under Will update and resubmit |
# |<---- Using a Maximum Of 50 Characters ---->| # Explain why this change is being made # |<---- Try To Limit Each Line to a Maximum Of 72 Characters ---->| # Provide links or keys to any relevant tickets, articles or other resources # Example: Github issue psychrometrics#23 # --- COMMIT END --- # Type can be # feat (new feature) # fix (bug fix) # docs (changes to documentation) # style (formatting, missing semi colons, etc; no code change) # refactor (refactoring production code) # test (adding missing tests, refactoring tests; no production code change) # chore (updating grunt tasks etc; no production code change) # -------------------- # Remember to # Separate subject from body with a blank line # Limit the subject line to 50 characters # Capitalize the subject line # Do not end the subject line with a period # Use the imperative mood in the subject line # Wrap the body at 72 characters # Use the body to explain what and why vs. how # Can use multiple lines with "-" for bullet points in body # -------------------- # For more information about this template, check out # https://gist.github.com/adeekshith/cd4c95a064977cdc6c50
|
@dmey It's on CRAN now! https://cran.r-project.org/web/packages/psychrolib/index.html |
|
Great! But I am bit confused as the binaries are not available -- my understanding when we discussed the PR about having C++ source was that the package on CRAN would not require the user to compile psychrolib from source. Can you clarify this please? |
|
It usually takes few days for CRAN to compile the package for Windows and MacOS. So just wait. |
|
@dmey I believe this PR is ready to be merged. Right now Windows and macOS binaries have been built. You can check that by installing the package via |
|
Thanks for letting me know -- I will try to create the release and merge this in the next couple of days. |
First submission try, still got a NOTE. CRAN maintainer replied:
According CRAN policy, year field in MIT LICENSE should start as
YEARnotYear. Also, DOI prefix should be removed.This PR modified
src/r/tools/deploy.Randsrc/r/inst/CITATIONaccordingly.