Dev call 10/27/2010

, | Tweet this

Miro 3.5 status (roadmap)

  • done!

Miro 4.0 status (roadmap)

  • we're going to wait a while to figure out whether we need to do a 3.5.1 or whether we can sit on it for a while.
  • we're now pushing on 4.0

Miro Community 1.1.2 status (roadmap)

  • Asheesh is the new MC for MC
  • working on bugs


  • pushed Miro 3.5 out
  • worked on conversions matrix
  • working on ffmpeg issues on OSX


  • pushed Miro 3.5 out
  • updated the Miro User Manual
  • updated ubuntu packaging scripts
  • worked on trac to mediawiki work


  • worked on syncing support; all basic functionality is implemented on all platforms now
  • now working on interface bits and figuring out how to sync feeds


  • worked on implementing metadata discovery, storage and ui for it


  • worked on performance changes for making startup, switching tabs and other ui things faster


  • worked through OSX bugs in Bugzilla and triaging/fixing them
  • fixed issues with unicode/str issues with file paths


  • worked on making the Facebook login more featureful for Miro Community
  • spent a bunch of time chasing down an IE8 bug that then disappeared
  • planning to continue working on Facebook login issues
Order of business:
  • Welcome to Geoffrey!
  • We're pretty psyched to have gotten Miro 3.5 out the door.
  • Talked about id3 metadata bits and storage.
  • Talked about device syncing.
  • Talked about performance enhancements.
  • If you can't contribute your time, please consider contributing funding by donating. Your money goes directly to ongoing development of Miro and related projects.
  • Did you know there's a Miro User Manual? If you haven't looked at it yet, it's worth taking a look at. You can find it at

Bugzilla stats for Miro:

  • 20 bugs/feature-requests created
  • 13 bugs marked WORKSFORME
  • 5 bugs marked INVALID
  • 12 bugs marked DUPLICATE
  • 7 bugs marked WONTFIX
  • 17 bugs marked FIXED
  • 9 bugs marked INCOMPLETE
Want to comment? Send an email to willkg at bluesock dot org. Include the url for the blog entry in your comment so I have some context as to what you're talking about.