-
Notifications
You must be signed in to change notification settings - Fork 8
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
Help maintain packages currently held by the CRAN team #26
Comments
Let me ask around my team. |
At our meeting today, we had a productive discussion about the impact of packages maintained by CRAN. Taking maintainership of those package is seen as challenging for junior developers to maintain such complex codebase. As a working group, we agreed to start by examining the package's dependencies and assessing how its deprecation would affect users and other packages that rely on it. To ensure the smooth transition of users to alternative packages, we discussed a few potential actions that our group could take, including deciding on a threshold of top X or top Y% packages and assisting with the update to a more modern package. Once we've identified these crucial packages and they are updated to use the replacements, we can work towards transitioning away from deprecated packages in a coordinated manner to minimize friction between packages and with the CRAN checks. We agreed that a reasonable timeline for the transition would be within 2-5 years. As a next step, I offered to present a detailed analysis of the dependencies and potential replacement packages at our next meeting/month. |
I don't seem to be able to join the meeting with the link I have, I prepared some analysis in my blog. HTH |
The CRAN team is looking for maintainers of at least 2 packages they maintain.
Lifting that burden might help them focus in other tasks, some of which might be those we have been discussing.
The text was updated successfully, but these errors were encountered: