Will's blog

minutes

Miro 3.0 status (roadmap) (was Miro 2.6)

• should be pushed out soon

Miro 3.1 status (roadmap)

• work is coming along nicely--probably done with development by the end of March.

Miro Community 1.0 status (roadmap)

• coming along

Luc:

• added support for running unit tests on osx
• made some other clean-ups in the mac build

Will:

• worked on Miro 3.1
• wrote an article for Gnome Journal
• continued research

Paul:

• spent some time on Miro Guide fixing bugs from django-refactor going live
• Miro Guide should be fine now for the Miro 3.0 launch
• continued working on Miro Community 1.0 stuff

Janet:

• continued working on eggplant tests for Miro
• tested other things

bugzilla

• 9 bugs/feature-requests created
• 9 bugs marked FIXED
• 1 bugs marked WORKSFORME

I'm a Miro developer employed by Participatory Culture Foundation. I wrote a post about me back in September of 2007 which covered a bit of what I do. A lot has changed since then as my role on the project has increased in scope and I've moved and various other things like that. This is an update.

What I do:

I'm involved in project management, release planning, release engineering, maintaining development infrastructure (bugzilla, git, wiki pages, documentation, build scripts, nightly builds, bogon deflector, syncing translations with Launchpad, ...), Ubuntu packaging, some testing, bug triage, user support, and I'm a liason between the Miro project and packagers and related projects.

I also do a lot of Miro development primarily on the Windows and Linux platforms. I keep track of bugs in Debian and Fedora and fix them upstream. I handle most of the incoming patches from contributors and try to help contributors where I can to make their lives easier.

I spend a ton of time on Miro work--probably between 60 and 80 hours a week.

How does telecommuting work:

I telecommute which makes it easier to work on Miro whenever I have a free moment (blessing and a curse). I work with the other Miro people through email, IRC, Bugzilla comments and weekly conference calls. We're all pretty autonomous and it works pretty well. I imagine this is in large part because we're such a small team. If the team grew, we'd have to adjust the way we do things accordingly.

Development setup:

I bought a Del 1420N with Ubuntu on it a couple of years ago and do all my development on that. I'm running a pretty stock Ubuntu Karmic with a bunch of virtual machines in Virtual Box to cover different versions of Ubuntu and Windows and also other Linux distributions. This is my primary development machine. It's yellow.

I also have:

• a Macbook running OSX 10.4 for nightly and release builds (work machine)
• an old Dell something running Windows XP for nightly and release builds (work machine)
• a Mac Mini running OSX 10.5 for OSX development (work machine)
• a Dell XPS M1210 laptop (terrible machine) for Windows testing (work machine)
• an AMD64 box I built for AMD64 builds and testing
• an ASUS EeePC 701 running Ubuntu Karmic UNR for testing on a netbook
• a circa 2002 Gateway laptop running Debian Testing for testing
• a Neuros Link (graciously donated by Neuros Technology) for testing

I'd really like to get a bigger monitor. The 1440x900 display I have now is small and cramped most of the time. I also need to build a better desk.

Ways you can get a hold of me:

irc: willkg on #miro-hackers on irc.freenode.net
email: will dot guaraldi at pculture dot org

Meet me for coffee:

I live in North Chelmsford, MA, USA. It's about 30-45 minutes from Boston. If you're in the area, I'd love to hang out for coffee. I head into Boston periodically for conferences and hanging out with family and friends. I'm definitely interested in hackfests or talking shop.

The rest of my world:

My web-site is at http://bluesock.org/~willg/. I curate Python Miro Community and Gnome Miro Community. I maintain PyBlosxom. I'm a member of the Free Software Foundation. I'm a lover, not a hater.

minutes

Miro 3.0 status (roadmap) (was Miro 2.6)

• should be pushed out soon

Miro 3.1 status (roadmap)

• work is coming along nicely--probably 3 to 4 weeks of development

Miro Community 1.0 status (roadmap)

• coming along

Janet:

• working on creating eggplant test cases from litmus test cases
• 25% of them are created now

Will:

• worked on Python Miro Community and Gnome Miro Community
• made source tree layout changes to master branch for Miro 3.1
• finished up User Manual for Miro 3.0

Paul:

• moved Miro Guide to a new server--faster, fewer errors, better performance
• worked on performance fixes and bug fixes for Miro Community

Ben:

• working on Miro 3.1 stuff

bugzilla

• 14 bugs/feature-requests created
• 1 bugs marked DUPLICATE
• 3 bugs marked FIXED
• 1 bugs marked WORKSFORME
• 3 bugs marked INVALID

minutes

Miro 3.0 status (roadmap) (was Miro 2.6)

• we're ready for a release. srsly.
• making builds today and pushing it out over the next few days.

Miro Community 1.0 status (roadmap)

• coming along

Will:

• finishing up the user manual
• will talk to Nick about putting manual on getmiro.com

Luc:

• worked on 10.4 super weird issues
• blind fixes seem to be working--so that's good
• talked to perian folks--they're close to a release

Paul:

• mostly worked on sysadmin things
• changed the workflow for bug handling for Miro Community which should make it easier to get fixes in faster
• working with sys admins to move Miro Guide to a new server

Ben:

• really sick last week
• triaged crash reports from 3.0 rc3
• started organizing for 3.1 stuff

Janet:

• fell off the call
• continued regression testing testing Miro 3.0
• worked on User Manual for Miro 3.0

bugzilla

• 18 bugs/feature-requests created
• 3 bugs marked DUPLICATE
• 2 bugs marked WORKSFORME
• 1 bugs marked INVALID
• 4 bugs marked FIXED

This is the last call for translations for Miro 3.0.

Translations are done with the Launchpad translation interface.

If you do translation work or know someone else who does, take some time today (Monday, February 22nd, 2010) to help improve the translations for Miro 3.0.

minutes

Miro 3.0 status (roadmap) (was Miro 2.6)

• rc2 is going well: 150 Windows downloads, 60 OSX downloads, 30 source downloads
• there are a few bugs we're still working on, then another release candidate

Miro Community 1.0 status (roadmap)

• coming along

Janet:

• continued testing Miro 3.0

Ben:

• worked on subtitle support issues on Windows
• looking into weird crashes that Nick saw
• looking into crashes on upgrade

Will:

• worked on some bugs
• worked on the miro user manual
• worked on python and gnome miro community

Luc:

• fixed some bugs that Janet found on Monday

Paul:

• worked on Miro Community stuff over the last week
• we have two designers working on the style sheets and html
• working with Morgan on an admin system refresh
• working on moving feed updates to a separate server with a queue

bugzilla

• 24 bugs/feature-requests created
• 1 bugs marked
• 1 bugs marked DUPLICATE
• 13 bugs marked FIXED
• 1 bugs marked WONTFIX

minutes

Miro 3.0 status (roadmap) (was Miro 2.6)

• we released a 3.0 rc1 and it's looking really good
• we're planning to do an rc2, get wider testing, and possibly do a release next week

Miro Community 1.0 status (roadmap)

• we're working on 1.0 now--probably a 4-6 week dev cycle

Paul:

• fixed a couple of bugs with comments
• fixed some other bugs with RSS feeds
• fixed the disk space problem on Monday
• working on moving thumbnails to S3

Janet:

• we did the Miro 3.0 rc1 release on thursday
• did regression testing on Windows
• blogged release on Miro Testing site and sent an email to the mailing list
• we've had around 100 downloads of rc1
• we're ready for blogging it on the main blog
• excited about 3.0--things are really coming together

Will:

• busy week
• did bugzilla housekeeping
• wants to upgrade bugzilla to the latest version
• did some basic Miro extensions work

Old wiki page about extensions: https://develop.participatoryculture.org/trac/democracy/wiki/extensionsystem. There is also an old (obsolete) section in the journey about extensions: https://develop.participatoryculture.org/trac/democracy/wiki/thejourney.

Luc:

• fixed some minor issues in master
• working on fixing the downloader daemon shutdown slowness
• +1 on doing an rc2
• thinking about playback-during-download for a future release
• wants to get unit tests working on OSX

Ben:

• checked in some more changes into master that should go out with 3.0 and suggests we do another RC.
• still working on vlc-related fixes

bugzilla

• 17 bugs/feature-requests created
• 2 bugs marked DUPLICATE
• 10 bugs marked FIXED
• 1 bugs marked INVALID
• 1 bugs marked INCOMPLETE

minutes

Miro 3.0 status (roadmap) (was Miro 2.6)

• we're really close to a release candidate now--just squaring away some issues that have popped up and letting the code bake

Miro Community 1.0 status (roadmap)

• we're working on 1.0 now--probably a 4-6 week dev cycle

Ben

• Fixed bugs.
• Feeling great about 3.0.
• Has a few more things to do, but is pretty much set for 3.0 things.

Luc

• Fixed bugs for 3.0.
• Worked on testing. Started seeing memory leak issues.
• We can release even with the Perian issue as long as we mention the issue in the release notes.

Janet

• Going through testing and bugs and keeping up with changes.
• We're really close to release-candidate worthy.
• Worked on performance testing and testing on OSX--lots of performance fixes in 3.0.

Will

• Fixed bugs.

Paul

• Worked on Miro Community post 0.9 issues.
• Now working on 1.0. Looking at a 4-6 week time frame.

bugzilla

• 33 bugs/feature-requests created
• 3 bugs marked DUPLICATE
• 23 bugs marked FIXED

minutes

Miro 3.0 status (roadmap) (was Miro 2.6)

• went through P1s one by one to figure out where we were with them all
• need help testing
• shooting for a release candidate as soon as we can

Miro Community 1.0 status (roadmap)

• Miro Community 0.9 was released!
• working on 1.0 now

Paul

• rolled out Miro Community 0.9 (w00t!)
• 308 Miro Communities out there
• working on 1.0 now

Janet

• split time between testing Miro Community and Miro
• working on Miro regression testing
• continued building regression tests in Eggplant

Luc

• got his Internet connection back (w00t!)
• updated overlay pallette in OSX code to display subtitle items all the time
• worked on slow first-playback issue on OSX
• reimplemented MultilineTextEntry for OSX widgets
• worked on fixing up Edit Item dialog
• tracked down Perian developers and asked about their release timeframe for 1.2.1

Ben

• worked on a ton of Miro 3.0 bugs
• working on VLC playback issues; testing out vlc bindings

Will

• reworked GStreamer playback video renderer
• did a huge pylint pass

bugzilla

• 24 bugs/feature-requests created
• 5 bugs marked WORKSFORME
• 1 bugs marked INVALID
• 2 bugs marked DUPLICATE
• 3 bugs marked WONTFIX
• 19 bugs marked FIXED
• 3 bugs marked INCOMPLETE

I keep seeing people say things like, "I'm not a programmer, so I can't help."

I think this is a common misconception about Free Software. Free Software empowers you. Let me say that again...

Free Software EMPOWERS You.

Miro is a Free Software project and like all Free Software projects, there are a variety of ways that you can be involved. By being involved you are taking the responsibility to help solve your own problems.

You can test nightly builds and release candidates.

You can submit bugs and help us triage and fix them.

You can send in patches. Patches can be for code, documentation, packaging, ...

You can package Miro for other distributions.

You can translate strings.

You can tell your friends and family about Miro and help them get setup. You can blog about Miro. You can dent about Miro.

You can adopt a line of code. This helps fund ongoing development. If we had more funds, we could have more paid developers.

Miro is built and maintained by all of us working together contributing our time and resources. There are features to be implemented, bugs to be squashed, systems and software to integrate with, standards to develop--the future is great with possibilities. There's a lot of stuff that can be done and you can help the Miro community do it.