Hi, I'd like to get SVN commit access. I'm the et owner. I have a CVS account from bug 429361. My LDAP account is: email@example.com I need write access to the following locations: svn.mozilla.org/projects/mozilla.com/trunk/et/ svn.mozilla.org/projects/mozilla-europe.org/trunk/et/ Thanks.
Has to come through the proper channels, before IT can grant access. Re-assigning.
Vouching for Sander, he should be added to our @localizers group on SVN so as to be able to commit on any web project in Estonian
https://bugzilla.mozilla.org/show_bug.cgi?id=429361#c5 indicates that we had a committer's agreement signed on file, Marcia could you confirm? Thanks
Erica: Can you please confirm that we have a form for Sander. If so, this one can move over to server ops.
Seems like i'm still waiting for my account?
That's because we don't have confirmation that your form has been received. Please be patient, the bug will be re-assigned to IT when it is ready and access will be granted.
I have a form for Sander on file.
over to server-ops for addition to @localizers
svn enabled, svn_mozilla bit flipped (sander didn't have access to svn before this) and added to localizers. Gavin, should I have to enabled scm_level_ bits as well? if so, what would be appropriate here?
(In reply to comment #9) > Gavin, should I have to enabled scm_level_ bits as well? if so, what would be > appropriate here? There isn't much point, until bug 561326 is fixed. And even when it is, I think localizers will still be kept separate (per bug 561326 comment 4).
(In reply to comment #9) > svn enabled, svn_mozilla bit flipped (sander didn't have access to svn before > this) and added to localizers. > > Gavin, should I have to enabled scm_level_ bits as well? if so, what would be > appropriate here? It looks like you're going to need to. He can't commit to svn over ssh:// but can update the working copy(so public key is ok). Please keep in mind that LDAP uname is changed to firstname.lastname@example.org Milos.
Updated @localizers to email@example.com