[ ] Rewrite the Path reconstruction section by being more explicit, and check other sections that need clarification (it's OK to have several aims for 1 package, 1 aim for several packages, but not several aims for several packages).
Long term organisation
[ ] Add individual issues for each package of the list, so we have one place for all discussion points related to a package. We could certainly have templates for basic messages (for instance those that are on CRAN or checks CRAN tests).
[ ] Consider contacting maintainers of each package to let them know about the CTV and their individual issue for relevant discussion.
Dev features
[ ] Use GitHub Actions for continuous integration of the CTV (just like a R package). That would allow to automatically test current packages. New packages would only be tested when formally added. See here for relevant examples.
[ ] Check renv as a replacement to packrat to deal with the private library of packages. Migration tools are provided with renv.
[ ] Implement automatic CRAN package search in our workflow, for instance with pkgsearch::pkg_search(), fixing some search terms (#33).
Markdown CTV file
Long term organisation
Dev features
renv
as a replacement topackrat
to deal with the private library of packages. Migration tools are provided withrenv
.pkgsearch::pkg_search()
, fixing some search terms (#33).