draft 2012 & 2012Q1 goals for review

[Dan Mosedale]

Here are some (extremely) draft-y possible goals that Alan and I came up with for both 2012 and 2012 Q1.  Because of holiday schedule complications, they haven't yet gotten any input from a number of different important stakeholders (quite possibly including you).

Next Steps:

1) MoCo management needs a copy of this now, so I'll send it along to them at the end of today in its current state, clearly marked as a draft. 

1a) If you have input that can be incorporated today, let me know.

2) We'll have a call next week (if sufficient stakeholders are around) or the week of the 9th (otherwise) to review and revise these goals. Once the goals are revised, I'll post the updates and pass them along to MoCo management.

The Goals:

2012 draft goals

* evolve Paladin project to deliver clear, quantifiable value to the Mozilla & gaming universes

** develop & spread a crisp narrative for the Mozilla community and to attract others

** choose metrics and set 2012 targets for user base and community growth

** improve geodistribution of core Paladin team beyond Toronto by growing the SF cell

** evolve roadmaps for both Paladin as a whole as well as individual projects

* ship at least one release of Gladius or an affiliated JS library per month

** work with humph & students to create a virtuous development feedback cycle of mini-games driving Gladius & associated libraries

** land new browser features aimed at game developers

* release innovative (in the sense of only-possible-with-the-web) mobile game built on Gladius

** demonstrates important new tech such as apps, identity, gecko features...

** generative (a la minecraft, leveler games)

** evolve a prototype game into a publishable project

** ship as default B2G sample game

2012 Q1 draft goals

** clarify relationship between labs, foundation, & platform team interests & efforts

** land mouse-lock API in mozilla-central

** land gamepad API in mozilla-central

** ship two Gladius releases, and one release of another project (input.js?)

** choose metrics and set 2012 targets for user base and community growth