Request for creation of CVS Account - Arougthopher

RESOLVED FIXED

Status

mozilla.org
Repository Account Requests
RESOLVED FIXED
16 years ago
16 years ago

People

(Reporter: Paul, Assigned: marcia)

Tracking

Details

(Reporter)

Description

16 years ago
I am a developer working on the port to BeOS.  I would like to be able to
check-in some of the patches that I have created, that others have not checked
in for me.
Yes, I'm vouching with the understanding that checkins will be limited to BeOS
specific dirs only.  Changes to BeOS ifdefs under other modules would still have
to go through the normal patch/review process for now.  

Since BeOS isn't a tier-1 platform for mozilla.org, I'm assuming that the usual
super-reviewer & tree closure exceptions apply for ports.  Someone correct me if
I'm wrong:

1) You do not need a super review for ports changes although they must be
reviewed by someone else familiar with the code. 

2) Each checkin comment should have the bug number and r=<name and/or email
address of reviewer>

3) If you're checking in changes for someone else, please give proper
attribution in your checkin comment.

4) We do have a BeOS tinderbox so, of course, it must stay green after your
checkins.

5) You can check in during a closed tree to fix tinderbox bustage and you should
note this in your checkin comment.

6) You can check in platform porting fixes to the tree during the daily closure
under either the "NOT PART OF THE BUILD" or "<platform> ONLY" loophole.  (Not
sure if that should be encouraged but that's the current standard.)

7) Milestone tree closures still require approval from the build verification
team/sheriff before checking in.

Also make sure that you read the 'Rules & Tips' section of the reviewers' doc,
http://www.mozilla.org/hacking/reviewers.html as well as the coding practices
doc, http://www.mozilla.org/hacking/best-coding-practices.html .


(Assignee)

Comment 2

16 years ago
I will need you to fill out the CVS contributor form 
(http://mozilla.org/hacking/getting-cvs-write-access.html) and get it back to me 
to get the process started. 
Status: NEW → ASSIGNED
Summary: Request for creation of CVS Account → Request for creation of CVS Account - Arougthopher
(Reporter)

Comment 3

16 years ago
I have just faxed in the CVS Contributer form.

Comment 4

16 years ago
ah well, if cls didn't vouch, i would have. but i guess that spot's taken.
hrm... sr=s... Reading through http://www.mozilla.org/hacking/reviewers.html and
http://mozilla.org/hacking/getting-cvs-write-access.html in conjunction w/ cls's
comments i wonder if sr's aren't required for this account.
(Assignee)

Comment 5

16 years ago
Form received.  Timeless raised an interesting issue - any SRs on the cc list 
care to comment? 
(Reporter)

Comment 6

16 years ago
I don't mean to be pushy or rude, but I was just wondering what the progress of
the request was.  Thank you.
blizzard, you're ports exception rule-setter.  What do you think?

/be
As long as checkins are limited to the beos specific directories it's fine with
me.  For other code in the tree the usual rules apply.  Play nice and stick
close to your voucher!
(Assignee)

Comment 9

16 years ago
account activated. 
Status: ASSIGNED → RESOLVED
Last Resolved: 16 years ago
Resolution: --- → FIXED
(Reporter)

Updated

16 years ago
Blocks: 151401
You need to log in before you can comment on or make changes to this bug.