| «« Iron Ring Ceremony | Agility vs Quality »» |
|
About
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.
Projects
» 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
BulletBlog
Now hosted on Hey! Heads Up -- check it out!
Syndication
Pings
Recent
Derek Lowe's (Ryan's older brother) words at Ryan's funeral
blog@ryanlowe.ca no more Forging Email Headers: Good, Bad or Ugly? Sarcastic Dictionary (Part 1 of Many) Tags Hierarchies Twisting Rails is Risky Business Risky Business? My Take on Early Alphas Whoa, it's August 2007 Closing Comments A Postscript to "Growth at the grassroots" »» All Blog Posts
Linkage
del.icio.us/ryanlowe
technorati/ryanlowe.ca/blog Aurora Roy Jim Andrew Trasker Travis Kibbee Karen Dr. Unk Ayana Van Bloggers Joel Spolsky Robert Scoble Tim Bray Dave Winer Raymond Chen James Robertson Ruby/Rails Bloggers rubyonrails.org weblog David Heinemeier Hansson Dave Thomas James Duncan Davidson Mike Clark Jamis Buck Signal vs. Noise Tobias Luetke Amy Hoy: (24)slash7 Jeremy Voorhis Eclipse Bloggers Planet Eclipse EclipseZone Luis de la Rosa Eclipse Foundation Kim Horne Billy Biggs Ian Skerrett Mike Milinkovich Bjorn Freeman-Benson Denis Roy
Archives
|
The AudioMan Project Begins
I hereby kick off the AudioMan Project. I wrote some tentative ideas down and I'm looking for feedback. Here's an excerpt from the page: AudioMan is a digital music organizer for personal computers. The purpose of the AudioMan Project is not only to create a useful product but also to explore software engineering practices and tools and to collaborate on a group project without severe pressure from market forces. The processes and code of the AudioMan Project will be completely transparent and free for the general public to read and discuss. This transparency will also allow members to second-source others. In that sense, this project will be artifact-heavy. If you don't like writing about what you are doing this project is probably not for you. One of the primary goals is to stimulate discussion of software engineering topics. The project will start with the code that Karen, Peter, Trevor, Jim and I produced during our year-long fourth year school project. Update 8:18 AM: I guess I should give more details. :) Yes, it's open source -- at the end of the school project (this month) we decided to release the AudioMan source code. We have not decided on a license yet. I wouldn't call it an experiment since we are writing a (hopefully) useful product. I would say it's a typical open source project but done by software engineers. So in terms of organization it is more like the Eclipse project than the Linux kernel project. Rather than use the BIFI (build-it, fix-it) approach that is common in open source projects we will use a more organized process. Sure, this may slow us down a little in the short term but I am confident that long term gains will be realised. Collaboration will probably be mostly online but given that most of the prospective members are from the Ottawa area I'm sure we can have face-to-face meetings over beers every once in a while. You don't have to be in Ottawa to join the project though. Posted at December 02, 2003 at 04:10 AM ESTLast updated December 02, 2003 at 04:10 AM EST Comments
Is it open source? Is this some Internet collaboration experiment? » Posted by: at December 2, 2003 07:46 AM"this project will be artifact-heavy" I would also be interested in experimenting with various types of artifacts - to further my thesis work from u of o. I also believe that this artifact-heavy approach is not necessarily big-design-up-front (BDUF) docs - but more along the eclipse line... documenting the entire approach for others to follow what we have learned. Sounds like an excellent plan... I like the notion of *trying* tools, approaches, styles on a real system. I'm in » Posted by: aforward at December 2, 2003 08:50 AMNeed any marketing help ;-) I think I can provide a good user/market prospective, so let me know if there is anything I can help out with. T. » Posted by: Travis at December 2, 2003 10:13 AMI'd like to join. ;-) I'd really like to be able to try things out in parallel to work, not having a job on the line, and be able to see what works and doesn't. » Posted by: Jim at December 2, 2003 10:20 AMMarketing and the user interface/experience will be something we'll probably need help with. :) » Posted by: Ryan at December 2, 2003 10:36 AMhttp://sourceforge.net/projects/audioman/ » Posted by: at December 2, 2003 11:22 AMYeah, I've seen that project. It hasn't been updated in a year and a half -- it's probably dead in the water. » Posted by: Ryan at December 2, 2003 11:28 AMWhat a coincidence. I'm searching for this phrase on google: "should I get masters or a job" and your page turns up as the second hit. P.S. (I'm the first poster in this comment block) » Posted by: at December 2, 2003 02:10 PMYeah, I went through that thought process "out loud" and decided I'm not much of an academic. :) » Posted by: Ryan at December 2, 2003 03:49 PMAs this project has been officially kicked off, I would like to added to the special teams unit. » Posted by: James at December 3, 2003 02:07 PMYou mean like Punt and Kick-off returns? hehehe. Sorry. I couldn't help myself. » Posted by: roy at December 3, 2003 07:11 PMI haven't heard a joke that bad since your last one, Roy. ;) » Posted by: Ryan at December 3, 2003 08:04 PM |