Improve scheduling of sessions for summit
Registered by
Alexander Sack
We want to get rid of implicit tools requirements to make sessions be picked up by the summit scheduler and do something smarter about it. Brainstorming and innovation needed.
Initial requirements from asac/kiko:
+ Avoid to rely on the name/project/series in any way to pick blueprints up and also don't require the blueprints to be necessarily linked from a roadmap card.
+ Avoid the need for creating session blueprints for every roadmap card.
Blueprint information
- Status:
- Complete
- Approver:
- Данило Шеган
- Priority:
- Undefined
- Drafter:
- None
- Direction:
- Needs approval
- Assignee:
- None
- Definition:
- Obsolete
- Series goal:
- Accepted for trunk
- Implementation:
-
Unknown
- Milestone target:
- None
- Started by
- Completed by
- Данило Шеган
Related branches
Related bugs
Sprints
Whiteboard
[asac, May 7, 2012]: lets discuss these requirements at connect session and see if we can fold them in elsewhere.
[dzin, Jun 21, 2012] This will be handled in the summit area. Obsolete here.
[danilo, Jan 16, 2013] We are not looking at this anymore, obsoleting.
(?)
