[pony-build] Sprint thoughts

C. Titus Brown ctb at msu.edu
Thu Jan 7 21:01:22 PST 2010


Hi all,

again to the UCOSP students --

between now and the sprint, I'd like you to think about what you want to
do at the sprint and to start thinking about what you would like to do this
term with pony-build.

--

pony-build is pretty "young" and it's not a lot of code, so some core
projects are pretty accessible.  See, for example,

  http://wiki.github.com/ctb/pony-build/projectlets

There's a lot of technical debt to be paid off, too; see

  http://wiki.github.com/ctb/pony-build/bigprojects

Documentation, examples, and tests are a great way to be productive, too,
as are UI reviews and fixes.

--

For the sprint, I'd like to suggest that we do some or all of the following:

0. Get pony-build up and running on your machine and in your account on
my server (which I have not yet set you up with, yes).

1. Go through the use and abuse of git and github.  git is pretty complicated,
but it's also quite awesome.  If you walk away from this term with a
thorough knowledge of git, it will all be worth it :)

2. Look at some of the world-changing projects here,

  http://wiki.github.com/ctb/pony-build/leaderboarddesign
  http://wiki.github.com/ctb/pony-build/recipes

and try to break down the various issues and tasks to get a prototype
or outline of the code working.

3. Figure out how to use Google Wave (Max?)

I'm pretty flexible and quite happy to go with the flow, IF there's a flow.
If there's not I will create my own and you will be brought along in the
undertow :)

Thoughts? Comments?

--titus
-- 
C. Titus Brown, ctb at msu.edu



More information about the pony-build mailing list