Onboarding New Tech Working Group Team Members: Difference between revisions
No edit summary |
No edit summary |
||
Line 13: | Line 13: | ||
# Add your SSH public key to the [https://git.coop/social.coop/tech/ansible/-/tree/master/roles/server/files/public-keys?ref_type=heads ansible repo, in roles/server/files] | # Add your SSH public key to the [https://git.coop/social.coop/tech/ansible/-/tree/master/roles/server/files/public-keys?ref_type=heads ansible repo, in roles/server/files] | ||
# Add your GPG public key to the [https://git.coop/social.coop/tech/pass/-/tree/master/keys?ref_type=heads pass repo, in the keys folder] | # Add your GPG public key to the [https://git.coop/social.coop/tech/pass/-/tree/master/keys?ref_type=heads pass repo, in the keys folder] | ||
# In the second merge request, add the email address associated with your GPG key to the <code>.gpg-id</code> file. | |||
Next you will need an existing TWG member to post [https://www.loomio.com/d/jrbG5tue/server-access a poll to Loomio] about granting your server access. | Next you will need an existing TWG member to post [https://www.loomio.com/d/jrbG5tue/server-access a poll to Loomio] about granting your server access. |
Revision as of 02:24, 24 September 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
- 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-id
file.
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 e-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
One gotcha: wiki
actually refers to join.social.coop.