Hey @KShivendu,
These are very good observation.

I'm good with this location.
Just a question about the url, would that be:
docs.softwareheritage.org/roadmap/roadmap-2021
or
docs.softwareheritage.org/devel/roadmap/roadmap-2021?
or both?

Another link for author roles: https://allcontributors.org/docs/en/emoji-key

InvenioRDM tests on staging looks good

Redirect https://archive.softwareheritage.org/browse/help/ to the user documentation

We can identify three general types of personas:

• visitors: people who want to know what is the SWH initiative and archive
• users: people who want to use the SWH features
  • as a service
  • as a module by running a local instance
• contributors: people who want to contribute to the SWH project, specifically on a feature or in general
  • source code contributors
  • sys-admins contributors
  • documentation contributors

FYI there is a lister tutorial already in the docs updated with D5069

Nicely documented.

In the task description there are two links, one to a blog post and another to the documentation.
If the docs aren't specific enough to complete the task, let us know, what is missing.
I prefer not to give further instructions to really see what is the limit of the documentation.
We are also trying to improve the documentation, so this would be a win win.

Hi @KShivendu, nice to see you claimed the task :-)
You don't have to use the cff-converter tool, but it can be a test (to ensure coherence).

https://github.com/citation-file-format/cffconvert-github-action
https://github.com/citation-file-format/cff-converter-python

From swh-devel:
On Fri, Feb 12, 2021 at 4:43 PM Stefano Zacchiroli <zack@upsilon.cc> wrote:

Discussion during the deposit sprint:

1. the first will be a new deposit and the following deposits will be an update
2. we wish to stop generating a new origin for each test

Discussion on deposit sprint with @ardumont and @anlambert

• login / mdp classic (not most secured)
• authentication by token
• create account for each application and give permissions depending on the account
• to give permission for the deposit functionality an admin needs to change the account permission
• we don't want to break the existing usage (login /mdp)

> use login/mdp

1. you get the login/mdp in headers from clients,
2. the server will send it to keycloak

authentication backend (which is used in swh-web

3. direct grant (Oauth) open ID connect

Add property in main table to filter between deposit types.

After a few exchanges with Yannick we have resolved the task on HAL's end after the change of an endpoint.

Removed comments have moved to T3036

Here is an online first draft:
https://www.softwareheritage.org/?page_id=24009&customize_changeset_uuid=072de555-8e9c-4e7c-ae8d-385045486588

https://geodynamics.org/cig/index.php?cID=1390

Nice tutorial!
Very informative for me.
I have added a couple of stylish comments and a few questions for improvement.

swh.model identify =>
swh:1:cnt:98843a5a92ed2abc10d48e6330d0b0f3919c86f3;origin=https://pypi.org/project/swh.model/;visit=swh:1:snp:5cddd4ca41543684ff0336ee7c0d1e42ab89106b;anchor=swh:1:rev:a1c38b45b0b93b2a3f953e71f17c1591ef372c5f;path=/swh.model-0.12.0/swh/model/identifiers.py/

Specification is enough to reference than a .xsd file.