llnl / llnl/open-source-guidelines
Requiring 2FA?
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 7
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Description
What do folks, e.g. @LLNL/admins think about requiring GitHub 2FA for the organization? I'm inclined to do this, but there are some potential issues:
- Some users don't have 2FA enabled, would need to enable or get booted from the org
- Org members: https://github.com/orgs/LLNL/people?utf8=✓&query=%20two-factor%3Adisabled
- Org collaborators: https://github.com/orgs/LLNL/outside-collaborators?utf8=✓&query=%20two-factor%3Adisabled
- What about locations that don't allow phones on site?
- Response on this from GitHub support has been that users can use recovery codes as 1 time 2FA codes. Don't know of a better way...
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the discussion in issue #9 and the linked GitHub Support response. Resolve the policy questions for organization members, outside collaborators, and sites that restrict phones; the work is done when the organization’s 2FA decision and resulting guidance are documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github
- Domain
- authentication, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100