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
I've been trying to track down some discrepancies in how we calculate the number of reviewed packages in the Annual Reporting.
One thing is that there are some packages that used to be listed in the registry/packages jsons which are no longer included.
There is a "type" field in the registry (active, experimental, archived), so shouldn't we always list packages, even those archived, unless the owner requests removal?
The following have been archived, but are not listed in the registry as archived:
Rclean
bittrex
bomrang
citesdb
cleanEHR
dbhydroR
getlandsat
gtfsr
infx
monkeylearn
mregions
nbaR
outsider
refimpact
ropenaq
rromeo
rtimicropem
tidytags
tabulizer
The roregistry README suggests that only packages in the ropensci repo are included, so this probably explains why those in ropensci-archive are excluded. Is this by design? Would it be possible to get all packages listed in the registry?
The text was updated successfully, but these errors were encountered:
[Moved from https://github.com/ropensci/roregistry/issues/46]
I've been trying to track down some discrepancies in how we calculate the number of reviewed packages in the Annual Reporting.
One thing is that there are some packages that used to be listed in the registry/packages jsons which are no longer included.
There is a "type" field in the registry (active, experimental, archived), so shouldn't we always list packages, even those archived, unless the owner requests removal?
The following have been archived, but are not listed in the registry as archived:
The roregistry README suggests that only packages in the
ropensci
repo are included, so this probably explains why those inropensci-archive
are excluded. Is this by design? Would it be possible to get all packages listed in the registry?The text was updated successfully, but these errors were encountered: