Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Package 'raveio' has been archived on CRAN for more than 60 days #9

Open
kurthornik opened this issue Apr 22, 2024 · 4 comments
Open

Comments

@kurthornik
Copy link

Package raveio is currently listed in CRAN Task View MedicalImaging but the package has actually been archived for more than 60 days on CRAN. Often this indicates that the package is currently not sufficiently actively maintained and should be excluded from the task view.

Alternatively, you might also consider reaching out to the authors of the package and encourage (or even help) them to bring the package back to CRAN. See the section on CRAN package archivals in the maintenance guidelines for more details.

In any case, the situation should be resolved in the next four weeks. If the package does not seem to be brought back to CRAN, please exclude it from the task view.

@muschellij2
Copy link
Collaborator

@dipterix

@dipterix
Copy link

dipterix commented Apr 22, 2024

Hi @muschellij2, one of our upstream package ravetools was pulled off by CRAN due to misrepresentation of the authorship.

Last month we submitted a fix to CRAN but we haven't got any reply yet.

I don't think there is much I could do now because CRAN is usually slow in package reviewing process

@ktabelow
Copy link
Collaborator

If you did a submission a month ago, it might be appropriate to contact CRAN-submissions@R-project.org (for submissions) and ask.

@dipterix
Copy link

@ktabelow I did, still no reply. I guess Ligges was very mad at my previous submissions (I had several attempt to fix the package). He told me he was not going to review my package until the issue was fully resolved... even though I told him I consulted lawyers and fixed all issues he brought up.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants