Confirmed users
2,473
edits
SCM/GitHubFAQ: Difference between revisions
→Why not host Mozilla’s canonical repositories on GitHub?
| Line 12: | Line 12: | ||
# <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>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. (For more information see [[SCM/GitHubFAQ#Why_aren.E2.80.99t_GitHub_URLs_stable.3F|Why aren't GitHub URLs stable?]]) | # <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 treee. | # <b>Limited permission support</b> - This impacts our ability to limit commit access to portions of the treee. | ||