GitHub: Difference between revisions
m (→Are there other unofficial or Mozilla-related repositories hosted on Github?: - remove duplicates) |
(pulled mozilla-related orgs out from within repo list.) |
||
Line 26: | Line 26: | ||
'''Do not "fork" a repository into a Mozilla organization.''' Doing so gives ''every team in the org'' rights to it. | '''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, | 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 org admin. | # If you're not a member of any team, talk to an org admin. | ||
# Under the repo admin, transfer ownership to the Mozilla organization. If you don't see this option, return to step 1. | # 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 owner privileges. If you don't chose any you will lose push access to the repo and have to talk to an org admin. | # 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. | ||
# Fork the repo from Mozilla (mozilla/myrepo) back to your account (recreating | # 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. | ||
# Add the appropriate teams to the new Mozilla repo or ask an org admin if you lost ownership. | # Add the appropriate teams to the new Mozilla repo or ask an org admin if you lost ownership. | ||
Line 42: | Line 42: | ||
On large teams we recommend you separate teams for read/write and repository administration. | On large teams we recommend you separate teams for read/write and repository administration. | ||
=== | === 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 will create a large number of sub-repositories will create their own "organization". Here is a (probably incomplete) list of them: | |||
* [https://github.com/jetpack-labs https://github.com/jetpack-labs] : Jetpack Labs | * [https://github.com/jetpack-labs https://github.com/jetpack-labs] : Jetpack Labs | ||
* [https://github.com/mozilla-b2g https://github.com/mozilla-b2g] : Mozilla | * [https://github.com/mozbrick https://github.com/mozbrick] : Mozilla Brick (web components library) | ||
* [https://github.com/mozilla-b2g https://github.com/mozilla-b2g] : Mozilla Boot2Gecko / Firefox OS | |||
* [https://github.com/mozilla-services https://github.com/mozilla-services] : Mozilla Services | * [https://github.com/mozilla-services https://github.com/mozilla-services] : Mozilla Services | ||
* [https://github.com/Mozilla-TWQA https://github.com/Mozilla-TWQA] : Mozilla-TWQA | * [https://github.com/Mozilla-TWQA https://github.com/Mozilla-TWQA] : Mozilla-TWQA | ||
* [https://github.com/mozillahispano https://github.com/mozillahispano] : Mozilla Hispano | * [https://github.com/mozillahispano https://github.com/mozillahispano] : Mozilla Hispano | ||
Line 58: | Line 55: | ||
* [https://github.com/servo https://github.com/servo] : servo | * [https://github.com/servo https://github.com/servo] : servo | ||
* [https://github.com/rust-lang https://github.com/rust-lang] : The Rust Programming Language | * [https://github.com/rust-lang https://github.com/rust-lang] : The Rust Programming Language | ||
* [https://github.com/mozillayvr | * [https://github.com/mozillayvr https://github.com/mozillayvr] : Mozilla Vancouver @MozillaYVR | ||
* [https://github.com/mozilla-comm https://github.com/mozilla-comm] : Calendaring and Messaging related projects | |||
* [https://github.com/webcompat https://github.com/webcompat] : Web Compatibility Team | |||
* [https://github.com/mozilla-metrics https://github.com/mozilla-metrics] : Mozilla Metrics | |||
* [https://github.com/mozilla-appmaker https://github.com/mozilla-appmaker] : Mozilla Appmaker | |||
* [https://github.com/tabulapdf https://github.com/tabulapdf] : Tabula project | |||
* [https://github.com/hackasaurus https://github.com/hackasaurus] : Hackasaurus | |||
* [https://github.com/drumbeat-badge-sprint https://github.com/drumbeat-badge-sprint] : Badge Lab | |||
* [https://github.com/mdn https://github.com/mdn] : Mozilla Developer Network | |||
* [https://github.com/mozilla-appmaker https://github.com/mozilla-appmaker] : Mozilla Appmaker | |||
* [https://github.com/bugzilla https://github.com/bugzilla] : Bugzilla (the product) | |||
* [https://github.com/MozillaSecurity https://github.com/MozillaSecurity] : Mozilla Platform Fuzzing Team master repo with many fuzzing tools under it. | |||
=== Are there other unofficial or Mozilla-related repositories hosted on Github? === | |||
Why, yes! In no particular order: | |||
* [https://github.com/mozilla/addon-sdk https://github.com/mozilla/addon-sdk] : Mozilla Add-on SDK (aka Jetpack) | |||
* [https://github.com/mozilla/jpm https://github.com/mozilla/jpm] : Jetpack Manager | |||
* [https://github.com/kinetiknz/nestegg/ https://github.com/kinetiknz/nestegg/] : WebM demuxer | * [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/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/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/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/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/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/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/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/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/wptserve https://github.com/w3c/wptserve] : Web server designed for use with web-platform-tests | ||
Line 80: | Line 86: | ||
* [https://github.com/w3c/testharness.js https://github.com/w3c/testharness.js] : (no description) | * [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/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/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 | ||
Revision as of 23:45, 9 January 2015
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).
![]() |
---|
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.
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.
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, 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 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 owner privileges. If you don't chose any you will lose push access to the repo and have to talk to an org admin.
- 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.
- 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.
No, there are plenty of Mozilla-related "organizations" on github. As a rule of thumb, initiatives that will create a large number of sub-repositories will create their own "organization". Here is a (probably incomplete) list of them:
- https://github.com/jetpack-labs : Jetpack Labs
- https://github.com/mozbrick : Mozilla Brick (web components library)
- https://github.com/mozilla-b2g : Mozilla Boot2Gecko / Firefox OS
- https://github.com/mozilla-services : Mozilla Services
- https://github.com/Mozilla-TWQA : Mozilla-TWQA
- https://github.com/mozillahispano : Mozilla Hispano
- https://github.com/mozfr : Mozilla Francophone
- https://github.com/opennews : Knight-Mozilla OpenNews
- https://github.com/servo : servo
- https://github.com/rust-lang : The Rust Programming Language
- https://github.com/mozillayvr : Mozilla Vancouver @MozillaYVR
- https://github.com/mozilla-comm : Calendaring and Messaging related projects
- https://github.com/webcompat : Web Compatibility Team
- https://github.com/mozilla-metrics : Mozilla Metrics
- https://github.com/mozilla-appmaker : Mozilla Appmaker
- https://github.com/tabulapdf : Tabula project
- https://github.com/hackasaurus : Hackasaurus
- https://github.com/drumbeat-badge-sprint : Badge Lab
- https://github.com/mdn : Mozilla Developer Network
- https://github.com/mozilla-appmaker : Mozilla Appmaker
- https://github.com/bugzilla : Bugzilla (the product)
- https://github.com/MozillaSecurity : Mozilla Platform Fuzzing Team master repo with many fuzzing tools under it.
Why, yes! In no particular order:
- https://github.com/mozilla/addon-sdk : Mozilla Add-on SDK (aka Jetpack)
- https://github.com/mozilla/jpm : Jetpack Manager
- https://github.com/kinetiknz/nestegg/ : WebM demuxer
- https://github.com/xiph/opus/ : Modern audio compression for the internet.
- https://github.com/webmproject/libvpx : Mirror only. Please do not send pull requests.
- https://github.com/campd/fxdt-adapters : Firefox Developer Tools protocol adapters
- https://github.com/kripken/emscripten : Emscripten: An LLVM-to-JavaScript Compiler
- 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 : A map showing where in the world Firefox OS phones are being sold.
- 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 : Test Suites for Web Platform specifications
- https://github.com/w3c/wptserve : Web server designed for use with web-platform-tests
- 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 : (no description)
- https://github.com/jdm/asknot : Ask not what Mozilla can do for you but what you can do for Mozilla.
- https://github.com/mozilla/webtools-bmo-bugzilla : bugzilla.mozilla.org