Integrate CRAN

[mattbk]

The repository for R packages.

Like #4148.

[chadwhitacre]

Looks like CRAN is on https://libraries.io/. My thinking is that after #4148, we will have a much better idea of what we need from Libraries.io in terms of API. Ideally they would be able to build out whatever API we might need, and then we can go from 1 to 30+ other package managers in one fell swoop. Does that sound right to you?

[mattbk]

Sounds good. Wanted to get it on the list.

[mattbk]

Working with http://www.crantastic.org/ would be great as well. It's a search/review site for CRAN packages. They're on GitHub: https://github.com/hadley/crantastic/tree/master

[mattbk]

I mentioned this here, too, apparently.

[daroczig]

Crantastic (as far as I know) is not under active development anymore, unfortunately :(
I'd rather suggest checking METACRAN at https://www.r-pkg.org

Pinging @gaborcsardi, I think he might be interested in this.

[mattbk]

Looks like you're right, no commits since 2014. Thanks!

Will have to check out https://github.com/metacran.

[gaborcsardi]

👍

I am not sure what kind of API you need from the packages manager, but I'll be happy to improve the CRAN API at METACRAN.

[nobodxbodon]

Re-ticketed to integrate with software repositories / package manager for further discussion and planning. After deciding on concrete implementation plan and dev work starts, this will be reopened for tracking purpose.

[mattbk]

I know you're trying to get things organized, but why can't we have issues in both places? I assume the IG issue is going to be about prioritizing which to implement first?

[nobodxbodon]

@mattbk IMO, as there are other similar issues it's better to be planned together. In case contributor from external platform wants to make a push on this, or someone wants to just discuss about it, that assembly issue is still a good place to start with, as we'll still need to decide relative priority among those similar issues, and (if decide to start working) who from our side to work with them, while keeping in mind our short-term focus.

In case an arbitrary contributor wants to pick some open issue to work on, there are still plenty other more actionable issues with higher severities (bugs, usabilities, UI, etc), and closing issues that are not immediately actionable will make the other issues more likely to be solved, as those contributors will be more focused.