Miro 4.0 status (roadmap)

• lots of flux in git-master, but the code is stabilizing

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

• probably a release in May or June--we're working hard on it!

Paul:

• Worked on bugs across Miro: device bugs, ui bugs, sidebar bugs, ...

Will:

• Finished working on close/destroy implementation issues which took a while.

• Continuing to sync translations, run tests, peer review code, triage bugs and all that.

• Wrote up a bunch of bugs that were complex where i wasn't able to reproduce them several days later. It's possible there are flux issues involved, but this concerns me.

Ben:

• Worked on a bunch of bugs and got sidetracked into import progress updating issues.

• Planning to work on tableview selection issues going forward.

• Put in a request for better comments in the code and better checkin comments.

Kaz:

• Made changes to list view column sizing for OSX and GTK.

• Working on P1 bugs going forward. Half of the P1s are selection issues. Will coordinate with Ben on fixing them.

Geoffrey:

• Worked on a bunch of P1 bugs for ui stuff, crashing bugs, daap bugs, and some other things.

Jonas:

• Worked on P1 bugs.

Janet:

• Doing a lot of Miro testing.

• Focusing on verifying bug fixes. When she does this, she adds additional tests to Sikuli and Litmus so we'll catch regression issues.

• Fixing Sikuli tests in regards to ui changes.

Order of business:

• git master is in pretty heavy flux right now and because of that nightlies are probably unstable--use them at your own risk. This will sort itself over time when there are fewer massive changes being made. If you're interested in testing, but don't want to test bleeding edge, then it's worth waiting until we hit the release candidate portion of the dev cycle. We're currently thinking that'll be in a couple of weeks.

• 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:

• 78 bugs/feature-requests created

• 5 bugs marked WORKSFORME

• 4 bugs marked INVALID

• 10 bugs marked DUPLICATE

• 2 bugs marked WONTFIX

• 79 bugs marked FIXED

• 4 bugs marked INCOMPLETE

I haven't posted the PyCon 2011 videos to Python Miro Community, yet. First, I was waiting for Ogg Theora versions of the videos to get posted. Then I was waiting for Miro Community 1.2 to get released. Now I'm waiting for duplicate Ogg Theora versions of the videos to get removed so that I can successfully pull in all the videos without fear of them getting moved around and the urls to get stale.

A month ago, I knew we were doing some things we hadn't done before and therefore it was going to take longer than it usually does. But I never expected it to take this long. It's sort of been a perfect storm of things to block on.

Regardless, the Miro Community released 1.2 and it includes a bunch of fixes to the admin side of the site that make some things doable again. Additionally, it includes a few fixes I submitted upstream--these are my first contributions to Miro Community to fix issues I was working around with Python Miro Community. I look forward to fixing some more things especially now that I have a working Miro Community development environment. Congratulations to the Miro Community team on a successful release!

That's where things are at. I haven't forgotten about PyCon 2011--it's just taking a lot longer than I expected it to.

Miro Community 1.2 status

• Miro Community 1.2 has shipped! Congratulations to the MC team!

Miro 4.0 status (roadmap)

• lots of flux in git-master, but the code is stabilizing

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

• probably a release in May or June--we're working hard on it!

Will:

• Ubuntu Natty releases on April 28th. I've spent some time already making sure that Miro works on Natty and we have a helper script already. I'm planning to wait until it's out before I spend a ton of time fixing issues.

• I want to set up a second PPA for testing on Ubuntu Maverick and Natty. That'll alleviate issues people are having with missing dependencies when testing Miro on Ubuntu. Planning to wait until the release candidate cycle to set this PPA up.

• I'm mostly done with the new Add Files dialog, but there are some outstanding issues I'm still working on.

• I plan to do my work on Windows for the next week.

Paul:

• Worked on ui tickets all week.

• Waiting on log files for device-related issues.

• Spent time on Miro Guide getting a development server going so that he can spend some time on Miro Guide stuff.

Kaz:

• Working on issues in local branches.

• Working mostly on OSX next week.

Jonas:

• Worked on P1 issues.

Geoffrey:

• Working on sort ui issues for standard view.

• No big issues--mostly just cruising through bugs.

Ben:

• Worked on bugs--got a bunch of P1 bugs done.

Janet:

• Caught a cold and feels icky.

• Working on testing Miro and Universal Subtitles things. Feels like the current round of bugs are smaller and less "this whole thing is totally broken".

Order of business:

• Talked about where we're at with Miro 4.0. Lot of newly created bugs over the last week, but we're done with new features. Bugs are getting smaller and more specific. We're getting close to a release candidate.

• Talked about setting up a miro-testing PPA for Ubuntu Maverick and Natty. We're going to wait on this until the release candidate phase.

• Talked about the plan for Natty. We've done some testing already and some setup and Miro looks ok so far. When Natty releases (April 28th), one or more of us will upgrade and do more granular testing. Will is working on an appindicator support extension. At some point Will plans to look at what things we can do to fit into the Unity and GNOME 3 interfaces better, too.

• git master is in pretty heavy flux right now and because of that nightlies are probably unstable--use them at your own risk. This will sort itself over time when there are fewer massive changes being made. If you're interested in testing, but don't want to test bleeding edge, then it's worth waiting until we hit the release candidate portion of the dev cycle. We're currently thinking that'll be in a couple of weeks.

• 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:

• 69 bugs/feature-requests created

• 12 bugs marked DUPLICATE

• 56 bugs marked FIXED

• 2 bugs marked WORKSFORME

• 1 bugs marked INVALID

Miro 4.0 status (roadmap)

• lots of flux in git-master, but the code is stabilizing

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

• probably a release in May or June--we're working hard on it!

Will:

• Spent most of the time on BD. Long drama, but it should be fine now. I spent most of the time addressing privacy issues, but also did some restructuring as well.

• Worked on upsizing issues with conversions. Pretty sure I have it fixed, but since the changes are pervasive, I want to do more testing. I didn't have to do anything outlandish like I had feared last week, so that's good.

Paul:

• spent some time fixing Miro Guide issues, mostly django errors

• worked on P1 bugs, mostly ui stuff

Jonas:

• continued working on P1 bugs

• added support for hex-encoded magnet URIs

Geoffrey:

• working on P1 bugs, particularly ui bugs

Ben:

• working on P1 bugs

• finished up keyboard shortcut issues--should be pretty solid now

Janet:

• spent a bunch of time with sikuli tests and Miro

• worked on testing Universal Subtitles

• working on testing things and writing new tests so we continue to increase the regression tests

Order of business:

• Talked about where we're at with Miro 4.0. Lot of newly created bugs over the last week, but we're pretty much done with new features. Seems like we're just working on bugs now. Getting close to a point where we could do a release candidate.

• git master is in pretty heavy flux right now and because of that nightlies are probably unstable--use them at your own risk. This will sort itself over time when there are fewer massive changes being made. If you're interested in testing, but don't want to test bleeding edge, then it's worth waiting until we hit the release candidate portion of the dev cycle. We're currently thinking that'll be in a couple of weeks.

• 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:

• 80 bugs/feature-requests created

• 3 bugs marked WORKSFORME

• 3 bugs marked INVALID

• 2 bugs marked ---

• 12 bugs marked DUPLICATE

• 2 bugs marked WONTFIX

• 54 bugs marked FIXED

• 2 bugs marked INCOMPLETE

Last week I got back from PyCon 2011 and it was flabbergastingly awesome. This was the first PyCon I'd ever been able to go to. In previous years, I just read blog posts and watched session videos online.

Now that I've been, I realize how little of the conference is captured in blog posts and session videos. Honestly, Doug and others are right and the talks are maybe 1/5 of the conference if that. There's also:

• tutorials

• sprints that allow for in-person group collaboration

• giving lightning talks about things that are important to you to an interested audience of 800+

• talking with people whose code you use

• talking with people who use your code

• talking with people who work on libraries that solve the same problems but in different ways

• poster sessions

• the expo hall where a bunch of companies were hiring and a bunch of groups are showing off what they're doing

• talking with people about non-Python things

• free t-shirts, mugs, stickers, and bottle openers (which turned out to be very handy)!

• looking over peoples' shoulders and watching them use tools you've never heard of

• meeting other people who also wrote a mocking library, micro web framework, blogging system, or enum library (which covers at least half the attendees)

• ...

Being part of the video crew, there was some talk about how videoing the conference sessions reduces the number of people who go. Honestly, if you don't go to PyCon because you think you get the same experience from watching the videos that get posted online, you're horribly mistaken.

I thought of some analogies to help understand:

• It's like seeing a 4x6 picture of a peach pie vs. having a slice sitting in front of you that was just taken out of the oven and it's got a nice honkin scoope of vanilla ice cream that's melting as you watch.

• It's like hearing a 15 second muzak-like ring tone of your favorite song vs. listening to it being played live at a concert.

• It's like looking at a JPEG image saved with a quality of 10% of your birthday party vs. being there. (You wouldn't skip your own birthday party, would you?)

I don't want to belabor the point beyond that. There are other reasons people don't go to PyCon that are perfectly valid. Not going because the conference sessions are posted online and that's equivalent to going to the conference is not one of them. I hadn't gone previously because of money, classes, work and family issues. I regret it now.

While at PyCon, I was on the video crew and ran the camera in room 5 on Friday and Saturday. When I wasn't running the camera, I was watching Carl, Ryan, Dave and others coordinate the video-recording side of the conference. The amount of work, technology, and calamity-preventing know-how that goes into videoing a conference is awe-inspiring. Carl even took a moment to teach me how to coil cables correctly.

The Next Day Video crew have all the videos currently posted on http://pycon.blip.tv/. They're working on encoding them in Ogg Theora so that I can post them on Python Miro Community with the Universal Subtitles embed code making it possible to caption and translate these videos. We've already worked out the workflow, so it's just a matter of finishing up encoding and posting them.

Carl and I gave a lightning talk about melding Python Miro Community with Universal Subtitles. I'm really excited about this work. It makes these videos more accessible which is really important. This work is funded by a grant from the PSF. (Thank you!)

PyCon 2011 was amazing and I met a lot of amazing people, ate some great food, participated in some great conversations, ...--it's hard not to slide into absurd amounts of rampant hyperbole when talking about it.

Thank you so much to all the people who made this possible. PyCon is a fantastic conference that's about people, building relationships, enabling conversations, and reinforcing the community and the work you put into it really shows.

I feel the need for the obligatory I'm *passionate* about PyCon.

Podcasts come and go. I thought I'd do an update on things I watch and list the podcasts I'm currently testing with.

• The Ben Heck Show (Add to Miro) - TBHS is really fun to watch, educational, and really fun to watch. Ben spends each episode on a project such as a Super Can Cooler, a Portal Shirt, a Portable CNC Router, ... It's just fascinating.

• Lawrence Lessig's blip.tv (Add to Miro) - Lawrence Lessig talks about corruption of money in politics and occasionally about copyright reform.

• Wait wait... don't tell me! (Add to Miro) - "Wait wait... don't tell me!" is a radio show that I like listening to on the weekends, but I often miss it. So I subscribe to the podcast and get to listen to it when it's convenient for me.

• Onion News Network (Add to Miro) - ONN is just too funny. The videos are short, so they download quickly. The content is fantastic. They produce new content with great frequency. It's a great podcast to test with.

• Python Miro Community (Add to Miro) - This is the New feed for Python Miro Community. This is a site that has a curated index of Python-related videos around the Internet. It has conference videos from conferences like the various PyCons, DjangoCons, and PyOhio. Since I program primarily in Python, this feed helps me continue my Python education. It's an invaluable resource. (I also run the site.)

Miro 4.0 status (roadmap)

• lots of flux in git-master, but the code is stabilizing

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

• probably a release in April or May--we're working hard on it!

Janet:

• worked on testing over the week

• worked on sikuli tests now that the ui is more stable

• feels that things are finally coming together

Will:

• worked on an upgrade problem with torrent directories

• implemented Import Media dialog -- will talk to Nick about this to figure out UI issues

• strings are still in flux, so it's not stable enough for translations

• working on conversion bugs now

Paul:

• worked on P1 bugs

• working on P1 bugs assigned to admin and taking bugs from other people

Kaz:

• worked on scrolling issues and selection issues

• working on a bunch of P1 miscellaneous bugs

Ben:

• worked on a ton of P1 bugs

• did a bunch of ui stuff: item details pane, standard view, conversion item renderer

Jonas:

• finished up magnet uri support

• working on P1 bugs

Order of business:

• Talked about how Miro does conversions and reworking it to fix some problems.

• Talked about where we're at with Miro 4.0. Things are looking good. Bug data suggests we've reached a point of inflection where we're fixing bugs faster than new bugs are coming in. There are still a fair amount of P1 bugs to do, but it seems manageable.

• git master is in pretty heavy flux right now and because of that nightlies are probably unstable--use them at your own risk. This will sort itself over time when there are fewer massive changes being made. If you're interested in testing, but don't want to test bleeding edge, then it's worth waiting until we hit the release candidate portion of the dev cycle. We're currently thinking that'll be in a couple of weeks.

• 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:

• 34 bugs/feature-requests created

• 5 bugs marked DUPLICATE

• 47 bugs marked FIXED

• 5 bugs marked WORKSFORME

• 1 bugs marked INCOMPLETE

Miro 4.0 status (roadmap)

• lots of flux in git-master, but the code is starting to stabilize

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

• past the codefreeze--switching to mini-deadlines for important functionality.

Ben:

• got a lot of ui overhaul stuff done: main display, item details widget

• lot of other things to work on

Paul:

• worked on ui overhaul stuff: top chrome, sidebar tweaks, and investigating complex issues

• working on Amazon stores-related things

Geoffrey:

• picked up OSX titlebar bug

• worked on sharing issues and tidying up the code

Kaz:

• worked on tablist issues and list view columns

Will:

• worked on windows build environment issues

• fixed up a bunch of P1 bugs, synced translations, ...

Jonas:

• worked on magnet uri support and landed it today

• worked on resume playback changes

Asheesh:

• worked on paypal payment system for MC tiers

• worked on the POV theme

Order of business:

• Talked about associating Miro with magnet uris; the problem is that magnet uris require a protocol association, so there's nothing in Miro that currently does this. The other problem is that the different platforms have different conventions for associations. Jonas is going to create a few tickets and we'll figure out what to do going forward.

• We're pushing on P1 bugs--going to give mini-deadlines a break for a week.

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

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

Bugzilla stats for Miro for the last week:

• 134 bugs/feature-requests created

• 6 bugs marked WORKSFORME

• 1 bugs marked INVALID

• 8 bugs marked DUPLICATE

• 3 bugs marked WONTFIX

• 73 bugs marked FIXED

A couple of weeks ago at Carl's urging, I applied for a grant from the Python Software Foundation. This would cover Miro Community service costs for the next year as well as work on a series of improvements to the site. Things like:

• Universal Subtitles support

• using transcriptions in the search corpus for videos

• implementing an API in Miro Community allowing for automated data validation

I talked about all this at length in my call for funding.

I'm very pleased to announce that the PSF has awarded me a grant. I know how selective they are in their grant approval and I really appreciate this. It helps me a ton and I will work hard to make it money well spent.

I'll be at PyCon 2011.. I hope to spend some time with Carl, Asheesh and others working on Miro Community. I'm also hoping to talk with people who've used the site and what kinds of things we can make better going forward. If you see me, feel free to say, "Hi!"

Miro 4.0 status (roadmap)

• lots of flux in git-master, but the code is starting to stabilize

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

• past the codefreeze--switching to mini-deadlines for important functionality.

Will:

• worked on subtitle issues; discovered some irritating things about our subtitle support

• worked on p1 issues

Paul:

• worked on device support problems

• switched to working on ui overhaul stuff

Kaz:

• working on custom table headers; will probably implement this on OSX and skip GTK platforms

• continuing to work on the edit item dialog

Jonas:

• working on magnet uri support; keeps bumping into metadata-related issues

• mostly done with magnet uri support

Geoffrey:

• merged in transcoding branch last week

• working on polishing and fixing edge-case issues

• mostly done with things now--just some edge-case issues to handle

Ben:

• working on ui overhaul bugs; having some problems but thinks he can get the majority of it done

• after that, will work on a variety of small ui bugs

Janet:

• spent a lot of time testing device support and sharing support

Order of business:

• We missed the codefreeze. We've got a lot accomplished, but there are still problems that need to be addressed. We're pushing out the deadlines a bit and also switching to a mini-deadline model.

• Next mini-deadline is for user-interfaces issues. That's end of Friday.

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

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

Bugzilla stats for Miro for the last week:

• 78 bugs/feature-requests created

• 4 bugs marked WORKSFORME

• 1 bugs marked INVALID

• 6 bugs marked DUPLICATE

• 1 bugs marked WONTFIX

• 52 bugs marked FIXED

• 1 bugs marked INCOMPLETE