Confirmed users
685
edits
Websites/Mozilla.org/Roadmap 2011/Q2WebsiteOnsite: Difference between revisions
Jump to navigation
Jump to search
Websites/Mozilla.org/Roadmap 2011/Q2WebsiteOnsite (view source)
Revision as of 18:44, 11 April 2011
, 11 April 2011no edit summary
(Created page with "== Session Meeting Notes<br> == === 1. Launch Retrospective Phase 1<br> === '''Pain Points'''<br> Would be good to have a checklist of what needs to happen on release day and ...") |
No edit summary |
||
| Line 43: | Line 43: | ||
<br> | <br> | ||
== Goals<br> == | == Goals<br> == | ||
Morgamic: Overview of How to Set Goals<br> | Morgamic: Overview of How to Set Goals<br> | ||
Everyone should know what the mission is: to promote innovation, openess and opportunity on the web.<br> | Everyone should know what the mission is: to promote innovation, openess and opportunity on the web.<br> | ||
From there, you have two areas: Strategic (steering comitte, exec team) and Operational (take high level goals and make them happen)<br> | From there, you have two areas: Strategic (steering comitte, exec team) and Operational (take high level goals and make them happen)<br> | ||
Goals ARE YOURS. If you don't understand how goals map to you it's your responsibility to make that clear. Ask us!<br> | Goals ARE YOURS. If you don't understand how goals map to you it's your responsibility to make that clear. Ask us!<br> | ||
Hitting 100% of your goals may not be a good thing. You're not setting goals that are hard enough.<br> | Hitting 100% of your goals may not be a good thing. You're not setting goals that are hard enough.<br> | ||
Goals should be measurable - easy to quantify<br> | Goals should be measurable - easy to quantify<br> | ||
John: Web Team and Engagement Goals Draft: https://wiki.mozilla.org/Mozilla.org/Roadmap_2011/Q2 (read those) | John: Web Team and Engagement Goals Draft: https://wiki.mozilla.org/Mozilla.org/Roadmap_2011/Q2 (read those) | ||
<br> | |||
From a WebDev Perspective: | |||
Goals: moving the to GIT and fixing the Product Release Details libraries. <br><br> | |||
Feedback: | |||
Seems like a lot. How do we track and manage what we're doing? A quarter is only 3 months. | |||
How are incoming Mozilla.com bugs triaged? (Let's talk more about that tomorrow during the release cycle post-mortem) | |||
Prioritization will also be super important throughout | |||
Possibly deeming pages that we know will end of life | |||
Seems like the merge will affect a lot of things - we haven't yet defined a "merge owner" - us as a team should figure out who that person is EOW | |||
Infastructure Architecture needed before the merge (Morgamic)<br> | |||
Figure out the right sequencing of these goals - it could be that this quarter is a lot of storyboarding and planning<br> | |||
<br> | <br> | ||
<br> | <br> | ||
<br> | <br> | ||
<br> | <br> | ||
<br> | <br> | ||
<br> | <br> | ||
<br> | <br> | ||
<br> | <br> | ||
<br> | <br> | ||