A few years ago, we switched from Trac to Bugzilla. After doing this, we discovered there were some things we really missed about Trac. The first was a unified timeline so that we could see what was going on in the bug tracker. The second was a roadmap that showed us, for a given milestone, where we were at.

I coded up both of these and over the years have made some adjustments. I made the timeline script available a while back, but I don't think I ever made the roadmap script available.

The repository with both of these is at https://git.participatoryculture.org/bugzillascripts/.

They work with our Bugzilla 3.6 instance. I haven't tested either on other versions or other instances.

If you use either or both, send me an email about whether it works for you, bugs, comments, ...

Miro 3.1 status (roadmap)

• working on rebuilding the Windows build environment

Paul:

• Working on getting Miro Community to work on multiple servers

Janet:

• Worked on Universal Subtitles testing

• Worked on Miro bugs

Luc:

• Worked on weird problems with Miro on OSX

Ben:

• Worked on Miro 3.1 bugs

Will:

• Worked on unit tests, cleaned up downloader code, worked on getting new Windows build environment working

bugzilla

• 13 bugs/feature-requests created

• 1 bugs marked WORKSFORME

• 1 bugs marked INVALID

• 1 bugs marked DUPLICATE

• 2 bugs marked WONTFIX

• 4 bugs marked FIXED

• 2 bugs marked INCOMPLETE

Miro 3.1 status (roadmap)

• osx build box is rebuilt

• working on rebuilding the windows build environment

Janet:

• worked on Miro regression testing

• worked on Universal Subtitles testing

Ben:

• spent the week fixing subtitle issues

Luc:

• worked on bugs for Miro 3.1 related to conversion

• worked on difficult hard-to-reproduce issues

Will:

• rebuild the osx build box with 10.6

• worked on getting the miro community server running

• got video conversions working on windows

• started redoing the build environment for windows; basing on Python 2.6.5 and Visual Studio 2008 Express; ran into problems with xulrunner pyrex files

bugzilla

• 23 bugs/feature-requests created

• 3 bugs marked INVALID

• 3 bugs marked DUPLICATE

• 3 bugs marked WONTFIX

• 9 bugs marked FIXED

• 1 bugs marked INCOMPLETE

note

I was away last week, so I wasn't on the call and didn't take notes.

Miro 3.1 status (roadmap)

• osx build box needs to be rebuilt

• video conversion code needs testing and probably some fixing

Ben:

• working on allowing the user to specify the encoding in the subtitle file

Janet:

• worked on MVC testing and Universal Subtitles

• switching back to Miro testing

Luc:

• reworked building Miro on OSX so we can do builds from OSX 10.6 that work on other systems (yay!)

• continuing to work on video conversion stuff

Will:

• messed up his router like a big idiot, then fixed it

• spent some time trying to get the osx build box up and running but had problems

• implemented video conversion bits on Windows

bugzilla

• 25 bugs/feature-requests created

• 8 bugs marked DUPLICATE

• 2 bugs marked FIXED

• 1 bugs marked WORKSFORME

• 2 bugs marked INVALID

I was working on identifying and removing dead code in the Miro tree today when I decided to do some stats on the Miro codebase over the last bunch of versions.

python:
    44700 (94.91%)
cpp:
      1313 (2.79%)
ansic:
       790 (1.68%)
xml:
       264 (0.56%)
sh:
        30 (0.06%)

cpp:
    58403 (58.71%)
python:
    39985 (40.20%)
ansic:
       790 (0.79%)
xml:
       264 (0.27%)
sh:
        30 (0.03%)

cpp:
    58491 (58.53%)
python:
    40187 (40.21%)
ansic:
       796 (0.80%)
xml:
       265 (0.27%)
sh:
       196 (0.20%)

cpp:
    73663 (58.74%)
python:
    49198 (39.23%)
ansic:
      1831 (1.46%)
xml:
       438 (0.35%)
sh:
       282 (0.22%)

cpp:
    73808 (57.63%)
python:
    51631 (40.31%)
ansic:
      1874 (1.46%)
xml:
       432 (0.34%)
sh:
       328 (0.26%)

python:
    52869 (95.73%)
cpp:
       832 (1.51%)
ansic:
       692 (1.25%)
xml:
       432 (0.78%)
sh:
       403 (0.73%)

python:
    53305 (95.98%)
cpp:
       832 (1.50%)
ansic:
       692 (1.25%)
xml:
       432 (0.78%)
sh:
       279 (0.50%)

There are a couple of interesting things here. First is that we switched to libtorrent in Miro 1.1. We had libtorrent code in the tarball in Miro 1.1 and removed it in Miro 3.0--that's the bulk of the cpp code.

Second, we did a ui overhaul for Miro 2.0. In doing that, we switched all three platforms to using gettext and thus only had to have one set of translations. We also ditched a bunch of binary data. That reduced the tarball size significantly.

Third, the number of lines of Python code has been going steadily up since Miro 1.1. This is the number I'm most concerned with. In adding more Python code version after version after version, we're adding more complexity and a larger domain of things to test. This adds to the maintenance work we have to do between versions, too.

We sure could use some help coding, fixing, maintaining, testing, documenting and translating.

I decided that having a Facebook account primarily for extending the marketing/publicity for the work that I'm doing wasn't worth it. I disagree with Facebook's "public by default" policy and the way they roll out changes to their Terms of Service and privacy settings. I think their recent change to make the ui for privacy settings easier to use (and not require a phd) is a good one, but not good enough for me to feel comfortable giving my data (or that of my friends and family) to them.

I'm also in the process of signing the copyright assignment statement to join the GNU Social project to build a federated system that gives people full control over their data. I'll be looking into building these features into PyBlosxom, as well.

I just pushed out Miro 3.0.2 to address a few problems that users have discovered since we released 3.0.1. If you haven't upgraded to a Miro 3 series release, it's worth doing.

This is the last release we're doing for OSX 10.4. Miro 3.1 and future releases will not work on OSX 10.4.

I'm in the process of building packages for Ubuntu Jaunty, Karmic and Lucid now. As a reminder, Ubuntu packages are in the miro-releases Launchpad PPA at here.

There were two big things that drove this release. The first is that Miro on Linux sucked if you had XULRunner 1.9.2. This release fixes that by switching from XULRunner to WebKit. One of the big benefits we get from that is that it's much easier to compile Miro on Linux. The second set of changes had to do with the changes I made to the GStreamer renderer on Linux. This release fixes thumbnail building, playback from one media item to the next, and volume.

As always, release notes for Miro 3.0.2 are here.

Update 5/23/2010: I just finished up Ubuntu packages and pushed them to the PPA.

minutes

Miro 3.0.2 status (roadmap)

• needs testing and then will get pushed out

Miro 3.1 status (roadmap)

• things need fixing; couple more things to implement; needs testing

Miro Community 1.0 status (roadmap)

• some style changes needed; needs testing; might release this week?

Janet:

• Got the MacBook she has for testing up and running with 10.6

• Did testing on Miro 3.0.2, 3.1

• Worked on testing Miro Community and setting up regression testing and automated testing scripts

• Started testing Miro Subtitles

• Did some testing on final builds for Windows for Miro Video Converter

Paul:

• Getting really close to a Miro Community 1.0 release

• Working on updating Miro Community to work on latest Django

Luc:

• Did nothing for a bit

• Worked on getting Miro unit tests working better on OSX--running unit tests on OSX works fine now

• Worked on fix for 3.0.2 which will make sure OSX 10.4 users don't get an update notification for Miro 3.1

• Continued improving the OSX sandbox code

Ben:

• Fixed bugs related to libcurl changes.

Will:

• Worked on bugs targeted for 3.0.2 and some 3.1 issues, too.

bugzilla

• 23 bugs/feature-requests created

• 2 bugs marked DUPLICATE

• 13 bugs marked FIXED

• 6 bugs marked INVALID

minutes

Miro 3.0.2 status (roadmap)

• need to cherry-pick Linux webkit fixes from master

• need to test on Linux

• it'll get pushed out this week or early next week

Miro 3.1 status (roadmap)

• dropped support for OSX 10.4

• landed libcurl

Miro Community 1.0 status (roadmap)

• coming along nicely--single-digit number of bugs left

Will:

• Switched Linux platform from xulrunner 1.9.2 to webkit

• Fixed a handful of 3.1 bugs

• Struggled with getting translations for Miro 3.0 series working in Launchpad (again)--looking forward to looking at Transifex

Janet:

• Regression testing on Windows

• Tested libcurl changes for Miro

Paul:

• Miro Community work is going well

• Working on last bugs for version 1.0

Ben:

• landed libcurl

• worked on a bunch of other Miro 3.1 bugs

bugzilla

• 31 bugs/feature-requests created

• 3 bugs marked WONTFIX

• 21 bugs marked FIXED

• 4 bugs marked DUPLICATE

• 1 bugs marked INVALID

minutes

Miro 3.1 status (roadmap)

• we decided for sure that we're dropping support for OSX 10.4

Miro Community 1.0 status (roadmap)

• coming along nicely

Janet:

• Worked on testing for Miro, Miro Community, and Miro Video Converter.

• Worked on getting the Miro Community test server working with tests so we can run with a cron job.

Luc:

• Worked on problems with the downloader process not quitting on OSX. Suspicions are currently on libtorrent.

• Worked on problems created by autohiding the download and conversions tabs.

• Worked on libcurl changes for binary kit.

• We're going to ditch OSX 10.4. This means we'll have to upgrade infrastructure to 10.5 (test boxes, build box, ...).

• Worked on conversion feature fixes.

Paul:

• Worked on Miro Community stuff--mostly styling changes.

• Started working on user profiles.

Ben:

• Worked on libcurl changes--ready to check it in.

• Fixed a bunch of small bugs.

• Talked with Will about switching to webkit for Linux.

Will:

• Tweaked the bugzilla email template.

• Updated development machines to Ubuntu Lucid.

• Worked on problems with Miro web browser on Lucid.

bugzilla

• 18 bugs/feature-requests created

• 1 bugs marked WONTFIX

• 5 bugs marked FIXED

• 2 bugs marked INVALID

• 3 bugs marked DUPLICATE

• 1 bugs marked INCOMPLETE