|«« Communicating and Collaborating on a Vision||Week 01 Status Report »»|
I'm Ryan Lowe, a Software Engineering graduate living in Ottawa, Canada. I like agile software development and Ruby on Rails.
I write this blog in Canadian English and don't use a spell checker. Typos happen.
» Full-time Ruby on Rails freelancer
» Full-time with Rails since May 2005
» Former committer for RadRails (now Aptana)
» I also have a few Rails side-projects in development:
1. wheretogoinTO.com Toronto nightlife
2. Hey Heads Up! TODO list and sharing
3. Layered Genealogy family history research
4. foos for foosball scoring
5. fanconcert for music fans (on hold)
Hiring Rails developers? I can telecommute by the hour from Ottawa, Canada
»» Email: rails AT ryanlowe DOT ca
Now hosted on Hey! Heads Up -- check it out!
Derek Lowe's (Ryan's older brother) words at Ryan's funeral
email@example.com no more
Forging Email Headers: Good, Bad or Ugly?
Sarcastic Dictionary (Part 1 of Many)
Twisting Rails is Risky Business
Risky Business? My Take on Early Alphas
Whoa, it's August 2007
A Postscript to "Growth at the grassroots"
»» All Blog Posts
David Heinemeier Hansson
James Duncan Davidson
Signal vs. Noise
Amy Hoy: (24)slash7
Luis de la Rosa
Iteration 1 Weekend
- a list of things to do in this iteration
User feedback of iteration x determines which things from the short and long term buckets go into iteration x+1.
To make things easy it's probably best if AudioMan2, Durham and jid3v2 all have synchronized release schedules with the same version numbers. It will be just like how the Rich Client Platform (RCP) is released with Eclipse and they have the same version numbers.
AudioMan2 has dependencies on Durham so either Durham will hold up implementation of features in AudioMan2 or AudioMan will drive Durham development and iteration priorities. It might even be better for a Durham feature to be implemented one iteration before it is needed, so it has a chance to stabilize.
How long is an iteration? Open source projects are less predictable here because you never know how much free time people will have to contribute. The early iterations will definitely be "when it's done" but later we could release more often and on a regular schedule. We don't want iterations to get too long or too big.
The other thing I want to do is make a nice diagram of how all of the AudioMan projects and components will work together. Hopefully that will help to answer questions like: where does the database (data persistence) fit in?Posted at February 25, 2005 at 06:58 PM EST
Last updated February 25, 2005 at 06:58 PM EST