Requiring 2FA for the ESLint GitHub organization
See original GitHub issueIn light of recent events, I think this would be a good time to start requiring 2FA to be enabled for members of the eslint
organization on GitHub. People in the organization (particularly TSC members) have a lot of access with their GitHub accounts, and it’s important for us and for our users that we keep the accounts safe.
Currently, 26 of the 34 members of the organization have 2FA enabled. Of the remaining 8, two are bot accounts (@eslintbot and @jquerybot) and two are TSC members. In order to do this, we would need to enable 2FA for all of the remaining accounts, otherwise those accounts would be removed from the organization when we started requiring 2FA. We would also have to ensure that the bot accounts are still able to function correctly with 2FA enabled, or we could remove them from the organization if their functionality has been superseded by eslint-github-bot
. (I think the @eslintbot account is still used to push commits during releases.)
Issue Analytics
- State:
- Created 5 years ago
- Reactions:7
- Comments:12 (11 by maintainers)
Top GitHub Comments
@jquerybot has been removed from the organization since it’s not used for anything anymore.
In the TSC meeting today, there seemed to be a consensus that we should plan to enable the setting two weeks from today (i.e. September 13th). However, there wasn’t a quorum present at the time.
@eslint/eslint-tsc Please add a 👍 to this comment if you’d like to approve enabling the setting on September 13th.