76147 - new cvs account for Wade Majors

Status: RESOLVED FIXED

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

Description

[kurros (Wade Majors)]

This is a request for CVS write access. I would be handling BeOS related
bugs and checkins.

Comment 1

[Marcia Knous [:marcia]]

Wade: Please go to http://mozilla.org/hacking/getting-cvs-write-access.html and 
fill out the CVS access form.  That link also provides info about what else you 
need to do if you will be checking code into the tree.

Comment 2

[kurros (Wade Majors)]

I have faxed the CVS contributor form to Marcia Knous. I will mail the hard 
copy upon confirmation if needed.

I believe Christopher Seawood ([e-mail]) will be vouching for me.

Daniel Nunes ([e-mail]) has agreed to this under the assurance that I 
will only be checkin modifications to beos specific folders.

Comment 3

[cls]

Yes, I'm vouching with the same understanding as leaf, changes 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 .

Comment 4

[kurros (Wade Majors)]

I can agree with those guidelines. Most of which were on the form I signed.

Comment 5

[kurros (Wade Majors)]

Just checking in. I know you guys are busy with 0.9 work, don't want to be an annoyance. Is there something else I need to do? What's the next step?

Comment 6

[Daniel (Leaf) Nunes]

marcia, wade is outside the regular criteria, on the basis that he's going to be 
 touching BeOS specific folders. cls vouching was the only thing he needed.

Comment 7

[Marcia Knous [:marcia]]

Per Leaf's comment, account activated. resolving as fixed.