The sysadm team is ok on this [1]

And like i mention in the crash ticket [2], moving to this scheme brings another pros to the
party, making the docs access more resilient.

[1]

12:34 <+olasd> in any case, I think I've voiced my concerns already. I don't like the idea of moving away from the wiki(s) to something with a much higher barrier to contribution (sphinx + restructured text + code review + git), but the unification and restructuring of docs probably outweighs this concern
12:35 <+olasd> and in that sense I'me fine with the proposal
12:36 <+olasd> (and the thing I'd want us to move towards doesn't exist yet, so...)

(quoting here because as usual, the arguments were nicely put and worth mentioning)

[2] T3444

@olasd , @ardumont and @vsellier : I think that we can gently resolve this task.

Thank you for a very fruitful sprint[1]!

[1] https://hedgedoc.softwareheritage.org/2021-october-documentation-sprint?edit

We have followed the plan on the hedgedoc (in the last comment).
Just realized we haven't decided if the support-tools should be in sys-admin dimension, so I'm adding this to this task to decide.

section: Support services

• Reference: Overview of support services
  • HedgeDoc from https://wiki.softwareheritage.org/wiki/HedgeDoc
  • IRC from https://wiki.softwareheritage.org/wiki/IRC -> user
  • Phabricator from https://wiki.softwareheritage.org/wiki/Phabricator
  • ? https://wiki.softwareheritage.org/wiki/Phabricator_callsign_naming_convention
  • new gitlab?
• Reference: Jenkins architecture
  • from https://wiki.softwareheritage.org/wiki/Jenkins

Makes sense to me to add them in sysadm.
Also, jsyk, currently, the support-services stub files are already present in the sysadm instance, remains to to fill in the blank at some point.

2 more pages migrated (published and redirect installed in the intranet):

• https://docs.softwareheritage.org/sysadm/user-management/onboarding.html
• https://docs.softwareheritage.org/sysadm/user-management/outboarding.html

(which i used to outboard hakb \o/, i believe that's the first time I actually outboard someone, i usually do the onboarding ;)

All existing sysadm pages have been migration from the wiki and from the intranet to the docs.softwareheritage.org/sysadm pages.
The redirection have also been configured to those pages.

So this can be closed now.