Thunderbird Localization (L10n)

Thunderbird 3.0b3 schedule change

2009-04-27T06:14:00.000-07:00

The Thunderbird developers have decided that there are enough blockers that aren't going to make it by tomorrow that beta3 (and therefore the string freeze as well) will have to be slipped by some number of weeks. By how many weeks is currently unclear. We'll hopefully know more within the next several days and expect to have a proposal soon...

Localizing the values in search-attributes.properties for Thunderbird and SeaMonkey

2009-04-21T03:37:00.000-07:00

A few weeks ago in mid-March we came across a fix (for bug 483629) that changed an existing string without changing the entity name. Instead of fixing that, we opted for going into the direction of fixing all the strings in

properly and get rid of all the magic numbers that posed as entity names (and remove some obsolete strings in the process as well). Fortunately that work has now been completed by Kent James and the fix for bug 484147 was landed a few days ago.

What this means for new localizers is, that the entity names are now much more self-explaining than they were before. However for existing localizers this means, that a lot of new strings have shown up, which you will now have to tackle again. We believe that this is the right solution for the reasons outlined above.

If you have any questions, feel free to ask in the corresponding thread in the mozilla l10n newsgroup.

Updated Thunderbird 3 beta3 release schedule for localizers

2009-04-15T02:49:00.000-07:00

There's been a slight change of plans for the Thunderbird 3 beta3 release. The release schedule has been pushed back a week. That means that the new release schedule is now (All dates use time of 23:59 PST - l10n-relevant dates are bold):

Slushy String freeze date: 2009-04-28 (Tuesday)
Slushy Code Freeze date: 2009-04-30 (Thursday)
Firm String / Code freeze date: 2009-05-05 (Tuesday)
l10n-mozilla-1.9.1 freeze date: 2009-05-07 (Thursday)
Target Build Ship date: 2009-05-12 (Tuesday)

As with our beta2 release, these dates have the following goals:

All string-related work should done by the slushy string freeze date
All other code-related work plus the late-string work should ideally be done by the slushy code freeze date
The firm freeze date will be for fixing remaining bugs and regressions found in the nightlies
The l10n-mozilla-1.9.1 date would be the last time by which we would accept changes in localizations
Late string changes will require an additional approval by the beta3 release driver Dan Mosedale (dmose on IRC)

If you have any questions or concerns, please do not hesitate to respond here.

Thunderbird 3 beta3 release schedule for localizers

2009-03-30T04:02:00.000-07:00

The Thunderbird developers have finalized the release schedule for Thunderbird beta3. Here it is (All dates use time of 23:59 PST - l10n-relevant dates are bold):

Slushy String freeze date: 2009-04-21 (Tuesday)
Slushy Code Freeze date: 2009-04-23 (Thursday)
Firm String / Code freeze date: 2009-04-28 (Tuesday)
l10n-mozilla-1.9.1 freeze date: 2009-04-30 (Thursday)
Target Build Ship date: 2009-05-05 (Tuesday)

As with our beta2 release, these dates have the following goals:

All string-related work should done by the slushy string freeze date
All other code-related work plus the late-string work should ideally be done by the slushy code freeze date
The firm freeze date will be for fixing remaining bugs and regressions found in the nightlies
The l10n-mozilla-1.9.1 date would be the last time by which we would accept changes in localizations
Late string changes will require an additional approval by the beta3 release driver Dan Mosedale (dmose on IRC)

If you have any questions or concerns, please do not hesitate to respond here.

Feedback required: Time needed for TB3 l10n release preparation?

2009-03-26T06:08:00.000-07:00

The Thunderbird developers are currently discussing the potential schedule for localizers for the final release of Thunderbird 3, which is currently scheduled to be released somewhere in June or July.

The main issue currently is the overall string freeze date for TB3.

We currently do not have a good feeling on how many string-related changes might still be needed for the final TB3 release. So the question basically comes down to:

"How much time do you need at a minimum before the final release date?"

This question goes mostly to those of you, who have not been part of our alpha or beta releases so far and therefore have a large amountof missing and obsolete strings left. The localizations that are most affected by this are: Danish, English (UK), Gujarati, Macedonian, Mongolian, Slovenian, Turkish, Chinese (Traditional)

So we'd really like to hear from you guys!

But of course this question also affects all other locales, as we assume that you guys want to do a lot more internal and external QA work on your localizations than you did for the alpha or betareleases. So we'd like to hear from all other locales as well.

We'd really appreciate a broad feedback from the l10n community here. Please remember, that this is the first major release for pretty much everyone, who is currently in a leadership position in the TB community. So we really need your feedback to make a good decision.

Please direct all your feedback to the discussion of this matter in the l10n newsgroup. That will make it much easier to track all your feedback

On the road to 55 locales

2009-03-17T02:09:00.000-07:00

Seth recently blogged about Firefox reaching 70 supported locales. That's very impressive indeed.

So, some of you might ask, how is Thunderbird holding up?

The short answer: We're doing great!

The long answer: We're currently at 54 supported locales and are closing in on the 55th (Bengali). Within the last six months, we've added 10 locales:

Arabic
Estonian
Frisian
Galician
Indonesian
Icelandic
Albanian
Tamil
Ukrainian
Vietnamese

and more are on the way. If we manage to release Thunderbird 3 in all those 55 locales, we will have increased our locale outreach by 17 locales compared to Thunderbird 2.

This is really a critical pillar of Thunderbird's growth strategy, because it will enable us to compete with other mail applications in many parts of the World, where we couldn't compete before, because people could only download the English version.

I believe this also shows that the creation of Mozilla Messaging was a smart move, that has not only invigorated the mailnews developer community, but the localization community as well.

This wouldn't be possible without the drive and passion of all the individuals who are eager to translate Thunderbird into their native language. Thanks a lot, guys! We really appreciate your efforts!

Thunderbird 3 beta2 l10n post-mortem

2009-03-03T15:09:00.000-08:00

As the Thunderbird developers are planning a post-mortem meeting for the beta2 release tomorrow, I thought that maybe we can do the same here on the blog with an exclusive focus on l10n matters.

So I would be interested in what you thought of the release process from an l10n perspective.

What worked well?
What didn't work?
What can be improved?
What lessons have you learned?
What lessons do I need to learn as the l10n coordinator?

Please post your answers and suggestions as a comment here in the blog. Thanks for your support in this matter.

Accesskey improvements in the Thunderbird preferences window

2009-02-25T14:33:00.000-08:00

I just pushed a fix for bug 453256 to the comm-central repository.

What this fix does, is to take advantage of the fix for bug 143065, to make sure that the accesskeys that we use in the Display, Composition, Privacy, and Advanced prefpanes are now much more sane, than they used to.

Prior to this fix accesskeys were shared across all tabs, so that if Advanced/General used "A" for "Automatically..." then Advanced/Update couldn't use A as an accesskey. That resulted in a lot of inadequate accesskey choices.

So dear localizers: If you haven't already taken advantage of the fix for bug 143065, please do so now and improve your accesskey story in the Thunderbird preferences window.

Thunderbird 3 Beta2 l10n update

2009-02-23T01:42:00.000-08:00

We're in the last stages of the beta2 release cycle for Thunderbird 3, after some last minute l10n checkins. And the good news is that we have more and more locales on board. We will release beta2 in 43 languages, five more than what we achieved with beta1.

Looking back at the whole Thunderbird 3 release cycle, we see a steady increase:

Thunderbird 3 alpha1: 1 language
Thunderbird 3 alpha2: 12 languages
Thunderbird 3 alpha3: 28 languages
Thunderbird 3 beta1: 38 languages
Thunderbird 3 beta2: 43 languages

This is a great achievement, given that we released Thunderbird 2 with only 38 languages. I want to thank all our localizers for making this happen. I'm now pretty optimistic about breaking the 50 languages barrier in the final Thunderbird 3 release later this year.

Unfortunately we are missing three locales in the beta2 release that were included in the beta1 release, but hopefully we can pick those up again with our next release (beta3) or our final release.

All Thunderbird strings are now frozen for the beta2 release

2009-02-17T05:45:00.000-08:00

I just wanted to remind everyone that as of last night, Tuesday, February 17 at 23:59 PST, the firm code and string freeze went into effect. That means that all strings are now entirely frozen until we release Thunderbird 3 beta2.

As of now 28 locales have already opted-in to be part of this release. An additional 9 locales are green (meaning that they have no missing strings in their localization) on our l10n dashboard and will hopefully opt-in soon. Hopefully even more will follow so that Thunderbird 3 beta2 will be the largest release in terms of the number of localized versions ever.

If you want be part of this release, please opt-in in the corresponding opt-in thread in the mozilla.dev.l10n newsgroup.

One additional note to localizers:
Please take a close look at the status of your tinderbox (at http://tinderbox.mozilla.org/showbuilds.cgi?tree=Mozilla-l10n-locale where "locale" must be replaced with your locale code (e.g. es-ES or de). I've seen some locales having a red Windows tinderbox, because those locales didn't follow this change to our installer strings. Please check if this applies to you and make the necessary changes before opting-in.

Thunderbird 3 beta2 slushy string freeze in effect

2009-02-12T14:25:00.000-08:00

Some of you have probably already noticed, but for those who didn't:

Since Tuesday, 23:59 Pacific Time we're in the so-called slushy string freeze for TB3 beta2. "Slushy" in this context means that from that date on only string changes in blocker bugs will be accepted (and marked as late-l10n) until the firm string freeze next Tuesday, Feb 17 23:59 PST.

Unfortunately we screwed up a little bit shortly before the slushy string freeze date by committing some string-only patches. Something the introduction of the "slushy" period was intended to fix.

The downside of this is that some strings were introduced which might be hard to translate because the UI is still missing for those. The upside is, that because of that we don't have any more blockers left with a potential string impact, so the risk of late-l10n changes is pretty slim.

So please start your work now, if you did not already.

I'll also start an opt-in thread shortly in the mozilla.dev.l10n newsgroup.

REMINDER: String freeze for Thunderbird 3 beta2 in four days

2009-02-06T06:15:00.000-08:00

Just as a heads up for everyone involved. We're getting nearer to our two proposed string freeze dates. The first date, the so-called "slushy string freeze" will be on Tuesday, February 10 23:59 pacific time. We hope to have all blocker bugs with string impact done by this date. I've talked with the Thunderbird developers about this and they have told me that they will make an effort to get all of those bugs done by next Tuesday.

There's a second line of defense as well, that being our firm string freeze on Tuesday, February 17 23:59 pacific time. All of the bugs with l10n impact that aren't fixed by then and any potential late-l10n bugs will have to be fixed by that date to make the release.

From that point on, localizers will have two full days until Thursday, February 19 23:59 pacific time to get their localization in shape and opt-in for the beta2 release. After that date, we will start with testing our candidate builds and hopefully release Thunderbird 3 beta2 on Tuesday, February 24.

We know that this is a tight schedule, so we believe it would be a sensible approach for all localizers to start working on the remaining missings strings after the "slushy string freeze" and not to wait with all the remaining until the firm freeze.

Let me know what your thoughts are on this.

New (and hopefully final) release schedule for Thunderbird 3 beta2

2009-01-28T13:56:00.000-08:00

We finally have release schedule for TB3 beta2 for you.

Here it is (All dates use time of 23:59 PST):

Slushy String freeze date: 2009-02-10 (Feb 10 2009)
Slushy Code Freeze date: 2009-02-12 (Feb 12 2009)
Firm String / Code freeze date: 2009-02-17 (Feb 17 2009)
l10n-mozilla-1.9.1 freeze date: 2009-02-19 (Feb 19 2009)
Target Build Ship date: 2009-02-24 (Feb 24 2009)

As I said before, we've tried to emulate what the Firefox devs did for their beta2 release, as we got the impression that this worked pretty well.

The idea is to have all string-related work done by the slushy string freeze date and all other code-related work plus the late-string work by the slushy code freeze date. Late string changes will require an additional approval by our TB3 beta2 release driver Bryan Clark (clarkbw on IRC).

The firm freeze date would be for fixing remaining bugs and regressions found in the nightlies and the l10n-mozilla-1.9.1 date would be the last time by which we would accept changes in localizations.

Thunderbird drivers have also evaluated the current state of things and have decided to add another beta release (beta3) to the release schedule. A firm decision on a release date has not yet been made, but it is probably safe to say, that beta3 will be released somewhere between the end of March and the end of April.

If you have any questions or concerns, please do not hesitate to respond here.

[Update] Release schedule for Thunderbird 3 beta2

2009-01-22T13:54:00.000-08:00

I've gotten some feedback, that many European localizers will be at the FOSDEM 2009 conference during the proposed beta2 release crunch time. We've also looked at the list of the remaining blocker bugs for the Thunderbird 3 release.

And after careful consideration it has been decided, to postpone the release schedule for TB3 beta2 by a week or two. I can't give you exact dates right now, but hopefully I can give you those dates until the end of the week.

Release schedule for Thunderbird 3 beta2 ... and other stuff

2009-01-19T12:53:00.000-08:00

Happy new year to everyone!

I know that I've been awfully quiet on the state of things in the Thunderbird world. I'm sorry for that. I was trying to nail down some stuff (release scheduling, website l10n story of which I will talk more in a later post), which took longer than anticipated.

I want to inform you about our release schedule for the upcoming Thunderbird releases.

First of all the dates for the upcoming Thunderbird beta2 release:
- Slushy string freeze: January 29th (Thursday)
- Slushy code freeze: February 3rd (Tuesday)
- Firm code/string freeze: February 5th (Thursday)
- l10n-mozilla-1.9.1 freeze: February 8th (Sunday)
- Gozer (our build engineer) starts the builds: February 9th (Monday)
We've tried to emulate what the Firefox devs did for their beta2 release, as we got the impression that this worked pretty well.

The idea is to have all string-related work done by the slushy string freeze date and all other code-related work plus the late-string work by the slushy code freeze date. Late string changes will require an additional approval by our TB3 beta2 release driver Bryan Clark (clarkbw on IRC).

The firm freeze date would be for fixing remaining bugs and regressions found in the nightlies and the l10n-mozilla-1.9.1 date would be the last time by which we would accept changes in localizations.
We know that this is a tough schedule and that this announcement comes pretty late. Therefore if significant objections are raised by you, we will reconsider this schedule and will discuss, whether this warrants a pushback of this schedule by one week.

Thunderbird drivers have also evaluated the current state of things
and have decided to add another beta release (beta3) to the release schedule. A firm decision on a release date has not yet been made, but it is probably safe to say, that beta3 will be released somewhere between the end of March and the end of April.

If you have any questions or concerns, please do not hesitate to respond here.

I've been tagged as well aka the "seven things"-disaster continues

2009-01-16T01:32:00.000-08:00

I had really hoped to escape the "seven things"-madness, but KaiRo aka Robert Kaiser thought otherwise and tagged me unmercifully. That means that I need to share seven things you may (not) know about me. You have been warned...

The rules:

Link to your original tagger(s) and list these rules in your post
Share seven facts about yourself in the post
Tag seven people at the end of your post by leaving their names and the links to their blogs
Let them know they’ve been tagged

The seven things you may (or may not) know about me:

My first computer was the legendary C64 (Commodore 64), which I got somewhere back in 1986 if I recall correctly. Damn, I'm getting old!
The longest period of uninterrupted game-playing I've ever had was 18 hours, playing Pirates! on that same C64.
I'm a die-hard fan of the Science-Fiction classic series Babylon 5, which I still regard as one of the best pieces of television ever.
Right now, I'm very much into the new Battlestar Galactica series, whose 2nd part of its 4th and final season will start today. Yay!
I've been an avid fan of J.R.R Tolkien's epic work "The Lord of the Rings", which I read for the first time at the age of 15 (15 years ago) and have read again each year since then.
I've wondered for a long time, why it is that mainly German, Polish and French people drive the Mozilla localization efforts, but haven't come to a conclusion yet.
My first contact with Mozilla was back in 2000, when I tried a beta release of the infamous Netscape 6 release. It's really a small wonder that I decided to stay in the community after working with that piece of garbage :-)

The poor souls that I'm tagging and need to continue this meme:

Rafael Ebron - Mozilla Messaging marketing guru, who needs to blog more
Bryan Clark - Mozilla Messaging UI guru, who needs to blog more
Clint Talbert - Firefox QA guru and Calendar developer, who needs to blog more
David Bienvenu - Mailnews guru, who really needs to blog more
Seth Bindernagel - Firefox l10n guru, who needs to blog more
Henrik Skupin - Firefox QA guru, who just got a new job
Dan Mosedale - best German-speaking American I've ever encountered

Number of strings to translate in Thunderbird or Lightning

2008-12-17T12:07:00.000-08:00

A question that often comes up with new localizers that want to localize Thunderbird or the Calendar products (Lightning and Sunbird) is "How many strings do I need to translate/localize?"

Finally I have the answer to that question and I'm posting it here, because

Someone else than me might be interested in the answer as well
I need a page that I can point people to

So for Thunderbird you need to translate 5749 strings (as of now).
For the Calendar products you need to translate 2065 strings (as of now).

That's really a lot and it really makes it that more impressive when you think about the great work that localizers are doing for our products.

Localized Thunderbird 3.0 Beta 1 RC builds available

2008-12-02T01:23:00.000-08:00

We have our very first Thunderbird 3.0 Beta 1 Release Candidate builds available. We will be testing these builds in the next few days and we would appreciate it, if you could test them as well.

The usual disclaimers apply - either backup your current profile, or create a new profile and run TB 3.0 Beta 1 RC1 against the new profile.

If you see real showstopper bugs, then please let me know ASAP and make sure that a bug is filed on that issue.

38 languages are part of Thunderbird beta1

2008-12-01T05:49:00.000-08:00

A little bit over three weeks ago, when I announced the string freeze planning for beta1, I said that I hoped that we could increase our number of supported locales for this release to 30 or maybe even (in the most optimistic case) to 35 locales.

Well, as of now 38 locales (including en-US) have opted in for the Thunderbird 3 beta1 release, thereby totally blowing away my expectations. This is notable, because already with beta1 we're just one locale short of what we had achieved with the Thunderbird 2 final release, which is currently supported by 39 locales (including en-US).

So thanks a lot to everyone in the l10n community. You guys rock!

String freeze in effect for Thunderbird 3 beta1 release

2008-11-15T06:34:00.000-08:00

As of midnight Pacific time yesterday (roughly six and a half hours ago) we're in string freeze for the Thunderbird 3 beta1 release.

This means that any l10n strings in the mail/ and editor/ui/ directories in the comm-central repository are now frozen. Since Firefox is also in string freeze for it 3.1 beta2 release right now the strings in browser/, dom/, netwerk/, security/manager/ and toolkit/ are frozen as well. So we don't need to worry about any breakage that might come from that front.

The code freeze for our beta 1 will be on Tuesday 18th November at 23:59 Pacific time. We'll cut the release sometime after that once we've had some baking. So this means basically that your locales should be ready by that date. I'll open up a opt-in thread for you guys as soon as the code freeze is in effect.

We will be having a test day for beta 1 soon, that will be covering the new features and checking for any significant regressions. More details coming soon.

Please check the dashboard for up-to-date information on the state of your locale. We also have l10n nightly builds available at the regular location.

Making life easier for new localizers

2008-11-12T03:23:00.000-08:00

When you look at recent posts in the Mozilla l10n space, sooner or later you'll find out that a lot of localizations only exist for Firefox, but not for the comm-central application Thunderbird, Sunbird or SeaMonkey. If you look at the numbers, you'll see that Firefox 3.1 currently has 65 localizations compared to 48 localizations for Thunderbird 3.0, 36 localizations for Sunbird 1.0 and 18 localizations for SeaMonkey 2.0.

This is not totally surprising, since Firefox has many more users and much more buzz than all three other applications combined. And even for locales that support more than just Firefox, Firefox is the natural leader in terms of localizer attention and status, because of its market share and popularity. This is nothing to complain about since people generally are more likely to work on something that makes a big difference and localizing Firefox into e.g. Vietnamese makes a much bigger difference than localizing Sunbird into Vietnamese instead.

For us in the Thunderbird/Sunbird/SeaMonkey communities this means that we need to adjust to this fact. To be more precise we need to make the actual localization for people as easy as possible, because when push comes to shove our apps will always come in second, third or fourth.

Most of us obviously can't help a new localizer with the basic translation parts, since in most cases we don't speak the language, but what can be done is to make all the other aspects of localizing a Mozilla application as easy and as less burdensome as possible. This means

reducing the bureaucracy around the l10n processes
providing better tools for localizers
communicating clearly and effectively with localizers
making sure, that localizers can concentrate on what they are good at, the actual translation/localization part

On the first item, I think we are doing pretty well, since we do not require nearly as many approvals, reviews, etc. from localizers as Firefox does. I hope we can continue to keep our processes lean as we grow our communities and get more more localizations.

The second item is very well covered by the growing l10n team at Mozilla Corporation. Especially Pike and Gandalf are currently doing great stuff in the tools space, that will make life easier for many localizers.

The third item is hard for me to comment on, since I'm doing the l10n communication for Thunderbird and Sunbird and it is hard to judge yourself. I haven't heard any complaints yet, but maybe I just missed it. I certainly hope that people will give me constructive feedback if I screw up.

On the last item, we made a few huge steps lately. For two weeks various people (including me) have done a script-based analysis of our codebase in search of unused strings. Unused strings are bad for new localizers, because you need time to translate them, which could be put to better use. We recently fixed three bugs or are in process of fixing them, which removed (or will remove) a total of 670 strings (219 for Thunderbird, 127 for Thunderbird and SeaMonkey, 324 for SeaMonkey. This is a lot of stuff (for Thunderbird roughly 1/8 of all localizable strings) that a new localizer will no longer have to wade through.

[Reminder] Thunderbird 3 beta1 string freeze in eight days (2008-11-14)

2008-11-06T05:45:00.000-08:00

I want to remind everyone, that we're the string freeze for the Thunderbird 3 beta1 release is approaching fast. We will freeze our strings for the beta1 release on Friday, November 14.

For those of you, who do not try to keep up with our string changes on a daily basis, now is a good time to take a look at all the string changes that have happened lately.

The l10n dashboard should give you a good indication on which areas of your locale need the most work. Documentation of the dashboard is available.

What many of you will notice right away is, that we've worked hard on removing unused/obsolete strings in the last weeks. Removing all those strings from your localization is something that can already be done before the string freeze as we are not planning on bringing those strings back. I know that this cleanup work means additional work for you, but hopefully it will make things easier for new localizers signing up to work on Thunderbird l10n.

In our last pre-release (alpha3) we managed to release with 28 locales. I hope that we can increase this number in this pre-release to 30 or maybe even 35.

I really hope that you will surprise me :)

If you have any questions, do not hesitate to ask here, in the l10n newsgroup or in #l10n on IRC.

Updated l10n documentation for Thunderbird - please give feedback

2008-11-04T07:01:00.000-08:00

In the past few days, I have actively worked on adding content to and updating the existing content of the Thunderbird l10n documentation page.

I added/updated

a pointer to and an explanation of the l10n dashboard (as already mentioned yesterday)
a pointer to this blog
a pointer to an up-to-date release schedule, which includes the string freeze schedule
a description of the responsibilities of developers during a string freeze and when breaking the string freeze
a first draft of a locale tier structure (based on the Firefox l10n tier structure)
the link to the TB source code in comm-central

I would really appreciate some feedback on this page from the l10n community. What information do you need, that this page or the links provided on that page does not currently offer?

Right now, I know of two areas, which still need work or content:

the link to the devmo documentation at the top on how to localize Thunderbird links to outdated content (the old cvs world)
the page still lacks content for the localization of web content, that will be created for the final Thunderbird 3 release

If you have any suggestions, please post them here or directly work on the wiki. That's what it is for :)

Updates to the l10n dashboard

2008-11-03T05:00:00.000-08:00

A few weeks after we had initially set up an l10n dashboard for Thunderbird, Calendar and SeaMonkey localization, Axel Hecht (Pike) managed to import the Thunderbird, Calendar and SeaMonkey trees into the main l10n dashboard as well.

We have let these two dashboards run in parallel for the last few weeks, but in the end, it didn't make any sense to have two dashboards for the same thing. We have therefore retired the Mozilla Messaging l10n dashboard and redirected all calls to it to the mozilla.org l10n dashboard. Please use the mozilla.org dashboard exclusively from now on.

To make you more familiar with the various options, that the dashboard provides, I've written up a short guide to its various functions on the mozilla.org wiki. I'd appreciate feedback on this guide.

Meeting the European l10n community

2008-10-26T03:04:00.000-07:00

I'm sitting here in Barcelona at MozCamp Europe 2008 with a lot of the European l10n Localization community and the more I talk to everyone, the more amazed I am of the passion and the energy that everyone has, when it comes to localize not just Firefox, but all the other applications (Thunderbird, Sunbird, etc.) that are out there in the mozilla ecospace.

For example, I spoke with one localizer (I can't remember his locale anymore, as there are so many people I talk to here), who spoke about working on Sunbird, Thunderbird, SeaMonkey and Firefox in parallel and still having a day job to pay the bills, that I had to wonder, how people do all of that with a day that just has 24 hours :)

One never ceases to be amazed by this community!