Flock Blog

Some time ago, I wrote a document that is targeted to all developers around the world, who creates their products and speak only english.

It may help you understand how the localization process looks like, what are the common problems and how can you make localizers life easier by avoiding small mistakes that result in their drama.

Feel free to comment, edit, update, and promote it. I hope you’ll find it interesting

We’re probably one day from second round of Flock localization for Flock 0.7!

We’re hunting bugs in current 0.7.4 and if all goes properly, tomorrow, we’ll send localization bundles, and after next few days we’ll release over 16 localizations!

I’ll post more tomorrow, once 0.7.4 codebase is clean

I just came out from the Flock team meeting, where we once more discussed the issue of openness. We are open, we want to be more open, and we see that it’s something more than simply opening the source code. Actually, it requires resources. To became really open for all our users, for all potential contributors, for our partners, friends, competitors, for the market and for the world; we need to use more energy than it takes to stay silent. That’s one of the lessons I learned recently.

If you don’t pay attention, you drift toward a closed model.

Last month was awesome. We’re almost ready with Flock 0.7 release, and we want to make it the first release with semi-official localization builds.

If you want to help us, and you speak any language beside of US English, it’s a good time for you

Please, take a look at my Flock-l10n maillist post and contact me!

Yes. It’s official now. See Will’s meeting notes. And now it begins.

Today, we started money rewarding our developers for every bug/patch upstreamed to bugzilla.mozilla.org!

It simply means that beside of supporting Mozilla in their mission (to preserve choice and innovation on the Internet), we also joined the list of companies that are supporting Mozilla development by their employees worktime!!!

We’re very proud to be a part of the Mozilla world, we believe that we can do much more than previously to help in bugfinding and bugfixing of Gecko, Editor and Firefox, but we want to give more.

We’re regrouping before the XTech! Add your name if you’re going to be there

There’s the awesome tool made by Robert Ginda called Venkman Debugger.

There’s even a great tutorial on how to use Venkman, but it covers only the area of debugging your website scripts.

So, with help from Vera, using Yosh and Ian as a testers, I hacked a small tutorial that covers the hole and presents two trivial examples on how to use Venkman to hack Flock (and also applies to hacking Camino, Seamonkey, K-Meleon, Firefox your extension and your website of course).