Onboarding New Tech Working Group Team Members: Difference between revisions
Jump to navigation
Jump to search
mNo edit summary Tags: Mobile edit Mobile web edit Visual edit |
m (Combine the two email steps) |
||
| (One intermediate revision by the same user not shown) | |||
| Line 5: | Line 5: | ||
There are a few places you'll need to be granted access to start your onboarding process to join the [[Tech Working Group]]. These first 3 steps require help from an existing TWG member. | There are a few places you'll need to be granted access to start your onboarding process to join the [[Tech Working Group]]. These first 3 steps require help from an existing TWG member. | ||
# [[Setup a user@social.coop forwarding email address]] | # [[Setup a user@social.coop forwarding email address]] and add the new forwarding email to the <code>tech.group</code> and <code>admin</code> email aliases | ||
# [https://git.coop/users/sign_up A git.coop account] | # [https://git.coop/users/sign_up A git.coop account] | ||
# [https://git.coop/groups/social.coop/tech/-/group_members Group Membership in the "social.coop/tech" project] | # [https://git.coop/groups/social.coop/tech/-/group_members Group Membership in the "social.coop/tech" project] | ||
| Line 27: | Line 27: | ||
pass show social.coop/path/to/secret | pass show social.coop/path/to/secret | ||
Latest revision as of 12:20, 30 October 2024
Up to: Tech Working Group
How to set new members up with TWG
There are a few places you'll need to be granted access to start your onboarding process to join the Tech Working Group. These first 3 steps require help from an existing TWG member.
- Setup a user@social.coop forwarding email address and add the new forwarding email to the
tech.groupandadminemail aliases - A git.coop account
- Group Membership in the "social.coop/tech" project
Once you have those things you can continue to the next step of creating two merge requests (same idea as a "pull request" on Github):
- Add your SSH public key to the ansible repo, in roles/server/files
- Add your GPG public key to the pass repo, in the keys folder
- In the second merge request, add the email address associated with your GPG key to the
.gpg-idfile.
Next you will need an existing TWG member to post a poll to Loomio about granting your server access.
Finally, someone with existing access will need to re-encrypt pass files with your new GPG key, granting you access to the infrastructure credentials.
You can get an overview of all the infrastructure using pass:
cd ~/.password-store/social.coop pass
To access any given pass secret:
pass show social.coop/path/to/secret