Confirmed users
954
edits
Firefox/Projects/Animation priorities: Difference between revisions
Jump to navigation
Jump to search
Firefox/Projects/Animation priorities (view source)
Revision as of 19:35, 28 September 2009
, 28 September 2009→Next Steps: +stuff
(-old info) |
(→Next Steps: +stuff) |
||
| Line 23: | Line 23: | ||
To implement these three areas of animation, first they should be divided into two sprints: one longer-term sprint for tab tearoff and tab movement, and one shorter-term sprint for find-on-page. The reason for this is that tab tearoff and tab movement both involve backend core development (roc & crew), while find-on-page can be done front-end (possibly firefox team). Though its contingent on who has free cycles, both sprints can be developed simultaneously. | To implement these three areas of animation, first they should be divided into two sprints: one longer-term sprint for tab tearoff and tab movement, and one shorter-term sprint for find-on-page. The reason for this is that tab tearoff and tab movement both involve backend core development (roc & crew), while find-on-page can be done front-end (possibly firefox team). Though its contingent on who has free cycles, both sprints can be developed simultaneously. | ||
==Phase 1 (~1.5 - 2 weeks) | ==Phase 1 (~1.5 - 2 weeks)== | ||
* Set up two separate sprints: tearoff and tab movement | * Set up two separate sprints: tearoff and tab movement | ||
* Have initial meeting with developers to outline what skills and time are needed to implement them | * Have initial meeting with developers to outline what skills and time are needed to implement them | ||
* Find developers with free cycles and interest in the sprints | **(talk to Vlad first half of week 1) | ||
* Blog about the beginning of implementation | * Find developers with free cycles and interest in the sprints (zpao?) | ||
* Blog about the beginning of implementation (srsly) | |||
* Tightening up wireframes in preparation for implementation | * Tightening up wireframes in preparation for implementation | ||
==Phase 2 (~2 weeks)== | ==Phase 2 (~2 weeks)== | ||
* Detailed implementation plan begun | * Detailed implementation plan begun based on meetings during phase 1 | ||
* Bugs created to track progress & are assigned | * Bugs created to track progress & are assigned | ||
* Informal user testing to optimize for speed, transitions, magnitized locking distance, etc | * Informal user testing to optimize for speed, transitions, magnitized locking distance, etc | ||