Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

entries/github: Put this information in "Onboarding" or something similar? #28

Closed
signekb opened this issue Sep 5, 2023 · 1 comment · Fixed by #31
Closed

entries/github: Put this information in "Onboarding" or something similar? #28

signekb opened this issue Sep 5, 2023 · 1 comment · Fixed by #31
Assignees

Comments

@signekb
Copy link
Member

signekb commented Sep 5, 2023

team/entries/github.md

Lines 5 to 22 in 15f3eeb

## Setting up two-factor authentication (2FA)
We of course use GitHub for our work, so as a team member or contributor
you need to have a [GitHub account](https://github.com/join/). Since you
will likely also have access to our repositories to write and modify
content, we need to consider potential for security risks of your
account being compromised and impacts on our work. While we
organizationally have settings in place to minimize that risk, we
individually need to have security features in place.
For that reason, all internal contributors need to set up 2FA on their
GitHub account. Follow the steps within this [GitHub
documentation](https://docs.github.com/en/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication)
to set it up. While GitHub doesn't explicitly recommend any specific
time-based one-time password (TOTP) apps, good ones are [Google
Authenticator](https://support.google.com/accounts/answer/1066447?hl=en&ref_topic=2954345&sjid=1964065568409601298-EU)
or [Microsoft
Authenticator](https://www.microsoft.com/en-ww/security/mobile-authenticator-app).

This info would have been helpful yesterday, when I was invited to join the seedcase-project organisation (even though, it was fairly easy to figure out). I'm wondering if this info could be put somewhere more specifically to onboarding to ensure that it is seen before a new colleague spend time figuring it out on their own?

@signekb signekb assigned signekb and lwjohnst86 and unassigned signekb Sep 5, 2023
@lwjohnst86
Copy link
Member

That's very true! We need like a "onboarding checklist" or something.

@signekb signekb mentioned this issue Sep 6, 2023
@signekb signekb linked a pull request Sep 6, 2023 that will close this issue
@signekb signekb assigned signekb and unassigned lwjohnst86 Sep 29, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants