GitHub: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
m (done some minor edits)
No edit summary
Line 1: Line 1:
{{stub}}
== Organizations ==
There are several Mozilla organizations on Github.  Below are details about known repositories


Various groups at Mozilla use https://github.com/mozilla differently. Alphabetically:
==== https://github.com/mozilla ====
* A cornucopia of projects at Mozilla. Use the [https://mail.mozilla.org/listinfo/github-owners github owners mailing list] for any support questions


* '''devtools''' runs a fork of mozilla-central and maintains several projects.
==== https://github.com/mozilla-appmaker ====
* '''labs''' maintain their own stuff
* Source related to [https://appmaker.mozillalabs.com/ Appmaker]
* '''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:
** http://mozweb.readthedocs.org/en/latest/


== Forking vs Transfering ==
==== https://github.com/mozilla-cordova ====


'''Do not "fork" a repository into the Mozilla organization.''' Doing so gives ''every team in the org'' rights to it.
 
==== https://github.com/mozilla-b2g ====
* Main source for [[B2G|B2G]]
 
==== https://github.com/rust-lang ====
* Repository for the [http://www.rust-lang.org Rust Programming Language]
 
==== https://github.com/x-tag ====
* Repository for [http://www.x-tags.org x-tags]
 
 
== Recommendations and FAQ ==
 
=== 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
 
=== 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:
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:
Line 22: Line 35:
# 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.
# 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.
# Talk to an org admin to add the appropriate teams to the new Mozilla repo.
# Talk to an org admin to add the appropriate teams to the new Mozilla repo.
#* Who are the org admins? Where do we find a list of them?
== I Have a Problem ==
see `@fwenzel`
=== we want a team ===
Email. `fwenzel@` the
# proposed team name
# members github usernames 
# repos the team need access to.


"The organization has its own repos, and access to those repos is controlled by teams within the organization.  I can create a ux team and put people on it but it doesn't do much unless there are repos it needs access to!"
=== 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.

Revision as of 17:35, 24 February 2014

Organizations

There are several Mozilla organizations on Github. Below are details about known repositories

https://github.com/mozilla

https://github.com/mozilla-appmaker

https://github.com/mozilla-cordova

https://github.com/mozilla-b2g

  • Main source for B2G

https://github.com/rust-lang

https://github.com/x-tag


Recommendations and FAQ

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

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 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.

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.

Retrieved from "https://wiki.allizom.org/index.php?title=GitHub&oldid=938028"