I agree that the file shows the _reasons_ but that is not the same as
a _process_.
With the high volume of packages that the CRAN maintainers handle, an
explicit procedure beyond "request it" is needed or should at least be
spelled out. We have pushed everything CRAN-related else towards
automatio
The README states clearly that a package is orphaned under any of three
conditions:
1. The Maintainer requests is.
2. The maintainer email bounces
3. The maintainer is unresponsive to requests regarding the package from
CRAN maintainers
But I think that it is a good idea to include th
The CRAN policy page
(https://cran.r-project.org/web/packages/policies.html) implies that
there is a formal procedure for orphaning a package but none is
mentioned in the Extensions manual
(https://cran.r-project.org/doc/manuals/r-devel/R-exts.html).
This page (https://cran.r-project.org/src/contr
