|
|
| (43 intermediate revisions by 8 users not shown) |
| Line 1: |
Line 1: |
| This page is specifically about [https://github.com/mozilla the "mozilla" organization on GitHub]. There are several other GitHub organizations you may be interested in, cf. the incomplete list [[#other_github|below]].
| | '''2026-10-07: GitHub Enterprise ownership has been transitioned from IT to CloudEng.''' Customer documentation has been moved to [https://mozilla-hub.atlassian.net/wiki/spaces/GHE/pages/3087892663/Getting+help+with+GitHub Getting help with GitHub] in Confluence. Please update any links to this page accordingly. If you are an external contributor, please reach out to your sponsor in the appropriate [https://chat.mozilla.org/ Matrix channel] for support. |
| <div id="contact">
| |
| {| class="wikitable"
| |
| |-
| |
| ! [[File:Red_question_mark.png|72px|Question Mark]] Do you have a GitHub administration question for an org?<br > See [[#other_github|table]] for contact info for each organization.
| |
| |}
| |
|
| |
|
| == News ==
| | This content has been moved to: https://mozilla-hub.atlassian.net/wiki/spaces/GHE/pages/3087892663/Getting+help+with+GitHub |
| * 2021-01-21 - [[/Converting to a "2FA required policy"|Converting to a "2FA required policy" for an organization]]/
| |
| * 2021-01-19 - [[/Changing Default Branch|Notes on renaming the default branch of your GitHub repositories]].
| |
| * 2019-02-19 - Mozilla's Code of Conduct is required to be included in every repository, following [[/Repository Requirements|this procedure]].
| |
| * 2018-03-29 - new [[/Repository Security|Guidelines for securing sensitive repositories]] published. These are good practices for any repository that does "releases", and some groups my require adherence on their repositories.
| |
| | |
| == Recommendations and FAQ ==
| |
| | |
| The actions below are specifically for the 'mozilla' organization on GitHub. Other organizations may have different or additional procedure. Please refer to the [[#other_github|other organizations]] table below for the proper service request address and contact information.
| |
| === SAML or SSO questions ===
| |
| As we move into GitHub Enterprise, we're not changing permissions, but we are requiring people to use people.mozilla.org to authenticate into Mozilla operated spaces. Signing up in people.m.o is automatic if you're an employee, but if you're a contributor, you can create an account using a Firefox account.
| |
| Directions and a FAQ around SAML are [[GitHub/GHE SAML User FAQ|here]]
| |
| | |
| ==== Getting asked to SAML in every day ====
| |
| Sadly this is unavoidable with the stack of tech we have - we're continuing to evaluate options to see if there's any path to allowing longer SAML sessions. But at this point we're limited to 24 hours.
| |
| | |
| ==== Needing to SAML in to see even public things ====
| |
| This is a known bug on GitHub's part - their documentation (at the time of this writing) says that only private or org things need to SAML in - but the behavior is that access to ANY org resource requires a valid SAML session. | |
| | |
| === Where should I ask additional questions? ===
| |
| * Please use the '''[[#other_github|contact list]]''' to find the best address.
| |
| * If the issue relates to the [https://github.com/Mozilla Mozilla] org, then you can send an email to '''{{emailentry|github-owners|mozilla.org|at=is}}''' and one of the volunteers will respond.
| |
| * For other orgs, the volunteers in the [https://chat.mozilla.org/#/room/#github-admin:mozilla.org #github-admin] room on Matrix may be able to point you in the correct direction.
| |
| | |
| === How do I hook up a new GitHub Actions or 3rd party application to a repository in the mozilla org? ===
| |
| {{note|There are now multiple 3rd party application types. "GitHub Apps" (nee integrations) are the new approach and preferred.|gotcha}}
| |
| {{note|Some 3rd party apps use GitHub as an OAuth identity provider for their website (e.g. for a dashboard). An ''OAuth Application'' will block the installation process if the app is not already approved. The "Request access" block is what this section describes.|gotcha}}
| |
| | |
| Each type has it's own installation and approval process. Please follow the instructions in the correct section below.
| |
| | |
| ==== GitHub Actions ====
| |
| [https://help.github.com/en/actions/getting-started-with-github-actions/about-github-actions GitHub Actions] allow automation to be initiated by various repository events. GitHub Actions are now available for all public repositories. Each organization makes a decision on whether or not they should be enabled. Check with your organization owners if you have questions.
| |
| | |
| {{note|GitHub Actions have not yet been fully evaluated for use on "sensitive repositories". The current guidance is to only use actions authored by GitHub or your development team. Please work with your security team if you wish to utilize non-GitHub-authored GitHub Actions on a sensitive repository.|gotcha}}
| |
| | |
| To request a non-GitHub-authored action to be used in the "mozilla" organization, follow the procedure for requesting approval for a new GitHub App, immediately below.
| |
| | |
| ==== GitHub Apps Installation & Approval Process ====
| |
| | |
| GitHub Apps (formerly called "integrations") are "Installed" into either the entire organization, or into individual repositories. Each integration has a documented and granular access to repository resources. This is good.
| |
| | |
| However, the GitHub App installation can only be done by an organization owner, who may have to do additional housekeeping. This is not so good, so please plan accordingly (you may need to coordinate with [[#contact|GitHub owners]]).
| |
| | |
| * File a request using this [https://bugzilla.mozilla.org/enter_bug.cgi?comment=I%20want%20to%20use%20the%20NAME_HERE%20addon%20in%20ORG_NAME_HERE%20for%20the%20following%20reasons%3A%0D%0A%0D%0ABelow%20are%20my%20answers%20to%20your%20stock%20questions%3A%0D%0A%0D%0A%2A%2A%20Which%20repositories%20do%20you%20want%20to%20have%20access%3F%20%28all%20or%20list%29%0D%0A%0D%0A%2A%2A%20Are%20any%20of%20those%20repositories%20private%3F%0D%0A%0D%0A%2A%2A%20Provide%20link%20to%20vendor%27s%20description%20of%20permissions%20needed%20and%20why%0D%0A%0D%0A%2A%2A%20Provide%20the%20Install%20link%20for%20a%20GitHub%20app%0D%0A&component=Github%3A%20Administration&product=mozilla.org&short_desc=Assess%20use%20of%20external%20addon%20NAME_HERE%20in%20Mozilla%27s%20GitHub%20organization%20ORG_NAME_HERE bug template]
| |
| * Include answers to the questions prompted for in the above template. Additional notes:
| |
| ** ''Which repositories do you want to have access? (all or list)'' -- "All" will rarely be granted - every repository should have control over anything that can access their repository.
| |
| ** ''Are any of those repositories private?'' -- In general, OAuth apps will not be granted access to private repositories, as that grants access to ''all'' private repositories.
| |
| ** ''Provide link to vendor's description of permissions needed and why'' -- Hopefully they have this documented, or at least provide a screenshot of the authorization screen which lists the permissions. If not, we may ask you (the requestor) to engage with the app's support team to obtain the answers.
| |
| ** ''Provide the Install link for a GitHub app'' -- mandatory, as we can't install the app without it.
| |
| | |
| * If you are not an "admin" for the repository, an "admin" will have to approve the request. Please set a "Need Info" on the appropriate repository admin.
| |
| | |
| ===== Initial Installation =====
| |
| If this is the first time this GitHub App is being installed in the organization, a few extra checks and coordination are needed. An organization owner will need to perform these steps:
| |
| * Determine if the GitHub App previously had an OAUTH version in use in the same org. (The simplest way is to see if the app is listed under the "Third-party Application" section of the organization settings page. ''Any mention'' -- including "declined" -- counts as "in use" for this purpose.)
| |
| ** If the OAuth app was in use, check the app installation documentation to see if there are any caveats. (We've only seen one app transition where there was an impact, but better safe than sorry.)
| |
| ** If there are caveats that apply, ask the requestor to contact all current repositories using the classic OAUTH application to coordinate, cc'ing [[#contact|GitHub owners]]. This task is non-trivial, you usually need to access the OAuth app's dashboard, and have knowledge of how the app works. ('''Do NOT''' authenticate to any OAuth app with your owner account.)
| |
| * Install the GitHub app for "specific repositories", and enable the ones in the request.
| |
| | |
| '''Please do not install GitHub apps with organization wide scope without first discussing with [[#contact|GitHub owners]].'''
| |
| | |
| ===== Additional Installations or Removals =====
| |
| If the GitHub App has already been installed in the organization, the new repository simply needs to be added or removed from the list. An organization owner has to make this change. Please still [https://bugzilla.mozilla.org/enter_bug.cgi?comment=I%20want%20to%20use%20the%20NAME_HERE%20addon%20in%20ORG_NAME_HERE%20for%20the%20following%20reasons%3A%0D%0A%0D%0ABelow%20are%20my%20answers%20to%20your%20stock%20questions%3A%0D%0A%0D%0A%2A%2A%20Which%20repositories%20do%20you%20want%20to%20have%20access%3F%20%28all%20or%20list%29%0D%0A%0D%0A%2A%2A%20Are%20any%20of%20those%20repositories%20private%3F%0D%0A%0D%0A%2A%2A%20Provide%20link%20to%20vendor%27s%20description%20of%20permissions%20needed%20and%20why%0D%0A%0D%0A%2A%2A%20Provide%20the%20Install%20link%20for%20a%20GitHub%20app%0D%0A&component=Github%3A%20Administration&product=mozilla.org&short_desc=Assess%20use%20of%20external%20addon%20NAME_HERE%20in%20Mozilla%27s%20GitHub%20organization%20ORG_NAME_HERE file a bug]. As before, a repository admin has to approve the request.
| |
| | |
| If you're an org owner, you can [https://github.com/organizations/mozilla/settings/installations see what has already been installed].
| |
| | |
| ==== OAUTH (classic) Applications ====
| |
| | |
| * Authorizing an application to work with GitHub utilizes the permissions your account has -- so, any repositories you have access to the application will have access to as well (including private ones). If you want to grant access to an application that no one else has used with the Mozilla organization yet you'll see a "Request access" button during the set up flow. You'll need to click that button to request approval. See below for an example:
| |
| | |
| [[File:github_approval.png]]
| |
| | |
| * In some cases, the application does not need to be "approved" to function correctly, as it has read only access to any public repository. (Some applications only want write access to help you configure the application first time.)
| |
| | |
| * In other cases, the application does need write permission, and/or permission to read a private repository. In these cases, open a bug using [https://bugzilla.mozilla.org/enter_bug.cgi?cc=comment=I%20want%20to%20use%20the%20NAME_HERE%20addon%20in%20ORG_NAME_HERE%20for%20the%20following%20reasons%3A%0D%0A%0D%0ABelow%20are%20my%20answers%20to%20your%20stock%20questions%3A%0D%0A%0D%0A%2A%2A%20Which%20repositories%20do%20you%20want%20to%20have%20access%3F%20%28all%20or%20list%29%0D%0A%0D%0A%2A%2A%20Are%20any%20of%20those%20repositories%20private%3F%0D%0A%0D%0A%2A%2A%20Provide%20link%20to%20vendor%27s%20description%20of%20permissions%20needed%20and%20why%0D%0A%0D%0A%2A%2A%20Provide%20the%20Install%20link%20for%20a%20GitHub%20app%0D%0A&component=Github%3A%20Administration&product=mozilla.org&short_desc=Assess%20use%20of%20external%20addon%20NAME_HERE%20in%20Mozilla%27s%20GitHub%20organization%20ORG_NAME_HERE this template].
| |
| ** Please be sure to have clicked the "Request Approval" link before submitting bug.
| |
| * Include answers to these questions:
| |
| ** Provide link to vendor's description of permissions needed and why
| |
| ** Provide installation instructions (both may be needed):
| |
| | |
| === Reviewing owners and permissions ===
| |
| As an owner or repository admin you're responsible for maintaining the list of people with access to your projects. Please be active and prudent about maintaining this list.
| |
| | |
| === Can I be an Owner of the Mozilla Organization? ===
| |
| The Owners group on GitHub has complete administrative power and will be limited to a minimal number of people and reviewed regularly. If a person is an owner, they are expected to actively participate in the group and assist others as requested. Owners will be added as a need arises (for example, support in another timezone) as determined by the current owners.
| |
| | |
| <div id="join"> </div>
| |
| === Can I be a Member of the Mozilla Organization? ===
| |
| No one automatically becomes a member of any of our GitHub Organizations, even staff. We require everyone to be "sponsored" for membership by being invited to a specific team, as outlined below.
| |
| | |
| {{Note|
| |
| Good news! You do not need to be a member of the Mozilla organization on GitHub before you can contribute to Mozilla!!!! We have several sites which can help you find the best fit for contribution:
| |
| * General [https://www.mozilla.org/en-US/contribute/ volunteering options],
| |
| * Or pick from [http://whatcanidoformozilla.org/ these areas],
| |
| * Or jump right into [http://www.joshmatthews.net/bugsahoy/ fixing a bug].
| |
| * If you're already a contributor (THANK YOU!) looking for a place to have your work recognized (even if not coding related), please see the [https://www.mozilla.org/credits/FAQ Credits FAQ] for inclusion in the [https://www.mozilla.org/credits/ credits].|reminder}}
| |
| | |
| Once you're working on a project, the project leaders and/or team maintainers can help you get access to anything you need. Instructions for them are directly following.
| |
| | |
| ==== Team Maintainers & Project Leads ====
| |
| | |
| 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 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 GitHub] 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.
| |
| | |
| To get access for a new Contributor, please have the ''team maintainer'' or ''repository admin'' [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], and fill in the details.
| |
| | |
| '''Please Note:'''
| |
| * All organization members '''MUST''' have an entry on people.mozilla.org and '''MUST''' have their verified GitHub identity entered there.
| |
| * GitHub cancels any invitation which is not accepted within 2 weeks.
| |
| * All members and outside contributors of the Mozilla organization on GitHub '''MUST''' have [https://help.github.com/articles/about-two-factor-authentication/ 2FA enabled].
| |
| * 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 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 owners for access to [https://github.com/mozilla/admin_for_mozilla_private/wiki/Billing-Notes Billing Notes]
| |
| | |
| === Forking vs Transferring ===
| |
| '''Do not "fork" a repository into a Mozilla organization.''' Doing so gives ''every team in the org'' rights to it. There are a number of limitations to just pushing your repo's content into a new repo under mozilla (you loose all GitHub metadata). Refer to [https://docs.github.com/en/free-pro-team@latest/github/administering-a-repository/transferring-a-repository GitHub's docs] for details.
| |
| | |
| If you have created a repo on your own account (for example, myuser/myrepo) and it should live under the Mozilla organization, here are the steps:
| |
| | |
| # If you're not a member of any team, talk to an [[#contact|org admin]].
| |
| # Under the repo admin, transfer ownership to the Mozilla organization. If you don't see this option, return to step 1.
| |
| # 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 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? ===
| |
| Not in the 'mozilla' organization. If you are a member, you can create a repository. Other organizations may restrict repository creation. However, it's preferred that you create repositories in the context of a team. Teams are created [https://github.com/orgs/mozilla/teams here], if necessary. Once you have created a repo, you can configure it to give rights to members of particular teams.
| |
| | |
| {{note|Remember that all repositories must comply with the [[GitHub/Repository Requirements]].|reminder}}
| |
| | |
| Being an open source company, Mozilla tries to do things in the open. However, the need for private repositories is clear for various non-public data and other business reasons, and in order to track them, please request private repositories using this [https://bugzilla.mozilla.org/enter_bug.cgi?assigned_to=nobody%40mozilla.org&bug_ignored=0&bug_severity=--&bug_status=NEW&bug_type=task&cf_fx_iteration=---&cf_fx_points=---&comment=I%27ve%20read%20all%20of%20the%20%5Brepository%20creation%5D%5B1%5D%20section%2C%20and%20want%20to%20request%20a%20private%20repository.%20I%27ve%20filled%20in%20all%20the%20required%20fields.%0D%0A%0D%0AOrg%20for%20repo%3A%20REQUIRED%0D%0AName%20of%20Repository%3A%20%20REQUIRED%0D%0ALink%20to%20your%20people.m.o%20entry%20with%20verified%20GitHub%20login%3A%20REQUIRED%0D%0A%0D%0A%5BData%20Classification%5D%5B2%5D%20of%20data%20in%20repo%3A%20REQUIRED%0D%0AOther%20business%20justification%20for%20private%20repo%3A%0D%0AWhen%20can%20the%20repository%20be%20made%20public%3F%20REQUIRED%0D%0A%0D%0A%5B1%5D%3A%20https%3A%2F%2Fwiki.mozilla.org%2FGitHub%23Do_I_need_to_be_an_owner_to_create_repositories.3F%0D%0A%5B2%5D%3A%20https%3A%2F%2Fwiki.mozilla.org%2FSecurity%2FData_Classification%0D%0A&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&groups=mozilla-employee-confidential&maketemplate=Remember%20values%20as%20bookmarkable%20template&op_sys=Unspecified&priority=--&product=mozilla.org&qa_contact=cknowles%40mozilla.com&rep_platform=Unspecified&short_desc=Request%20for%20a%20Private%20Repository%20in%20the%20ORGNAME%20GitHub%20organization&target_milestone=---&version=other Bugzilla template]. Be sure to answer all questions marked 'REQUIRED' in the form. As well as the ORGNAME in the title.
| |
| | |
| As the creator, you will automatically have "admin" permissions on the repository. Repository Admins are responsible for the security settings of the repository. This includes approving (or not) requests for GitHub Apps to be added to the app.
| |
| | |
| Please review all the settings for your new repository, and disable features you will not be using. The default values can change, and new services added, so specific guidance can't be given. But do you really need that wiki? Or the project board? You can always enable them later if you decide you need them.
| |
| | |
| === We have sensitive code or data in this repository - any extra steps I should take? ===
| |
| Yes. Even if your repository is private, there are steps you can take to ensure you know if something has changed. See the [[GitHub/Repository Security]] page for additional information and a checklist.
| |
| | |
| === We're done with this project - what should we do with the repository? ===
| |
| | |
| That is really up to the team. However, if you have forks or other active user participation, it's a good idea to be clear about the status of Mozilla's commitment to the project. Your options include:
| |
| * Delete the repo (obviously the worst alternative).
| |
| * Add the [http://unmaintained.tech/ Unmaintained] badge to the readme
| |
| * Archive the repository, using [https://help.github.com/articles/about-archiving-repositories/ GitHub's suggestions].
| |
| | |
| '''PLEASE''' make sure the repository is clearly licensed before leaving it. Without a license, many other folks can not build upon your work.
| |
| In most Mozilla controlled GitHub organizations deletion is only an option for owners of the org - file a bug [https://bugzilla.mozilla.org/enter_bug.cgi?product=mozilla.org&component=Github%3A+Administration here], with any reasoning and we're happy to discuss.
| |
| | |
| === Are there requirements for when or how I should create a new team? ===
| |
| No. When requirements were proposed they all seemed too rigid and time consuming. Instead we recommend staying flexible and using good naming and documentation for projects (similar to naming CSS classes or variables).
| |
| | |
| On large teams we recommend you separate teams for read/write and repository administration.
| |
| | |
| <div id="other_github"></div>
| |
| === Is "mozilla" the only GitHub "organization" related to Mozilla? ===
| |
| No, there are plenty of Mozilla-related "organizations" on GitHub. 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;">
| |
| <big>'''NOTE:''' All GitHub Organizations in this section are subject to the [[GitHub/Repository_Requirements|Repository Requirements]].</big>
| |
| </div>
| |
| </div>
| |
| <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;">
| |
| <big>'''NOTE:''' As Mozilla IT works to consolidate GitHub support in the Mozilla related organizations, it is often a good idea to file any bugs [https://bugzilla.mozilla.org/enter_bug.cgi?product=mozilla.org&component=Github%3A+Administration here], and if needed, we will work with you to relocate the request.</big>
| |
| </div>
| |
| </div>
| |
| | |
| {| class="wikitable sortable"
| |
| |-
| |
| ! Organization !! Description !! Contact Owner !! Service Requests
| |
| |-
| |
| | [https://github.com/mozilla mozilla] || Mozilla main organization || Matrix [https://chat.mozilla.org/#/room/#github-admin:mozilla.org #github-admin:mozilla.org]; Email {{emailentry|github-owners|mozilla.org|at=is}} || Please check above for a more specific link, otherwise use [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& mozilla.org :: Github: Administration]
| |
| |-
| |
| | [https://github.com/mozilla-it mozilla-it] || Mozilla IT's repositories || Matrix [https://chat.mozilla.org/#/room/#github-admin:mozilla.org #github-admin:mozilla.org]; Email {{emailentry|github-owners|mozilla.org|at=is}} || [https://bugzilla.mozilla.org/enter_bug.cgi?product=mozilla.org&component=Github%3A+Administration Bug here.]
| |
| |-
| |
| |[https://github.com/mozillabrasil mozillabrasil] || Mozilla Brazil|| ?
| |
| |-
| |
| | [https://github.com/bugzilla bugzilla] || Bugzilla (the product, not bugzilla.mozilla.org) || #bugzilla||
| |
| |-
| |
| | [https://github.com/drumbeat-badge-sprint drumbeat-badge-sprint] || Drumbeat Badge Lab || ?||
| |
| |-
| |
| | [https://github.com/hackasaurus hackasaurus] || Hackasaurus || ?||
| |
| |-
| |
| | [https://github.com/jetpack-labs jetpack-labs] || Jetpack Labs || ?||
| |
| |-
| |
| | [https://github.com/mdn mdn] || Mozilla Developer Network || [https://github.com/jwhitlock John Whitlock]||
| |
| |-
| |
| | [https://github.com/mozbrick mozbrick] || Mozilla Brick (web components library) || ?||
| |
| |-
| |
| | [https://github.com/mozilla-applied-ml mozilla-applied-ml] || MAML - Mozilla Applied Machine Learning || maml-github@mozilla.com ||
| |
| |-
| |
| | [https://github.com/mozilla-appmaker mozilla-appmaker] || Mozilla Appmaker || ?||
| |
| |-
| |
| | [https://github.com/mozilla-b2g mozilla-b2g] || Mozilla Boot2Gecko / Firefox OS || ?||
| |
| |-
| |
| | [https://github.com/mozilla-bteam mozilla-bteam] || Bugzilla.Mozilla.org || #bteam||
| |
| |-
| |
| | [https://github.com/mozilla-cit mozilla-cit] || Mozilla Community Ops || {{Mozillians|tanner|Tanner Filip}} or {{Mozillians|yalam96|Yousef Alam}}||
| |
| |-
| |
| | [https://github.com/mozilla-comm mozilla-comm] || Calendaring and Messaging related projects || ?||
| |
| |-
| |
| | [https://github.com/mozilla-cordova mozilla-cordova] || Firefox OS Support for Apache Cordova || ?||
| |
| |-
| |
| | [https://github.com/mozilla-iam mozilla-iam] || Mozilla's identity and access management || atoll || [https://bugzilla.mozilla.org/enter_bug.cgi?product=mozilla.org&component=Github%3A+Administration Bug here.]
| |
| |-
| |
| | [https://github.com/mozilla-iot mozilla-iot] || Mozilla's Internet of Things program || {{Mozillian|dbryant|David Bryant}}, {{Mozillian|bfrancis|Ben Francis}}|| No longer active. Has transitioned to community ownership using new organization [https://github.com/WebThingsIO/ WebThingsIO].
| |
| |-
| |
| | [https://github.com/mozilla-lockbox mozilla-lockbox] || Mozilla Lockbox iOS, Android, desktop extension || [https://github.com/orgs/mozilla-lockbox/people?utf8=%E2%9C%93&query=role%3Aowner mozilla-lockbox owners]||
| |
| |-
| |
| | [https://github.com/mozilla-metrics mozilla-metrics] || Mozilla Metrics || ?||
| |
| |-
| |
| | [https://github.com/mozilla-platform-ops mozilla-platform-ops] || Mozilla Platform Operations || [[Platform_Operations]]||
| |
| |-
| |
| | [https://github.com/mozilla-raptor mozilla-raptor] || Mozilla Raptor / Firefox OS Performance || {{Mozillian|eliperelman|Eli Perelman}}, {{Mozillian|rwood|Rob Wood}}||
| |
| |-
| |
| | [https://github.com/mozilla-releng mozilla-releng] || Mozilla Release Engineering || #releng||
| |
| |-
| |
| | [https://github.com/mozilla-services mozilla-services] || Mozilla Services || [https://github.com/orgs/mozilla-services/people?utf8=%E2%9C%93&query=role%3Aowner mozilla-services owners]|| [https://github.com/mozilla-services/github-management/issues Open Issue]
| |
| |-
| |
| | [https://github.com/mozilla-mobile/ mozilla-mobile] || Mobile: Android Product Team & Firefox iOS teams || [https://github.com/orgs/mozilla-mobile/people?utf8=%E2%9C%93&query=role%3Aowner mozilla-mobile owners]||
| |
| |-
| |
| | [https://github.com/mozilla-spidermonkey mozilla-spidermonkey] || Mozilla SpiderMonkey Team tools and embedding info || {{Mozillian|tcampbell|Ted Campbell}}; Matrix #spidermonkey:mozilla.org ||
| |
| |-
| |
| | [https://github.com/mozilla-standards mozilla-standards] || Mozilla Standards (for IPR Contributions) || [https://mozillians.org/u/dbaron/ dbaron], [https://mozillians.org/u/annevk/ annevk]||
| |
| |-
| |
| | [https://github.com/mozilla-svcops mozilla-svcops] || Mozilla Cloud Services Ops || {{Mozillian|relud|Daniel Thornton}}||
| |
| |-
| |
| | [https://github.com/Mozilla-TWQA Mozilla-TWQA] || Mozilla Taiwan QA || ?||
| |
| |-
| |
| | [https://github.com/mozillahispano mozillahispano] || Mozilla Hispano || ?||
| |
| |-
| |
| | [https://github.com/MozillaReality MozillaReality] || Mozilla Mixed Reality program || {{Mozillian|estanley|Erica Stanley}}||
| |
| |-
| |
| | [https://github.com/MozillaResearch MozillaResearch ] || Mozilla Research space|| {{Mozillian|larsberg|Lars Bergstrom}}||
| |
| |-
| |
| | [https://github.com/MozillaScience MozillaScience] || Mozilla Science Lab || ?||
| |
| |-
| |
| | [https://github.com/MozillaSecurity MozillaSecurity] || Mozilla Platform Fuzzing Team master repo with many fuzzing tools under it. || ?||
| |
| |-
| |
| | [https://github.com/MozillaWiki MozillaWiki] || MozillaWiki (wiki.mozilla.org) || {{Mozillian|ckoehler|Christie Koehler}}, {{Mozillian|gphemsley|Gordon P. Hemsley}}||
| |
| |-
| |
| | [https://github.com/mozillayvr mozillayvr] || Mozilla Vancouver @MozillaYVR || {{Mozillian|bclark|Brian Clark}}, {{Mozillian|shobson|Stephanie Hobson}}||
| |
| |-
| |
| | [https://github.com/mozfr mozfr] || Mozilla Francophone ||||
| |
| |-
| |
| | [https://github.com/opennews opennews] || Knight-Mozilla OpenNews || ?||
| |
| |-
| |
| | [https://github.com/rust-lang rust-lang] || The Rust Programming Language || {{Mozillian|aturon|Aaron Turon}}||
| |
| |-
| |
| | [https://github.com/servo servo] || Servo (browser engine written in Rust) || {{Mozillian|larsberg|Lars Bergstrom}}, {{Mozillian|jdm|Josh Matthews}}||
| |
| |-
| |
| | [https://github.com/mozilla-l10n mozilla-l10n] || Mozilla l10n-drivers team || Francesco Lodolo https://mozillians.org/u/flod/||
| |
| |-
| |
| | [https://github.com/taskcluster taskcluster] || [[TaskCluster]] Team || [https://github.com/gregarndt Greg Arndt]||
| |
| |-
| |
| | [https://github.com/MozillaCH MozillaCH] || Mozilla [[Switzerland]] || {{Mozillian|mkohler|Michael Kohler}}, {{Mozillian|freaktechnik|freaktechnik}}||
| |
| |-
| |
| | [https://github.com/mozmeao MozMEAO] || Mozilla [[Marketing]] || {{Mozillian|bensternthal|Benjamin Sternthal}}, {{Mozillian|pmac|Paul McLanahan}}|[https://bugzilla.mozilla.org/enter_bug.cgi?product=mozilla.org&component=Github%3A+Administration Bug here.]|
| |
| |-
| |
| | [https://github.com/mozilla-payments mozilla-payments] || Implementation of Web Payment APIs || {{Mozillian|Marcos Caceres}}||
| |
| |-
| |
| | [https://github.com/mozilla-jetpack mozilla-jetpack] || Resources for Mozilla's Add-on SDK || ?||
| |
| |-
| |
| | [https://github.com/web-ext-experiments web-ext-experiments] || WebExtension API Experiments || {{Mozillian|andym|Andy McKay}}||
| |
| |-
| |
| | [https://github.com/mozilla-conduit mozilla-conduit] || Mozilla Conduit work || {{Mozillian|glob|glob}}||
| |
| |-
| |
| | [https://github.com/mozsearch mozsearch] || The code that runs Searchfox.org || {{Mozillian|kats|Kartikaya Gupta}}||
| |
| |-
| |
| | [https://github.com/MozillaCZ/ MozillaCZ] || [https://www.mozilla.cz/ Mozilla.cz] || {{Mozillian|mstanke|Michal Stanke}}, {{Mozillian|MekliCZ|Michal Vašíček}}, {{Mozillian|zelitomas|Tomáš Zelina}}||
| |
| |-
| |
| | [https://github.com/MozillaSK/ MozillaSK] || [https://www.mozilla.sk/ Mozilla.sk] || {{Mozillian|mstanke|Michal Stanke}}, {{Mozillian|kusavica|Juraj Cigáň}}||
| |
| |-
| |
| | [https://github.com/MozillaDataScience MozillaDataScience] || Ad-hoc analyses by data scientists. || Matrix: #data-science:mozilla.org ||
| |
| |-
| |
| | [https://github.com/mozilla-extensions mozilla-extensions] || CI- and release-enabled privileged webextensions and system addons. || Slack: #addon-pipeline ||
| |
| |-
| |
| | [https://github.com/mozilla-frontend-infra Mozilla-Frontend-Infra] || Frontend Testing support || || [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&short_desc=%5bMozilla-Frontend-Infra%5d Mozilla Frontend Infra request]
| |
| |-
| |
| | [https://github.com/mozilla-rally mozilla-rally] || ION (former Pioneer) platform. || Slack: #ion ||
| |
| |-
| |
| | [https://github.com/firefox-devtools firefox-devtools] || Firefox Developer Tools || ? ||
| |
| |-
| |
| | [https://github.com/common-voice common-voice] || Common Voice || {{Mozillian|phirework|Jenny Zhang}}, Matrix: #common-voice:mozilla.org ||
| |
| |}
| |
| | |
| === Are there other unofficial or Mozilla-related repositories hosted on GitHub? ===
| |
| Why, yes! In no particular order:
| |
| | |
| * [https://github.com/kinetiknz/cubeb/ https://github.com/kinetiknz/cubeb/] : Cubeb cross platform audio library.
| |
| * [https://github.com/djg/cubeb-rs/ https://github.com/djg/cubeb-rs/] : Rust bindings for cubeb.
| |
| * [https://github.com/kinetiknz/nestegg/ https://github.com/kinetiknz/nestegg/] : WebM demuxer.
| |
| * [https://github.com/xiph/opus/ https://github.com/xiph/opus/] : Modern audio compression for the internet.
| |
| * [https://github.com/webmproject/libvpx https://github.com/webmproject/libvpx] : Mirror only. Please do not send pull requests.
| |
| * [https://github.com/campd/fxdt-adapters https://github.com/campd/fxdt-adapters] : Firefox Developer Tools protocol adapters
| |
| * [https://github.com/kripken/emscripten https://github.com/kripken/emscripten] : Emscripten: An LLVM-to-JavaScript Compiler
| |
| * [https://github.com/bbondy/codefirefox https://github.com/bbondy/codefirefox] : Video and exercise based tutorial site for coding Firefox and other Mozilla related technology
| |
| * [https://github.com/nickdesaulniers/where-is-firefox-os https://github.com/nickdesaulniers/where-is-firefox-os] : A map showing where in the world Firefox OS phones are being sold.
| |
| * [https://github.com/jdm/bugsahoy https://github.com/jdm/bugsahoy] : A landing page to make finding relevant bugs easier for new Mozilla contributors.
| |
| * [https://github.com/w3c/web-platform-tests https://github.com/w3c/web-platform-tests] : Test Suites for Web Platform specifications
| |
| * [https://github.com/w3c/wptserve https://github.com/w3c/wptserve] : Web server designed for use with web-platform-tests
| |
| * [https://github.com/w3c/wptrunner https://github.com/w3c/wptrunner] : Cross-browser and multi-platform test runner for web-platform-tests. Used in mozilla-central and servo.
| |
| * [https://github.com/w3c/testharness.js https://github.com/w3c/testharness.js] : (no description)
| |
| * [https://github.com/jdm/asknot https://github.com/jdm/asknot] : Ask not what Mozilla can do for you but what you can do for Mozilla.
| |
| * [https://github.com/jeffbryner/MozDef https://github.com/jeffbryner/MozDef]: Mozilla Defense Platform.
| |
| * [https://github.com/jgraham/webdriver-rust https://github.com/jgraham/webdriver-rust]: WebDriver library for Rust.
| |
| * [https://github.com/ehsan/mozilla-cvs-history https://github.com/ehsan/mozilla-cvs-history]: A git conversion of the full Mozilla CVS history, useful for code archaeology.
| |
| * [https://github.com/djg/audioipc-2 https://github.com/djg/audioipc-2]: Audio IPC for Gecko.
| |
| * [https://github.com/hsivonen/encoding_rs https://github.com/hsivonen/encoding_rs]: encoding_rs (character encoding converters for Gecko)
| |
| * [https://github.com/choller/firefox-asan-reporter https://github.com/choller/firefox-asan-reporter] : Internal addon used in conjunction with special ASan builds of Firefox.
| |
| * [https://github.com/jrmuizel/qcms https://github.com/jrmuizel/qcms] : Fork of 'quick color management' for Firefox
| |
| * https://github.com/webcompat : Web Compatibility Team (Industry wide) -- {{Mozillian|kdubost|Karl Dubost}}
| |