Changes

Generally, mozilla/gecko-dev and mozilla/gecko-projects are organization-supported mirrors using production synchronization, while mozilla/gecko is an unsupported mirror using best-effort synchronization. Issues with the gecko-dev and gecko-projects, such as [https://bugzilla.mozilla.org/show_bug.cgi?id=1350696 bug 1350696] and [https://bugzilla.mozilla.org/show_bug.cgi?id=1362350 bug 1362350], are a high priority for Mozilla, and are actively addressed. It isn't obvious how to report an issue with mozilla/gecko. == mozilla/gecko-dev == mozilla/gecko-dev is a read-only mirror of a variety of Mercurial repositories, including mozilla-central, aurora, beta, release, fx-team, inbound, ESR releases, and every branch that led to a published release. It includes the entire history of Gecko, including the history from CVS, before Mozilla migrated Gecko to its Mercurial repository (which doesn't include that history). It is maintained by [[DeveloperServices|Developer Services]] or [[ReleaseEngineering|Release Engineering]] and is synchronized automatically via a service multiple times per day. No commits are made in Git on gecko-dev. All commits are made on hg.mozilla.org. So committer emails don't always match to GitHub accounts. == gecko-projects ==

mozilla/gecko-projects is a read-only mirror of [https://hg.mozilla.org/projects/ hg.mozilla.org/projects/] that is similarly maintained and synchronizedsimilarly to gecko-dev. It contains experimental work (mirrors of various hg.mozilla.org/projects/ repos) which are "reset" often, so they only show the most recent experiment. (Successful experiments are merged into mozilla-central.)

No As with gecko-dev, no commits are made in Git on gecko-dev or gecko-projects. All commits are made on hg.mozilla.org. So committer emails don't always match to GitHub accounts.

== mozilla/gecko, on the other hand, is a mirror of a single Mercurial repository: mozilla-central. It doesn't include CVS history, nor does it include other Mercurial repositories (aurora, inbound, etc.). Its "central" branch is read-only, but Gecko developers are welcome to create and commit to other branches in the repo. It's maintained by [https://mozillians.org/en-US/u/myk/ Myk Melez] and is synchronized manually via Git and [https://github.com/glandium/git-cinnabar git-cinnabar] daily on weekdays and occasionally on weekends.==

More generally, mozilla/gecko-dev and is a mirror of a single Mercurial repository: mozilla/gecko-projects are organization-supported mirrors using production synchronizationcentral. It doesn't include CVS history, nor does it include other Mercurial repositories (aurora, inbound, while mozilla/gecko etc.). Its "central" branch is an unsupported mirror using bestread-effort synchronizationonly, but Gecko developers are welcome to create and commit to other branches in the repo. Issues with the former, such as It's maintained by [https://bugzilla.mozillamozillians.org/show_bug.cgi?id=1350696 bug 1350696en-US/u/myk/ Myk Melez] and is synchronized manually via Git and [https://bugzillagithub.mozilla.orgcom/glandium/show_bug.cgi?id=1362350 bug 1362350git-cinnabar git-cinnabar], are a high priority for Mozilla, daily on weekdays and are actively addressed. Whereas it isn't obvious how to report an issue with the latteroccasionally on weekends.

(Myk created mozilla/gecko because he was synchronizing mozilla-central to a Git repo using git-cinnabar for his own development, and he thought it might be helpful for other developers who want to clone a Gecko repo that is smaller than gecko-dev and/or use git-cinnabar to interact with a Mercurial repo. He hasn't publicized it or otherwise explored the extent to which it's helpful, and it might in fact be better for such developers to clone mozilla-central via git-cinnabar directly.)