We're trying to get a bunch more user stories in the appropriate places
so that Humph's students have things that they can dig into.
Overall status: one set of stories (algorithms) has been added; we have
a deeper understanding of two more sets.
Next steps:
* Humph: are the stories in
https://www.pivotaltracker.com/projects/373719 tagged with algorithms at
a reasonable granularity for you to work with? If not, what else would
be helpful?
* Dan to set up an algorithms github repo templated from the math one Monday
* Dan (and maybe Alan) to create browserId-mediated score-saving project
& user stories on Monday
* humph & jbuck to nail down higher-level joystick API project &
user-stories sometime soon
* some subset of (humph, dmose, jbuck, ack, and luke) need to have a
phone call to get some more of the testing pieces figured out. Monday
would be ideal.
Random bits and pieces:
Alan and I are figuring out how to write better user stories for
Gladius. We've started substituting in "game developer" rather than
"user" as the mental affordance for keeping focus on who the particular
story is intended to support.
I spent some thinking about and talking over the browserId-mediated
scoreboard idea. I ultimately came to the conclusion that the UX for
that is unlikely to be good enough, because the email verification dance
is too high a barrier for the little benefit it gives. Alan suggested a
way to do a saved-game server prototype that wouldn't have that problem.
I talked to a bunch of different folks about various performance test
issues and possible harnesses, and started to get a feel for some of the
issues there. Alan and I dug into some of the various things we
can/could do performance testing around, and focused on a few areas
which seemed like good starting points.
Some etherpads we've been using that may be interesting or may just be
confusing:
https://etherpad.mozilla.org/paladin-perf
https://etherpad.mozilla.org/decoupling
Dan