Closed Bug 169026 Opened 22 years ago Closed 20 years ago

Request for CVS checkin privs. - David King

Categories

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

Product:
mozilla.org
Component:
Repository Account Requests
Platform:
x86
Windows XP
Type:
task
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED WONTFIX

People

(Reporter: d_king, Assigned: marcia)

References

(
URL
)

Details

User-Agent: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.2a) Gecko/20020913 Build Identifier: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.2a) Gecko/20020913 Created this bug as per instructions. Reproducible: Always Steps to Reproduce: 1. 2. 3.
David: Can you please resend the CVS Contributor Form to me? Also, please let me know if you want CVS write access or docs access. Also, please add the bugs that you sent in the email to the bug, especially if you are seeking write access.
Status: NEW → ASSIGNED
The CVS permission form will be resent ASAP. I primarily want CVS write access for JS files, however, I have noticed several documentation pages that are out of date (including some www.mozilla.org pages), so access to that would be useful as well. The bugs I am currently working on are http://bugzilla.mozilla.org/show_bug.cgi?id=152504 and http://bugzilla.mozilla.org/show_bug.cgi?id=160942 In the future there will be others from the tracking bug http://bugzilla.mozilla.org/show_bug.cgi?id=104624 that I will attempt to work on.
OK, the form will be resent tomorrow to the following address (as per http://www.mozilla.org/hacking/form.html) :- Marcia Knous Netscape Communications Corp. Mailstop MV-066 466 Ellis Street Mountain View, California 94043 USA
Did you receive my second attempt at sending in the CVS auth form?
Form Received. Adding Asa to the bug since he is interested in documentation. David: For the write access portion of your request, you will need to get a voucher and some SRs. The only way you will get them to look at your code is to add them to this bug. See the mozilla.org/hacking page for a list of the SRs and their area of specialty.
Blocks: 152504
Adding Ben as per Asa's instructions.
Summary: Request for CVS checkin privs. → Request for CVS checkin privs. - David King
David, until you've established a track record it is unlikely that you'll be able to convince 3 super-reviewers to vouch for you. The normal process is that you develop a bunch of patches, get them reviewed, super-reviewed and checked in (by someone else, possibly one of the reviewers). After you've done this for a while you will have interacted with super-reviewers enough and have developed enough code that finding 3 super-reviewers to vouch for you and your code shouldn't be very difficult. For making changes to the documents at the website the barrier is quite a bit lower. Send me email letting me know what kinds of work you're interested in doing there and if it sounds reasonable then I'll vouch for you (one voucher is all that's required for website editing).
I have a patch that I'm trying to get someone to checkin, but after several requests to sr's to checkin for me, I have had no luck. As for web page changes/fixes. http://www.mozilla.org/owners.html needs work to update peoples eMail addresses. (e.g. the address for blakeross is not, I beleive, at telocity.com http://bugzilla.mozilla.org/bug_status.html needs work to embelish the descriptions to be more informative to new users. I already offered to do this page, but noone seemed interested. http://www.mozilla.org/newsbot/ this should probably be removed as mozillazine has all the latest news and reviews. Then, of course, there are the release notes, inparticular "Known Problems" which always seems to be missing useful information (see Bug #171441 for an example of this).
David: Regarding the items you want to work on: David wrote: http://www.mozilla.org/owners.html - needs work to update peoples eMail addresses. (e.g. the address for blakeross is not, I beleive, at telocity.com Someone from mozilla.org staff will look at the owners page and update the email addresses. David wrote: http://bugzilla.mozilla.org/bug_status.html needs work to embelish the descriptions to be more informative to new users. I already offered to do this page, but no one seemed interested. Who did you contact re: this? David wrote: http://www.mozilla.org/newsbot/ this should probably be removed as mozillazine has all the latest news and reviews. David wrote: Then, of course, there are the release notes, inparticular "Known Problems" which always seems to be missing useful information (see Bug #171441 for an example of this). Adding dawn endico to this bug, she can comment re: the release notes.
>David wrote: http://bugzilla.mozilla.org/bug_status.html needs work to embelish >the descriptions to be more informative to new users. I already offered to do >this page, but no one seemed interested. > >Who did you contact re: this? This was offered in Bug #52116 on 7/30/02. I offered as things got somewhat heated due to my reading the rather limited descriptions vs "old hands" who know what the various status' really mean.
Updating data as per recent activity.
No longer blocks: 152504
OS: Windows 98 → Windows XP
Adding another sr'er to the cc list
David, can you point to patches that you've contributed, had reviewed and landed? That would help move this request forward.
I've done :- Bug #152504 Bug #191248 (was checked in after getting an "a" due to being a release blocker) Bug #192584 Bug #216222 has an "r" and is waiting on an "sr" Bug #216609 is waiting on an "r" and a "sr" Bug #209877 has an "r" and an "sr" and I've asked jag to check it in for me
Update, Bug #220978 has a R and approval to checkin to the closed 1.6b tree.
Seth, bz, ben, have you guys seen enough to stamp your sr= for David King?
To be truthful, of the patches pointed to thus far in this bug only two look like they required understanding of what was actually going on around that code (were not repetitive changes)... I'd need to see more to be able to reasonably judge code quality.
My style of programming is to work on the smaller bugs that tend to not attract any "big guns". The problem with that is the resulting code changes are minor and don't show much about my programming abilities. Anyway, here is an update on the bugs that currently have my attention :- Bug #200659 has a "r", waiting on a "sr" (asked for sr on 30 Dec) Bug #216609 waiting on "r" and "sr" (both asked for on 15 Dec) Bug #219938 Still working on this one Bug #225163 has a "r", waiting on a "sr" (asked for sr on 31 Dec) Bug #227896 this has two seperate patches Patch 1 - waiting on a "r" (asked for r on 7 Jan) Patch 2 - has a "r" and a "sr", waiting for someone to checkin for me
I'm not saying you're a bad programmer, David. I'm just saying that the patches I've seen don't provide the information I need.... The patches listed in comment 18 look much more substantive (not in terms of the amount of code changed, but in terms of what one needs to know to change said code). Please send me mail once a few of those have reviews and are checked in, and I'll take another look?
David: Can you please make sure to follow up with Boris via email so we can move this along? Thanks.
David did send me email, and I've looked over the list of bugs he included in that mail (and I apologize for taking so long to do it). The situation is still basically what it was in comment 19....
I have found that I don't have the time to prove my c and c++ programming skills. Rather, I've focused on minor compiler warnings, typos and Javascript code. And when I do have a patch, no one seems willing to do an r or sr or check it in for me.
Status: ASSIGNED → RESOLVED
Closed: 20 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.