This commit moves information from the Technical Working Group's (TWG)
[git.coop
wiki](https://git.coop/social.coop/tech/operations/-/wikis/home) into a
subdirectory of the main wiki. The current TWG wiki on git.coop is
currently public. These changes are predicated on the idea that we want
to move forward with the
[proposal](https://www.loomio.com/d/2Rwh5z3H/time-to-consolidate-wikis-/69)
to consolidate wikis in preparation for the move to a more user friendly
wiki platform.

**Note:** This commit includes an update to the Tech Working Group section of the
Bylaws to point to the relevant section in the general wiki rather than
the old TWG specific git.coop wiki.

Quite a bit of the information contained in these pages needs to be
consolidated and/or updated. But for historical purposes the thought was
to bring these pages over largely unchanged and then update them either
here in Git, or once the content has been moved to a new wiki.

If/when this merge request is pulled in the Tech Working Group pages
should become available at wiki.social.coop. At that point the old
https://git.coop/social.coop/tech/operations repository can be [archived](https://docs.gitlab.com/ee/user/project/settings/#archive-a-project).

tech-working-group/How-to-add-a-socialcoop-email-address.md

+Only those with whitelisted (i.e. `@social.coop`) email addresses can create new accounts on this GitLab instance.
+
+Currently we use Web Architect's SMTP server to manage the `social.coop` top-level domain. Generally we only assign aliases, which simply forward mail to the user's personal address, not full accounts. Partly because this is all that is needed, but significantly because we only have 1MB space allocated on the server!
+
+In order to give someone such an address, an existing administrator with access needs to follow these steps:
+
+- Log into https://webarch.email/ as `socialcoop` *(the password should be in the [keyringer](https://git.coop/social.coop/tech/keyringer) keystore and accessible to admins real-soon-now)*.
+- Select the 'Aliases' tab, (oddly it has a dropdown too, select 'aliases' here, not 'domain aliases')
+- Click on the button to add an alias, which will open a dialog.
+  - The top box *Alias address/es* should contain `<new account>@social.coop` (and optionally other incoming social.coop addresses to create).
+  - The bottom box *Goto addresses* should contain the users' personal address to forward to ~(and optionally any other destination addresses).
+  - Ensure the 'active' box is checked.
+- Submit the dialog.
+- If the user is a member of any working groups which have their own dedicated group email addresses, like `tech.group` or `finance`, add their `@social.coop` address to the relevant aliases for these too (so that any changes to the user's forwarding address just requires the one alias to be updated).
+- Optionally, test the alias.
+- Notify the user the alias is ready.
+
+Done.
\ No newline at end of file