Open aitap opened 1 month ago
I think this should be first addressed at r-package-devel as it affects also packages on Bioconductor. Note that there was also some change on how comment
is used (not sure what was the intention but saw some commits about it).
My apologies, I had assumed that the presence of a CRAN team member offered a more direct way of clarifying rules. Let's hope that after an R-package-devel discussion we'll be able to make it into a pull request.
There is nothing to apology, I might be wrong. The CRAN team is divided in groups, and I don't think the CRAN QA group is checking this repository. I think they are more likely to see this on the mailing list.
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.
Thank you! I see the policy for organisations is being updated as well.
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
argument