When git-svn is painfully slow...

, | Tweet this

When I upgraded from Intrepid to Jaunty, I noticed that git svn things were painfully slow. I had looked into this before, but couldn't remember how I found the answer or what it was. After skimming through thousands of lines of IRC logs, I re-rediscovered what I discovered the first time.

  rm -rf .git/svn
  git svn rebase --all

I found it at this site (oebfare.com).

I'll be at the Open Video Conference

, | Tweet this

My jury duty trial finished up yesterday freeing me up for going to the Open Video Conference. The conference schedule looks pretty interesting. I'll try to hit development related things as much as possible.

Sunday is going to be a hackfest day--looking forward to seeing other Miro devs and devs from related projects and working on the future of Open Video.

If you're at the conference, say hi!

Moved Miro stuff over

, | Tweet this

I work at Participatory Culture Foundation and I have a work blog there that I use primarily for blogging about things related to PCF, Miro development, Miro-related development and other things of that ilk. It's on a WordPress system.

I decided after a while that having two blogs sucked. Also, I don't like Wordpress. Also also, I was getting crazy amounts of comment spam on my work blog.

As such, I did a couple of pushes to finish up PyBlosxom 1.5 enough so that I could write a tags plugin that I like so that I could migrate. Then I wrote a Wordpress to PyBlosxom migration script and the result is that I'm now blogging here for all Miro related things. Since it's easier to blog here, I'll probably be talking more about Miro-land. w00t!


, | Tweet this

I spent a few hours throwing together a new tags plugin that makes use of the new commandline features of code in PyBlosxom trunk (which will be PyBlosxom 1.5). Then I spent a while adding tags to all my entries.

I'm still mulling over my choice of tags, but I imagine I'll hone it into a set I'm happy with over time.

Also, I used :: as a tag separator, but I think I'd recommend something that doesn't require a shift key to enter. Perhaps ;; or //.

Tag information is stored in two dicts that are pickled and thrown in a file. It seems to be pretty fast to load for my blog (~500 entries). I picked pickle because it was easy, but if it turns out to be a problem, I'd be game for other storage formats.

I've been waiting for tags support before I did more blogging. Now that I've got tags support, I plan to move my work blog here. That'll make things easier and get me off WordPress.

PyBlosxom status: 05/16/2009

, | Tweet this

I finished up some additional work and I'm at a testing stage for PyBlosxom. I want to do some more testing and some documentation then it'll be ready for testing releases.

Also, I spent a couple of minutes upgrading my blog to use 1.5 in trunk. Bumped into bunch of weird issues with the comments plugin, but otherwise it was really smooth.

Adopt a line of Miro code!

, | Tweet this

Participatory Culture Foundation is the non-profit organization I work for working to build a distribution system for video and audio on the Internet that has no bottlenecks, no filter points, uses open standards, and Free Software.

Most of the software that we write is written in Python. Miro, an Internet video player, is written in Python and runs on a variety of platforms. Miro Guide and Miro LocalTV are both systems that are written in Python using Django. Miro Fullscreen is written in Python using Clutter.

Python has made it possible for a very very small group of us to tackle such a large project with very limited resources.

Earlier this week, we launched our Adopt a Line of Code, a fundraising campaign to help us fund the work we're doing. No one has ever done a fundraising campaign like this before. We think it could be a good model for other Open Source and Free Software projects to raise funds.

Take a moment to check out the Adoption Center and adopt your very own line of code! Support us in our work to make video open for everyone.

Jaunty packages released

, | Tweet this

I finished up a set of Miro 2.0.4 packages for Jaunty for amd64 and i386, pushed them out, and updated our download instructions page.

Two things to clarify:

  1. In the Ubuntu universe repository are Miro 2.0.3 packages, but these packages have a backported patch from Miro 2.0.4 so they're essentially equivalent to the 2.0.4 packages I just built.
  2. I put out PCF-built packages because we support Ubuntu and not because Iain and others aren't doing a fantastic job packaging Miro for Ubuntu.

I'm sorry it took so long, but I was gone most of last week, so I was a bit late to the party.

I'm currently working on getting Miro in trunk to work with Jaunty... there are a few other issues that need to be worked out still.

Instructions for installing the PCF-built Miro 2.0.4 packages are at http://www.getmiro.com/download/for-ubuntu/ .

Going forward I'll continue to build packages for Hardy, Intrepid and Jaunty. I'm no longer building packages for older versions of Ubuntu.

me from april 18th through 25th and a call for help

, | Tweet this

Me for the next week

I'm going on a service trip for a week to help out rebuilding and such. When I get back, I'll be spending quality time with Miro on Ubuntu Jaunty, Python 2.6 and a bunch of other support issues that have popped up and I'll be back on Miro development duty helping Ben and Luc with the changes going into Miro 2.1.

Call for help

Also, if you are technical and use Gentoo, Arch Linux, or OpenSUSE, toss me a line either in the comments below, on #miro-hackers on irc.freenode.net or by email at will.guaraldi at pculture dot org. I'd really like to get help on supporting these three systems better for Miro--I just can't do it myself.

db changes garner no response

, | Tweet this

I'm surprised that Ben's post didn't garner any response. I thought there was a significant number of people chomping at the bit for these db changes.

If you're one of the people that was looking forward to these changes but wasn't aware they were happening, then definitely take a look at trunk. If there are use-cases you have that you don't think are going to be handled, let us know as soon as possible.