Dev call 11/04/2009 minutes

Note: This is an old post in a blog with a lot of posts. The world has changed, technologies have changed, and I've changed. It's likely this is out of date and not representative. Let me know if you think this is something that needs updating.



  • Is sick.

  • Bug fixes and small features for Miro Community.

  • We have a lot of sites and things seem pretty stable.

  • Working on Miro Community 0.9 now. 0.9 isn't very feature-full, but it improves on things for style, look and feel, and such.


  • Worked a couple of days on subtitle support for Miro on Windows using VLC. Building a test application in C. Once he's got that working, he'll transcribe it to Python and ctypes.

  • Switched gears to help Will to fix libtorrent build problems with the new binary kit system. Bumped into problems getting it to compile on OSX 10.4 (expletive expletive expletive). Worked around it.


  • Continued working on libtorrent and binary kit changes.

  • Wants to do a 2.5.4 that includes vlc 1.0.3, libtorrent/unicode fixes on Windows, and database fixes from Ben.


  • Fixed database problems with duplicate ids.

  • Spent time removing sorts.pyx and filetypes.pyx from the codebase. This reduces complexity of the build.

  • Wants to push out a 2.5.4 with database fixes he's done recently.

  • Wants to finish the fasttypes removal work on OSX.

  • Talked about the sniffer code.


  • Tested changes in Miro and Miro Community.

  • Working on making it easier to assign tasks to volunteers and get more volunteers involved in the process without losing track of them.

  • Wrote up a wiki page for subtitle implementation work and testing. This will become the specification of what we're implementing now that we're mostly done research.

  • Is having her wisdom teeth taken out next week.


  • 19 bugs/feature-requests created

  • 1 bugs marked DUPLICATE

  • 7 bugs marked FIXED

  • 1 bugs marked WONTFIX

  • 2 bugs marked INVALID

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.