Milos Dinic - Development junkie - Coding all - HTML5, CSS3, JS, AngularJS, jQuery, PHP, Python, Magento, Ionic

30 Aug

Firefox Flicks contest website

Firefox Flicks

In Q4 last year, Mozilla has started working on a Firefox Flicks project. Furthermore, it’s a global video contest to tell the Firefox Story. You can enter at www.firefoxflicks.org. Firefox Flicks is a contest that invites Firefox fans and filmmakers from all over the world to create short videos (or “flicks”). By doing that, you will help tell the Firefox story.

Firefox flicks plan

Firefox Flicks
Firefox Flicks logo

We want the world to know more about what makes Firefox different. That we’re a non-profit organization aimed at keeping the power of the Web in people’s hands. Finally, our hope is that through high-quality videos made by our committee and Firefox fans from all around the world, we can help mainstream Internet users know more about the issues that affect their online lives. And, more importantly, how Firefox as a product addresses these issues.

In the beginning

Since the very beginning, we’ve been promoting the project via mozilla.org website. After that we started working on the Firefox Flicks content website. As most of the stuff we’re working on, most products and websites, that is, we want to give people opportunity to read this website in their own language, as well, so we once again ask our tremendous localization community to join us on our journey. We’ve create a thread on mailing list, and immediately got opt-ins from several languages. Yes, that’s how awesome we are!

Firefox Flicks Wrap Party
2012 Firefox Flicks winners posing with celebrity judges and Gary Kovacs, CEO of Mozilla – Photo by: http://blog.mozilla.org

Ever since then, a lot of teams within Mozilla were working on this, giving their best and staying up late, which eventually brought us a new website we’re really proud of: Firefox Flicks contest website! We released the contest website yesterday night(PDT), and besides default English(en-US), we can serve it in following languages: German(de), Spanish(es), French(fr), Ligurian(lij), Dutch(nl), Polish(pl), Brazilian Portuguese(pt-BR), Slovenian(sl) and Chinese(zh-CN). I’d like to use this chance and say “Way to go!” and thank you! To all of you that have been involved in translating this project.

Just a note before I end this post: Winning videos will be used in worldwide marketing campaigns and public service announcements. The contest is planned to close on May 1.

16 Nov

Firefox 8 release process

Firefox Logo

We’ve been working hard on moving localized Firefox builds out of the beta channel straight into final releases, Finally, that effort started paying off. There are several languages we keep in the focus. A few of them made significant progress in that field. Even though for some of them we have only beta localized builds, we still made it.

Firefox translation nvolvement

First of all, I’d like to shout “Yay!” to Armen, Jurk and Kerim for working hard on Armenian(hy-AM), Kashubian(csb) and Bosnian(bs) productization bits, respectively. Productization, for those who don’t already know, means adapting some features to a language/region. It includes default search engine set, protocol handlers, feed readers and live-marks(live bookmarks), along with a set of web pages on http://mozilla.org/ so that we are able to promote localized builds.

So, I’m happy to announce that we have made tremendous progress with aforementioned three locales. Consequently, we’ll be probably seeing them soon as final builds. For one, we made Bosnian locale out of beta channel. Also, we have managed to do everything in time for Firefox 8 release. So now, run to http://www.mozilla.org/bs/firefox/ and download!

Results

I’m also happy to say that Armenian is probably going to follow the Bosnian path soon(I really hope that that’ll be for Firefox 9, in December). Also, Kashubian should probably be joining final localized builds in the very beginning of 2012. Looking forward to that!

21 Apr

Bugzilla C3PO

Bugzilla Logo

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

13 Apr

wiki.mozilla.org Theme

Wikimedia

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!

24 Feb

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

12 Nov

Interview with David Tenser – Firefox Support Director

Hello David,
Thank you for agreeing to do this interview!
First things first: Can you tell me a bit about yourself and how you first got involved in Mozilla? I heard it was a long time ago 🙂

Yes, the years have definitely flied by. 🙂 It started around the Netscape 6 days around 2001 when I discovered that Mozilla was basically the same thing as Netscape, only with different branding — or, rather, a lack of branding. Being the geek that I am, I wanted to learn more about this new open source project, so I started to participate in the newsgroups discussions and made connections with other people online. Before I knew it, I was pretty heavily involved with both asking and answering questions about the use, design, and direction of projects like the Mozilla suite and this new browser called Phoenix (which later became more known as Firefox).

Although I majored in Computer Science and have a history of software engineering, my involvement with Mozilla has mostly been focused on helping users. Part of the reason for that focus was that the Mozilla code base felt overwhelming and wasn’t something I had a strong desire to master. It was more fun to just help others while at the same time learning more and providing feedback on product features and decisions — especially since I was already busy with writing software in the non-Mozilla world. Also, helping people with computer problems has always been something I’ve enjoyed doing, so that part of me isn’t restricted to Mozilla.

So, that’s a bit of my history with the project. If you want the longer story, I wrote a longer blog post last year about what made me discover, and ultimately stay with Mozilla throughout all these years.

Aside from Mozilla, my main hobby is photography. I’m constantly on the lookout for new camera equipment, but I must admit I spend almost more time reading about cameras than actually using them. I guess that comes with the package of being a nerd. 😉 A more recent branch of this hobby is post-processing of photography, which I started to do this year. Being the open source evangelist as I am, GIMP is of course my photo editor of choice — actually, I even find it enjoyable to use now that I’ve set it up to use my custom keyboard shortcuts. It’s really not as bad as people say, it just takes a bit of time getting used to it!

Lastly, I’m Swedish, I live in Sweden, and I look pretty much exactly like the typical Swedish stereotype. I’m not a chef, though.

What did the very first SUMO looked like, and what were its pros and cons compared to the time it’s developed in?

The first version of SUMO, released in the fall of 2007, was very crude, but it still represented an important step up from the old support content that had been hosted on mozilla.org since the Firefox 1.0 launch in 2004. There were a number of improvements, but perhaps the main difference was that the support content was now hosted on a wiki, making it possible for people in the community to participate in the effort to improve the quality and grow the number of support articles. Essentially, the Firefox support became much more dynamic than it had been before.

Another benefit from the previous support content was that we now had the ability to see which articles were most popular, providing us with important insights about which problems Firefox users most frequently encountered. We could also finally see the most common search terms, browser usage stats, and much more. This led to an even faster growth of support articles and the ability to feature the most common support issues prominently on the support start page.

How it actually looked like? Here’s an old screenshot. Of course, a lot of things have improved over the three years SUMO has existed — it’s hard to even know where to start! Perhaps the most notable change is the sheer size of the project — both in terms of number of Firefox issues we have solutions for, and the number of people who devote time and energy every week to helping Firefox users have a better experience on the web. Our community is definitely the biggest strength with SUMO.

What’s the magic that got a lot of people involved in SUMO and why do you think a one would like to be a SUMO localizer?

I see two parts of the magic. One is the inherent magic of Mozilla itself and its products. If you’re helping people on SUMO, you do it because you love Mozilla’s products and believe in our mission.

The other part is the impact your contributions have on SUMO. Just as an example, if you spend just one hour to translate a popular support article into your language, that one-time effort can end up helping thousands of people every week. Depending on the language, your work could impact millions of users every year!

That said, there’s definitely a lot of magic yet to happen with the SUMO community — I don’t think we have truly taken off yet, despite having 50-100 active contributors every week. There are many areas where we can improve, and will improve. For example, we recently launched the Army of Awesome project, which focuses on helping people who are tweeting about their Firefox problems. It’s a great, fun, and simple way for anyone to give Firefox users a helping hand by pointing them in the right direction if they need assistance with solving a problem.

Another example is our upcoming knowledge base back-end, which is going to be a huge improvement to content editors and localizers worldwide. You can read more about this gigantic project in Kadir’s summary blog post — or you can check it out live on the testing server: master.support.mozilla.com.

After a lot of thinking about the platform SUMO is using, you decided to make some key changes to it?

I think you’re referring to the decision to completely rewrite the SUMO platform. Yes, this has ended up being the major development focus of 2010, and the decision was based on the current state of the SUMO platform at the time. The list of wanted features and fixes was growing faster than our development team was able to keep up with, and the fact that Firefox was becoming so popular forced us to spend a lot of our time just patching things up while the website was slowly grinding to a halt. We simply had to do something radical if we wanted to ensure we could remain competitive and agile, so we decided to build something new from scratch. A more detailed summary of the history behind this decision can be found in a blog post from February this year. Today we’re finally beginning to see the fruit of our hard work over the year — and the result is Kitsune!

What would be the 3 most important new features of Kitsune?

There are so many improvements in our new SUMO web platform (internally more known as Kitsune), it’s really hard to rank them. Our amazing development team has really gone above and beyond, working around the clock to give us a support platform we can feel truly proud of. We already have a new support forum based on Kitsune that has been out in the wild for a few months now, so I’ll focus on the knowledge base here, since that’s our big focus right now. Here’s my personal top three list:

Third on my list is the new localization and editing interface that has been radically improved to streamline all common use cases — from editing an English support article, through reviewing an edit made by someone else, to translating an article into another language. Have a look at the typical contributor scenarios we’ve worked on improving. To say that we’ve spent a lot of thought about what goes into the platform would be an understatement… 🙂 Special thanks to Chris, Michael and Kadir for their hard work in the critical design phase of the project.

On second place is the source code of the platform. This might not seem like a big deal at first, but it really is: the entire platform has been rewritten from scratch using the modern, python-based Django framework. What this means — aside from getting rid of countless of bugs and other issues that have plagued us for many years — is that we’ll be able to develop new features and fix bugs much faster than we’ve done in the past. Our SUMO development lead James Socol summarizes many of the benefits of the new platform in his recent blog post.

The most amazing new feature of Kitsune? Performance! The new Firefox Help website will be so much faster, both for users and contributors. In some places, Kitsune is almost 30x faster than the current website. It’s like we’ve gone from an old Wartburg to a brand new Koeningsegg! And we really needed it — with 400 million Firefox users and a thriving community of localizers around the world, timeouts and other weird behavior when editing support articles have become far too common on the website today. This will all be history when we release the new SUMO at the end of this month. 🙂

Where do you see SUMO in a 3 years period?

That’s an interesting question. I think there’s a lot of room for SUMO to grow way beyond our current size and reach. The recent Army of Awesome project has helped us reach out to more users in need of help, but there are still lots of Firefox users out there that aren’t aware of us — they simply don’t know that there’s an entire community of people ready to help if they have a problem with Firefox.

Three years from now, I believe that everyone who uses Firefox will know about its support site — and our community will be strong enough to help all of them. As for the support web platform we’re shipping this year, I can definitely see it turn into an open source support platform of choice for other projects like SeaMonkey and even non-Mozilla products. SUMO is already being used by Firefox (including mobile versions and Firefox Home) and Thunderbird, and this is just the beginning.

What message you’d like to send to people thinking about if they should join your team of contributors?

Please do! Helping Firefox users with their problems is simple, fun and only takes as much time as you’re willing to put into it. There are so many different ways to help — you can translate a support article into your language, which thousands of people will benefit from. Or you can help us improve the English articles. Or you can answer individual questions in the forum. Or you can interact with people directly using live chat, which is extremely addictive and rewarding. If you’re good vith video or image editing, you can help improve support articles by adding screencasts and screenshots. And if you think you don’t have enough time or lack the expertise needed to be helpful to others, we’ve got the solution for you. It doesn’t have to take more than a couple of minutes per day — and really, anyone can do it!

One last reminder: we’re just about to switch to a brand new knowledge base system. Please help us test the new stuff on master.support.mozilla.com so we can ensure a successful release at the end of this month! You can always ping us in the irc.mozilla.org channel #sumo, or post in our SUMO community forum if you have any questions. Welcome to the SUMO community!

14 May

Interview with Seth Bindernagel – Director of Mozilla Localization

Hi Seth. Can you tell me a bit about yourself, how you got into working for Mozilla and what were your first tasks?

Sure. I first started working for Mozilla back in 2006 when I was asked to start Mozilla’s Community Giving and Empowerment program. With the help of Asa Dotzler, I was able to launch a program to help members of our community with reasonable levels of support that would both assist and amplify a volunteer’s or a community’s contribution to the Mozilla project. Because so many of our community members had their beginnings in the localization work, I learned a great deal about localization and the needs of the community. It was clear that Mozilla should formalize even further the localization-drivers team to increase our focus on the global distribution of Mozilla applications and websites. Because I had much exposure to our volunteers, I was asked to help lead the l10n-drivers team.

Can you compare the importance of localization against some other parts of a complex projects like Firefox?

From a technical standpoint, someone could argue that localization is not as difficult as hacking on the Mozilla platform code or doing php web development, and they would be correct!  However, that is a bit like comparing apples to oranges because localization is incredibly important to the release engineering process at Mozilla.  If we were not able to localize our code, our global audience would not have as rich a user experience as they do now with a localized product.  Localization touches many parts of the release process along the way to final release, including the user interface, QA, and build.  Therefore, our localizers often have to wear many hats, understanding how to translate the language of the user interface, how to access nightly builds, how to read html and php code, and how to test the versions ready for release.

How do you see the localization in the future, in terms of a popularity among localizers and its complexity?

I think the localization of Mozilla products has gotten easier in the past two years, with more tools, reporting, and documentation available for localizers to use. I also believe that it will continue to get easier. But, the important fact here is not to eliminate choice. Our volunteers should be able to choose how they want to localize products and websites, whether using a “slick” webtool or using a more technical code editor. The point is that we should make hard things easy and let everyone experiment and participate as they choose.

Can you tell me, based on your experience, can we expect more and more localizers, and what do Mozilla do to attract new contributors and to promote using the localized builds of its applications?

We work very hard to continue to attract new localizers. This takes a combination of steps. The first step is to work with local communities to help build contributors. If a local community wants to actively build new contributors, we need to work with them to push that authority to them and to the edges to make sure they are empowered to do so. We are in the midst of planning one such event now with Mozilla’s “Inter-Balkan Meetup”. The second step is to build tools for better localization. This includes improvements to our infrastructure, documents, and tools for translation. New localizers do not always know exactly how our process works. So, we need to create a clear path for them to engage and learn how to contribute. With those two steps in combination, I think we will always be adding new community.

What does Mozilla do to improve the ease of translation for its localizers?

One very specific step we have taken is to implement tools like Verbatim. If a localizer visits http://localize.mozilla.org, he or she will see all the open web projects needing translation for various languages. This brings the work flow and avenue for participation to the localizer in a fairly understandable and clear way. Secondly, we try hard to furnish up-to-date statistics about the state of product and web localization through our dashboards. Localization communities can always see the status of various projects (including how many strings are needing translation and where they are located in the code base) by vising this URL: https://l10n-stage-sj.mozilla.org/ If we continue to enhance our tools and streamline our infrastructure to provide to our localizers the most timely information and statistics about work needing to be done, we will continue to make the process easier.

What message would you send to all potential localizers reading this?

Give localization a try!

  • If you speak a particular language, check out what needs to be done at the Verbatim URL: http://localize.mozilla.org.
  • Contact the locale leader for your language. You can see who the locale leaders are for various language teams here: https://wiki.mozilla.org/L10n:Teams
  • Email me if you have any questions. You can find my contact information at my blog: http://blog.mozilla.com/seth

We always look for new contributors and welcome anyone with any level of experience to participate.

10 Apr

Importance of localization

As I already said in some of my earlier posts, I see the localization as one of the most important things out there. Although I’m writing this blog in English, I do and always will support having localized applications and documentation for it, so non tech-savvy users could enjoy using them with flavor of all its features. Of course, as much as the application a one uses is good, the localization gets more on importance.

On the other hand, it looks like most of the tech-savvy people in Serbia do not agree with aforementioned statement. As some of you might know, I’m the Mozilla Serbia community leader, Web Localizer, Firefox localization peer and Mobile Firefox localization coordinator. Mozilla localization team allowed all lead localizers to have a brief stats on how many Firefox downloads we had last week, and what’s even more important, what percent of those downloads are actually downloads of localized versions of Firefox.

Last week I took a look at those statistics, and noticed that more than 60 percent of Firefox downloads from Serbia belongs to en-US locale, or the default one. That is something that worried me a bit, because we have Firefox localized in Serbian for several years now, and by now a one would expect that more than 70 percent of people in Serbia using Firefox, to actually use it in Serbian language.

I crawled the web a bit these days, and saw that many Serbian website’s web-masters tend to link to official Mozilla website rather than to Mozilla Serbia community website or even official Mozilla website in Serbian. Also, I asked a few of them if they could change the links with an brief argument, and believe it or not, always got the response saying that they DO NOT SUPPORT SERBIAN LANGUAGE ON THE INTERNET. Now, that got me amused, and made me wonder what could cause such a thing, and how should we treat it. So here’s the thesis:

Why would a man/woman from Serbia prefer English over Serbian(in apps)

  • People got used to English
  • Some of them are not actually reading the whole strings, but can recognize them by reading first few letters
  • Some translations in Serbian may sound weird or funny

So, now we came to the point where we should ask ourselves the following: “How to change that, or how to convince people that can change things that we should really encourage users to use native language?”. There is no simple nor ultimate answer that can explain the process as it should be done. The first thing is the root, and if we’re talking about Firefox(I am), than that is Mozilla. I have noticed that Mozilla actually cares about this, and is trying to promote both localized versions and local Mozilla communities, to help localizers their “product” is seen. We can see a link to Mozilla Serbia local community on Firefox Support, Thunderbird Support, Spread Firefox…

Another thing that we could do, is to advertize the localized version of our product to users coming from Serbia (using GeoIP tech) and are using Firefox in en-US locale. The pages on which we need this the most are the ones you get when you start Firefox after installation or upgrade process. That would, in my opinion, significantly improve the percentage of usage of localized Firefox. Also, we need to spread the word, to ask wherever we can and whoever we can to promote the localized Firefox for the sake of all newbies that will and are using Firefox.

23 Feb

Web browser choice matters

Our lives are full of choices. Where to eat? What to read? Who to spend time with?

The choices we make determine the quality of our life, and how we see the world. So many of these choices we take quite seriously, weighing the consequences, thinking about the implications, and choosing carefully and thoughtfully.

So it’s strange, then, that the majority of people in the world haven’t ever considered the Web browser on their computer or mobile phone — that so many people every day use the browser that comes by default.

It’s an important choice because the Web browser has become one of the most critical and trusted relationships of our modern lives – with nearly perfect knowledge of everything we do. It is the lens through which we look at the virtual world, and the medium by which we connect, learn, share, and collaborate. The browser you choose is responsible for providing you with the necessary tools to manage your online life, and to protect your privacy and security.

And so we’re pleased to support the European Commission and Microsoft in also recognizing how important choice is. In accordance with a landmark settlement, if you’re using a Windows PC in Europe and you’re still using the default Web browser, in the coming weeks and months you’ll see a Browser Choice screen appear. That screen will provide you the opportunity to make an active choice in the source of the software that acts on your behalf to broker your online experiences, and meet your own unique needs and interests.

As an international non-profit organization, Mozilla has always believed that the freedom to make smart choices should be central to making the Web, and the world, a better place. This shows through with Mozilla Firefox, a free, open-source Web browser that more than 350 million people around the world have chosen to use every day. Values of choice and self-determination are built into everything that we do, including Firefox.

We believe that the Browser Choice screen is an important milestone towards helping more people take control of their online lives — and we hope for the conversation to become broader and deeper. We’ve set up opentochoice.org as one place for you to discuss what this choice means to you — and we hope that you’ll add your own voice to this conversation and those to come.

Whether or not you decide to keep your current Web browser, we encourage you to learn more about your browser and the impacts it has on the way you see the world, and to make your own choice.

Mitchell Baker, Mozilla Chair & John Lilly, Mozilla CEO

Taken from:

www.opentochoice.org