Current work is in the swh-loader-repository within the package-loader branch.

@douardda We have a separate task(T1777) for rubygem lister. I guess we can add a separate column in the table by @anlambert showing status of the lister implementation and the tasks related to it.

In T1389#27957, @anlambert wrote:

Package manager	Packages listing url	Package metadata url	Package source tarball url
Rubygems	No public api endpoint available	https://rubygems.org/api/v2/rubygems/[package]/versions/[version].json	available in the medata

Extending over the plan by @olasd. Here are some of my thoughts on the implementation of base loader.

In T1389#33215, @zack wrote:

Thanks @olasd, @ardumont, and @anlambert for this, it's a great plan and I like it a lot !
Just a few comments on the sidelines:

The lister will generate a one-shot task to load each package for the given repository, with the full information needed to do the data fetching.

This seemed clear from a different part of the description, but fwiw here I'm assuming the plan is to only load the version of the packages not already known/ingested in the past.

Thanks @olasd, @ardumont, and @anlambert for this, it's a great plan and I like it a lot !

npm is now archived continuously by Software Heritage (see for instance: https://archive.softwareheritage.org/browse/origin/https://www.npmjs.com/package/webpack/).

It is done ! npm packages are now available in the archive content so closing this.

I think the only thing missing here is adding the NPM logo to the archive coverage page.

I think this is now done, right @anlambert ?

We've discussed a plausible plan for a "base package manager loader" with @ardumont and, to some extent, @anlambert.

I've stopped the npm loader, and created a new dashboard to track the errors [1]

1. Create role