Paladin/Tuesday 2011-Oct-11 goals: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
(Created page with "== constraints == * because it's already mid-Oct & holidays in Dec, effectively ~2 months (8 weeks) left. * 3 weeks before NewGame conference * dmose on paternity leave for sever...")
 
(joystick/input.js blogged about)
 
(7 intermediate revisions by 2 users not shown)
Line 1: Line 1:
== constraints ==
== constraints ==
* because it's already mid-Oct & holidays in Dec, effectively ~2 months (8 weeks) left.
* because it's already mid-Oct & holidays in Dec, effectively 2.5 months (10 weeks) left.
* 3 weeks before NewGame conference
* 3 weeks before NewGame conference
* dmose on paternity leave for several weeks (prob starting late November)
* dmose on paternity leave for several weeks (prob starting late November)


== current finalist goals ==
== current finalist goals ==
* release minimum viable Gladius (graphics, maybe sound) 0.1 at NewGame conf (stretch goal: good enough to livecode a cool thingy)
* present Gladius at NewGame conference
* non-trivial experiment with paired TDD in Gladius
* build a performance test framework that is very useful to us (for preventing regressions) and to the JS team (for preventing regressions & targeting improvements)  
* build a performance test framework that is very useful to us (for preventing regressions) and to the JS team (for preventing regressions & targeting improvements)  
** We've been talking to Luke Wagner on the JS team above about this one.  It seems like a good goal, because it's fairly crisp, necessary, and depends only very lightly on the JS team.
** We've been talking to Luke Wagner on the JS team above about this one.  It seems like a good goal, because it's fairly crisp, necessary, and depends only very lightly on the JS team.
* release one mini-game this quarter built around an important platform feature (e.g. browserId, joystick, touch...)
* release minimum viable Gladius 0.1 (graphics, maybe sound)
* release one mini-game as Open Web App this quarter built around an important platform feature (e.g. browserId, joystick, touch...)


== other stuff we'd like to see move forward ==
== other stuff we'd like to see move forward ==
* spin up web presence (blog intros, blogging, getting involved -- jbuck?)
 
** joystick (input.js) - jbuck
*spin up web presence (blog intros, blogging, getting involved -- jbuck?)  
** turn jbuck's blog post about module owners into a mozilla.org wiki page - jbuck
**<strike>joystick (input.js) - jbuck</strike> - Intro [http://jbuckley.ca/2011/10/getting-started-with-input-js/ blogged], code/issues on [https://github.com/jbuck/input.js Github]
** get paladin dev environment running on your platform of choice
**turn jbuck's blog post about module owners into a mozilla.org wiki page - jbuck  
* workflow improvement: continuous integration, retrospectives
**get paladin dev environment running on your platform of choice  
* get one WebAPI (joystick API) landed in mozilla-central - ted
*workflow improvement: continuous integration, retrospectives  
* Get git added to mozilla-build? (Contact Kyle Huey for direction) for low barrier to entry
*get one WebAPI (joystick API) landed in mozilla-central - ted  
* add perf/[paladin] searches to wiki page - dmose
*<strike>Get git added to mozilla-build</strike>? [https://bugzilla.mozilla.org/show_bug.cgi?id=590921 Filed], slated for mozilla-build 1.7. [http://jbuckley.ca/2011/10/getting-git-working-in-mozilla-build/ Workaround] on my blog, will be integrated into the dev environment setup for Windows.
*add perf/[paladin] searches to wiki page - dmose


== random brainstorms that no one has currently signed up for ==
== random brainstorms that no one has currently signed up for ==

Latest revision as of 16:28, 19 October 2011

constraints

  • because it's already mid-Oct & holidays in Dec, effectively 2.5 months (10 weeks) left.
  • 3 weeks before NewGame conference
  • dmose on paternity leave for several weeks (prob starting late November)

current finalist goals

  • present Gladius at NewGame conference
  • non-trivial experiment with paired TDD in Gladius
  • build a performance test framework that is very useful to us (for preventing regressions) and to the JS team (for preventing regressions & targeting improvements)
    • We've been talking to Luke Wagner on the JS team above about this one. It seems like a good goal, because it's fairly crisp, necessary, and depends only very lightly on the JS team.
  • release minimum viable Gladius 0.1 (graphics, maybe sound)
  • release one mini-game as Open Web App this quarter built around an important platform feature (e.g. browserId, joystick, touch...)

other stuff we'd like to see move forward

  • spin up web presence (blog intros, blogging, getting involved -- jbuck?)
    • joystick (input.js) - jbuck - Intro blogged, code/issues on Github
    • turn jbuck's blog post about module owners into a mozilla.org wiki page - jbuck
    • get paladin dev environment running on your platform of choice
  • workflow improvement: continuous integration, retrospectives
  • get one WebAPI (joystick API) landed in mozilla-central - ted
  • Get git added to mozilla-build? Filed, slated for mozilla-build 1.7. Workaround on my blog, will be integrated into the dev environment setup for Windows.
  • add perf/[paladin] searches to wiki page - dmose

random brainstorms that no one has currently signed up for

  • recruit one or more projects to consume Paladin work
  • release one mini-game on mobile (WebGL perf dependency)
  • release one mini-game on mobile that uses a sensor in an interesting way (no WebGL)
  • release one mini-game on mobile using touchlock/multitouch
  • release one mini-game using assets authored from some open-assets partnership (talk to CJ, humph)