Bugzilla C3PO

A few days ago I needed to file 70+ bugs for the same thing for each locale we support on www.mozilla.com. I then decided to make use of BZAPI(Bugzilla Web Service API), and have created a tiny PHP script to do the job for me. It worked pretty well even the first time I tried it on on http://landfill.bugzilla.org, so I could expect only better performance on bugzilla.mozilla.org.

I will definitely use it in the future, so I created a web interface for it, so the user could choose component, product, version, bugs to block, whiteboard status and such.

On the road to make this work everything went pretty well. Bugzilla as a more-than-a-ticketing-system™ provides you with a publicly available config file, which is in JavaScript, and that contains all the component>product

If you think my code is bad, or that you can do it better, feel free to fork or send me the patch. Code is at https://github.com/milossh/bugzilla-c3po

wiki.mozilla.org Theme

An hour ago, wiki.mozilla.org got a new default template, or in media-wiki lingo – a new skin. I’ve been working on this skin whenever I had some spare time, and it finally payed off. While creating the skin, my guideline for the design was mozilla.org. Also, I did my best to make it as readable as possible, as a lot of us do a lot of wiki reading.

 

After the initial skin submission, I received awesome(marvelous?) feedback fromMozillians, and I tried to make it better in this new retouched skin. My main points of focus were the headers, or how to make them different(at least). I really believe that I managed to do so, and that you’ll use it with ease.

Now, a brief comparison to Cavendish theme, the one we used so far:

  • It looks pretty much the same as our mozilla.org template
  • Main content area takes 77% of the screen, which allows people with wide screens forget about scrolling down a lot to see the whole page.
  • Side menu use really small font size, so it doesn’t take a lot of space
  • Headers have improved a lot: they’re quite different now so it’s a lot easier to distinguish paragraphs
  • Code blocks are much cuter now
  • Broken tab functionality on prefs page is fixed

Last but not the least, I’d like to thank everyone for a great feedback, and for making this possible!

News: mozilla.org and wiki.mozilla.org

During my internship at Mozilla Europe, I’ve been working on a lot of stuff. I’ve been helping with Marketing and community engagement, localization, WebDev, QA, SUMO… All in all, I had my hands always full with a bunch of adorable tasks. Due to being work-o-holic, I find this extremely thrilling and fun.

After some time, I had a very informative chat with David Boswell, who asked me to help him make mozilla.org website localizable, so we can serve its content in many languages, just as we do with mozilla.com. My internship supervisor Pascal Chevrel and I agreed that I should spend some time working on that, integrating current mozilla.org content into the system Pascal was building for a few years now. We use that framework for mozilla-europe.org website, and it’s much similar to what we have on mozilla.com. After almost 2 months, I can say I’m almost done, and I’d like to present my work in this blog post.

All the development work can be seen on hagege branch on Mozilla’s public svn – http://svn.mozila.org/projects/mozilla.org/branches/hagege. Hagege is the name of the famous French poliglote who spoke 50 different languages fluently, and Pascal Chevrel is the one to blame for this marvelous symbolism.

As of this moment, we have 5 working languages, being English, Greek, French, Croatian(partially) and Hebrew. I won’t talk much, but I’ll post some pictures instead:

 

All in all, it looks pretty good, and if you want to check it out live and working, please visit http://hagege.stage.mozilla.com

Beside that, I have some more good news: wiki.mozilla.org got a new theme, and you’re all welcome to use it and give us your feedback. Here’s what it looks like:

 

This skin is currently optional skin, and you can test it by setting it as a default one in your user preferences on wiki.mozilla.org