user: Unify 'listers' and 'loaders' tables into a single 'forges' table

Users do not care about technicalities like the difference between listers and loaders; instead this shows all forges on a single page, which I expect is what users expect.

This also allows providing a single documentation page for everything related to a forge, without duplicating between loader and lister (eg. explanation of how the forge works)

Additionally, this fixes some of the links to swh-web

This MR contains a commit from !351 (merged) and includes the change from !350 (merged)

added 1 commit

• 3474a730 - user: Unify 'listers' and 'loaders' tables into a single 'forges' table

Compare with previous version

changed the description

added 1 commit

• 83ddda8c - Move link to tracking issues to 'status' column

Compare with previous version

added 1 commit

• 632425a2 - Fix more links to swh-web

Compare with previous version

changed the description

Jenkins job DDOC/builds #277 succeeded .
See Console Output and Coverage Report for more details.

Jenkins job DDOC/builds #279 succeeded .
See Console Output and Coverage Report for more details.

Jenkins job DDOC/builds #278 succeeded .
See Console Output and Coverage Report for more details.

Jenkins job DDOC/builds #280 succeeded .
See Console Output and Coverage Report for more details.

Jenkins job DDOC/builds #281 succeeded .
See Console Output and Coverage Report for more details.

Jenkins job DDOC/builds #282 succeeded .
See Console Output and Coverage Report for more details.

mentioned in merge request !354 (merged)

Great, I love it! :)

I wish we could find a better wording for this. A common term for “forges and VCS” would be great. “Source” comes to my mind but confusing in the context. Just ”providers”? “Source providers” maybe?

I also feel unsure about using the word “supported”…

“Source code providers”? (probably we could drop “Software Heritage” given the context)

I don't think it's possible to find a unifying term for forges and VCSs that isn't overly generic. And I wouldn't call Git or Mercurial providers :/

A term that we use in multiple places, to mean either an individual repository, or a collection of repositories (e.g. a hosting platform or a group of individual sources that share a common trait) is "software origins".

changed this line in version 5 of the diff

done