Confirmed users
2,473
edits
SCM/GitHubFAQ: Difference between revisions
→GitHub.com is great for engaging the community. How can we engage the community?
(Created page with "=Hosting on GitHub FAQ= ==What are the options for hosting on GitHub?== There are two options to host on GitHub software: # GitHub.com, the open source bazaar, with which mo...") |
|||
| (5 intermediate revisions by the same user not shown) | |||
| Line 4: | Line 4: | ||
There are two options to host on GitHub software: | There are two options to host on GitHub software: | ||
# GitHub.com | # GitHub.com, with which most people are familiar. | ||
# GitHub Enterprise, essentially GitHub in a box, which is deployed internally within an organization. | # GitHub Enterprise, essentially GitHub in a box, which is deployed internally within an organization. | ||
| Line 10: | Line 10: | ||
Four issues with hosting Mozilla’s repositories on GitHub: | Four issues with hosting Mozilla’s repositories on GitHub: | ||
# <b>No pre-receive hooks hooks</b> - GitHub only supports post-receive hooks, which increases the requirements on developers to configure their environment and reduces Mozilla’s control over what is committed to our repositories. | # <b>No pre-receive hooks hooks</b> - GitHub only supports post-receive hooks, which increases the requirements on developers to configure their environment and reduces Mozilla’s control over what is committed to our repositories. (For more information see [[SCM/GitHubFAQ#What_is_the_issue_with_post-receive_hooks.3F_Can_we_achieve_the_same_functionality_as_we_have_with_Hg.3F|What is the issue with post-receive hooks?]]) | ||
# <b>Stable URLs</b> - Hosting with GitHub.com decreases control over our repository URLs. We want stable URLs for linking in Bugzilla, pushlog, and elsewhere. | # <b>Stable URLs</b> - Hosting with GitHub.com decreases control over our repository URLs. We want stable URLs for linking in Bugzilla, pushlog, and elsewhere. (For more information see [[SCM/GitHubFAQ#Why_aren.E2.80.99t_GitHub_URLs_stable.3F|Why aren't GitHub URLs stable?]]) | ||
# <b>Network availability and latency</b> - This has been a problem causing build failures over the last year. This problem can be mitigated with internal mirrors but this increases the complexity for the releng team and requires running a Mozilla instance of Git. | # <b>Network availability and latency</b> - This has been a problem causing build failures over the last year. This problem can be mitigated with internal mirrors but this increases the complexity for the releng team and requires running a Mozilla instance of Git. (For more information see [[SCM/GitHubFAQ#Can_we_pay_GitHub_for_improved_availability.3F|Can we pay GitHub for improved availability?]]) | ||
# <b>Limited permission support</b> - This impacts our ability to limit commit access to portions of the | # <b>Limited permission support</b> - This impacts our ability to limit commit access to portions of the tree. (For more information see [[SCM/GitHubFAQ#What_are_the_limitations_of_GitHub.E2.80.99s_permission_system.3F|What are the limitations of GitHub's permission system?]]) | ||
==What is the issue with post-receive hooks? Can we achieve the same functionality as we have with Hg?== | ==What is the issue with post-receive hooks? Can we achieve the same functionality as we have with Hg?== | ||
| Line 42: | Line 42: | ||
==GitHub.com is great for engaging the community. How can we engage the community?== | ==GitHub.com is great for engaging the community. How can we engage the community?== | ||
We can mirror Mozilla’s repositories to GitHub for easy disoverability and cloning. Patches will need to be applied on Mozilla’s hosted repository. | We can mirror Mozilla’s repositories to GitHub for easy disoverability and cloning. Patches will need to be applied on Mozilla’s hosted repository. Several people (doublec, ehsan, releng) are already trying similar attempts. Whatever our approach it must work reliably at scale and be officially supported by Mozilla. | ||
==Will Mozilla require all repositories currently hosted at GitHub.com to move to a Mozilla’s owned server?== | ==Will Mozilla require all repositories currently hosted at GitHub.com to move to a Mozilla’s owned server?== | ||
This has not yet been discussed and no decision has been reached. | This has not yet been discussed and no decision has been reached. | ||