Confirmed users
358
edits
CloudServices/Github: Difference between revisions
no edit summary
(Created page with "== GitHub for Cloud Services Engineers == Aside from some [https://hg.mozilla.org/services/ legacy projects] in mercurial, all of the code for the Cloud Services team lives i...") |
No edit summary |
||
| Line 1: | Line 1: | ||
Aside from some [https://hg.mozilla.org/services/ legacy projects] in mercurial, all of the code for the Cloud Services team lives in [https://github.com GitHub]. There are over a thousand Mozilla-related repositories in total, but no over-arching corporate policy on How Mozilla Should Use GitHub, so it can easily get a bit confusing - this document exists to help you make some sense of it all. | Aside from some [https://hg.mozilla.org/services/ legacy projects] in mercurial, all of the code for the Cloud Services team lives in [https://github.com GitHub]. There are over a thousand Mozilla-related repositories in total, but no over-arching corporate policy on How Mozilla Should Use GitHub, so it can easily get a bit confusing - this document exists to help you make some sense of it all. | ||
| Line 5: | Line 4: | ||
It's all guidelines, not actual rules. Do what works, but please review the below as well as the top-level [[Github]] info page. | It's all guidelines, not actual rules. Do what works, but please review the below as well as the top-level [[Github]] info page. | ||
== Organizations == | |||
Cloud Services code is spread across two github organisations: | Cloud Services code is spread across two github organisations: | ||
| Line 15: | Line 14: | ||
* Projects that are mostly infrastructure-related, or are heavily specific to Mozilla's internal needs, should go in "mozilla-services". Examples include [https://github.com/mozilla-services/circus Circus] and [https://github.com/mozilla-services/heka Heka] as well as various puppet configuration repos. | * Projects that are mostly infrastructure-related, or are heavily specific to Mozilla's internal needs, should go in "mozilla-services". Examples include [https://github.com/mozilla-services/circus Circus] and [https://github.com/mozilla-services/heka Heka] as well as various puppet configuration repos. | ||
* Projects that will be of more general interest to the Mozilla community should go in "mozilla". Examples include the [https://github.com/mozilla/persona Persona] and [https://github.com/mozilla/fxa-auth-server Firefox Accounts] application servers. | * Projects that will be of more general interest to the Mozilla community, or that are more clearly in services of Mozilla's mission and brand, should go in "mozilla". Examples include the [https://github.com/mozilla/persona Persona] and [https://github.com/mozilla/fxa-auth-server Firefox Accounts] application servers. | ||
You will not have to look hard to find counter-examples to the above. Don't fret. Just do what you think is sensible. | You will not have to look hard to find counter-examples to the above. Don't fret. Just do what you think is sensible. | ||
== Teams and Permissions == | |||
== Security == | |||
Make sure you have two-factor auth enabled on your account. This goes double if you're an Owner. | Make sure you have two-factor auth enabled on your account. This goes double if you're an Owner. | ||