Closed Bug 775413 Opened 12 years ago Closed 11 years ago

Scenario E : the mentee does not answer anymore

Categories

(Mozilla Reps Graveyard :: Planning, task)

Product:
Mozilla Reps Graveyard
Component:
Planning
Type:
task
Priority:
Not set
Severity:
critical

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: gpmeneses, Assigned: gpmeneses)

References

(
URL
)

Details

(Whiteboard: u=rep c=planning p=1) 

Sometimes a new applicant is accepted but he/she does not finish the process. How much time a mentor have to wait for an answer? How a mentor must to fill the bug?
I suggest we reject the applicant and close the bug if the applicant has not finished the application process and has not shown any sign of life for 1 month. 

Page to be edited: https://wiki.mozilla.org/ReMo/SOPs/Mentoring/Screening
URL: https://wiki.mozilla.org/ReMo/SOPs/Me...
Status: NEW → ASSIGNED
Component: Mentorship → Planning
Whiteboard: [SOP]
Group: mozilla-reps-admins
I have edited the page. Please, review the redaction
Assignee: pierros → gpmeneses
Severity: normal → critical
Whiteboard: [SOP] → [SOP] needs review
A note must be made for the mentor to roll back steps that they may have done, e.g. set up a profile
I have reviewed and I have made the necessary tweaks. 

I think we're good to go with this SOP update now.
Whiteboard: [SOP] needs review → [SOP] final tweaks made - council should do a last pass
Flags: remo-approval?
Whiteboard: [SOP] final tweaks made - council should do a last pass → [SOP] final tweaks made - council should do a last pass #docsprint1212 #remoto12
Whiteboard: [SOP] final tweaks made - council should do a last pass #docsprint1212 #remoto12 → [SOP] final tweaks made - council should do a last pass #docsprint1212 #remoto12 #remocamp12
Whiteboard: [SOP] final tweaks made - council should do a last pass #docsprint1212 #remoto12 #remocamp12 → u=rep c=planning p=1
Status: ASSIGNED → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Product: Mozilla Reps → Mozilla Reps Graveyard
You need to log in before you can comment on or make changes to this bug.