GitHub: Difference between revisions

Jump to navigation Jump to search
206 bytes added ,  4 January 2017
Add cancellation policy
(remove redundant and obsolete reference to 2FA requirement)
(Add cancellation policy)
Line 86: Line 86:
** "Team Member": team maintainers can add GitHub users to a team, if they are already a member of the organization. If you are not yet a member of the organization, the team maintainer should [[#contact|request your addition]] to their team, as a form of vouching. "Team Member" is roughly analogous to "Level 2" or "Level 3", with the distinction being the content of the repositories managed by the team.
** "Team Member": team maintainers can add GitHub users to a team, if they are already a member of the organization. If you are not yet a member of the organization, the team maintainer should [[#contact|request your addition]] to their team, as a form of vouching. "Team Member" is roughly analogous to "Level 2" or "Level 3", with the distinction being the content of the repositories managed by the team.


{{note| As of June 30, 2016, all members of the Mozilla organization on github '''MUST''' have [https://help.github.com/articles/about-two-factor-authentication/ 2FA enabled].|reminder}}
{{note| As of January 6, 2017, we will start cancelling any invitation to the organization which is not accepted within 2 weeks of the invitation.}}
 
{{note| As of June 30, 2016, all members of the Mozilla organization on GitHub '''MUST''' have [https://help.github.com/articles/about-two-factor-authentication/ 2FA enabled].|reminder}}


{{note| Automation accounts are also required to have 2FA enabled. Scripts should use [https://help.github.com/articles/creating-an-access-token-for-command-line-use/ access tokens] with minimum permissions to accomplish the task.}}
{{note| Automation accounts are also required to have 2FA enabled. Scripts should use [https://help.github.com/articles/creating-an-access-token-for-command-line-use/ access tokens] with minimum permissions to accomplish the task.}}


The best way to ask for a Contributor to be invited to the organization is to [https://bugzilla.mozilla.org/enter_bug.cgi?comment=I%27ve%20read%20https%3A%2F%2Fwiki.mozilla.org%2FGithub%2C%20and%20need%20help%20with%20the%20following.%0D%0A%0D%0A&component=Github%3A%20Administration&form_name=enter_bug&product=mozilla.org& open a bug] including the contributor's GitHub login, and the team(s) they need access to.
The best way to ask for a Contributor to be invited to the organization is to [https://bugzilla.mozilla.org/enter_bug.cgi?comment=I%27ve%20read%20https%3A%2F%2Fwiki.mozilla.org%2FGithub%2C%20and%20need%20help%20with%20the%20following.%0D%0A%0D%0A&component=Github%3A%20Administration&form_name=enter_bug&product=mozilla.org& open a bug] including the contributor's GitHub login, and the team(s) they need access to. A team maintainer or manager should approve in the bug.


=== Should I make a separate github organization or just create a repository in an existing one? ===
=== Should I make a separate github organization or just create a repository in an existing one? ===
Confirmed users
1,364

edits

Navigation menu