For many contributions, there's "paperwork" that sticks around allowing me to programmatically figure out who has helped out. For example, the author field in git checkins, reporters/commenters in bugzilla, ...

For other things (translations, testing, ...), I don't have a good way to programmatically figure out who's helped out, who's participated, who's worked with me and other contributors to Miro's development to make Miro as awesome as we can make it.

Going forward, I'll continue to work on making sure that we're doing a good job of crediting everyone who worked on a release because other projects do it and we should be doing it to.

For this release, I want to make sure we credit everyone. If you've contributed to Miro development, let me know because I want to include you in the CREDITS file and other places. Either leave a comment or send me an email.

If you read this entry (and the previous one, please dent it, tweet it, and mention it wherever you can so that we can credit as close to everyone we can as possible. Thank you!

We pushed out Miro 3.5 rc1 on Friday and in doing that, we've marked the end of this development cycle. Strings at this point should be very stable--what's there is what'll be there for the release.

Miro users need your help! According to Launchpad, as of this writing, the following languages have complete translations:

• French

• Serbian

• Ukranian

The following languages are pretty close:

• Galician - 6 untranslated strings

• Spanish - 14 untranslated strings

• Swedish - 28 untranslated strings

• Malay - 29 untranslated strings

• Russian - 30 untranslated strings

All other languages have more than 30 untranslated strings.

Miro users need your help!

Miro users need your help!

Please go to https://translations.launchpad.net/democracy/trunk/+translations and help us make Miro great for users who speak languages you know! We've worked really hard on Miro over the last six months to fix bugs, add new functionality, and take Miro to the next level. But this work won't make a lick of difference if users can't use the application because it's in a foreign language for them.

We're looking at doing a Miro 3.5 final release in the next few weeks--somewhere around October 11th.

Miro users need your help!

Also, if you've spent time working on translations, let me know! We have a hard time tracking who is doing translation work on Miro and we want to make sure that you are appreciated and thanked. Either comment below or send me an email.

Miro 3.5 status (roadmap)

• focusing on P1 issues and trying to get the release done--almost there

Miro Community 1.1.2 status (roadmap)

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

Will:

• synced translations

• worked on Miro 3.5 bugs

• wrote a script to figure out contributors; still need to add Janet's QA team (need to do manually), add translators (scrape launchpad?), other contributors?

• worked on ubuntu packaging and clearing out issues

Ben:

• worked on Miro 3.5 bugs

Paul:

• worked on a bunch of Miro and MC things

Janet:

• tested the Windows installers

• tested bug fixes and regression tested for Miro 3.5

Order of business:

• Miro 4 plans:

  • need clarification on cd/dvd ripping and bonjour/rondevous thing where miro can broadcast to a device where it can stream or download files

  • work might get split into two or more releases

• Priority is being put on finishing development work on Miro 3.5. Any help with this would be huge. There are a series of bugs on the roadmap that need to be fixed. If you want to help out but don't know where to start, see http://getmiro.com/userguide/contributing.html. If there are bugs you want fixed that aren't in our queue, consider submitting a patch.

• If you can't contribute work, 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:

• 36 bugs/feature-requests created

• 1 bugs marked WONTFIX

• 25 bugs marked FIXED

• 2 bugs marked DUPLICATE

Miro 3.5 status (roadmap)

• focusing on P1 issues and trying to get the release done--almost there

Miro Community 1.1.2 status (roadmap)

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

Janet:

• Worked on Universal Subtitles testing.

• There's been a ton of bug fixes for Miro in the last few days that need to be tested and areas that need to be regression tested.

Will:

• Worked on 3.5 bugs.

Ben:

• Worked on 3.5 bugs, but mainly on http downloading and conversions.

Paul:

• Switching over from Miro Community to Miro.

• We're having a lot of total failure problems with Amazon EC2 and RDS and it's becoming a pain in the ass.

Order of business:

• We say goodbye to Luc. He's done a ton of work on Miro and has been on the team for a long time. Good luck in your future endeavors! We'll miss you!

• Talked about switching to Skype for conference calls because the system we're using now sucks.

• Priority is being put on finishing development work on Miro 3.5. Any help with this would be huge. There are a series of bugs on the roadmap that need to be fixed. If you want to help out but don't know where to start, see http://getmiro.com/userguide/contributing.html. If there are bugs you want fixed that aren't in our queue, consider submitting a patch.

• If you can't contribute work, 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

• 3 bugs marked WORKSFORME

• 2 bugs marked INVALID

• 2 bugs marked DUPLICATE

• 1 bugs marked WONTFIX

• 19 bugs marked FIXED

• 9 bugs marked INCOMPLETE

Miro 3.5 status (roadmap)

• focusing on P1 issues and trying to get the release done

Miro Community 1.1.2 status (roadmap)

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

Paul:

• reviewed Miro Guide patches

• worked on Miro Community fixes

• talked with Anne and Dean about Miro Community future

Janet:

• worked on Miro 3.5 regression testing focusing on OSX

Luc:

• worked on OSX issues

• looking at P3-P5 issues and worked on them

Ben:

• lost his Internet connection

• worked on bugs anyhow (git ftw)

Will:

• peer reviewed and fiddled with conversions code

• worked on the libfaac bug

• fixed the Windows system tray suckage bug

Order of business

• We talked about the Miro 3.5 schedule. We're focusing on P1 bugs only at this point. Nothing should get added to the list without discussion.

• Priority is being put on finishing development work on Miro 3.5. Any help with this would be huge. There are a series of bugs on the roadmap that need to be fixed. If you want to help out but don't know where to start, see http://getmiro.com/userguide/contributing.html. If there are bugs you want fixed that aren't in our queue, consider submitting a patch.

• If you can't contribute work, 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:

• 11 bugs/feature-requests created

• 7 bugs marked FIXED

• 1 bugs marked DUPLICATE

• 1 bugs marked WORKSFORME

• 1 bugs marked INVALID

• 12 bugs marked INCOMPLETE

Miro 3.5 status (roadmap)

• working on fixing up video conversion issues

• working on cleaning things up

Miro Community 1.1.1 status (roadmap)

• released!

Miro Community 1.2 status (roadmap)

• starting the new development cycle

Paul:

• worked on Miro Community 1.1.1 with added admin functionality and bug fixes

• updated sites on PCF7 to use the same database system the other sites are using; should reduce load on that server and make things better

Janet:

• working on regression testing for Miro 3.5

• Miro 3.5 is looking good

• Universal Subtitles is in a state of flux that's hard to test

• working on moving tests to selenium and doing nightly test runs

• looking at Sikuli

Luc:

• worked on Miro 3.5 bugs

• fixed memory leaks that happened on OSX; fixed subtitle track display

• working on crash when switching between site tabs

• worked on subtitles freeze bug, but it seems like that's a problem in Perian

Ben:

• worked on httpauth overhaul

• worked on password-protected proxy support

Will:

• rebuilt libtorrent 0.14.11 with VC++ 9.0 (VS 2008)

• helped move infrastructure from PCF2 to new server

• did a pass through Miro bugs on the Fedora system, added comments, fixed some issues

• started peer reviewing conversions code

Order of business

• We talked about where we're at with Miro 3.5 development and what's left to finish up. We re-prioritized some things.

• 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/.

• Priority is being put on finishing development work on Miro 3.5. Any help with this would be huge. There are a series of bugs on the roadmap that need to be fixed. If you want to help out but don't know where to start, see http://getmiro.com/userguide/contributing.html

• If you can't contribute work, please consider contributing funding by donating. Your money goes directly to ongoing development of Miro and related projects.

Bugzilla stats for Miro:

• 20 bugs/feature-requests created

• 1 bugs marked DUPLICATE

• 7 bugs marked FIXED

• 1 bugs marked WORKSFORME

• 1 bugs marked WONTFIX

• 2 bugs marked INVALID

We've had a few servers are a hosting facility in Marlboro, MA, USA for a long time now. Over the last year, we've been moving applications, sites, systems and all that from the servers in Marlboro to the Amazon cloud system. We're in the process of moving the last set of things to Amazon.

We're working on making the transition go smoothly, but there are a lot of pieces and it's possible we'll miss something along the way. If you notice PCF/Miro-related sites being down, let me know.

Miro 3.5 status (roadmap)

• working on fixing up video conversion issues

• working on cleaning things up

Miro Community 1.1.1 status (roadmap)

• Miro Community 1.1 was released last week

• working on some bug fixes targeted for 1.1.1

Paul:

• pushed Miro Community 1.1 out to the new servers

• looking at moving the db to another machine

Ben:

• continued working on bugs for Miro 3.5

• implemented font selection for subtitles on Windows

Will:

• implemented the PCF bug triage Firefox addon

• worked on database startup failure problems

Janet:

• working on Windows installer things

• and other things

Order of business

• We talked a little about what Miro 4 will entail. We're going to try to plan it out in a wiki rather than plan it out in Bugzilla because Bugzilla is difficult to use for iterative design. When tasks become sufficiently defined, we'll move them to Bugzilla and start implementing.

• 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/.

• Priority is being put on finishing development work on Miro 3.5. Any help with this would be huge. There are a series of bugs on the roadmap that need to be fixed. If you want to help out but don't know where to start, see http://getmiro.com/userguide/contributing.html

• If you can't contribute work, please consider contributing funding by donating. Your money goes directly to ongoing development of Miro and related projects.

Bugzilla stats for Miro:

Lot's of bug churn this week in part because of focus on regression testing and because of the creation (and heavy usage of) the PCF bug triage Firefox addon.

• 20 bugs/feature-requests created

• 3 bugs marked WORKSFORME

• 1 bugs marked INVALID

• 3 bugs marked DUPLICATE

• 1 bugs marked WONTFIX

• 12 bugs marked FIXED

• 30 bugs marked INCOMPLETE

Miro 3.5 status (roadmap)

• working on fixing up video conversion issues

• working on cleaning things up

Miro Community 1.1 status (roadmap)

• working on it--probably a release today or tomorrow

Paul:

• Planning to tag Miro Community 1.1 and pushing out the release in the next day or two. Yay!

• Worked on the Miro installer for Windows.

Ben:

• Worked on bugs for Miro 3.5.

• Talked about how to tackle bug 14203.

Will:

• Worked on bugs.

• Tested Miro on Maverick.

Order of business

• We spent some time talking about fundraising. We're trying to get to the point where Miro development is self-funding.

• 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/.

• Priority is being put on finishing development work on Miro 3.5. Any help with this would be huge. There are a series of bugs on the roadmap that need to be fixed. If you want to help out but don't know where to start, see http://getmiro.com/userguide/contributing.html

• If you can't contribute work, please consider contributing funding by donating. Your money goes directly to ongoing development of Miro and related projects.

Bugzilla stats for Miro:

• 13 bugs/feature-requests created

• 1 bugs marked WONTFIX

• 7 bugs marked FIXED

• 1 bugs marked WORKSFORME

• 1 bugs marked DUPLICATE

• 1 bugs marked INCOMPLETE

I spent a good amount of time over the last few months migrating Miro on Windows to a new Windows build environment that uses Python 2.6.5 and Visual C++ 9.0 (part of Visual Studio 2008).

I landed the changes two weeks ago. Janet, Ben and I identified a couple of problems and sorted those out. Last week I got the Windows build box to produce nightlies without requiring any babysitting.

Yay!

Features of the new Windows build environment:

1. It's a lot easier to configure. Previously, we had to set PATH, INCLUDE, and LIB environment variables to the right magic values to build correctly. Python 2.6 automatically pulls those values from Visual Studio 2008 files. So we don't need to deal with those anymore.

2. It uses Visual C++ 9.0 (Visual Studio 2008) rather than VC++ 7.1 (VS 2003). The latter can no longer be acquired legally (thank you MS). There's an Express version of the former available on the Microsoft site for free.

3. We were using Python 2.5 which had a bunch of bugs we had workarounds for. We're now using Python 2.6.5 which doesn't have these issues and also has a series of optimizations that should make Miro run better.

4. There's a get_requirements.sh script that downloads the versions of Python and libraries that you need automatically.

This also means that we can require Python 2.6 or later on all platforms for Miro. Therefore we can:

• fix try/except blocks http://www.python.org/dev/peps/pep-0352/

• use with and contexts http://docs.python.org/release/2.6.5/whatsnew/2.6.html#pep-343-the-with-statement

The one thing we still want to do is upgrade from gtk 2.16 to gtk 2.20. Bug 14037 covers the problems here. We're blocked by Bug 625972 in gtk.

I've written up instructions on setting up the new Windows build environment. It takes me about 30 minutes to do--mostly because it takes a while to install Visual C++ 9.0 Express. It's much easier to set up the new environment than the previous environment. When I first started at PCF a few years ago, it took me a couple of days to get the Windows build environment working.

For more details on the new Windows build environment, see the wiki page on WindowsBuildDocs.