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

Finalizing Github setup for new team members #181

Closed
2 tasks done
ExperimentsInHonesty opened this issue Nov 20, 2019 · 0 comments
Closed
2 tasks done

Finalizing Github setup for new team members #181

ExperimentsInHonesty opened this issue Nov 20, 2019 · 0 comments
Assignees
Labels
APBMDA Move issue to project board, Move to Done, Archive Feature Missing This label means that the issue needs to be linked to a precise feature label. size: missing Status: Urgent Needs to be worked on immediately

Comments

@ExperimentsInHonesty
Copy link
Member

ExperimentsInHonesty commented Nov 20, 2019

Overview

All team members need to have 2 Factor Authentication setup on their Github accounts. And it is good (but optional) if they have their Hack for LA membership marked public.

Action Items

  • After hackforla github admin adds the new person to our github and to team, and notifies you, then send them the message via slack and ask them to follow up with you when completed with 2FA and membership public.
  • When completed, ask hfla github admin to check it.

Resources/Instructions

Message for you to send to new person:
_I just sent you an invite to the github account and the hack for la website team on github. If you don't see it in your email you can go to: https://github.com/hackforla

Once you have accepted (invite comes via email), please do the following:
Mark your own membership public
https://help.github.com/en/articles/publicizing-or-hiding-organization-membership#changing-the-visibility-of-your-organization-membership
Setup two factor authentication on your account
hackforla/governance#20_

Compelling reason to make your membership public:

Screen Shot 2019-11-20 at 10 43 50 AM

@ExperimentsInHonesty ExperimentsInHonesty added the Status: Urgent Needs to be worked on immediately label Nov 20, 2019
@ExperimentsInHonesty ExperimentsInHonesty added this to Ice box in Project Board via automation Nov 20, 2019
@ExperimentsInHonesty ExperimentsInHonesty moved this from Ice box to Prioritized backlog in Project Board Nov 20, 2019
@harishlingam harishlingam moved this from Prioritized backlog to In progress in Project Board Nov 20, 2019
@harishlingam harishlingam moved this from In progress to Done in Project Board Dec 23, 2019
@Providence-o Providence-o removed this from Done in Project Board Mar 8, 2022
@Providence-o Providence-o added this to Done in Issues Closed 13 months or more via automation Mar 8, 2022
@ExperimentsInHonesty ExperimentsInHonesty added the Feature Missing This label means that the issue needs to be linked to a precise feature label. label Aug 13, 2023
@ExperimentsInHonesty ExperimentsInHonesty added the APBMDA Move issue to project board, Move to Done, Archive label May 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
APBMDA Move issue to project board, Move to Done, Archive Feature Missing This label means that the issue needs to be linked to a precise feature label. size: missing Status: Urgent Needs to be worked on immediately
Development

No branches or pull requests

3 participants