Closed Bug 582066 Opened 15 years ago Closed 15 years ago

Request to re-activate access to mozilla-europe.org SVN account

Categories

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

x86
macOS
task
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: kstawarz, Assigned: jlaz)

Details

User-Agent: Opera/9.80 (Macintosh; Intel Mac OS X; U; es-ES) Presto/2.5.24 Version/10.53 Build Identifier: I would like to re-activate my subversion account which got disabled due to inactivity (for various reasons I didn't have time to use it). I had access to the Moz-Eu l10n (Polish branch) repository. The email address assigned to the account was kasia.stawarz@gmail.com (if it's possible to update the email, can I have it changed to kstawarz@aviary.pl?). Reproducible: Always
Summary: Reguest to re-activate access to mozilla-europe.org SVN account → Request to re-activate access to mozilla-europe.org SVN account
Confirming. Kasia plans to get back into contributing to MozEu, so it'd be nice to have her account working again. :)
Status: UNCONFIRMED → NEW
Ever confirmed: true
Reed, Marcia: is there anything more needed for this bug to get fixed? We (the pl l10n team) really need Katarzyna to have svn access again. :) As for repositories, she would need not only the Moz-Eu l10n branch, but also the Mozilla.com one, too.
Marek: http://www.mozilla.org/hacking/commit-access-policy/ has the new policy - can you please clarify which level of access she would need (and maybe would also help to have the original bug where she got access) to figure out if anything else is still needed. Thanks.
The commit-access-policy lists developer accounts. This request is for a website localizer account originally created in bug 435782 and modified in bug 514312.
Marek: the commit access policy is meant to cover all access requests, including localizer website access. Assuming the account already exists and has the appropriate permission bits (it may predate the creation of @localizers?), reactivating is an IT action - over to them.
Assignee: marcia → server-ops
Though I now see that there's no mention of a committer's agreement having been submitted in the original bug... if you haven't sent one in, can you please try to do that ASAP? Details at http://www.mozilla.org/hacking/notification/. Erica: do you have a form on file for Katarzyna?
Assignee: server-ops → jlazaro
I do not have a form for Katarzyna.
We'll need to get a form on file before we can re-activate the account. Should be relatively quick if you email it in per instructions at the link in comment 6.
Assignee: jlazaro → marcia
I've just emailed a scanned copy of the Agreement to Erica. I was sure I took care of it already as I remember receiving an email about new Committer's Agreements, but somehow I must have forgotten. Sorry for trouble!
I have received Katarzyna's Committer's Agreement.
Over to server-ops to re-activate Katarzyna's account. Please also list her current SVN permissions.
Assignee: marcia → server-ops
Assignee: server-ops → jlazaro
LDAP account/email changed to kstawarz@aviary.pl, SVN bit re-enabled. Looks like she is listed in @localizers and has rw to /projects/mozilla-europe.org/trunk/pl
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
Justin, can you give Katarzyna rw access to: /projects/mozilla.com/trunk/pl (and any other localizable web content for pl)?
pascalc, approval?
yes, no problem
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
kstawarz@aviary.pl given rw to /projects/mozilla.com/trunk/pl
Status: REOPENED → RESOLVED
Closed: 15 years ago15 years ago
Resolution: --- → FIXED
(In reply to comment #16) > kstawarz@aviary.pl given rw to /projects/mozilla.com/trunk/pl It doesn't seem to work: Sending mobile/customize/index.html Transmitting file data .svn: Commit failed (details follow): svn: Can't open '/repo/svn/mozilla/db/tempfile.tmp': Permission denied svn info: URL: svn+ssh://kstawarz%40aviary.pl@svn.mozilla.org/projects/mozilla.com/trunk/pl
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Katarzyna, we use https not svn+ssh for svn work, you should switch your repo url, the identification is done with your LDAP password.
Status: REOPENED → RESOLVED
Closed: 15 years ago15 years ago
Resolution: --- → FIXED
(In reply to comment #18) > Katarzyna, we use https not svn+ssh for svn work, you should switch your repo > url, the identification is done with your LDAP password. Oh, right, sorry!
You need to log in before you can comment on or make changes to this bug.