509712 - Make sure all CVS committers to mozilla.org web site has access to SVN

Status: RESOLVED FIXED

(Infrastructure & Operations Graveyard :: Account Requests, task)

Description

[David Boswell]

As part of the www.mozilla.org relaunch we are moving the code from CVS to SVN and we need to make sure that all recent www.mozilla.org committers have access to the new repository.  The list of recent committers is at

http://bonsai-www.mozilla.org/toplevel.cgi

Many of these people already have SVN access and I'm not sure who needs access.

The new repository is at

http://svn.mozilla.org/projects/mozilla.org/

In terms of timing, we'd like to have this taken care of before the new site goes live.  We don't have a launch date set yet, but it will probably be sometime next week.

Comment 1

[Marcia Knous [:marcia]]

Back over to server-ops - someone will have to cross reference the bonsai list and see who does not currently have SVN access. For those that do not have access, I assume we would want to follow the guidelines for SVN access posted here: https://wiki.mozilla.org/Commit_Policy:Current_Procedures

Comment 2

[Aravind Gottipati [:aravind]]

Currently, the only people, that are allowed to check into /projects/mozilla.org/trunk are [e-mail], [e-mail], [e-mail], [e-mail], [e-mail], [e-mail], [e-mail], [e-mail].

The only folks that can check in to /projects/mozilla.org/tags are [e-mail], [e-mail], [e-mail], [e-mail], [e-mail], [e-mail], [e-mail], [e-mail].

I am assuming that you want me to open that up to everyone in http://bonsai-www.mozilla.org/toplevel.cgi ?

Comment 3

[Aravind Gottipati [:aravind]]

Attachment: Folks missing a svn account.

Comment 4

[Aravind Gottipati [:aravind]]

Also, these are some other avenues through which people update content on mozilla.org (like doctor, iirc).. are all those avenues covered?  Have people been informed that the only way to update mozilla.org going forward is through svn.

Will you be contacting folks in the list above and asking them to request svn accounts or do you want us to do it?

Comment 5

[David Boswell]

Re comment #2, Yes, please give access to everyone who has access to the current live site.

Re comment #4, Yes, we've notified people that CVS and Doctor are going away and SVN will be the only method for updating the site (at least until we have a Doctor replacement available).  As for contacting folks, can we just automatically give them access without each of them having to request it?

Comment 6

[matthew zeier [:mrz]]

Aravind's out, chizu, easy to handle?

Comment 7

[David Boswell]

For timing, we're currently planning on going live with the site on Tuesday, August 25th.  If it won't be possible to make this change by then, please let us know.

Comment 8

[chizu]

Yes, it's easy to add the missing SVN accounts. Should everyone get access to both trunk and tags (as it is currently)?

Comment 9

[David Boswell]

Yes, for now let's just give everyone the same level of access.  At some point later though, I think we'll scale things back and limit access to everything to a smaller group.

Comment 10

[Reed Loden [:reed]]

(In reply to comment #8)
> Yes, it's easy to add the missing SVN accounts. Should everyone get access to
> both trunk and tags (as it is currently)?

No, just trunk (@mozilla-org-trunk, iirc). Leave the tags group as it is (only a few people).

Comment 11

[Samuel Sidler (old account; do not CC)]

(And note that we aren't really using tags at all yet, but likely will in the future.)

Comment 12

[chizu]

Out of aravind's list, everyone now has SVN commit access to mozilla-org-trunk except these two who I can't track down LDAP accounts for:
[e-mail]
[e-mail]

Comment 13

[David Boswell]

I'll contact both of the people mentioned in #12 and see if they want SVN access.

Comment 14

[David Boswell]

mrmazda wanted SVN access, so I set up a bug to get him an LDAP and SVN account at bug 512294.

Comment 15

[fantasai]

I'm having trouble checking in. Get this error message:

$ svn co http://svn.mozilla.org/projects/mozilla.org/trunk/ mozorg
$ svn commit -m "Add developer forums to Community section" developer-forums.html 
svn: Commit failed (details follow):
svn: Server sent unexpected return value (500 Internal Server Error) in response to MKACTIVITY request for '/!svn/act/662f8d66-819f-4ef8-95c6-355b6bb99c53'

Don't know what that means.

Comment 16

[fantasai]

nm, reed sorted it out for me

Comment 17

[chizu]

Closing this, anyone else needing access moved over from CVS should file a new bug.

Comment 18

[Reed Loden [:reed]]

Multiple people have been complaining saying that they can't use SSH to commit content. It seems something wasn't set up correctly. I'm reopening this to diagnose the problems and get them solved.

Comment 19

[chizu]

(In reply to comment #18)
> Multiple people have been complaining saying that they can't use SSH to commit
> content. It seems something wasn't set up correctly. I'm reopening this to
> diagnose the problems and get them solved.

Which accounts? I'll need to know this to diagnose any problems.

Comment 20

[Reed Loden [:reed]]

(In reply to comment #19)
> Which accounts? I'll need to know this to diagnose any problems.

bug 513087, bug 513125, bug 512294, bug 512633

Outside of those bugs, I have e-mails from [e-mail] and [e-mail] that say that they can't commit using SSH but can using https://.

Comment 21

[chizu]

(In reply to comment #20)
> (In reply to comment #19)
> > Which accounts? I'll need to know this to diagnose any problems.
> 
> bug 513087, bug 513125, bug 512294, bug 512633
> 
> Outside of those bugs, I have e-mails from [e-mail] and
> [e-mail] that say that they can't commit using SSH but can using
> https://.

[e-mail] had no imported key, this is fixed. The rest of these are already dealt with or have their own bug.