Your package got removed from CRAN

[romanzenka]

Hello!

I use and love restorepoint, but I noticed it got removed from CRAN because you did not fix some issues despite reminders.

Would you be willing to let me keep maintaining this package for my own benefit and keep it alive as a side effect?

[skranz]

Hi Roman,

nice to hear that you like the restorepoint package. If you are willing to maintain restorepoint at CRAN, that would be great. (While CRAN is very useful, I found out after several rounds of resubmission, that I was just not patient enough to resolve all notes required to maintain a package on CRAN).

I have not much experience how to best structure that process. Probably it would be best if you fork my restorepoint package on Github, make all necessary changes in the DESCRIPTION file (adding you as maintainer, me as creator) and the other required changes so that the package is accepted on CRAN. (There were some vignette issues. If too complicated to resolve, you may also just remove all vignettes and put the content into the README.md). Maybe we can then also update via a pull request my Github package with your version. That may be useful since from time to time, I make still some small updates to restorepoint.

[romanzenka]

Okay sounds like a plan!

…

--Roman From: Sebastian Kranz <notifications@github.com<mailto:notifications@github.com>> Reply-To: skranz/restorepoint <reply@reply.github.com<mailto:reply@reply.github.com>> Date: Tuesday, July 11, 2017 at 9:58 AM To: skranz/restorepoint <restorepoint@noreply.github.com<mailto:restorepoint@noreply.github.com>> Cc: "Roman M. Zenka" <zenka.roman@mayo.edu<mailto:zenka.roman@mayo.edu>>, Author <author@noreply.github.com<mailto:author@noreply.github.com>> Subject: Re: [skranz/restorepoint] Your package got removed from CRAN (#3) Hi Roman, nice to hear that you like the restorepoint package. If you are willing to maintain restorepoint at CRAN, that would be great. (While CRAN is very useful, I found out after several rounds of resubmission, that I was just not patient enough to resolve all notes required to maintain a package on CRAN). I have not much experience how to best structure that process. Probably it would be best if you fork my restorepoint package on Github, make all necessary changes in the DESCRIPTION file (adding you as maintainer, me as creator) and the other required changes so that the package is accepted on CRAN. (There were some vignette issues. If too complicated to resolve, you may also just remove all vignettes and put the content into the README.md). Maybe we can then also update via a pull request my Github package with your version. That may be useful since from time to time, I make still some small updates to restorepoint. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub<#3 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AAEECPnxhaSg8NY58yXfu3c3VpTXXlYHks5sM42FgaJpZM4OUUeL>.

[romanzenka]

I made another PR #6 which should actually work this time. Sorry for the massive delay.

I got Travis CI to work, here are the builds: https://travis-ci.org/romanzenka/restorepoint - you may want to enable Travis on your own and add their pretty badge to the README.md

[skranz]

Great. Thanks a lot for making the package CRAN ready and adding the tests and travic-ci. Would you also be willing to upload the package to CRAN and be the official maintainer, at least for all CRAN-related purposes?

(I am still happy to implement all CRAN-unrelated fixes, but I fear I may not always be willing to keep it CRAN-compliant in all future. The last time, there were changes in the CRAN requirements and I made several rounds of updates trying to be again CRAN compliant according to the newest R-devel version. But eventually restorepoint was taken away from CRAN because I did not put the word "Github" in the description text in single quotes but kept the double quotes. I then just decided to stop maintaining packages on CRAN...)

Anyway, if you are willing to manage the CRAN issues, I would set you as the official maintainer in the DESCRIPTION file (I think that is necessary for a CRAN upload), and I would remain as contributor and creator.

[romanzenka]

Ok, fine with me! It should mostly be an easy job as this package is pretty feature-complete, so it is really CRAN changes over time to keep up with.

[romanzenka]

Just noticed this on CRAN:

CRAN submission will be offline from Dec 21, 2018 to Jan 02, 2019 (CRAN team vacation and maintainance work).

I may not be able to get it through by then, so let's continue this effort in 2019!

[skranz]

Thanks a lot for maintaining the package for CRAN!

I just pushed a commit in which I set you as maintainer in the DESCRIPTION file and increased the version number and another commit where I updated the README.md and the Vignette (mainly removing typos). Let's hope the CRAN upload works without too many iteration steps next year!