We are standing up a "plan b" hg mirror on g.m.o. Please create the repository /gecko.git and grant Ehsan access to the repo at the filesystem level, and system access as necessary. Ehsan, can you please specify what exactly you need? Please don't act on this bug until mrz had a chance to see/approve this request.
We also need another helper repository, which can be called mozilla-history-tools.git. I need write access on both repos under my LDAP account (firstname.lastname@example.org). I will try to push to these repos remotely, and will file a new bug if I end up needing ssh access to the git server. We also need another server for running the update scripts to keep the repo updated, which I think we need to file another bug for, but that can be step 2 and we can keep gecko.git updated using my current scripts. We need to have somebody take over monitoring the update scripts once they're moved to Mozilla infrastructure. I can work with them to get the up to speed when someone gets assigned to this task.
Update: per phone conversations with agal, bmoss, & joduinn, releng is going to populate releases/gecko.git with the current copy of github:mozilla/mozilla-central and update from there. We will also be working the original "plan a" with an decision point Monday am (Nov 12) Also, we'll be adding in to the repos the tracker branches (based on gecko versions) requested by agal (which no repo has atm). Bottom line: no gecko.git repository will be created, releng will be populating the releases/gecko.git repo.
closing - "plan a" worked,