GitHub: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
Line 83: Line 83:
* [https://github.com/bugzilla/bugzilla https://github.com/bugzilla/bugzilla] : Bugzilla (the product)
* [https://github.com/bugzilla/bugzilla https://github.com/bugzilla/bugzilla] : Bugzilla (the product)
* [https://github.com/mozilla/webtools-bmo-bugzilla https://github.com/mozilla/webtools-bmo-bugzilla] : bugzilla.mozilla.org
* [https://github.com/mozilla/webtools-bmo-bugzilla https://github.com/mozilla/webtools-bmo-bugzilla] : bugzilla.mozilla.org
* [https://github.com/MozillaSecurity] : Mozilla Platform Fuzzing Team master repo with many fuzzing tools under it.
* [https://github.com/MozillaSecurity https://github.com/MozillaSecurity] : Mozilla Platform Fuzzing Team master repo with many fuzzing tools under it.

Revision as of 00:30, 20 November 2014

This page is specifically about Mozilla's GitHub. There are several other github organizations you may be interested in (mozilla-appmaker, mozilla-cordova, mozilla-b2g, rust-lang, x-tag, bugzilla, mozilla-services).

Red question mark.png Got a question?
Email github-owners [AT] mozilla.org

Recommendations and FAQ

Where should I ask additional questions?

  • Send an email to github-owners AT mozilla.org and we'll respond right away!

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.

Should I make a separate github organization or just create a repository in an existing one?

This is a personal preference. 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.

Forking vs Transfering

Do not "fork" a repository into a Mozilla organization. Doing so gives every team in the org rights to it.

If you have created a repo on your own account (for example, jsocol/myrepo) and it should live under the Mozilla organization, here are the steps:

  1. If you're not a member of any team, talk to an org admin.
  2. Under the repo admin, transfer ownership to the Mozilla organization. If you don't see this option, return to step 1.
  3. Choose which teams should be given owner privileges. If you don't chose any you will lose push access to the repo and have to talk to an org admin.
  4. Fork the repo from Mozilla (mozilla/myrepo) back to your account (recreating jsocol/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.
  5. Add the appropriate teams to the new Mozilla repo or ask an org admin if you lost ownership.

Do I need to be an owner to create repositories?

No. If a person has read/write access to another repository in that organization they can make more repositories in that organization.

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.

Are there other unofficial or Mozilla-related repositories hosted on Github?

Why, yes! In no particular order: