Re: [R-pkg-devel] Change package maintainer
Hi, I agree that the email handshake is the best approach (and very reasonable to expect it). I thought that maybe in cases like this there was a waiting period and/or multiple attempts to contact the maintainer and someone on the mailing list might have had some experience with the process. When I'm ready to take over the package I will ask the CRAN team and give them more details. Many thanks to all. Lluís Revilla On Fri, 2 Jul 2021 at 08:38, Uwe Ligges wrote: > > > > On 01.07.2021 23:52, Duncan Murdoch wrote: > > On 01/07/2021 3:11 p.m., Dirk Eddelbuettel wrote: > >> > >> On 1 July 2021 at 20:00, Lluís Revilla wrote: > >> | I have a question related to changing maintainers. > >> | What happens when the old/current maintainer does not respond to > >> | emails or other methods of contact? > >> | Would the new maintainer need to wait until the package is removed > >> | from CRAN to submit it again? > >> > >> Not speaking for CRAN here but my understanding always was that a full > >> and > >> complete 'email handshake' with both old and new maintainer was strongly > >> preferred / the default simply to prevent misunderstandings or > >> shenanigans. > > > > I'd agree in the normal case where the package is still active on CRAN. > > > > In the case where a package has unaddressed issues with no response to > > CRAN from the maintainer, they'd probably be quite happy to have someone > > volunteer to take over. > > ... and if in doubt, ask the CRAN team and give them details. > > Best, > Uwe Ligges > > > > Duncan Murdoch > > > > __ > > R-package-devel@r-project.org mailing list > > https://stat.ethz.ch/mailman/listinfo/r-package-devel __ R-package-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-package-devel
Re: [R-pkg-devel] Change package maintainer
I can suggest one example: multcompView: I created it during or before 2006 and passed it during or before 2011 to Luciano Selzer . I do not remember the exact process, and procedures could have changed since then. However, I think I remember communicating with the CRAN maintainers after Selzer and I agreed he would take it over. Beyond that, I see that the DESCRIPTION file for multicompView0.1-3 lists BOTH of us as Maintainer. The version before that lists me only, and the one after lists him.[1] Second, last September, Brian Ripley sent an email to 50 different people saying gdata had problems, the maintainer had not responded, and it was scheduled to be archived along with all its strong reverse dependencies on 2020-09-25. I don't know what happened from that except that the package is still on CRAN with date Published: 2017-06-06, but my Ecfun package no longer uses it. Beyond that, I'm pretty sure that anyone can adopt a package in the archives that is no longer on CRAN and resurrect it if you agree to fix the problems. However, you should discuss with the CRAN maintainers. Spencer [1] https://cran.r-project.org/src/contrib/Archive/multcompView/ On 7/2/21 5:30 AM, Lluís Revilla wrote: Hi, I agree that the email handshake is the best approach (and very reasonable to expect it). I thought that maybe in cases like this there was a waiting period and/or multiple attempts to contact the maintainer and someone on the mailing list might have had some experience with the process. When I'm ready to take over the package I will ask the CRAN team and give them more details. Many thanks to all. Lluís Revilla On Fri, 2 Jul 2021 at 08:38, Uwe Ligges wrote: On 01.07.2021 23:52, Duncan Murdoch wrote: On 01/07/2021 3:11 p.m., Dirk Eddelbuettel wrote: On 1 July 2021 at 20:00, Lluís Revilla wrote: | I have a question related to changing maintainers. | What happens when the old/current maintainer does not respond to | emails or other methods of contact? | Would the new maintainer need to wait until the package is removed | from CRAN to submit it again? Not speaking for CRAN here but my understanding always was that a full and complete 'email handshake' with both old and new maintainer was strongly preferred / the default simply to prevent misunderstandings or shenanigans. I'd agree in the normal case where the package is still active on CRAN. In the case where a package has unaddressed issues with no response to CRAN from the maintainer, they'd probably be quite happy to have someone volunteer to take over. ... and if in doubt, ask the CRAN team and give them details. Best, Uwe Ligges Duncan Murdoch __ R-package-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-package-devel __ R-package-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-package-devel __ R-package-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-package-devel
Re: [R-pkg-devel] Change package maintainer
On 02.07.2021 14:45, Spencer Graves wrote: I can suggest one example: multcompView: I created it during or before 2006 and passed it during or before 2011 to Luciano Selzer . I do not remember the exact process, and procedures could have changed since then. However, I think I remember communicating with the CRAN maintainers after Selzer and I agreed he would take it over. Beyond that, I see that the DESCRIPTION file for multicompView0.1-3 lists BOTH of us as Maintainer. The version before that lists me only, and the one after lists him.[1] Although, the CRAN policies require a single maintainer these days. Best, Uwe Second, last September, Brian Ripley sent an email to 50 different people saying gdata had problems, the maintainer had not responded, and it was scheduled to be archived along with all its strong reverse dependencies on 2020-09-25. I don't know what happened from that except that the package is still on CRAN with date Published: 2017-06-06, but my Ecfun package no longer uses it. Beyond that, I'm pretty sure that anyone can adopt a package in the archives that is no longer on CRAN and resurrect it if you agree to fix the problems. However, you should discuss with the CRAN maintainers. Spencer [1] https://cran.r-project.org/src/contrib/Archive/multcompView/ On 7/2/21 5:30 AM, Lluís Revilla wrote: Hi, I agree that the email handshake is the best approach (and very reasonable to expect it). I thought that maybe in cases like this there was a waiting period and/or multiple attempts to contact the maintainer and someone on the mailing list might have had some experience with the process. When I'm ready to take over the package I will ask the CRAN team and give them more details. Many thanks to all. Lluís Revilla On Fri, 2 Jul 2021 at 08:38, Uwe Ligges wrote: On 01.07.2021 23:52, Duncan Murdoch wrote: On 01/07/2021 3:11 p.m., Dirk Eddelbuettel wrote: On 1 July 2021 at 20:00, Lluís Revilla wrote: | I have a question related to changing maintainers. | What happens when the old/current maintainer does not respond to | emails or other methods of contact? | Would the new maintainer need to wait until the package is removed | from CRAN to submit it again? Not speaking for CRAN here but my understanding always was that a full and complete 'email handshake' with both old and new maintainer was strongly preferred / the default simply to prevent misunderstandings or shenanigans. I'd agree in the normal case where the package is still active on CRAN. In the case where a package has unaddressed issues with no response to CRAN from the maintainer, they'd probably be quite happy to have someone volunteer to take over. ... and if in doubt, ask the CRAN team and give them details. Best, Uwe Ligges Duncan Murdoch __ R-package-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-package-devel __ R-package-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-package-devel __ R-package-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-package-devel __ R-package-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-package-devel
