You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Every now and then, there is a need to directly include third-party code in an R package without a way to link to an external build of it as recommended by the policy. Here's a recent example: R-package-devel thread, eventual CRAN package with lots of cph, ctb co-authors. After a recent change in ?person, all the "natural person" co-authors are automatically considered cph. Do I understand it correctly that the correct way to include third-party code now is as follows?
Hi @aitap, Thanks for your question. I'm going to be writing up a somewhat relevant recipe issue: Description file: Using Authors@R soon and I'll take some time to think about how this question can be answered and included as a callout note at least for reference.
Small comment from my side as CRAN newbie submission team member:
Your list looks like a great summary. I can only tell you what I look for in packages with third-party code.
And packages following your list would probably pass my review (at least regarding this issue).
Every now and then, there is a need to directly include third-party code in an R package without a way to link to an external build of it as recommended by the policy. Here's a recent example: R-package-devel thread, eventual CRAN package with lots of
cph, ctb
co-authors. After a recent change in?person
, all the "natural person" co-authors are automatically consideredcph
. Do I understand it correctly that the correct way to include third-party code now is as follows?ctb
, organisations ascph, ctb
cph
co-authors, specify the ownership details in thecomment
argumentThe text was updated successfully, but these errors were encountered: