From amredd at gmail.com  Wed Sep 21 18:53:09 2016
From: amredd at gmail.com (Andrew Redd)
Date: Wed, 21 Sep 2016 16:53:09 +0000
Subject: [Rd] formal process for orphaning a package
In-Reply-To: <CAJ9CoW=EcE+Jw1u5UkOy81tY1MJqzVVdVxmAp1p3wEjp2bMeXA@mail.gmail.com>
References: <CAJ9CoW=EcE+Jw1u5UkOy81tY1MJqzVVdVxmAp1p3wEjp2bMeXA@mail.gmail.com>
Message-ID: <CAK_CNybVxs32LscopzD4ynPaB-2bo2R4rBGKtQOtE-kUZbxcgg@mail.gmail.com>

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 those conditions in the
manuals.

On Wed, Sep 21, 2016 at 9:30 AM Max Kuhn <mxkuhn at gmail.com> wrote:

> 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/contrib/Orphaned/README)
> implies that one would simply resubmit the package to CRAN with the
> text "ORPHANED" in the `Maintainer` field.
>
> Is this the case?
>
> If this is not documented somewhere, can it be added to the Extensions
> manual?
>
> Thanks,
>
> Max
>
> ______________________________________________
> R-devel at r-project.org mailing list
> https://stat.ethz.ch/mailman/listinfo/r-devel
>

	[[alternative HTML version deleted]]



[Rd] formal process for orphaning a package
Andrew Redd