<< Weekly Status Report, W35/2011 | The roads I take... | Integration eines Magento-2-Webshops mit FreeFinance und selbstgebautem Warenmanagement >>
Weekly Status Report, W36-40/2011
So, here's a short summary of Mozilla-related work I've done in weeks 36-40/2011 (September 5 - October 9, 2011):
- Mozilla work / crash-stats:
Tested some Socorro release that went online and communicated a lot with the Socorro team on things they have been working on, like fixing how connected bugs are reported or upcoming features like a hang pairs report or a signature summary as well as some skiplist additions.
Talked the CrashKill team's Q4 priorities for Socorro over with leads of both teams and put them up on the wiki.
Had some interesting discussions with various people at the Mozilla all-hands meeting on crash-related topics.
Talked with metrics about the possibility of leveraging their systems to create more flexible graphs of crash data, the first step is getting access to the data.
Invested more work in my prototype reports, next to updating them for various version changes, the components reports are still somewhat experimental, but start to get really useful.
As always, I investigated various new or rising crashes and made sure bugs get filed for them in the right places and get the needed attention.
- SeaMonkey releases:
I did put up SeaMonkey update snippets for linux64 updates to 2.3.3, the bug for 2.4.1 is filed but I didn't get around to this yet.
- German L10n:
I did most needed updates needed for German SeaMonkey 2.6 (now in Aurora) and a number of core strings also needed by Firefox 9.
On the first weekend of October, I also took part in the German Mozilla community meetup where we discussed a lot of matters surrounding the localization and community in German-speaking countries.
More work on updating EarlyBlue and LCARStrek for 2.4 versions, there's a bit more stuff I need to check there still, though.
- Various Discussions/Topics:
Mozilla all-hands, ESR proposal, Web APIs, B2G, etc.
Surrounding the Mozilla all-hands meeting in San Jose (where a mindboggling almost 600 people being paid by Mozilla gathered), working another week from the Bay Area and the comparatively tiny German community meetup, I didn't really get around to writing up those status reports, and I'm wondering how helpful it is in general to do those.
I obviously found it reasonable to do another one now, mostly because it's also nice for me to have some log of what I have achieved and what I spent my time with - but I wonder how useful those reports are nowadays to other readers of this blog, and if every week is the right format or if I should always combine multiple weeks in a report. Any opinions?
Entry written by KaiRo and posted on October 13th, 2011 00:00 | Tags: L10n, Mozilla, SeaMonkey, Status | 1 comment | TrackBack
Hi Kairo ... I find your blogposts interesting. Sometimes I learn reading them, some other times they are a bit complex or boring or it's probably me not having a good day. In any case, my opinion, I asume I am not the only one enjoying your reports, on the other hand , regarding to the blogposting cadence, maybe a weekly reporting is too much intensive, if you prefer reporting every two weeks or monthly ... is up to you. Whatever it makes you feel confortable may be ok. Regards.