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:28, 28 September 2009
, 28 September 2009+next steps
(→Mockups: +stuff) |
(+next steps) |
||
| Line 33: | Line 33: | ||
* (possibly) Creating quick iterations with interested developers | * (possibly) Creating quick iterations with interested developers | ||
= | =Next Steps= | ||
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) | ||
* | * 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 | ||
** | * Find developers with free cycles and interest in the sprints | ||
** | * Blog about the beginning of implementation | ||
* Tightening up wireframes in preparation for implementation | |||
==Phase 2 (~2 weeks)== | |||
* Detailed implementation plan begun | |||
* Bugs created to track progress & are assigned | |||
* Informal user testing to optimize for speed, transitions, magnitized locking distance, etc | |||
* Wireframes finalized into mockups | |||
==Phase 3 (~.5 weeks)== | |||
* Patches written | |||
* Final tweaks & testing, reviews & landing | |||
=Tab tearoff= | =Tab tearoff= | ||