Forge-to-Gitlab-migration-FAQ.md

@@ -8,8 +8,23 @@ INRIA Forge project administrators and/or users need to coordinate to decide *wh
 
 Coordination is paramount because if, as a project admin, you migrate for example the source control repository without telling the users, some of them might still use the old repository on the forge for checkouts or commits.
 
+### Communication with forge project members
+
 As there is no simple way for a forge project administrator to get the list of emails of project members (to communicate with everyone and be sure to forget nobody), we can provide these lists on demand to forge project administrators. Open a ticket for this.
 
+### Preventing project members from commiting / pushing
+
+#### Subversion
+
+Add a pre-commit hook which always returns false. For example:
+
+```
+ssh scm.gforge.inria.fr
+echo -e "#!/bin/bash\necho \"This repository is read-only\"\nexit 1" > /svnroot/<project unix name>/hooks/pre-commit && chmod a+x /svnroot/<project unix name>/hooks/pre-commit
+```
+
+#### Git
+
 ## Available documentation and help
 
 The gitlab documentation is available here: https://gitlab.inria.fr/help