Thunderbird to become the default in Ubuntu!

Great news from Budapest where Ubuntu project is holding their version of our All Hands 馃槈

According to Michael Larabel Thunderbird will become the default choice for Ubuntu’s mail/newsgroup client! That’s a strong prove of progress that Thunderbird has made, and trust me, Ubuntu does not swap the defaults that easily.

Well, it now seems that we’ll have two of our products used as pretty important defaults in this most popular Linux distribution – Firefox and Thunderbird! (although we do have a strong competition for the browser slot).

Congratulations to the team working on Thunderbird!

Falsy Values – volunteer opportunity

In just about a week Warsaw will be hosting a major JavaScript event – Falsy Values.

Falsy Values is brought to you by the two people – Damian Wielgosik and Pawe艂 Czerski – who made their way onto the Web Event Stage last year with their widely praised Front-Trends conference.

This year, they focus on hardcode JavaScript. This conference is not about soft disciplines, not about social science, it’s solely about hacking the modern Web.
With stellar workshops and talks, with names such as Douglas Crockford, Tantek 脟elik, Tom Hughes-Croucher and our homegrown stars like Kornel “porneL” Lesi艅ski, it has what it takes to be the powerful event to be at.

Now, such an event is not going to happen on its own, it takes passion, dedication and the one thing we all should value most – time – to shape it up and deliver.

One of the unique features of this conference is that it really is handmade by those two fellows who work 24/7 right now to plug all the cables in the right slots, bring supply to the tables and speakers to the microphone.

All hands on deck!

As you may have guessed from the title – we believe we could use some help during the event itself!

If you’re located in Warsaw, or if you will be here for the time of the event, and you’re looking for a chance to participate in what’s going to happen there, help us make it perfect, learn the unique lesson from behind the scenes, here’s your chance!

We’re looking for geeks who seek experience in helping us run this event. Several brave souls to support speakers, guide the crowd through the agenda, run fiercely to aid some brother in JavaScript arms who’s in danger of any kind (like – you know that moment when your WiFi doesn’t work?)

We expect you to be there with us (even an hour before the opening), assist when needed and enjoy the conference. We offer an opportunity to learn, gain experience and help us make the best event in the JavaScript world since Brendan invented this monster!

Get in touch with us! Email me (gandalf at mozilla dot org)聽 or contact Damian and Pawe艂 directly and we’ll go from there. Hurry up, we only have 5-7 slots available!

L20n gets tangible

While Firefox 4 was the main focus for the last weeks and months, I’ve been also making progress with the next iteration of Mozilla localization technology – L20n.

Here are three things that constitute a milestone for me and should make it much easier to test and play with the features of it.


Toobox guides you through the examples of various localization scenarios and how L20n solves them. It blends incremental learning of features available to both developer and localizer. At the bottom it contains several more complex example that should rarely happen but constitute the latter part of Pike’s “easy things easy, complex things possible” mantra.

XPCShell tests

It’s a small (two at the moment) set of tests that run l20n code. It’s a great start point to play with how the library works and how the format works. You can adjust the compiled code, or the library code and see if it gives the expected result.

Live toolbox

What can be better than a toolbox for a geek? Yes. A live toolbox. A toolbox you can not only read, but one that you can actually touch, change, hack on and see the result live.

It’s a hack itself, so don’t be harsh pls, but it does the job. I even included a set of 7 examples (example1 to example7) that correspond to what you can find in the Toolbox. Feel free to modify the L20n code, see if it compiles properly, play with the compiled code, change the HTML or JS and see the results live!

Also, if you encounter a bug, you can save your code and send it my way so that I can investigate it. The compiler is just an initial approach, and a moving target right now as we still don’t have a finalized JS structure schema, but it works for most simple and medium complexity cases, so I’d say it’s ready for you to play with it!

Next steps

Now, that we have Firefox 4 released (yay!), and mozilla-central is open again, I hope to work on landing the initial set of L20n Gecko bindings which requires some updates to the patches themselves first. With that part, we’ll be able to start investigating migration away from current DTD/properties format into the wonderland of L20n.


Web O’Wonder po polsku!

Pisa艂em niedawno o kampanii Web O’Wonder.

Nied艂ugo po moim po艣cie zg艂osi艂 si臋 do nas Krzysiek Wr贸blewski i zaoferowa艂 swoj膮 pomoc. Pomogli艣my mu za艂o偶y膰 konto na Verbatimie, przygotowali艣my stage, i prace ruszy艂y. Liderem lokalizacji by艂 Krzysiek, pomaga艂 mu Leszek “Teo” 呕yczkowski, a ja stara艂em si臋 by ich praca napotyka艂a jak najmniej przeszk贸d.

Kr贸tki wywiad:

G: Jak dowiedziale艣 si臋 o projekcie i co sprawi艂o 偶e si臋 zg艂osile艣?
K: O projekcie dowiedzia艂em si臋 oczywi艣cie z Twojego bloga na Polskiej Planecie Mozilli. Zg艂osi艂em si臋, bo chcia艂em zobaczy膰 jak przebiega proces t艂umaczenia i mia艂em troch臋 wolnego czasu 馃檪

G: Jak Ci si臋 pracowa艂o przy nim?
K: Pracowa艂o si臋 bardzo dobrze, na pocz膮tku musia艂em opanowa膰 Verbatima, ale nie by艂o to trudne, szczeg贸lnie z pomoc膮 pana Leszka. Nie zdziwi艂o mnie za to, w jaki spos贸b Wasz zesp贸艂 dyskutuje na temat najdrobniejszych szczeg贸艂贸w, bo z tego jeste艣cie znani 馃槈

G: Co bylo najtrudniejsze?
K: Co by艂o najtrudniejsze? Konieczno艣膰 porzucenia takich 艂adnych czcionek na rzecz standardowych, z powodu niedost臋pno艣ci polskich znak贸w 馃槢

G: Ile czasu zaj臋艂o Ci to t艂umaczenie?
K: t艂umaczenie zaj臋艂o chyba z tydzie艅, co raczej nie jest mistrzostwem 艣wiata, ale nie 偶a艂uj臋 po艣wi臋conego czasu 馃檪

Po zako艅czeniu pracy nad Web O’Wonder, Krzysiek pomaga przy kilku innych projektach specjalnych – t艂umaczy m.inn. gr臋 mobiln膮 Spark. Poza Krzy艣kiem, pomaga nam te偶 Pitazboras, oraz siecobywatel, a gro pracy wykona艂 Teo.
Poza wysokiej jako艣ci t艂umaczeniami, Krzysiek napisa艂 tak偶e dodatek do Thunderbirda – Glasser i mam nadzieje, 偶e b臋dzie mia艂 ochot臋 na prac臋 z naszym zespo艂em przy nast臋pnych projektach 馃檪

A za t艂umaczenie WoW nale偶膮 si臋 Krzy艣kowi gratulacje!

p.s. Je艣li masz ochot臋 si臋 przy艂膮czy膰 i pom贸c z t艂umaczeniem, za艂贸偶 konto na Verbatimie i dodaj sugestie. Je艣li chcia艂by艣 (chcia艂aby艣) przej膮膰 kt贸re艣 z t艂umacze艅, wy艣lij mi maila na zbigniew at aviary kropka pl.

Crazy times for the localizers

March of 2011 is special for all of us. It’s the Firefox 4 release month and the whole project is operating in it’s “crazy” mode.

One particular plane on which it’s pretty visible is localization as we’re involved in almost every aspect of the release, every little detail, every step of the product release, every engagement campaign and of course in every bit of discussion about the state of the web that happens in our respective countries.

The story

As an organization that has glocalisation imprinted on the very fabric of its universe, we always feel responsible for making sure that everything we do is localizable, so that our communities around the world can translate and adjust everything that Mozilla project creates and use it to promote the Mozilla mission in their regions.

That’s easy to say, much harder to do. Especially as we grow, and the number of projects that we touch goes up. Firefox 4 release brings an unprecedented number of web projects that are part of our push to make bring the web to the next level.

Those projects vary from HTML5 demo sites, through Mozilla Developer Network Demo Studio, social web projects for twitter and facebook, web games to new Mozilla Foundation campaign – Join Mozilla. In total, I believe, we’re preparing 12 separate projects that we call “special projects” that are going to more or less closely accompany Fx4 release (not to mention Firefox 4 l10n itself, and our major projects like SUMO, MDN, AMO).

Each of the projects is very different and unique, uses different set of technologies and is embedded into different environment and yet we need to unify it for our localization community so that they don’t have to learn how to localize each of them separately.

Given the usual amount of challenges multiplied by 12 different setups it could have been a mess and it should have been impossible, but thanks to a great work done mostly by Sta艣 Ma艂olepszy, our team of l10n-drivers unified the experience as much as possible and localizers are right now doing an amazing job by bringing those special projects to every corner of the Earth, to billions of people.

Below is a summary of what happens there. Continue reading “Crazy times for the localizers”

Mini kampania z okazji wydania Firefoksa 4

Wraz z nadchodz膮cym wydaniem Firefoksa 4 Mozilla planuje ma艂膮 kampani臋 promuj膮c膮 HTML5&Friends. szuka os贸b ch臋tnych do pomocy w t艂umaczeniu tej strony. Oferujemy dost臋p do serwera testowego, niewielk膮 ilo艣膰 string贸w do przet艂umaczenia i spor膮 dawk臋 zas艂u偶onego poczucia dobrze wykonanej roboty.

Zainteresowanych zapraszam do mailowania do mnie (zbraniecki at aviary dot pl) lub od razu do wej艣cia na Verbatim –聽 – zak艂adasz konto i dodajesz sugestie.

Uwaga, wysoka jako艣膰 t艂umaczenia mo偶e skutkowa膰 niemoralnymi ofertami dalszej wsp贸艂pracy ze strony 馃槈

Hard Blockers Counter 1.0

A little bit more of coding, a few bug reports later, HBC is ready for its prime time. Version 1.0 fixes the nasty toolbar height problem, it gives a user an indication of the interval covered by his plot and is just overall better.

It can be downloaded from an listing, and the source code is available at 馃檪

A few of the lessons learned and thoughts:

  • builder is awesome, but it needs more real life users. A lot of bugs are only reproduced after you write your extension for some time, hundreds of revisions etc.
  • AddonSDK is excellent for this kind of extensions. It has everything you may want and makes the whole code extremely clean and simple to write and maintain. Just look at it – about 50 lines of core code – your cat could read that.
  • AddonSDK needs more real life users. Like with the builder, bugs show up only when you really use the extension you created.
  • AMO is an excellent developer friendly platform – it gives me a lot of satisfcators in a form of stats, and ability to manage my extension release process.
  • AMO-builder bindings need more real life users. I felt like I’m the first to try to push builder based extension to AMO – many trivial bugs that can be only revealed if you try to go through the whole thing.
  • AMO’s review/release process is excellent for the extension of the Old Days. It gives us a pool of high quality, verified extensions, that are easy to find and safe to use. It does not work with agile development. Builder and AddonSDK makes creating ad-hoc extensions super simple and quick (literally, 2 hours and you’re done with the first version, every new version is about 15 minutes of work). When you then push it to AMO it feels like Matrix slow motion then – you suddenly wait days for a preliminary review, not to mention almost two weeks you have to wait for a full review. My last revised version is super old comparing to what I claim to be the “stable” one now 馃檨

This issue requires a little bit of description. I do not try to say here, that what AMO reviewers are doing is wrong – quite the opposite, I believe the whole process is excellent and anything that is exposed to the millions of users should get some time to season and be tested and be reviewed. It’s just that AddonSDK/Builder gives you a totally different setup that fits different needs. I believe AMO will need a workflow for extensions that are created in 10 minutes, distributed in 20 minutes, updated 5 times during 4 hours and are becoming useless after one or two days.

Think of a conference where schedule is updated often and people have hard time to track it. Using AddonSDK/Builder you can create an extension for it in literally 20 minutes (xhr, panel, widget). AMO is excellent for distributing it, updating your users etc., but it requires very different approach than say, AdBlock or Firebug. Then, you add a feature (ability to mark the talk you want to attend and get a notification when its room/time changes) and upload a new version 15 minutes later. You want to switch all your users to the new one now. Then you fix a small bug affecting linux users, and update users once again.

It’s amazing that Firefox is becoming a platform where it is possible, and I can’t wait for such application for AMO 馃檪

  • AddonSDK requires a lot of users with their use cases. Myk’s approach is to iterate often which means to get version 1 ASAP and then add new features for version 2 instead of trying to build an ultimate solution without a release. I love this approach and it serves AddonSDK well, but now we need version 2 of many of the packages there – it can only be done if people start using the packages for a real life extensions and report what they miss. Like – Widget content cannot be easily themed. Or, you cannot control Panel’s scrollbar appearance. Jetpack team cannot plan for those use cases, they have to come from jetpack users. So be brave! Try things, report everything you need! 馃檪
  • There is a group of at least 500 people who deeply care about our release process. They’re ready to increase the amount of items on their screen to have a continuous updates on our progress toward Firefox 4. And it’s been just two days. It can motivate people to help, make them feel the sense of progress, help them understand the challenges better. It sucks outsiders closer to the inner circle. I believe we can do much more and the nightly users, mozilla planet readers and the audience of my extension deserve the chance to get more info which can help them start contributing! 馃檪

Hard Blockers Counter 0.8 (0.9) – with a plot!

Tremendous success of the Hard Blockers Counter extension (it got over 300 daily users and 4 positive reviews – yet they were lost in the transition :() motivated me to spend another too-early-morning on adding a history plot for the counter.

It was a real pleasure and a good lesson to go through – simpleStorage, timer, panel, and contentScript communication stuff. I reported some bugs in the toolkit, in the builder and in the builder->amo release process. It’s all been fixed 馃榾
The only real unresolved issues is that the widget affects the height of the toolbar. Reported as bug 626728.

So, 0.8 is ready and waiting, enjoy and fight that bug number down! 馃檪

Source code as always available.

[update] Actually, Builder provided me an old version of my jetpack and I submitted it to AMO as 0.8. So now I added 0.9, but it has to wait to get a review – so if you want colorful plot, download it directly from here.

Firefox 4 hard blockers counter

Last night was a usual “15 hours on a plane brings your sleep cycle into the fifth dimension” one for me.

I was pondering through the planet mozilla and realized that despite great effort from our UX Team, Firefox 4 nightly does not show up the single, most important information piece about the state of my browser, it does not answer the question that our whole project is living now:

How many blockers do we have until we reach Release Candidate

Well, you probably can imagine everything from there – now, I present you the missing piece – Fx4 Hard Blockers Counter extension in its full glory.

Source code available.

Video w sieci rok p贸藕niej

Rok temu pope艂ni艂em wpis, w kt贸rym opisa艂em jak wygl膮da sytuacja z kodekami wideo, stanowisko jakie Mozilla Foundation przyj臋艂a w tej kwestii oraz widoki na przysz艂o艣膰.

W komentarzach napotka艂em du偶y op贸r, wi臋kszo艣膰 komentuj膮cych mia艂a zdanie skrajnie odmienne ode mnie, pisz膮c o nieuchronnym upadku Mozilli, rych艂ym spadku popularno艣ci Firefoksa, bezsensowno艣ci stawania na przek贸r tak pot臋偶nym firmom jak Google, Apple czy Microsoft…

Wystarczy, nie lubi臋 wy偶ywa膰 si臋, a poza tym tamta dyskusja by艂a nie fair – ja pisz膮c to wiedzia艂em, 偶e Google uwolni VP8, moi rozm贸wcy mogli odczyta膰 moje s艂owa jako pobo偶ne 偶yczenia – wszak nic wtedy jeszcze na to nie wskazywa艂o.

Summa summarum, dzi艣 sytuacja jest odmienna. Wydaje mi si臋, 偶e nasza postawa mia艂a niebagatelny wp艂yw na decyzje Google o porzuceniu h.264, cho膰 s膮dz臋, 偶e nasz wp艂yw by艂 raczej po艣redni – zatrzymali艣my adopcj臋 h.264, utrzymali艣my pole otwartym, tak, 偶e Google op艂aca艂o si臋 postawi膰 na WebM. Jestem dumny z tego jak Mozilla korzysta ze swojej pozycji do realizacji cel贸w statutowych.

Nie wygrali艣my tego jeszcze – wci膮偶 do przekonania s膮 Apple i Microsoft i podejrzewam, 偶e ta druga firma b臋dzie 艂atwiejszym partnerem, ale krajobraz po roku czasu jest znacz膮co odmienny.

Co przyniesie nast臋pny rok? S膮dz臋, 偶e dystans jaki dzieli WebM i h.264 w zakresie wsparcia sprz臋towego zniknie, Adobe Flash zacznie wspiera膰 VP8 (a mo偶e i WebM?), Microsoft do艂膮czy wsparcie dla WebM, a Apple stanie przed trudnym wyborem… a jak b臋dzie naprawde? Czas poka偶e 馃檪