|«« Week 08 Status Report||Week 09 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!
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"
An Abuse Trifecta
»» All Blog Posts
David Heinemeier Hansson
James Duncan Davidson
Signal vs. Noise
Amy Hoy: (24)slash7
Luis de la Rosa
Durham and AudioMan Moving to SourceForge
As I worked on AudioMan I realised that the metadata framework it used might be useful to other people so I separated it into a product called Durham. Now I'm going to call it the Durham Metadata Framework for Eclipse and make it the primary focus of my open source efforts.
Yes, AudioMan will still be a released product, it just won't be the main product. AudioMan will be an example metadata-using application that shows off what Durham can do. It will be open source so people can see how Durham can be used. AudioMan will be a client of Durham's API, helping me sympathize -- for lack of a better word -- with other developers using Durham.
I registered Durham with SourceForge.net and it was accepted. Over the next week I'll be renaming Java packages and reorganizing Durham, AudioMan and QuickEditor to fit into Durham's home on SourceForge. All three will be released from that one place at the same time.
I'm hoping that registering Durham with SourceForge will help me build more of an open source community around Durham and get it noticed.
This also affects when I choose to make a release. Before I made this switch I was releasing when AudioMan was done. Now the release date will all depend on Durham's stability. The stability and usability of AudioMan and Quick Editor are secondary.
When I make a release, AudioMan and Quick Editor will be less stable than Durham. This only makes sense from a testing standpoint. Durham will have three clients bashing on it -- the test suite, AudioMan and Quick Editor -- and from a testing perspective has an advantage over the two end-user products.
Indeed, I'm positioning Durham to be Yet Another Eclipse Framework. At least it doesn't have an ordinary TLA. I'm not going to make some official-looking Eclipse proposal document and then not follow through on it. I want to deliver real software. I'd like to get Durham out of the vapourware stage before I make any kind of proposal like that. When you don't have a big company behind you shipping working and stable software is a good way to be taken seriously. Maybe the only way. That is my goal ... and it's no secret.
I haven't decided what I'm going to do with the
Thanks to everyone for their support for AudioMan (and Durham) over the years! Yep, it's been years already.Posted at April 20, 2005 at 07:01 AM EST
Last updated April 20, 2005 at 07:01 AM EST