diff --git a/sysadm/deployment/deployment-environments.rst b/sysadm/deployment/deployment-environments.rst
--- a/sysadm/deployment/deployment-environments.rst
+++ b/sysadm/deployment/deployment-environments.rst
@@ -26,7 +26,7 @@
The source for the provisioning of those nodes is declared in the
`swh-sysadmin-provisioning
-`__
+`__
repository. Its source code is a mix of `terraform `__ with
`terraform-proxmox `__ plugin
DSL.
@@ -37,7 +37,7 @@
^^^^^^^^^^^^^^^^^^^^
The source for the configuration of those nodes is our `puppet manifest swh-site
-repository `__ on the
+repository `__ on the
*staging* branch (for the production nodes, it's the *production* branch).
Access
diff --git a/sysadm/puppet/howto-deploy-puppet-change.rst b/sysadm/puppet/howto-deploy-puppet-change.rst
--- a/sysadm/puppet/howto-deploy-puppet-change.rst
+++ b/sysadm/puppet/howto-deploy-puppet-change.rst
@@ -34,7 +34,7 @@
you@localhost$ cd puppet-environment
you@localhost$ bin/deploy-on machine1 machine2...
-Note: `puppet-environment `_
+Note: `puppet-environment `_
Remember to pass ``--apt`` to ``bin/deploy-on`` if freshly uploaded Software Heritage
packages are to be deployed. Also, ``bin/deploy-on --help`` is your friend.
diff --git a/sysadm/puppet/howto-manage-third-party-modules.rst b/sysadm/puppet/howto-manage-third-party-modules.rst
--- a/sysadm/puppet/howto-manage-third-party-modules.rst
+++ b/sysadm/puppet/howto-manage-third-party-modules.rst
@@ -1,5 +1,16 @@
.. _puppet_integration_of_third_party_puppet_modules:
+.. admonition:: Intended audience
+ :class: important
+
+ staff members with enough permissions to deploy
+
+.. admonition:: Warning
+ :class: warning
+
+ Deprecated documentation. Since we migrated to gitlab, the referenced script must be
+ adapted to work with it.
+
How to manage Third-Party modules
=================================
@@ -18,6 +29,7 @@
Adding a new external puppet module
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
In the *puppet-environment* repository, the ``bin/import-puppet-module`` takes care of
the following tasks:
@@ -49,7 +61,7 @@
git push
Once the module is added, you need to register it in the *swh-site* `Puppetfile
-`_.
+`_.
You should also check in the module metadata whether any dependencies need importing as
well, which you should do using the same procedure.
diff --git a/sysadm/puppet/reference-best-practices.rst b/sysadm/puppet/reference-best-practices.rst
--- a/sysadm/puppet/reference-best-practices.rst
+++ b/sysadm/puppet/reference-best-practices.rst
@@ -5,5 +5,5 @@
.. todo::
This page is a work in progress. Please refer to the `existing documentation
- `_ and `the
+ `_ and `the
wiki page `_.
diff --git a/sysadm/user-management/onboarding.rst b/sysadm/user-management/onboarding.rst
--- a/sysadm/user-management/onboarding.rst
+++ b/sysadm/user-management/onboarding.rst
@@ -56,6 +56,11 @@
- add user to phabricator `projects `_:
Developers, Staff, Reviewers, Interns (if applicable)
+- Create `Gitlab`_ account
+
+ - add user to the `Staff group `_
+ - TODO: Define further group memberships for new users
+
- `VPN `_ access
- HTTP auth credentials for the `intranet wiki`_
- Create account on the `intranet wiki`_ and ask someone to give you the shared auth credentials
@@ -108,3 +113,4 @@
.. _intranet wiki: https://intranet.softwareheritage.org
.. _public wiki: https://wiki.softwareheritage.org
.. _Phabricator: https://forge.softwareheritage.org
+.. _Gitlab: https://gitlab.softwareheritage.org