The roads I take...

KaiRo's weBlog

March 2012

Displaying entries published in March 2012. Back to all recent entries

Popular tags: Mozilla, SeaMonkey, L10n, Status, Firefox

Used languages: English, German


March 2021

April 2020

March 2020


March 26th, 2012

Weekly Status Report, W12/2012

Here's a short summary of Mozilla-related work I've done in week 12/2012 (March 19 - 25, 2012):
  • CSI:Mozilla / CrashKill:
    Got the Stability Dashboard up and running at!
    Based on its data and some investigation together with Naoki found that Fennec 12.0b1 had the wrong channel set (actually filed a dupe to that one, which was already known and fixed).
    Did some updates to custom reports reports wrt recent version changes.
    Triaged all Socorro skiplist bugs, either asking questions to make them actionable or forwarding them to Laura for being fixed.
    Updated categorized Socorro bug lists, seeing that some of them have shrunk, actually.
    Discussed discrepancies between a DB query and official crash rates.
    As every week, watched new/rising crashes, caring that bugs are filed where needed.
  • Themes:
    After some more work, I'm almost done with 2.8 versions of EarlyBlue and LCARStrek, and even did take a peek at what I need to work on for the 2.9 versions. :)
  • Various Discussions/Topics:
    SecureMail activation, H.264 and Mozilla, permission/security model proposals for B2G, L10n/L20n for B2G, ARMv6 work, WebAPIs, WebRTC, etc.

A lot of time this week went into discussions, be it around skiplists, Socorro features like ElasticSearch and other crash-related topics or around security, B2G and web standards and more general Mozilla topics. A ton of things are going on at Mozilla these days and it's really fun to work in such a dynamic place - even more as our arguments are not about what makes more profit but what's right for the web public and how to move the open web forward. I'm still left in awe about such a place existing for real and can't wait to see some of things come to life that we are talking about right now in this project. There's a lot left to do but I'm convinced that we can do it and make the web a better place for everyone. :)

By KaiRo, at 20:46 | Tags: L10n, Mozilla, SeaMonkey, Status | no comments | TrackBack: 0

March 19th, 2012

Weekly Status Report, W11/2012

Here's a short summary of Mozilla-related work I've done in week 11/2012 (March 12 - 18, 2012):
  • CSI:Mozilla / CrashKill:
    Improved readability of the Stability Dashboard.
    Updated versions reported on the dashboard and my custom reports to take into account the Firefox source uplifts / releases done this week.
    Fixed a long-going detection bug of "Firefox 4+" in my custom Flash reports.
    Discussed about and then filed a bug on Camino's way forward with Socorro.
    Reviewed some Socorro design/implementation work, e.g. on indicating startup crashes or url lists.
    Discussed formulae for explosiveness detection, will need to convert mine to something the team can work with.
    Investigated a spiking topcrash, finding out it's probably related to downloads in some way.
    Discussed remaining priorities for Q1 with the Socorro team and created a first draft of a Q2 priorities list.
    As every week, watched new/rising crashes, caring that bugs are filed where needed.
  • SeaMonkey:
    Landed the fix to my fix for the Data Manager test failure in time for the aurora merge, and landed a merged patch on beta.
    Reviewed Neil's patch for Data Manager content blocker permissions and found it to almost be there.
    Discussed Neil's patch for finalizing the Download Manager query and determined that the add-on needs an equivalent.
  • German L10n:
    Posted a call for help on German product L10n, discussed with the current community and possible volunteers about it and posted again about useful resources for those future German localizers.
  • Various Discussions/Topics:
    Planet Mozilla / Code of Conduct, SecureEmail, H.264 and Mozilla, permission/security model proposals for B2G, proposed download manager API changes, ARMv6 work, pwn2own and the Firefox release, new module requests, etc.

I spent a lot of time in the last few days getting my new HP laptop set up, and am pretty satisfied so far, esp. when it comes to running Linux on it, but I had a couple of WTFs with Windows. First, this machine has a 128 GB SSD as its only internal disk, and in the default setup it came with, Windows 7 took slightly over 40 of those, 20 more taken by a recovery and a HP tools partition, so roughly half of the drive space was not available for use in that default configuration! I couldn't find good clues on how I could shrink down the existing Windows installation (all the tools and software installed were not really that big after all), and given that HP had sent a 32bit and a 64bit Windows system DVD with the package, I wiped the SSD completely and did set up (openSUSE) Linux first, which worked like a charm and could run all the hardware out of the box - and everything is incredibly fast, compared to my previous, roughly 4-year-old machine. When I installed Win7 64bit from the DVD, it again took more space than expected, with somewhat over 20 GB for the system alone and that when it didn't even find drivers for the vast majority of the hardware, including Ethernet and WiFi, (Iron Lake) graphics, or the USB 3 ports. It took me lots of searching, using a USB stick to get network drivers onto the machine, and more searching for stuff like disabling hibernation and page files to get that secondary system to work reasonably and use a somewhat acceptable amount of disk space. While a full-fledged (64-bit) Linux with all kinds of applications takes a bit over 5 GB of space now, I could get Windows 7 Professional 64-bit down to slightly under 20 GB only with a real lot of searching around. Well, at least it works now for the occasional Firefox testing or even playing Age of Empires II (after again searching around how to get its colors fixed, which requires strange workarounds like killing Windows Explorer).
I remember when it was hard to get Linux to work decently and Windows was fine and problem-less (well, it was never small, though), esp. with new hardware it was sometimes hard to get Linux to work decently at all while it was easy to get stuff up on Windows. I must admit that the times have visibly changed. So, when did they say the year of the Linux desktop was coming? ;-)

By KaiRo, at 23:04 | Tags: L10n, Mozilla, SeaMonkey, Status | 2 comments | TrackBack: 0

March 15th, 2012


I just sat down to play a bit of guitar, and while I'm a quite mediocre player (probably due to lack of practice to a good part), I've written an number of songs - all in all I should have reached about 280, though some of those are only a few lines that never grew to a full song, and some are just new lyrics to existing songs. I taught myself to play guitar roughly 20 years ago, just from a chord table, mainly to be able to accompany my own songs, actually, and this is still one of the major reasons I play.

When I felt like it and took out some of my older songs to play through, I realized how ago long it really was, roughly 20 years ago, in 1992, when I wrote the first lyrics and full songs. Hard to believe even for myself, who lived through all of it! Man, it's been "ages" since I started to contribute to Mozilla in 1999, but this goes back even much further - and some of those songs still aren't too bad (granted, some of the lyrics I wrote as a 14-year-old sound naive today, but it's interesting how little of it, though that could just be me looking at myself).

Earlier today, I quoted some Country Music lyrics in a Mozilla IRC channel, and apparently it surprised people who know me pretty well Mozilla-wise that I'm a huge country fan, or there were even any outside the rural Southern US. ;-)
In fact, my dad played the drums in a country band in the 1990s (which inspired me a lot music-wise) and we have a pretty vivid country scene here in Austria - not mainstream, but good enough for common people to go to events and to have a thousand people or so at some of them. My dad stopped playing because being the CEO of a small company and having a family was ultimately more important to him, but the love of this kind of music stuck with him as well as my mum and myself. I continued writing songs, playing the guitar when I have time, listening to a lot of Country Music - and when I started singing Karaoke regularly, I took that music with me and I'm known in my regular Karaoke bar as the one who sings country stuff all the time. :)

Mentioning my dad being the CEO of a small company reminds me of him telling me sometimes how interesting it is that a lot of successful managers seems to be playing an instrument or sing in a band - possibly because both require a lot of harmonizing with those around you. And that reminds me of a brown bag session I attended via video earlier today on how to be a good manager (I'm technically in program management now but I don't manage any people, still I'm interested in those topics). I wonder how many Mozilla managers have music as one of their hobbies...

By KaiRo, at 22:46 | Tags: Country Music, guitar, management, music | 1 comment | TrackBack: 0

Weekly Status Report, W10/2012

Here's a short summary of Mozilla-related work I've done in week 10/2012 (March 5 - 11, 2012):
  • CSI:Mozilla / CrashKill:
    Improved the design and added some more verbosity in an info box on the Stability Dashboard.
    Got my correlation version update pulled into Socorro master to land with 2.5.1 right after the Firefox version updates land as well.
    Followed and took part in the Babylon library blocklisting issue, and was glad he could pull back from pushing on it when that company apparently fixed their product and crashes went down.
    Nervously followed and took part of discussions on the ongoing crashes with old graphics drivers until Benoit found a fix and we would be able to ship Firefox 11 with it.
    Was happy to see Socorro ElasticSearch infrastructure move forward.
    Could bring the revert of plugin hang timeout to conclusion.
    Discussed the state of Firefox 11 stability with CrashKill team members (and we saw it was good).
    Discussed the state of Camino on Socorro with their maintainer.
    As usual, continued watching new/rising crashes, caring that bugs are filed where needed.
  • SeaMonkey:
    Found the fix to my fix for the Data Manager test failure, requested review, and banged my head against my desk for the stupidity of the error I made in the first try.
    Continued discussing the data loss with POP3 filters while I stayed on beta build to not encounter it.
    Cheered for SeaMonkey project areas being updated.
    Reacted to a long-standing feedback request on Data Manager content blocker permissions and this turned into a patch I now have to review. :)
  • Web apps:
    Made Lantea Maps look a bit nicer, esp. on phones, and improved performance a bit.
  • German L10n:
    Landed the Firefox 11 strings patch by Archeopteryx more or less at the last moment, but we made it!
  • Various Discussions/Topics:
    Planet Mozilla rules and political views, SecureEmail, third-party add-on installs, 64bit Windows builds, B2G branding, B2G/Gaia UI consistency, permission/security model proposals, battery API, "HTML5" gaming, etc.

Yes, I'm running late again with this update. But it's release week and there's a lot of stuff to do. We just shipped Firefox 11 yesterday even though we first thought we might need to postpone it due to the graphics crashes I mention above, a security vulnerability found in Firefox 10 on Friday (which on Monday we found out had been fixed in 11 since the first beta) and Microsoft patch day (which was yesterday again and has burned us in the past so we are overly careful around it). We could overcome all those obstacles and still ship, though we'll only turn on automated updates tomorrow or so to be able to potentially react if the Microsoft updates don't cooperate well with us (looks good so far, though). Of course, Thunderbird and SeaMonkey also shipped updates - and we lifted our source up the channels and started to develop for Firefox 14 on Nightly. The trains all depart on time, every six weeks - and they are even quite punctual when they pull into the final destinations of releases. It's quite an interesting spectacle, and we seem to get the hang of it after doing it a number of times, and people now get more excited about "landing the patch early in the cycle" (to have a longer on-trunk testing phase) than "still making this train" (and reducing Nightly testing) which makes everyone way more relaxed. The system finally starts to work as it should. Now if we'd only get more people to run Aurora and Beta builds, which get the new features earlier, I'd be really happy (because we'd get better crash statistics and more chance to fix crashes before release, of course)! :)

By KaiRo, at 00:52 | Tags: L10n, Mozilla, SeaMonkey, Status | no comments | TrackBack: 0

March 14th, 2012

de: Nützliche Ressourcen für Mozilla-Übersetzer

Auf meinen Aufruf für neue Übersetzer haben sich ein paar Leute gemeldet, auch "alte Bekannte" haben gemeint, sie würden sich dafür interessieren, an der deutschen Thunderbird-, Firefox- oder SeaMonkey-Übersetzung mitzuhelfen.

Sebastian "Archeopteryx" hat im Thunderbird-Forum einen Beitrag mit wichtigen Ressourcen gepostet, ich will hier auf dem aufbauen und einen kleinen Überblick geben (teilweise 1:1 übernommen, teilweise von mir etwas mehr ausgeführt):

Wichtigste Regel:

Es gibt einige Werkzeuge, die man erste kennen lernen muss. Keine Angst, wir haben alle Fehler gemacht, nur daraus lernt man. Wir "anderen" beißen nicht, sondern helfen gerne!

Anfangs muss man eventuell etwas Software installieren, aber davon sollte man sich nicht abschrecken lassen, man kann auch jederzeit um Hilfe fragen oder falls etwas nicht verständlich ist.
  • Bugzilla ist die Seite, wo die meisten Entwicklungsentscheidungen und Fehlerberichte verwaltet werden.
    Berichte über die deutsche Übersetzung gehören dort in das "Produkt" "Mozilla Localizations" und dessen "Komponente" "de / German".
  • Localization Quick Start Guide - Einführung in die Mozilla-Übersetzungsarbeit mit vielen Links und Erklärungen verschiedener Werkzeuge und Begriffe.
    Da auch Webseiten-Übersetzungen usw. angesprochen werden, braucht man nicht alles davon, um ein Produkt wie Firefox, Thunderbird oder SeaMonkey zu übersetzen.
  • L10n Dashboard: Zeigt den Stand der Lokalisierung der verschiedenen Produkte an.
    Zeilen mit roter Farbe haben fehlende Texte, mit gelber nur (ev.) überflüssige, mit grüner haben sie alles übersetzt. Der "C"-Link in jeder Zeile zeigt an, welche "Strings", also Textstücke, wirklich fehlen oder überflüssig sind, sowie ev. Fehler und Warnungen.
  • Localization with Mercurial: Beschreibt, wie man die Texte für die Übersetzung runterlädt.
    Hier geht es um jenen Kern, der Leuten ohne Programmiererfahrung meist mal nicht ganz geheuer ist. Man gewöhnt sich aber dran und lernt Dinge, die man an vielen anderen Stellen auch brauchen kann (die meisten Open-Source-Projekte laufen auf ähnlicher Basis dazu). Wir arbeiten in der deutschen Übersetzung meist direkt mit den Textdateien, was manchmal komisch anmutet, aber sehr gut funktioniert.
  • Die "de"-Repositories: Central, Aurora, Beta
    Hier liegen die eigentlichen Übersetzungen, die 3 verschiedenen Repositories entsprechen den Firefox-Kanälen Nightly, Aurora und Beta (es gibt ein viertes für Release, das ist für uns Übersetzer aber belanglos, denn dort werden keine Änderungen mehr angenommen) - bei Thunderbird und SeaMonkey mögen die nicht ganz diese Namen haben, gelten aber äqulivalent, alle Produkte sind im gleichen Repository. Alle 6 Wochen, am Release-Tag, wird alles aus Aurora nach Beta übernommen, und für die englische Orginialversion auch Central nach Aurora. Wir versuchen auch für de Central und Aurora immer wieder zu synchronisieren, aber das passiert meist erst etwas später, für die meisten Übersetzer ist das aber eher wenig relevant. Die Hauptarbeit zur Übersetzung sollte auf Aurora passieren, denn da bleibt der Vergleich zu den "originalen" immer 6 Wochen lang konstant - wenn wir das aber übersetzt haben, versuchen wir, auch für Central mit deutschen Übersetzungen nachzuziehen, aber da kann sich ständig etwas ändern.
  • Patching a Localization und Creating a patch: Wie man die Änderungen in einer Datei speichert
    Wenn man (wie jeder, der mal "frisch" ins Team reinkommt), die Berechtigungen nicht hat, um direkt in Mercurial Änderungen einzuspielen, muss man diese Patch-Dateien erstellen und dann an einen "Bug" in Bugzilla als Attachment hochladen sowie einen, der schon im Team ist, um "Review" fragen (siehe Getting Reviews, von zweiterem Artikel verlinkt). Der zweitere Artikel stammt aus einer Serie, die für Änderungen am Programmcode von Firefox, Thunderbird und SeaMonkey auch gilt, für Übersetzungen läuft manches ähnlich, aber oft lockerer (kompilieren und testen ist nicht unbedingt vorher notwendig, und ähnliches).
  • L10n-checks und compare-locales: Zwei Werkzeuge (Skripts), um die Übersetzung auf Fehler zu übeprüfen (z.B. zweimal den gleichen Buchstaben für den Zugriff auf verschiedene Menüeinträge)
    Braucht man nicht unbedingt verwenden, aber sich hilfreich, um Probleme zu finden. Compare-locales ist exakt jenes Skript, das auch hinter dem "C"-Link im L10n-Dashboard (siehe oben) liegt, bringt also gegenüber dem nichts neues, man kann es aber auch gleich lokal verwenden, wenn man will, um am eigenen Computer zu kontrollieren, dass man "alles erwischt" hat.

An dieser Stelle möchte ich auch auf den IRC-Chat verweisen: In Channel (am Server sind einige deutsche Community-Mitglieder, inklusive Übersetzern wie Archeopteryx, Topal, KaiRo (ich), chewey und andere sehr oft online und helfen bei Fragen zu diesen Themen gern weiter, so weit wir können (allerdings, bitte Geduld haben, wir haben das oft neben der Arbeit offen und sehen nicht ständig rein und können nicht immer antworten).

Und jeden Mittwoch um 21 Uhr ist in #deMeeting ein Treffen der ganzen deutschen Übersetzer-Gemeinschaft, in dem wir durchbesprechen, was es in der jeweiligen Woche an Neuigkeiten gibt bzw. wo wir uns koordinieren müssen. Wir freuen uns über interessierte Teilnehmer!

Damit hoffe ich, einige interessante Hinweise geboten zu haben und hoffe, dass einige "neue" Leute uns in Zukunft bei den Übersetzungen helfen! :)

By KaiRo, at 22:20 | Tags: de, Firefox, L10n, Mozilla, SeaMonkey, Thunderbird | 1 comment | TrackBack: 2

March 12th, 2012

de: Die nächste Generation?

Alex Ihrig, unser langzeitiger deutscher Thunderbird-Übersetzer, hat vor kurzem bekannt gegeben, dass wir einen neuen "Maintainer" für Thunderbird brauchen, also jemanden, der die Übersetzung übernimmt. Alex hat 9 Jahre lang gute Arbeit geleistet, der deutsche Thunderbird ist ein wichtiger Beitrag für Mozilla, und Alex hat auch in den gemeinsamen Bereichen einiges übersetzt, was uns alles geholfen hat. Ihm gebührt großer Dank dafür.

Trotzdem heißt die Nachricht, dass er das nicht weiter machen wird, dass wir neue Leute für die Thunderbird-Übersetzung suchen. Aber nicht nur dafür: Kadir hat für die Firefox-Übersetzung etwas wenig Zeit übrig, seit er hauptamtlich und in anderen Bereichen für Mozilla arbeitet, und auch meine Zeit für die SeaMonkey-Übersetzung ist in letzter Zeit extrem beschränkt. Wir wären beide froh, bei diesen Produkten auch Unterstützung von anderen zu bekommen, sodass wir in Zukunft die Arbeit nach Möglichkeit auch mal anderen Community-Mitgliedern übergeben können.

Wir haben diesen Arbeitsbereich viel Erfahrung gesammelt, es ist an der Zeit, die an andere weiter zu geben und selbst neue Projekte zu suchen, die wir aufarbeiten können. Man sollte nicht zu lange in einer Routine stecken, andere können sicher wieder weniger abgestumpft daran arbeiten und daher die Qualität hoffentlich auch weiter verbessern.

Also, wenn ihr das lest und Interesse daran, habt, die deutschsprachigen Mozilla-Produkte vorwärts zu bringen, wir freuen uns über Hilfe!
Die nötigen Qualifikationen sind nicht allzu schwierig - gute Deutschkenntnisse, keine Scheu, auch mal über Wortwahl zu diskutieren und Rechtschreibregeln nachzusehen, und nach Möglichkeit etwas Erfahrung mit Reintexteditoren (aber die kann man sich auch direkt am Beispiel aneignen). Und keine Angst, wir sind ja da, um euch zu helfen und in die Materie einzuführen.

Übersetzungsarbeit ist eine gute Chance, um im Mozilla-Projekt mitzuhelfen, auch wenn man vielleicht keine Ahnung vom Programmieren hat, und in diese großartige Gemeinschaft "hineinzuwachsen" - mach mit!

By KaiRo, at 02:01 | Tags: de, Firefox, L10n, Mozilla, SeaMonkey, Thunderbird | 3 comments | TrackBack: 1

March 7th, 2012

Political Views

I just read a couple of messages about people shooting down a post about one community member's political views on Planet Mozilla.

I'm shocked once again how everything not conforming to "elite" far-left-wing views is being seen as rude, backwards, and unacceptable.

This is one reason why I post less and less in public at all about my personal views, as due to often not conforming with what is seen as being "cool" and "hype" in the left-wing standards apparently being in place widely both in the country I live in and the communities I tend to be part of online, I tend to get bombarded with negative statements every time I open my mouth about anything except my work.

Being open is to a large degree about accepting that other people have different views, even on controversial topics, tolerating their views, and requiring other people to change those to be able to work in the same community with them.
Unfortunately, it's is often those who insist most to call themselves "open" who seem to not be able to accept that.

That's what I find most sad about this discussion. Unfortunately it also means that people will not learn a lot about my personality on this blog - contrary to Gerv I don't have the stamina to be shot down on every controversial view I might take here (and note that I'll not even take a stand on either side of the topic he's writing about - I'll claim I know too little about the specific case to make any determination).

By KaiRo, at 15:52 | Tags: Planet, Politics | 14 comments | TrackBack: 0

March 6th, 2012

Weekly Status Report, W09/2012

Here's a short summary of Mozilla-related work I've done in week 09/2012 (February 27 - March 4, 2012):

Last week was pretty intense in terms of messages from Mozilla, with Boot to Gecko and Open Web Device, Mozilla Marketplace, Persona, Collusion, Firefox Flicks, maybe even more being announced and demonstrated. This is still only the beginning of the impact we're planning to make this year and beyond. "The web is the platform" is our central message in what we're doing right now, and we're working hard to make the people accessing the web be really in control of their experience and that their - our - privacy on that web is being respected. As Tron was "fighting for the user", Mozilla is fighting for openness, innovation and opportunity on the web, and that means both making the web an even better platform and basically the platform and ensuring that people are in control of their own privacy and experience on the web.

Look out for more to come in those areas in the next months, support us by using truly open standards and products (including our own) and help us in achieving those goals for the web and everyone connected to it!

By KaiRo, at 20:49 | Tags: L10n, Mozilla, SeaMonkey, Status | no comments | TrackBack: 0

Feeds: RSS/Atom