I'm uncertain about which scenario is tested.

I agree on linking Gitorious to the wiki page, but we should find a consistency that can generate automatically the coverage page.

Thanks for checking !

I'm not sure about my comment to change tool to fetcher.

@anlambert What do you think?

That's a good start !
I have some comments in-lined.
Maybe a clear plan for test and coverage, can be useful and help you continue the development.

A reference to AtomPub protocol which is used with SWORD:
https://www.ibm.com/developerworks/library/x-atompp1/x-atompp1-pdf.pdf

Prod
This was due to corrupted file. The error was difficult to understand and wasn't logged on the moderation view (on HAL side).
This task is now closed.

Examples for a community driven documentation:

• https://docs.godotengine.org/en/stable/
• https://javascript.info/
• https://wiki.archlinux.org/

Is the diagram in the link below the answer to this task?
https://docs.softwareheritage.org/devel/architecture.html

This list of user stories is something that can be written in a wiki.
@douardda or do you prefer having this list of scenarios in the docs ( for example in: docs.softwareheritage.org/user-stories)

Also we decided (on today's call) to keep diagrams with mermaid.

This is the blueprint page for all use-cases:
https://docs.softwareheritage.org/devel/swh-deposit/specs/blueprint.html

Reviewed and opened the HAL issue (which is on a closed forge, so most of you can't open):
https://gitlab.ccsd.cnrs.fr/ccsd/hal/-/issues/302

Redirection should be to https://docs.softwareheritage.org/devel/swh-model/persistent-identifiers.html

@ardumont it is exactly the diagram I was looking for. Thanks!
I think we need a diagram that shows the functionality dependence between modules.

The access to the glossary from the main docs page is hard find.
It's under Indices and tables which is not exactly the evident as a glossary related category.
Also there is no access from the left menu.