The roads I take...

Here's a summary of SeaMonkey/Mozilla-related work I've done in week 48/2010 (November 29 - December 05, 2010):

• Releases:
  I helped Callek to bring the 2.0.11 process further along, pushed that one to the beta channel and added the new versions to the crash-stats server.
• Build Infrastructure:
  I filed a bug on Linux leak test hangs which might be connected to some online/offline weirdness I'm seeing in my own builds, as investigation showed that failure happened with a regression window that contains a tweak to the offline detection stuff. We don't have a real clue of what's up yet, though - help wanted!
• Places:
  I updated the patch on Firefox places cleanup, I hope this version will pass reviews.
  I also filed a bug for retrieving the best available icon for a domain as my Data Manager is not the only place that could need something like that, and this rather complicated logic should be in a generic place. This will probably only happen after Mozilla 2.0, though.
• (Tahoe) Data Manager:
  The Tahoe Data Manager add-on version 1.3 is now public on AMO, with an interesting set of improvements over previous versions. All those are up for review on the SeaMonkey side as well.
• Site-specific Zoom:
  I almost dropped my work on site-specific zoom before I picked it up again, but new review comments are still not too encouraging to put a lot of work into this patch - still, they're constructive, so let's see if we can find some common ground on this.
• SeaMonkey Internals:
  We got a new mailing list set up to talk organizational stuff that can't be public yet, but should have the core of the community involved.
  Some people of us also discussed a new patch that can't be public just yet.
  In realted news, I published the new review rules for SeaMonkey that we had discussed and decided in Vienna.
• Various Discussions:
  Website updates, group/list spam, mobile woes and possibilities, ongoing graphics driver instabilities, hiding Firefox main browser chrome when displaying in-content UI, build machines, etc.

Please note that our SeaMonkey Triage Week has just started, please help us there to resolve bugs that developers can't work on as they can't be reproduced, have not enough information for being reproduced (and being able to see it himself in some way it paramount for a developer to fix a problem), as well as sort out reports that are not (our) bugs, or can't/won't be fixed. If we manage to do that, it will be way easier for (potential) developers to spot issues that need someone to work on, so investing your time and helping there does make a difference!

Also, there should be some people around on IRC almost all the time to help you get up to speed to be able to help - all you need is a recent SeaMonkey build (ideally a nightly build) and some time!