Miro (old posts, page 21)

Year end: 2010

, | Tweet this

I'm really proud of the work we did this year. Miro went through two major version releases that added support for conversions and subtitles, fixed a lot of issues, and fixed a lot of performance issues. Behind the scenes, we reworked the Windows build environment making building Miro on Windows sooooo much easier. We also switched from our home-grown httpclient to libcurl for faster, better HTTP downloads. We drastically improved our QA and testing. We migrated from Trac to Mediawiki for documentation.

Then in August, Nick stepped up to home plate, hefted his bat a few times, then pointed his finger clear across the field into the stands. Thus started the very aggressive and ambitious Miro 4.0 development cycle. The earth-shaking thunder of changes hitting git master has been growing into a deafening roar.

But the fun doesn't stop there! Miro Community has come a long way in the last year. There are dozens of really great Miro Community communities now and I regularly see urls to Miro Community site pages in Stack Overflow, forum conversations, blog posts, ....

Additionally, Universal Subtitles has gone from a gleam in someone's eye to a system for collaborating on subtitles and translating subtitles for videos across the Internet. Translating video and making it accessible to people is so important. This system is making that magic happen. It's awesome.

It's been a huge year for PCF and the projects we work on.

I want to bring it back down to the project I work on: Miro. Last year I wrote a year-end post with some stats I culled from Bugzilla and git along with some commentary. I do so again this year.

Bugzilla stats:

I took a look at last year's overall stats and I have no idea where I got those numbers. So I tweaked my script and produced new stats.

Last Year's Overall statistics
------------------------------
                                  2007  2008  2009
Opened reports at end of year:     453   705  1102  
Opened:                           4052  1625  1593
Closed:                           4368  2032  1654  
Users created:                     644  1083   771  
Comments created:                13564  7529  8329  


Overall statistics (recalculated)
---------------------------------
                                  2007  2008  2009  2010
Opened reports at end of year:     453   705  1102   720
Created:                          3805  1518  1162   968
Resolved:                         1038  1842  1157  1197
Comments created:                12588  6749  6191  6843
Users created:                     644  1083   771   611

"Opened reports at end of year" is the total number of opened bugs at the end of that year. So at the end of 2007, we had 453 open bugs. At the end of 2008, we had 705 open bugs, ...

As a reminder, we switched from Trac to Bugzilla half-way through 2007 which drastically reduced the amount of bug and comment spam we were getting and dealing with.

Looking at the overall statistics and the recomputed set, the new numbers are lower. I think the old numbers involved all bugs in our Bugzilla instance--Miro and non-Miro bugs. Prior to 2009, that was pretty much the only project we were working on, so the numbers made more sense. Now that Miro Community, Miro Video Converter and Universal Subtitles are using Bugzilla, we need to explicitly focus on Miro bugs.

We have the same problem with the Bugs closed by activity data I did for last year.

The drop in total opened bugs for 2010 happened because a bunch of us did a massive triage campaign at the end of December and resolved a lot of old, stale bugs.

Bugs closed by activity (old set)
---------------------------------

             2007  2008  2009
fixed         736   932   969
invalid       170   133    85
wontfix        35   142    71
duplicate     139   313   190
worksforme    169   344   151
incomplete      0    57    84


Bugs closed by activity (recalculated)
--------------------------------------

             2007  2008  2009  2010
fixed         545   887   648   570
invalid       167   126    72    83
wontfix        34   135    49   160
duplicate     132   305   173   141
worksforme    160   335   133    87
incomplete      0    54    82   156

For most of 2010, there were only two and a half developers working on Miro. We've picked up Geoffrey and Kaz and Paul has come back from Miro Community, so we're churning through fixes faster now. But it's definitely the case that the lower number of fixed bugs is due to reduced staff.

Top 10 bug reporters:
--------------------

     252 - Janet [pcf QA]
     100 - Will Kahn-Greene [pcf dev]
      51 - Geoffrey Lee
      47 - Ben [pcf_dev]
      26 - Nicholas Reville
      23 - Kaz Wesley
      12 - Paul Swartz [PCF dev]
      11 - m.shamraeva (qa-team)
      10 - Dean Jansen
       6 - Nicuta Nicolae

Of the 968 bugs created in 2010, 532 were reported by Miro developers and Janet's QA team.

I'm skipping the top 10 closers this year since it's not clear that number is very meaningful.

Top 10 bug commenters:
---------------------

    3417 - Will Kahn-Greene [pcf dev]
    1111 - Janet [pcf QA]
     525 - Ben [pcf_dev]
     388 - Geoffrey Lee
     192 - Paul Swartz [PCF dev]
     137 - Nicholas Reville
     113 - Luc Heinrich
      64 - Kaz Wesley
      24 - David Stoll
      16 - Dean Jansen

Most of these people are PCF staff. David Stoll is not--he helped a ton in fixing httpauth and http proxy issues for Miro 3.5.

Git stats

In 2010, we did 6 releases (2 major, 4 bugfix). We did 14 releases if you include release candidates. Version 3.0 added subtitles and a lot of performance fixes. Version 3.5 added http proxy and auth support, switch to libcurl, conversions and a lot of polish and some performance fixes.

Between Miro 2.5 and 3.0:
1017 files changed, 190346 insertions(+), 280726 deletions(-)
667 checkins

Between Miro 3.0 and 3.5:
1021 files changed, 307395 insertions(+), 253431 deletions(-)
606 checkins

Paul, Geoffrey and Kaz hopped on the Miro team post 3.5, so I think it's interesting to measure changes between 3.5 and HEAD:

Between Miro 3.5 and git master HEAD:
552 files changed, 31627 insertions(+), 22898 deletions(-)
521 checkins

You'll notice the number of insertions and deletions is an order of magnitude smaller--a lot of that churn happens before a release when I sync translations. I haven't synced translations in git master for 4.0, yet, so the insertion/deletion numbers are much lower.

In 2009, we did 1,382 commits. In 2010, we did 1,341 commits.

Contributor stats

In 2009, we had 19 contributed fixes. I doubt I checked in that many patches this year, but I don't have good stats for that this year.

Having said that, with Miro 3.5 we introduced a CREDITS file which is a much more comprehensive list of contributors since it covers people who report bugs, comment on bugs, fix bugs, translate, help with QA, donate money, ... This CREDITS file will be a better measure of how we're doing contributor-wise than looking at Bugzilla stats alone was. I still need to figure out a better method for figuring out who has helped with translations, testing nightlies, and supporting other Miro users -- those areas are important, but more difficult to quantify.

We continued to work on reducing the barriers to entry for contributing to Miro:

  • We switched from Trac to Mediawiki which will make it much easier to write, edit, and curate documentation on the project.
  • We hired Asheesh from OpenHatch to help us figure out how to build a community of contributors.
  • We overhauled the Windows build environment making it possible for people to build Miro on Windows. Prior to this work, we were using Python 2.5 and Visual Studio 2003 which wasn't available.
  • We continued triaging bugs and adding the "bitesized" keyword to bugs we think would be easier for new contributors to work on.

There's always more work to do.

Summary

The Miro 2.5 release in 2009 sucked. We've made a lot of improvements to our infrastructure, process, and code quality since then. 2010 was a good year and we got a lot accomplished despite having a painfully small number of staff for most of the year.

I'd love to see more contributions from other people. If you have some free time or some passion and want to help out, let me know. If you don't have free time, but have some spare change floating around, please donate--this helps PCF pay for staff to work on Miro. Having more staff and more contributors absolutely affect Miro's speed of growth.

Also, contributing to Miro gets your name in the Credits! I got my name in the Firefox 3.0 credits for work I did and it was one of the highlights of my year.

Dev call 01/05/2011

, | Tweet this

Welcome to 2011!

Miro 4.0 status (roadmap)

  • working on metadata support, device syncing, performance enhancements, extensions, streaming to other devices (ipad, ...), ...
  • working on project infrastructure: wiki, nightlies, nightly runs of unit tests, ...

Geoffrey:

  • continued working on pydaap--streaming is working now
  • working on getting Miro and Miro Video Converter into the Mac app store
  • wrote up a long missive regarding signal and concurrency issues

Kaz:

  • worked on automatic ratings based on play/skip counts
  • worked on coverart extraction from metadata
  • worked on views and other things, too

Asheesh:

  • merged Duke code into main so we're not working on two different Miro Community code bases
  • finishing up tiers

Paul:

  • worked on refactoring Item code so there's more shared code between Item and DeviceItem to make it easier for other data sources
  • worked on handling generic devices

Will:

  • Worked on a bunch of analysis stuff.
  • Started tackling the flashscraper -> vidscraper project.
  • Feeling kind of overwhelmed with how much is going on and what's on his plate.

Ben:

  • Worked on GtkTreeModel performance issues when displaying and manipulating item views.

Order of business:

  • Morgan is almost done with new ui mockups.
  • Talked about how to do ui workflow and whether to have one person do all the ui implementation or spread it out.
  • Elected chiefs of various domains:
    • Electing Ben as Chief Architect.
    • Electing Geoffrey as Chief OSX wrangler
    • Electing Kaz as Chief Linux wrangler
    • Electing Will as Chief infrastructure wrangler (unit tests, localizations, bugzilla, wiki,
    • Electing Will as Chief Windows wrangler
    • Electing Janet as Chief of QA
    • Electing Paul as Chief of Everything Else
  • Talked about GtkTreeModel performance issues.
  • git master is in pretty heavy flux right now and because of that nightlies are pretty unstable--use them at your own risk. This will sort itself over time when there are fewer massive changes being made.
  • PCF is looking to hire another Miro developer and a System Administrator. See the jobs page for more details.
  • Miro is developed by a community of people including you! If you can't contribute your time and work, please consider contributing funding by donating. Your money goes directly to ongoing development of Miro and related projects. See http://pculture.org/about/ for more details on these 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 http://getmiro.com/userguide/.

Bugzilla stats for Miro for the last week:

  • 29 bugs/feature-requests created
  • 1 bugs marked DUPLICATE
  • 7 bugs marked FIXED
  • 2 bugs marked INCOMPLETE
  • 4 bugs marked INVALID

Dev call 12/29/2010

, | Tweet this

Miro 4.0 status (roadmap)

  • working on metadata support, device syncing, performance enhancements, extensions, streaming to other devices (ipad, ...), ...
  • working on project infrastructure: wiki, nightlies, nightly runs of unit tests, ...

Kaz:

  • continued working on metadata-related work
  • working on a view menu for showing/hiding columns

Ben:

  • rewrote search code
  • continuing to work on ui performance enhancements

Geoffrey:

  • worked on pydaap
  • worked on bonjour support--running into license issues

Paul:

  • mic was dead

Will:

  • fixed a bunch of bugs
  • got extensions mostly done
  • planning to work on conversions-related bugs and looking into ditching flashscraper

Order of business:

  • Windows bonjour library: Licensed under the Apache license. Looks like we can't compile it without a full version of Visual Studio. Need to figure out what to do here.
  • database issues: there might be reentrant-related issues. Ben is going to check to make sure all database changes happen in the backend thread. Geoffrey is going to write up a bug about reentrant issues he's seeing in regards to signal handling. Ben and Geoffrey will continue researching this and we'll talk about it more next week.
  • performance issues with Gtk TreeView: Ben and Kaz are going to look into this over the next week.
  • extensions: Nick says he doesn't want any user-facing parts this time around, so I may just leave that portion as is. I sent out an email with where I'm at to the develop list. Is what I have ok so far? Are there any additional uses for extensions that we want to think about going forward? Is it ready to land?
  • How much work do we think we have left for 4.0? People should write up bugs for all the things they're planning on doing for the 4.0 cycle so we have a good idea of where we're at.
  • git master is in pretty heavy flux right now and because of that nightlies are pretty unstable--use them at your own risk. This will sort itself over time when there are fewer massive changes being made.
  • PCF is looking to hire another Miro developer and a System Administrator. See the jobs page for more details.
  • Miro is developed by a community of people including you! If you can't contribute your time and work, please consider contributing funding by donating. Your money goes directly to ongoing development of Miro and related projects. See http://pculture.org/about/ for more details on these 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 http://getmiro.com/userguide/.

Bugzilla stats for Miro for the last week:

  • 24 bugs/feature-requests created
  • 3 bugs marked WONTFIX
  • 14 bugs marked FIXED
  • 1 bugs marked WORKSFORME
  • 3 bugs marked DUPLICATE
  • 1 bugs marked INCOMPLETE

Dev call 12/22/2010

, | Tweet this

First off, I'm back from "paternity leave" as of Monday. I'm back to taking notes of the dev calls and posting the summaries.

I'm game for changing the way these summaries work. If you have thoughts or criticisms along those lines, let me know either by email or by comments.

Miro 3.5.1 status (roadmap)

  • released!

Miro 4.0 status (roadmap)

  • working on metadata support, device syncing, performance enhancements, extensions, streaming to other devices (ipad, ...), ...
  • working on project infrastructure: wiki, nightlies, nightly runs of unit tests, ...

Kaz:

  • fixed scroll position reset problems
  • working on audio/video detection
  • worked on bug triage

Will:

  • back, but it'll take me a week or two to phase in completely
  • did a lot of bug triage
  • going to switch to Windows for primary development for a while so that platform has someone paying attention to it
  • working on unit test framework bits
  • trying to finish up the extensions research work before the end of the year

Paul:

  • continued to work on device support
  • worked on bug triage

Geoffrey:

  • working on media sharing code (daap) and getting things into the Apple appstore

Janet:

  • worked on Universal Subtitles testing
  • just got builds for the next version of MVC and will test that
  • worked on bug triage

Ben:

  • worked on fast searching; looking at whoosh, but there are some complications

Official business:

  • talked about the state of unit testing and documentation for Miro
  • talked about how Miro will do device support; how users can add support for additional devices; supporting generic devices; supporting other USB mass storage devices (thumbdrives ftw!)
  • we spent a bunch of time over the last week having a massive bug triaging party! We resolved around 200 bugs and now have around 700 open bugs. There were a lot of stale/obsolete bugs that were closed, bugs that we needed input on but never got it that were marked as INCOMPLETE, bugs that got fixed, bugs that got put in the 4.0 target, and some enhancements we looked at and said, "That's just not the direction we're stewarding Miro" and marked as WONTFIX. I think this is the sort of thing we should do either after every new release or at the end of the year.
  • git master is in pretty heavy flux right now and because of that nightlies are pretty unstable--use them at your own risk. This will sort itself over time when there are fewer massive changes being made.
  • PCF is looking to hire another Miro developer and a System Administrator. See the jobs page for more details.
  • Miro is developed by a community of people including you! If you can't contribute your time and work, please consider contributing funding by donating. Your money goes directly to ongoing development of Miro and related projects. See http://pculture.org/about/ for more details on these 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 http://getmiro.com/userguide/.

Bugzilla stats for Miro for the last 4 weeks:

  • 132 bugs/feature-requests created
  • 30 bugs marked WORKSFORME
  • 12 bugs marked INVALID
  • 18 bugs marked DUPLICATE
  • 108 bugs marked WONTFIX
  • 74 bugs marked FIXED
  • 51 bugs marked INCOMPLETE

Note: Numbers above are so high because this is 4 weeks of data--not the usual 1 week of data.

Dev call 11/17/2010

, | Tweet this

Miro 3.5.1 status (roadmap)

  • still working on it

Miro 4.0 status (roadmap)

  • Paul landed the beginnings of device syncing in master
  • working on audio file metadata retrieval, storage, and ui
  • working on extension framework
  • switching testing from eggplant to sikuli

Will:

  • Worked on 3.5.1 stuff.
  • Still working on ffmpeg compliance stuff. I broke conversions in OSX, so I'm working on figuring that out and updating conversions from the matrix
  • We should bump the "application configuration" error up to a p1.
  • Miro is waiting on MVC builds for Windows from Adam, too.

Paul:

Kaz:

  • Added code to update the database to have metadata information.
  • Fixed the code to use mutagen instead of moviedata for audio files which is awesome. 5x faster.
  • Got tag-flattening working.

Geoff:

  • Working on streaming Miro stuff to an iPad.
  • Working on fixes for Miro 4.

Asheesh:

  • Worked on Miro Community 1.2 and fixing issues for Duke.

Janet:

  • Replaced her dead computer--it's now up and running.
  • Regression testing for 3.5.1.
  • eggplant license is about to expire--switching to sikuli

Ben:

  • Working on shepherding 3.5.1 and fixing bugz.

Order of business:

  • We talked about git workflow for R&D branches.
  • Talked about remaining 3.5.1 issues, who's working on what, and how soon we can get this release out.
  • Miro is developed by a community of people including you! If you can't contribute your time and work, please consider contributing funding by donating. Your money goes directly to ongoing development of Miro and related projects. See http://pculture.org/about/ for more details on these 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 http://getmiro.com/userguide/.

Bugzilla stats for Miro:

  • 27 bugs/feature-requests created
  • 2 bugs marked WORKSFORME
  • 4 bugs marked INVALID
  • 5 bugs marked DUPLICATE
  • 13 bugs marked FIXED
  • 4 bugs marked INCOMPLETE

Dev call 11/10/2010

, | Tweet this

Miro 3.5.1 status (roadmap)

  • still working on it

Miro 4.0 status (roadmap)

  • working on audio file metadata retrieval, storage, and ui
  • working on device syncing
  • working on performance enhancements for startup and displaying tabs
  • working on extension framework
  • switching testing from eggplant to sikuli

Paul:

  • device syncing is looking good and is probably ready to land
  • automated syncing of feeds doesn't quite work, yet, but it's getting there

Asheesh:

  • got some MC work done--keeps bumping into access issues and other roadblocks
  • wants to spend time with infrastructure to make things a lot easier going forward: deployment scripts, ...

Will:

  • finished up the documentation I needed to do
  • got most of the things in my queue done
  • working on 3.5.1 bugs and moving build boxes upstairs

Kaz:

  • started adding metadata items to the list view
  • we need to figure out how to add metadata items to the item view, too

Geoffrey:

  • did a lot of bug fixing on OSX
  • worked on importing itunes data into Miro

Janet:

  • started testing on new OSX version for MVC
  • testing Miro 3.5.1 bug fixes
  • worked on Miro Community documentation and testing
  • worked on Universal Subtitles documentation and testing
  • Litmus is broken--sent emails to admin, but haven't heard anything from it
  • one PC broke (Ubuntu and Windows 7 and Windows Vista and Windows XP) and eggplant tests

Ben:

  • worked on 3.5.1 bug fixes
  • fixed a bunch of playback issues
  • having a hell of a time tracking the VLC crash problem down

Official business:

  • talked about coding standards/conventions/etc; we have a document and it needs some additional bits covering utf-8/unicode/filename handling
  • talked about swapping out flashscraper for vidscraper for Miro 4.0; this would fix the problem where downloading a single item from YouTube and other video hosting sites doesn't get useful metadata; it should get done, but probably in January
  • talked about how to notify the user about things they can do with Miro in a context-specific way
  • Miro is developed by a community of people including you! If you can't contribute your time and work, please consider contributing funding by donating. Your money goes directly to ongoing development of Miro and related projects. See http://pculture.org/about/ for more details on these 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 http://getmiro.com/userguide/.

Bugzilla stats for Miro:

  • 49 bugs/feature-requests created
  • 1 bugs marked WORKSFORME
  • 3 bugs marked INVALID
  • 8 bugs marked DUPLICATE
  • 2 bugs marked WONTFIX
  • 18 bugs marked FIXED
  • 4 bugs marked INCOMPLETE

Dev call 11/3/2010

, | Tweet this

Miro 3.5.1 status (roadmap)

  • there are a handful of fixes that suggest we should do a 3.5.1 soon
  • 3.5.1 will include updates to the conversions
  • Ben elected to coordinate and shepherd 3.5.1

Miro 4.0 status (roadmap)

  • working on audio file metadata retrieval, storage, and ui
  • working on device syncing
  • working on performance enhancements for startup and displaying tabs
  • working on extension framework
  • switching testing from eggplant to sikuli

Will:

  • worked on documenting infrastructure, processes, and other things he's involved in
  • did a lot of peer-review on incoming changes
  • fixed some minor things--added app.debugmode
  • could disappear any day now for paternity leave--ping me if there are things you need me to do now

Ben:

  • landed a bunch of performance changes (and fixes)
  • working on figuring out all the things that make the iteminfocache invalid
  • sent email about setup_restored(...); working on that

Kaz:

  • worked out a different way of doing metadata
  • working on ui bits for metadata

Geoffrey:

  • worked on ui glitches and other bug fixing

Janet:

  • working on converting eggplant tests to sikuli tests
  • there are a few bugs that we should make p1 for 3.5.1
  • we should start thinking about doing a 3.5.1

Asheesh:

  • working on maturing Miro Community as a public FLOSS project

Order of business:

  • we updated the appcast file which notifies users that there's a new version of Miro out there; 3.5 is doing pretty well
  • talked about setup_restored(...); Ben has some steps for working on this going forward
  • Ben's going to shepherd the Miro 3.5.1 release which involves making sure all bugs for 3.5.1 are targeted appropriately and all fixes are cherrypicked into the Miro-3.5 branch--he's going to coordinate the 3.5.1 release going forward
  • for Miro 4.0 on Windows, we're going to switch from VLC to gstreamer and also from xulrunner to webkit; we talked about who's going to do this work and when and we're all pretty busy right now, so it'll likely happen in December or thereabouts
  • We decided to push off a Python 2.6 to 2.7 upgrade until a future release unless we hit a really compelling reason to do otherwise
  • Miro is developed by a community of people including you! If you can't contribute your time and work, please consider contributing funding by donating. Your money goes directly to ongoing development of Miro and related projects. See http://pculture.org/about/ for more details on these 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 http://getmiro.com/userguide/.

Bugzilla stats for Miro:

  • 38 bugs/feature-requests created
  • 7 bugs marked WORKSFORME
  • 7 bugs marked INVALID
  • 9 bugs marked DUPLICATE
  • 19 bugs marked FIXED
  • 12 bugs marked INCOMPLETE

As a side note, this is the third week we've been trending downwards in total open bug count for Miro. We're working on triaging and cleaning up bug reports. That's been a lot easier with additional staff--your donations go directly towards these efforts!

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

Janet:

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

Will:

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

Paul:

  • 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

Kaz:

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

Ben:

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

Geoff:

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

Asheesh:

  • 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 http://getmiro.com/userguide/.

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

Dev call 10/20/2010

, | Tweet this

Miro 3.5 status (roadmap)

  • did a Miro 3.5 rc3
  • fixed some bugs, but we're ready for a release

Miro 3.5.1 status (roadmap)

  • there will probably be a 3.5.1--I want to wait until after 3.5 is out to figure out the details.

Miro Community 1.1.2 status (roadmap)

  • Asheesh is the new MC for MC
  • working on bugs
Janet:
  • Regression testing Miro 3.5 rc3 all week long. Some bugs, but everything is currently fixed right now.
  • We have had new people testing Miro 3.5 rc3 through Litmus which is really great.
  • We've been tracking downloads for rc3 and it's looking ok, but we would have hoped to have more help testing.
Will:
  • Wishes we had more quantified Miro 3.5-rc3 testing. That would make him feel more comfortable with where we're at with the release.
  • We have a list of things we should look at and/or fix for Miro 3.5.1.
  • Migrated our developer stuff from trac to mediawiki. (Sent email about it.)
  • Updated the Miro User Manual for 3.5.
Kaz:
  • Working on metadata for Miro 4.0.
  • Mutagen is working out really well.
  • Working on figuring out the ui and db components for metadata storage, viewing, and possibly editing.
Paul:
  • Spent the last week and a half spending quality time with getting Miro on Windows to recognize USB devices.
  • Got it working on Linux. Now working on getting it working on Windows and OSX.
Ben:
  • Reworked configuration for Miro 4.0. (Sent email about it.)
  • Planning to work on performance tuning for Miro 4.0.
Asheesh:
  • Started working on Miro Community this week.
  • Also working on building the Miro community (lowercase c) so that there are fewer barriers to entry and it's more inviting.
  • Got his Miro Community system working and is now working on bugs.
Order of business:
  • Talked about where we're at with the Miro 3.5 release. General consensus is that we're ready.
  • Talked about id3 metadata bits and storage.
  • Talked a bit about device syncing.
  • Talked a little bit about streaming to external devices and Miro streaming apps. Paul had looked into DLNA possibilities to allow external devices control and stream content from Miro. Options look to be either writing our own DLNA system, or adding Twisted/Twisted.Web as dependencies and using an exisiting one. The iPad guy wants to do this in Bonjour.
  • Miro users need your help translating! See Translations for Miro 3.5 -- we need your help! for details.
  • 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 http://getmiro.com/userguide/.

Bugzilla stats for Miro:

  • 23 bugs/feature-requests created
  • 1 bugs marked DUPLICATE
  • 8 bugs marked FIXED
  • 3 bugs marked INVALID

Dev call 10/13/2010 minutes

, | Tweet this

Miro 3.5 status (roadmap)

  • did a Miro 3.5 rc2
  • fixed some bugs, planning to do an rc3
  • need help testing and translating Miro 3.5
  • probably a release on or around October 20th

Miro Community 1.1.2 status (roadmap)

  • focusing on small bugs that should get fixed before the long haul for 1.2.

Janet:

  • rc2 has been out for a little over a week
  • ran regression tests on rc2
  • no idea how many downloads we have for rc2, but there are a lot of new litmus testers which is a good sign
  • worked on automating universal subtitles testing

Ben:

  • working on 4.0 refactoring work
  • worked on bug 14609

Will:

  • wasn't around last week
  • worked on triaging and fixing rc2 bugs
  • we need an rc3--too many big changes

Paul:

  • worked on syncing stuff on Windows--problems with gio bits not implemented

Kaz:

  • worked on making sure Miro works with Python 2.7--it does
  • working on audio metadata research for Miro 4.0

Order of business:

Bugzilla stats for Miro:

  • 27 bugs/feature-requests created
  • 4 bugs marked DUPLICATE
  • 3 bugs marked FIXED
  • 1 bugs marked WORKSFORME
  • 1 bugs marked INVALID