351493 - [e-mail] needs cvs access and proper despot access to commit to the specific cvs repo (for www.mozilla.com)

Status: RESOLVED FIXED

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

Description

[(not reading, please use [e-mail] instead)]

[e-mail] given proper despot access to commit to the specific cvs repo (for www.mozilla.com)


Short story:  I need this in order to publish a couple pages on www.mozilla.com

Long story:

I'm looking to put up two pages on mozilla.com to be used next week, when we test out major updates and the licenseURL for Software Update.

The first page would be a HTML page that would appear in the initial stages of software update.  (See https://bugzilla.mozilla.org/attachment.cgi?id=234413, where I am using http://www.mozilla.com).  My version would be a simple page telling people not to panic, what's going on, and where to report issues.

The second page would be a "fake" EULA, just for test purposes.  (See https://bugzilla.mozilla.org/attachment.cgi?id=234414, where I am using http://www.mozilla.com/legal/eula/firefox-en.txt)  Note, I would not be using a real EULA.  (It would be a HTML page that says something like "Don't panic, this is not a real EULA.  But you need to accept it, in order to install the major update".)

All of this is to test my changes for https://bugzilla.mozilla.org/show_bug.cgi?id=329729 and https://bugzilla.mozilla.org/show_bug.cgi?id=348389, which if all goes well, I will be back porting to Firefox 1.5.0.x in order to support the eventual upgrade to Firefox 2.0.x

Comment 1

[(not reading, please use [e-mail] instead)]

I have cvs write access to cvs.mozilla.org, but I have a feeling I'd need cvs write access to another repository to do this.

Comment 2

[(not reading, please use [e-mail] instead)]

updating summary, cvs for the website is in another repository.

Comment 3

[Chris Beard]

ok, you should now have access to mozilla-com. thanks for playing.

Comment 4

[Dave Miller [:justdave]]

Your access should actually work now.  At some point your despot account was renamed from .org to .com, and the back-end changes to your shell accounts were never made to match.  I just renamed the shell accounts to match, so the permissions you are given in despot should actually work now.