472526 - SVN commit access to 'hu' AMO for Andras Timar

Status: RESOLVED FIXED

(mozilla.org :: Repository Account Requests, task)

Description

[Andras Timar]

Hi,

I'm the owner of the hu locale and I have just finished translation of AMO. I need write access to the following location:
   svn.mozilla.org/addons/trunk/site/app/locale/hu/

I have already an LDAP account, an SVN account, submitted SSH key etc. See bug #387688

My registered email is '[e-mail]'

Thanks.

Comment 1

[Wil Clouser [:clouserw]]

a=clouserw. thanks.

Comment 2

[Andras Timar]

Any news?

Comment 3

[Reed Loden [:reed]]

Bug 387688 doesn't mention anything about signing the Committer's Agreement.

Erica, do you have signed form on file for Andras?

Comment 4

[Andras Timar]

Last time I signed it in Whistler.

Comment 5

[Wil Clouser [:clouserw]]

I'm moving this from svn requests to account requests because we just need to add a line to the permissions file and this has been marked as a blocker for way too long.

Comment 6

[Dave Miller [:justdave]]

Confirmed, everything's already set up except for the authz line.

And now that's done.

Comment 7

[Reed Loden [:reed]]

(In reply to comment #5)
> I'm moving this from svn requests to account requests because we just need to
> add a line to the permissions file and this has been marked as a blocker for
> way too long.

That's not for you to do at all. When Andras originally received his SVN account, no Committer's Agreement was signed due to the way things were handled at the time for SVN accounts for website localizers. However, things have changed since then, and now we require a signed form for all VCS accounts. I asked Erica in comment #3 to see if a form was on file, and until she answered yes, this bug should have stayed where it is.

I'm sorry that Marcia and I overlooked this bug for two weeks, but you should not have bypassed set procedure by going around us, especially when such an important thing is still missing. We always wait for confirmation of the form, no matter what. Please don't let this happen again.

If Erica replies that she does not have a form on file for Andras, I will have to request that the account be disabled until such form is on file.

Comment 8

[Reed Loden [:reed]]

Also, please do not move bugs out of the account request components. If IT is needed to do something, we just change the assignee to server-ops@.

Comment 9

[Wil Clouser [:clouserw]]

(In reply to comment #8)
> Also, please do not move bugs out of the account request components. If IT is
> needed to do something, we just change the assignee to server-ops@.

That makes sense.  I wasn't clear on what all the variables were to page someone so I just moved it.

He already has access and this bug was about making sure he could commit to the other area where he contributes.  If there is a question of some people not having forms signed that sounds like someone should contact those contributers and file separate bugs to track the issue.

Comment 10

[Erica McClure]

I have received Andras' Committer's Agreement.

Comment 11

[Reed Loden [:reed]]

(In reply to comment #9)
> He already has access and this bug was about making sure he could commit to the
> other area where he contributes.  If there is a question of some people not
> having forms signed that sounds like someone should contact those contributers
> and file separate bugs to track the issue.

Gerv is currently working to get all current contributors to sign the new agreement (I just spoke with him about this last night, actually), but that's a separate issue. Until then, all new requests for any type of VCS access (including additional access to the same VCS) must be properly validated, including confirming that a valid new form is on file. Gerv agrees with this.

Comment 12

[:Gavin Sharp [email: [e-mail]]]

(In reply to comment #11)
> Gerv is currently working to get all current contributors to sign the new
> agreement (I just spoke with him about this last night, actually), but that's a
> separate issue. Until then, all new requests for any type of VCS access
> (including additional access to the same VCS) must be properly validated,
> including confirming that a valid new form is on file. Gerv agrees with this.

That's ridiculous. _Requesting_ a new form is one thing, but actively blocking simple permission change requests on the new form submission process is unreasonable.

Comment 13

[Reed Loden [:reed]]

(In reply to comment #12)
> That's ridiculous. _Requesting_ a new form is one thing, but actively blocking
> simple permission change requests on the new form submission process is
> unreasonable.

Again, I asked Gerv about this specifically, and he said new forms are required. However, if you want to just take this particular bug into context, we never had a form on file for Andras to begin with, so we _definitely_ needed to make sure we had a valid form for him.

Comment 14

[Gervase Markham [:gerv]]

Comment #10 says that Erica has received a (presumably new) form, and Andras said he signed one in Whistler. So what's the problem?

Gerv

Comment 15

[Reed Loden [:reed]]

(In reply to comment #14)
> Comment #10 says that Erica has received a (presumably new) form, and Andras
> said he signed one in Whistler. So what's the problem?

Nothing now, afaik. As far as I'm concerned, comment #10 resolved my complaint.