Changes

Jump to: navigation, search

GitHub

No change in size, 18:56, 25 October 2021
m
Fixing capitalization of GitHub
This page is specifically about [https://github.com/mozilla the "mozilla" organization on githubGitHub]. There are several other github GitHub organizations you may be interested in, cf. the incomplete list [[#other_github|below]].
<div id="contact">
{| class="wikitable"
Project owners and team maintainers may find the following information helpful when asking for access for a new team member (staff or community):
* We require the use of github GitHub teams when initially granting permissions to org members. (Collaborators have to be added individually.)* All members of the [https://github.com/mozilla/ Mozilla organization on githubGitHub] agree to be bound by [https://www.mozilla.org/en-US/about/governance/policies/commit/requirements/ Mozilla's Commit Access Requirements], and should follow the intent of the [https://www.mozilla.org/en-US/about/governance/policies/commit/access-policy/ Mozilla's Commit Access Policy] as much as practical. Of course, anyone interacting with Mozilla repositories agrees to [https://www.mozilla.org/en-US/about/governance/policies/participation/ Mozilla Community Participation Guidelines]
** "Outside Collaborator": repository admins can grant outside collaborator access to any GitHub login on a per repository basis. "Outside Collaborator" is roughly analogous to "Level 1a" access to Mozilla-hosted repositories.
** "Team Member": team maintainers can add GitHub users to a team, if they are already a member of the organization. If they are not yet a member of the organization, the ''team maintainer'' should [https://bugzilla.mozilla.org/enter_bug.cgi?assigned_to=nobody%40mozilla.org&bug_ignored=0&bug_severity=normal&bug_status=NEW&bug_type=task&cf_fx_iteration=---&cf_fx_points=---&comment=I%27ve%20read%20https%3A%2F%2Fwiki.mozilla.org%2FGitHub%23Team_Maintainers_.26_Project_Leads%2C%20and%20need%20help%20adding%20a%20contributor%20to%20the%20org%3A%0D%0A%0D%0AName%3A%20%0D%0AMozilla%20Email%3A%20%0D%0AGithub%20Profile%20link%3A%20%2AStaff%20%2A%2AMUST%2A%2A%20have%20their%20verified%20GitHub%20identity%20listed%20in%20their%20people.m.o%20entry%2A%0D%0AGithub%20Team%28s%29%20%2AREQUIRED%2A%3A%20%0D%0A%0D%0AIf%20this%20is%20not%20being%20requested%20by%20a%20team%20maintainer%2C%20please%20request%20their%20approval%20via%20need-info.&component=Github%3A%20Administration&contenttypemethod=list&contenttypeselection=text%2Fplain&defined_groups=1&filed_via=standard_form&flag_type-4=X&flag_type-607=X&flag_type-800=X&flag_type-803=X&flag_type-936=X&form_name=enter_bug&maketemplate=Remember%20values%20as%20bookmarkable%20template&op_sys=Unspecified&priority=--&product=mozilla.org&rep_platform=Unspecified&target_milestone=---&version=other file a bug using this link] to add you 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.
* 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.
=== Should I make a separate github GitHub organization or just create a repository in an existing one? ===
This is a personal preference, in general. (Some product lines may have policies about source code locations.) If you have a large enough project or organization feel free. We suggest you use the strategies and recommendations here as a model to manage the details. Additional resources on establishing an organization are:
* [https://mana.mozilla.org/wiki/display/POLICIES/Standard%3A+GitHub+repositories+and+organizations Mozilla Standards] <small>''login required''</small>
* [[/Repository Security|Guidelines for securing sensitive repositories]]
* If you need any paid services, contact github GitHub owners for access to [https://github.com/mozilla/admin_for_mozilla_private/wiki/Billing-Notes Billing Notes]
=== Forking vs Transferring ===
# Choose which teams should be given access. All chosen teams will have only 'read' access at this point.
# [https://bugzilla.mozilla.org/enter_bug.cgi?assigned_to=nobody%40mozilla.org&bug_file_loc=http%3A%2F%2F&bug_ignored=0&bug_severity=normal&bug_status=NEW&cf_fx_iteration=---&cf_fx_points=---&comment=I%20just%20transferred%20the%20NAME_HERE%20repository%20to%20the%20ORG_NAME_HERE%20organization%2C%20and%20thus%20no%20longer%20have%20admin%20access.%0D%0A%0D%0APlease%20enable%20admin%20access%20for%3A%0D%0A-%20the%20TEAM_NAME%20team%20%28preferred%29%2C%20or%0D%0A-%20just%20me%20--%20I%27ll%20take%20care%20of%20the%20rest&component=Github%3A%20Administration&contenttypemethod=list&contenttypeselection=text%2Fplain&defined_groups=1&flag_type-4=X&flag_type-607=X&flag_type-800=X&flag_type-803=X&form_name=enter_bug&maketemplate=Remember%20values%20as%20bookmarkable%20template&op_sys=Unspecified&priority=--&product=mozilla.org&rep_platform=Unspecified&short_desc=Admin%20access%20needed%20to%20transferred%20repository&target_milestone=---&version=other File a bug] to grant admin permissions to a team or yourself. {{note|As soon as you transfer, your repository will be in "limbo" (only you will have write access) due to a GitHub "feature" (see [https://docs.github.com/en/free-pro-team@latest/github/administering-a-repository/transferring-a-repository docs]). Make arrangements in advance to have an owner available to process the bug.|gotcha}}
# Fork the repo from Mozilla (mozilla/myrepo) back to your account (recreating myuser/myrepo). While the transferred repo becomes the root of the network on GitHub (e.g. all forks are now forks of mozilla/myrepo) other users may be pointing to your repo by URL. (Optional, github GitHub will redirect old URLs for transfers, but you probably want a local repo if you use the PR workflow.)
=== Do I need to be an owner to create repositories? ===
<div id="other_github"></div>
=== Is "mozilla" the only github GitHub "organization" related to Mozilla? ===No, there are plenty of Mozilla-related "organizations" on githubGitHub. As a rule of thumb, initiatives that create a large number of sub-repositories will create their own "organization". Here is a (probably incomplete) list of them:
<div style="display: flex; flex-flow: row wrap; width: 100%;">
<div style="order: 1; flex-grow: 3; margin: 0.5em; border: 0.1em solid darkgreen; padding: 0.5em; background-color: palegreen; min-width: auto; text-align: center;">
|}
=== Are there other unofficial or Mozilla-related repositories hosted on GithubGitHub? ===
Why, yes! In no particular order:
Confirm
107
edits

Navigation menu