Miro status

• 4.0.2 roadmap
• 4.1 roadmap
• we're going to keep working on Miro 4.0.2 for another week or two
• we're starting work on Miro 4.1

Ben:

• 4.0.2 is going pretty well. There are still a few blockers, but most things are in a nearly done state.

Jonas:

• worked on improvements to sidebar and continuous playback support.
• worked on gzip/deflate support for feeds
• going to switch to 4.1 development

Geoffrey:

• worked on fixing a series of nits for 4.0.2

Kaz:

• worked on unit tests for metadata

Janet:

• worked on 4.0.2 testing
• continuing to work on regression testing and updating test systems

Will:

• finished Miro User Manual updates
• almost done overhauling our Ubuntu packaging to make it easier to be easier to deal with
• sent Steven a contributor assignment form
• started working on the overhaul of Miro on Windows

Order of business:

• 4.0.2: Fix anything important, but this is probably our last point release for the 4 series. We're pretty close to having blockers finished.
• 4.1: We have a lot of clean-up work that we want to do, but probably can only work through some of it for 4.1. So we talked about doing theme-focused clean-up similar to what we've done on previous releases and clean up things related to things we're working on.
• Miro is developed by a community of people including you! If you can't contribute your time and work to development, testing, and translations, please consider contributing funding by donating. Your money goes directly to ongoing development of Miro and related projects like Miro Community and Universal Subtitles. 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://manual.getmiro.com/ .

Bugzilla stats for Miro for the last week:

• 58 bugs/feature-requests created
• 4 bugs marked WORKSFORME
• 1 bugs marked INVALID
• 2 bugs marked ---
• 8 bugs marked DUPLICATE
• 5 bugs marked WONTFIX
• 19 bugs marked FIXED

Miro status

• roadmap
• we're going to release Miro 4.0.1.1 in the next day or two to fix bug #17539
• we're going to release Miro 4.0.2 on June 6th
• we're going to continue working on some minor issues for a 4.0.3 at some point
• we're also going to start work on Miro 4.1, but that hasn't been planned out, yet

Janet:

• tested Universal Subtitles
• worked on sikuli automated tests for Miro on Windows
• working on other ways to have more comprehensive testing with Miro on Windows

Ben:

• fixed some issues with 4.0.1
• managing 4.0.2

Will:

• tracking downloads (147K downloads)
• built the ubuntu packages --- had problems with some issues
• working on updating the manual
• fixed a few bugs for 4.0.2

Paul:

• worked on Miro Community, Miro Guide and Miro stuff

Kaz:

• wrote some unit tests
• worked on some encoding issues

Jonas:

• worked on continuous playback options
• added an option for default list view

Order of business:

• Talked about bug #17593. We're going to do 4.0.1.1 just for Windows with that one fix.
• Going to do a 4.0.2 really soon.
• Bumping a few things to 4.0.3 and then everything else gets bumped to 4.1.
• Miro is developed by a community of people including you! If you can't contribute your time and work to development, testing, and translations, please consider contributing funding by donating. Your money goes directly to ongoing development of Miro and related projects like Miro Community and Universal Subtitles. 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://manual.getmiro.com/ .

Bugzilla stats for Miro for the last week:

• 70 bugs/feature-requests created
• 4 bugs marked WORKSFORME
• 1 bugs marked INVALID
• 9 bugs marked DUPLICATE
• 5 bugs marked WONTFIX
• 22 bugs marked FIXED
• 4 bugs marked INCOMPLETE

I tagged Miro v4.0 yesterday and did the final set of builds for source, Windows and OSX. It was a pretty monumental moment for me.

I think we started working on 4.0 back in October, though it might have been earlier. The feature set for 4.0 was really aggressive and we added a few new people to the Miro dev team. Also, I became a new dad in November.

The dev cycle was intense all the way through. I was pretty much working all available hours for the last few months or so including nights and weekends.

Now Miro 4 is released. Also, my baby is 6 months old. It's arguable which of these two monumentally life-changing events took more time, energy and patience. I honestly feel like a father of both projects.

In my queue of things left to do:

1. finish updating the Miro user manual
2. create builds for Ubuntu Lucid, Maverick, and Natty

I'll be working on those over the next few days.

We've already started working on a Miro 4.0.1 to address issues with 4.0 that were either impossible for us to get good data on or were things we had to defer in order to hit the May 23rd release date. I think the plan is to push 4.0.1 in a couple of weeks.

If you have problems, either write up a bug report or send me an email (willkg at bluesock dot org) with the specifics of your problem. I'll try to respond in a day or two.

On May 20th, we released Miro 4.0 rc2. This has a few known issues, but we've fixed a ton of stuff since rc1. We're 2 days away from tagging a final build. Please upgrade to rc2 and help us test it out.

Specifically, we need your help testing:

• using Miro to sync media between Miro and your Android device
• using Miro to stream through DAAP to other DAAP clients on your network
• Miro on Windows

Miro 4.0 rc2 builds are located on the nightlies page in the Sticky Files section.

Note that this is not a final release release! There are still some problems and tweaks we're working on.

Also, we really need help with translations. If you know multiple languages, please help us translate. On Launchpad, there's a Miro section for translations.

Also, if you help with testing and translation, please let me know so I can gleefully add you to the credits where you rightfully belong!

If you haven't helped before, now is a good chance to jump in and make your mark! Only 2 days left!

A while back, Ned Batchelder wrote about poxx.py which he wrote that generates a completely translated .po file to help find strings in his apps that weren't being translated.

We on the Miro dev team had a similar need. Additionally, we have the problem where in some languages, the translated string is longer than the English version and that creates some sizing issues in the ui code.

I took Ned's poxx.py, fixed some issues I had with it, then rewrote the transform to do something reminiscent of what the Swedish Chef would say. The transform has the following properties:

1. the output is vaguely readable
2. the output is longer than the input which helps us find ui issues
3. the output is clearly distinguished from English which helps us find strings that aren't getting translated
4. the output is mildly amusing which is sometimes important in dark times

I threw it together in an hour. It's not a beautiful transform and it doesn't add any "bork bork bork". I might tweak it some rainy day.

It's in our git repository here:

https://git.participatoryculture.org/miro/tree/tv/resources/locale/poxx.py

It'll also be in Miro 4.0. You can choose the Swedish Chef language in the language dropdown in the Preferences dialog. It's "swch" and it'll be towards the bottom.

Also, skimming the comments of Ned's entry, there's another tool that does this:

http://translate.sourceforge.net/wiki/toolkit/podebug

Miro 4.0 status

• roadmap
• we're working on rc2 today
• we're hoping to release on May 23rd

Ben:

• 6 bugs, some of them pretty icky, some should block and some shouldn't

Kaz:

• 4 bugs, 3 hours of work or so

Geoffrey:

• 1 bug, waiting for more information, shouldn't block an rc2
• working on OSX Lion support, looks like it might be fine without too many issues

Jonas:

• 1 bug, but it shouldn't block rc2

Will:

• 0 bugs, working on Miro User Manual updates and end-of-dev cycle stuff, will pick up P1 bugs as needed

Paul:

• 0 bugs, will pick up P1 bugs as needed
• working on MiroGuide stuff

Order of business:

• rc2 today
• Miro is developed by a community of people including you! If you can't contribute your time and work to development, testing, and translations, please consider contributing funding by donating. Your money goes directly to ongoing development of Miro and related projects like Miro Community and Universal Subtitles. 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://manual.getmiro.com/ .

Bugzilla stats for Miro for the last week:

• 113 bugs/feature-requests created
• 10 bugs marked WORKSFORME
• 5 bugs marked INVALID
• 4 bugs marked DUPLICATE
• 1 bugs marked WONTFIX
• 74 bugs marked FIXED
• 1 bugs marked INCOMPLETE

The good news is that we've done a really great job with overhauling the ui.

The bad news is that it's taking a long time, we didn't really get a good strings freeze, and thus translations of the strings in the interface are in bad shape.

German has 2 untranslated strings. Galician has 64. The rest are over 150. There are around 900 strings in Miro total.

I talked with Nick about this because we're planning to ship Miro 4.0 in a week and that's probably not enough time to make the translations better especially since the only way I have of contacting people who are interested in doing the work is the equivalent of shouting at the top of my lungs into the darkness.

So the plan is this:

1. I'm going to send this email and blog it and ask you to do whatever you can to help us fix this: help translate, blog about the situation, ...
2. We're going to ship Miro 4.0 with mediocre translations.
3. Any languages that have more than 450 untranslated strings will be removed from the release with the thinking that if there are that many untranslated strings, the interface is essentially unusable.
4. We're going to do a 4.0.1 release before June 6th. I hope that people use Miro 4.0, realize the translations are in bad shape, and do something about it.
5. I'll keep an eye on the translation status and continue to do releases with updated translations when appropriate for the next few months.

We currently use Launchpad for translations:

https://translations.launchpad.net/democracy/trunk

If you do help translate, please send me an email. I want to include you in the credits!

Miro 4.0 has a credits list that lists all the people that have helped us with all the things that went into the Miro 4.0 release cycle.

Part of the list is automatically generated from Bugzilla and git data (authors, bug reporters, bug commenters, ...).

However, there's a lot of work that people do that isn't easily divulged from Bugzilla and git.

If you're wondering whether you're on the list already, install Miro 4.0 rc1 and look at the About Miro dialog--the list is there.

If you helped with Miro 4.0 and you're not on the list, send me an email before Friday so that I can add you to the list.

If your name is in the list, but you want it written differently, send me an email before Friday.

Thank you in advance for your work however trivial you may think it was on Miro 4.0. It is a project of many hands.

On May 11th, we released Miro 4.0 rc1. It has some known issues, but we've fixed a ton of stuff since the beta. I encourage you to upgrade to rc1 and let us know if you run into any issues.

Specifically, we need your help to test:

• using Miro to sync media between Miro and your Android device
• using Miro to stream through DAAP to other DAAP clients on your network
• Miro on Windows

Builds are located on the nightlies page in the Sticky Files section.

Note that this is not a final release release! There are still some problems and tweaks we're working on.

Also, we really need help with translations. If you know multiple languages, please help us translate. On Launchpad, there's a Miro section for translations.

Also, if you help with testing and translation, please let me know so I can gleefully add you to the credits where you rightfully belong!

Miro 4.0 status

• roadmap
• we're working on a rc for today
• we're tentatively planning a rc for next week
• we're hoping to release on May 23rd

Will:

• worked on P1 bugs, synced translations, did peer reviews
• coordinated release candidate work
• had the flu
• fixed the keys on his Macbook except the spacebar

Jonas:

• worked on app indicator support and other P1 bugs

Goeffrey:

• worked on performance issues and crashes related to sharing
• planning to look at OSX Lion support

Paul:

• worked on device issues/crashes and ui issues
• waiting on information that we'll get in the next release candidate

Ben:

• fixed a bunch of issues

Kaz:

• worked on a ton of P1 blockers

Janet:

• did a ton of testing
• worked on automated testing which is working pretty well

Order of business:

• rc1 today
• rc2 may 18th?
• Miro is developed by a community of people including you! If you can't contribute your time and work to development, testing, and translations, please consider contributing funding by donating. Your money goes directly to ongoing development of Miro and related projects like Miro Community and Universal Subtitles. 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://manual.getmiro.com/ .

Bugzilla stats for Miro for the last week:

• 99 bugs/feature-requests created
• 4 bugs marked WORKSFORME
• 9 bugs marked INVALID
• 6 bugs marked DUPLICATE
• 1 bugs marked WONTFIX
• 81 bugs marked FIXED

Unrelated side note

I finally added the rst plugin for PyBlosxom to my blog so now I can post in restructured text rather than HTML. Yay!