Closed
Bug 134913
Opened 22 years ago
Closed 22 years ago
CVS account request for danp@oeone.com
Categories
(mozilla.org :: Repository Account Requests, task)
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: danp, Assigned: marcia)
Details
I would like an account with write permissions to the calendar project. I am currently submitting patches to mikep for calendar's email support. calendar is the only part of the tree that I need to touch.
Comment 1•22 years ago
|
||
Marcia, I'll vouch for Dan.
Comment 2•22 years ago
|
||
I can also vouch for Dan. Its ok to restrict him to the calendar code only.
Reporter | ||
Comment 3•22 years ago
|
||
fax sent, please confirm that it was received.
Comment 5•22 years ago
|
||
Calendar is very close to being enabled in the default builds, isn't it? That will make it fall under the "needs super-reviewing" rules which will mean that checkers-in will need the 3 sr vouchers to get/use CVS access.
Comment 6•22 years ago
|
||
I wouldn't say its close to being added, we've still got more than 1/2 the requirements as TODO (ie. we haven't started work on them). I don't see the calendar being turned on anytime soon. I'd say more like middle to the end of the summer.
Reporter | ||
Comment 7•22 years ago
|
||
3 sr's? I don't think there is a single sr working on calendar at the moment, the project will die when this happens.
Comment 8•22 years ago
|
||
That raises a good question: will we have to revoke access to CVS for MikeP, ColinP and MostafaH because they didn't get 3 sr vouchers? For now, DanP can submit changes to MikeP or ColinP to get them into CVS but we'll have to get this worked out soon. What will we do about CVS access for the current calendar contributors?
Assignee | ||
Comment 9•22 years ago
|
||
Any update on this? Is access still needed?
Comment 10•22 years ago
|
||
No, this isn't a big deal right now. Dan isn't doing much work on the calendar these days. I'll resolve this bug as won't fix.
Status: ASSIGNED → RESOLVED
Closed: 22 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•