GitHub: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
(Add Thunderbird.)
m (Add mozilla-japan)
Line 4: Line 4:


* '''labs''' maintain their own stuff
* '''labs''' maintain their own stuff
* '''mozilla-japan''' uses it for their parapara animation web app.
* '''releng''' uses it differently (as mirrors)
* '''releng''' uses it differently (as mirrors)
* [[Standards]] does not use the Mozilla github yet but is looking into it.
* [[Standards]] does not use the Mozilla github yet but is looking into it.

Revision as of 23:19, 23 May 2012

This article is a stub. You can help MozillaWiki by expanding it.

Various groups at Mozilla use https://github.com/mozilla differently. Alphabetically:

  • labs maintain their own stuff
  • mozilla-japan uses it for their parapara animation web app.
  • releng uses it differently (as mirrors)
  • Standards does not use the Mozilla github yet but is looking into it.
  • thunderbird uses it for the ispdb (migrated from svn).
  • webdev documents their use of Github in the webdev bootcamp docs:

Forking vs Transfering

Do not "fork" a repository into the 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 with admin, 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. 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.
  4. Talk to an org admin to add the appropriate teams to the new Mozilla repo.

Basics of Github Organizations

This article is a stub. You can help MozillaWiki by expanding it.

TODO(jsocol) Fill this out.