Linaro Connect Q1.12 Requirements
The requirements for LCQ1.12
Blueprint information
- Status:
- Complete
- Approver:
- Stephen Doel
- Priority:
- Essential
- Drafter:
- Chris Johnston
- Direction:
- Approved
- Assignee:
- Summit Hackers
- Definition:
- Approved
- Series goal:
- Accepted for summit-2012
- Implementation:
- Implemented
- Milestone target:
- lcq1-12
- Started by
- Chris Johnston
- Completed by
- Chris Johnston
Related branches
Related bugs
Sprints
Whiteboard
Per summit user roles:
Admin - Should admin maybe be a global role... A position for people who are responsible for assigning the scheduler/manager role? sounds like something in mhall119's job description.
Scheduler
Manager
Track lead
User
I'm not sure if we need an 'admin' and a 'scheduler' so that's my only maybe thought.
Each role has all perms assigned to roles below it.
Work Items:
Create user roles: DONE
Allow TLs and above to modify the schedule prior to the start of the event: POSTPONED
Allow for marking required participants in summit: DONE
Allow for adding email addresses for required participant who are non-Launchpad users: POSTPONED
Allow for scheduling meetings outside of normal slots: POSTPONED
Set up busy times to keep people from being allowed to be scheduled into two meetings at once: POSTPONED
Email non-Launchpad user to tell them about the meeting: POSTPONED
Provide leads and above the ability to edit their private meeting: DONE
Show users their Private Meetings: DONE
Linaro still wants autoscheduler working (see below): DONE
Wish list
Admin able to subscribe/
Being able to book a 2+ hour meeting over a break
"> The Summit rescheduler gets turned off when the event starts
Maybe this is something to reconsider as well (it shouldn't be too hard,
imho): we only need to stop rescheduler from touching stuff that
happened in the past (perhaps everything including the current day; but
that'd be up for debate)."
NOTES:
The ability to make a private URL which may be shared with non-attendees has been created.