User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.0) Gecko/20020618 Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.0) Gecko/20020618 I'd like to apply for my cvs checkin access. My interests are mainly in layout and calendar. Contributions: bug 92980: Fixed. r=jkeiser sr=kin guess out IE6's algorithm and provide patches. bug 166750: Checked in. r=jkeiser sr=kin p1 critical crasher. provide patch bug 50998: Fixed. r=biesi sr=rbs p2 normal. provide patches for qt/mac/mac/photon/beos platforms bug 170225: Fixed. r=jkeiser sr=bryner p2 regression crasher. provide patches. Reproducible: Always Steps to Reproduce: 1. 2. 3.
Too early... Need to learn more.
I don't know how stringent the requirements are for checkin, but I know Rick is a good programmer and works well with others. I will vouch.
rbs, surely i'll work hard to fix more bugs and learn more ASAP :) i am working on some other bugs these days and hope to get them fixed soon. john, thanks for ur vouching knous, i have faxed the form. did u get it?
Status: NEW → ASSIGNED
sr=bzbarsky. Rick has been doing good work in layout.
I agree with Bzbarsky, Rick has been doing good job on fixing layout problems, I vouch for Rick. BTW, Rick, I suggest you update your working list here in bugzilla.
sr=bryner. looks like good work.
email@example.com - Rick seems to have gotten a bit more familiar with how layout works over the last few months so I'd be comfortable giving him checkin privileges. rbs, do you still have any objections?
No further objections from my end.
Thanks you all!
rbs: are you giving an sr=? If so I can activate Rick's account. thanks.
Status: ASSIGNED → RESOLVED
Last Resolved: 16 years ago
Resolution: --- → FIXED
Rick, during some maintenance of the CVS server, it was noticed that your account was not set up correctly. For some reason, your account was "firstname.lastname@example.org" instead of the normal "rick.ju%sun.com". This has been corrected, so from now on, you'll need to use "email@example.com:/cvsroot" for your CVSROOT. Sorry for the inconvenience.
You need to log in before you can comment on or make changes to this bug.