I need write access to the Silme repository at hg.mozilla.org/l10n/silme , so that Gandalf won't have to push my own patches anymore.
Right now, we can't grant access to silme per se. Gandalf, should we get silme on a different hg level?
I'd find Adrian trustworthy enough to give him level 2 access in general.
The /l10n tree is under l10n-drivers control, not level 2. Mostly because we want restrictions to http://hg.mozilla.org/l10n/l10n-src-verification/
Bah, and I thought the new commit access policy would have eliminated mostly useless restrictions like that. :(
This may mean more work, but maybe it's time to consider moving l10n-src-verification out of l10n/? Then, l10n would require level 2, and l10n-src-verification--level 3. Seems like because of l10n-src-verification, we're a bit too restrictive about silme, django-site or l20n.
fwiw, we're talking about 1A for l10n-src-verification, I think. Not sure what would be the right level for the other repos. I guess I'd be fine with 2 for django-site. Gandalf, any opinion on silme? I guess we can scratch the empty l20n repo? FWIW, my current thinking is to just move the posix group restrictions from the l10n dir to the src-verification dir.
Axel, Gandalf: any updates here?
We changed permissions to the l10n repos a while back, IIRC, this should be FIXED.
Unfortunately, it doesn't work: $ hg push pushing to ssh://hg.mozilla.org/l10n/silme/ searching for changes remote: abort: could not lock repository /repo/hg/mozilla/l10n/silme/: Permission denied abort: unexpected response: empty string
Adrian, what account level do you have? Bug 632053 made l10n level 2.
Marking this incomplete, as we've lived with this for a while. As always, if this is actually still an issue, please reopen.