Posted on Jul 21, 2010

Firefox Input, now with Atom Feeds and L10n!

The Fx Input team has released out a new revision of our fun project within the Firefox Betas! We had our triagers in mind with this release and have some real goodies for them. Take a look below for what’s in this release. Of course, a hearty congratulations and thanks are in order for Fred Wenzel, Dave Dash, Stephen Donner, Shyam Mani, Chris Howse, the L10n team and James Socol for making it happen.

Features Added

  1. All searches now have feeds! For example, head over to a search results page for the term ‘love’ and look at the right side of your url bar. There you’ll see a pretty little feed icon present. Click on it and enjoy!
  2. L10n Help in the form of a localized Input  (check out the bottom of the submission and dashboard pages) and a “Translate!” link for each individual message that redirects the user to Google’s Translation Service with the message they select in-hand.
  3. A few UX changes like removing those space-taking boxes on each individual message and percentages between happy/sad on our Overview Box.

If you’re interested in the stuff we’re doing and want to help out, come over and join us at #input on irc.mozilla.org!

Technical Bug Stuff Below

Posted on Jul 15, 2010

What I’m going to do with my MBA

Short answer:

Provide and foster opportunity.

Long answer:

I’ve always had a love affair with the Internet. It started when I was 8 and figured out how to log-in to my father’s Prodigy account for the first time. When I graduated from my undergraduate degree from University of California, Irvine in Computer Engineering, I knew I wanted to help keep the internet going and thought l2/l3 was the place to be. So, after interviewing at various companies, it was a pretty easy decision (i.e. organizational culture, the team, job opportunities, etc.) to join Nortel as a 22 year old. After about half a year though, I realized that my abilities, as they were then, just weren’t going to cut it. A graduate degree was going to be a necessity in order to do anything there as pretty much everyone in the field had, at least, a MS in Network Engineering.

Yet, that path didn’t feel right. Mostly for the following reasons:

  1. I had learnt or was already learning everything at work that I would learn in a Masters program.
  2. I knew I didn’t have enough technical wizardry in me to do anything exceptional as an Engineer.
  3. I knew I couldn’t see myself as an Engineer my entire life.
  4. I knew I always had a good intuition for saving money, juggling costs and benefits (I’m a bit of a miser), figuring out the most practical use of technology in my life as well as being way too passionate, vocally, to be stuck in a cubicle all day.

So, I took the advice of a lot of folks and embarked on a MBA.

Then, a bunch of things happened very quickly that change my life forever. After almost 2 years at Nortel, I realized that the real innovation on the Internet wasn’t the L2/L3 side anymore. The industry was a hollow shell. It didn’t hold the Internet in the same point of view as I did. What’s a guy supposed to do at this point? Pretty much reboot.

So, I got back into volunteering trying to figure it all out again; first over at a Homeless Shelter in San Jose doing a bit of teaching and mentoring and at Mozilla (on a recommendation from a good college friend) to try out another part of the web. Both experiences re-taught me why I cared about the Internet in the first place. Each provided people with an opportunity to better their lives no matter what, where or who they were. Case in point, the kids at the homeless shelter didn’t have the same opportunities due to piss poor luck of being born into those situations. There were smart kids that, if put in a nurturing situation that allowed them to express themselves in constructive ways, could have really had better lives. It reminded me of a lot of things: what my parents forced themselves to go through for a better life for our family, the lack of proper help for friends and family that couldn’t afford living in better areas, the socio-economic disparities in Irvine and it’s surrounding cities and many other thoughts in the same line. It was painfully obvious that I had to do something about this.

So, I helped out in the Mozilla community trying to build my resume to hopefully get a position on the L5-L7 side. Though with some luck, Mozilla had an open position available and wanted me to take it; I grabbed it and haven’t looked back since then. Sure, I was starting a new career in a semi-new industry, while also starting a graduate program that was unrelated to my new job. I continued on anyways and, in the process, learned a whole lot. The past couple of years have really helped provide focus on what I want to do with my MBA. I’ve realized the purpose of an MBA is not to make gobs of money, it’s help to build a toolkit (i.e. nomenclature, learning to be a better enabler, business contacts, etc.) for the future to help create opportunities for myself and others.

My post-MBA goal now is pretty simple. It’s to make the world an easier place to create and foster opportunities on the Internet for those who want to better theirs or others’ lives.

Posted on Jun 25, 2010

Hi, my name is Firefox Input

Mozilla has a new Feedback Add-on in its collection! It’s a high-er touch feedback mechanism intended to funnel in what our users would like to tell us in terms of positive/negative experiences during the Firefox Beta Program. In order to see/use it, you’ll have to get onto a beta build for Firefox 4 (when it’s available) and head over to the right side of your navigation toolbar.

There you’ll see a small suite of options available to offer feedback to the Firefox team. For the purposes of this blog post, we’re going to look at the two options associated to the happy or sad smiley faces.

Feedback Submission

As you click on either of those menu buttons, a feedback submission page will load in a new tab that asks what you specifically like or did not like about browsing on the newest beta version of Firefox. The intention is to help us understand how to make our product better with observations on specific parts of our browser whether they be features, browsing capabilities, security, etc.

On top of that, we added the capability to add a web address that may associated with a piece of negative feedback or issue. The reason for that is to allow us to known what web properties are not only broken while using our build, but could also be enhanced by using our browser. After submission, your feedback is sent to a publicly available dashboard.

Public Dashboard and Search-able Interface

All of the feedback sent in from the submission pages can be seen at http://input.mozilla.com/! On there, we created a dashboard to show how many of our users are adding happy or sad feedback for our beta builds in a variety of different methods. Here’s some highlights:

  • User Sentiment Box: Shows Happy/Sad feedback relative to the total amount of messages received over a period of 1 day/1 week/1 month/all (i.e. entire length of time the beta has been available) and by product and product version.
  • Trends Box: A list of relevant terms that are seen the most on our database over the time interval selected under “User Sentiment”.
  • Demographics Box: Shows Platform and Locale information of the feedback received over the time interval selected under “User Sentiment”.
  • Last 10 Messages: A list of the last 10 messages received. The box dynamically updates every 5 minutes. Each message includes the corresponding Locale and OS associated to it as well as a URL if it’s added.
  • Search: A user can search for terms found within messages or URLs submitted. There’s an advanced search option that allows you to filter by Sentiment, OS, Locale and Date Range.

Finally, Privacy!

This wouldn’t be a true Mozilla Application if we didn’t protect the user from as many privacy violations as we could. Here’s a list of privacy features we’ve implemented in the application:

  • Client-side e-mail blocking
  • Static warning notification on our submission pages
  • Opt-in url submission
  • Ability to change url before submission
  • Server-side web address sanitization
  • Use of https

It was a sweet 4 week development ride for this feature and a ton of thanks needs to go out to Frederic Wenzel for developing the application (his post: “Under the Hood of Firefox Input” can enlighten you on some of the technical challenges he faced), Kevin Brosnan and Jesse Ruderman for throwing up a whole host of bugs during the very short beta process, Mike Beltzner/Alex Faaborg/Alex Limi for their ideas and general UX help and Jono DiCarlo, Jorge Villalobos and Jinghua Zhang for tying the extension portion of this application with the Feedback Add-on. Of course, if you’d like to replicate this application for your own projects, our codebase is open-sourced and available on a GitHub repository!

Posted on Jun 14, 2010

Install/Uninstall Fennec Nightly Builds for Android

Installing Fennec nightly builds for Android is very simple now. There is an automatic updater, so all you need to do is follow the steps below to manually get the new nightlies once and then use the Android system notification bar to update from then on! One note though, if you have a Firefox Beta installed on your device, make sure to uninstall it before installing a nightly build.

To Install
1. Download and install the latest fennec.apk file located on our ftp directory

To Update
1. Open Fennec
2a After 30 seconds to a minute, you should see a Fennec icon in your system notification bar at the top of the screen.
2b. If you don’t see a Fennec icon there, simply go over to “about:fennec” via your URL bar and click on “Check for Updates” within the page. You’ll see the Fennec icon pop up on the bar.
3. Slide open the system notification bar and click on the update notification.

Uninstall:
1. Go to the Applications menu -> Settings -> Applications -> Manage applications -> Fennec.
2. Click on “uninstall”.

Hope that helped!

P.S. Profiles are tied to the downloaded build. If it’s uninstalled, your profile will be uninstalled with it.

Posted on Jun 5, 2010

Introducing the the First Revision of QMO.next

Mozilla QA has been working on rethinking what a new, better QMO would look like and how it will match with the re-organization of our QA organization. From our brain storming session, we concluded the following problems to fix for the new QMO:

  • It was difficult to create content on the site
  • There was no focus to each page
  • Our community couldn’t easily communicate with each other

On an effort to fix these problems, we embarked on a 2 month endeavor to complete that usability refresh of our site. What you see now at quality.mozilla.org is a direct result of that work. There’s many things we’ve accomplished, so take a look below for a quick run down of the new QMO. Otherwise, the easiest way to find out about our new features is to simply go to http://quality.mozilla.org and check it out for yourself!

WordPress CMS

Raymond Etornam suggested we move over to the site and tested the platform’s ability to work with our own content structure. We not only found a great match and a much simpler solution, but we found such a great set of plugins that really gave QMO the abilities that we had been longing from Drupal for quite some time. We added a welcome video and more dynamic sidebar elements such as Related Docs, category-biased blog posts and more.

New Teams

We now have a one-to-one mapping to each group within our QA organization. Originally, we listed teams as rolling projects which were hard to maintain, define and follow up with. Not so anymore, each team created on our page will have a lead associated to it who is in charge of maintaining that page and funneling through new community members. On top of that, our sidebar snippets are populated with categorized content from the rest of the site, so users don’t have to go anywhere else to find out what’s the latest in the team that they’re interested in reading about.

Simpler Docs Tree

Instead of showing a persistent docs tree to the right of each document. We cut out the third column and gave the documents some more room to breath and made the experience of traversing the chapters of each section easier.

A Planet QA

We created a feed reader from blogs (and tweets!) from a great group of contributors within Mozilla Corp and especially within our QA Community.