aakashd

QMO has always had a lot of potential, but its always been a little bit lacking. We have always understood it is a community site that allowed our new and old community members to get more information about opportunities within our sphere of work, but nothing much past that. There were ideas, but no real cohesive strategy or vision about what it should have been and how it made Mozilla’s products better. It’s a whole lot cleaner and simpler than what it was previous, it’s also a very static site that doesn’t get updated as much as it should, provide a low bar to join our community and identify the people within the QA community that are really doing some good for the Mozilla project (and the Internet as a whole). So, Al Billings and I have been churning through ideas and plans on how to fix this and make it something that our community is really proud to be a part of. Here’s the mission and roadmap we’ve come up with and plan to execute:

Mission

* To become the source of updates and activity within QA’s teams and community members
* To identify and elevate the level of involvement of QA community members

How We’ll Get There

QMO 3.0

Purpose: Lower the bar for users to interact with the QA community and offer a method to better identify themselves within it.
Desired Results:
* Team Forums
* User accounts

QMO 3.5

Purpose: Add support for a reward system onto quality.mozilla.org that will help build growth and strengthen retention of community.
Desired Results:
* Reward system for users
* Team blogs

QMO 4.0

Purpose: Integrate statistics from Bugzilla on a per-user basis to better identify community member involvement around quality-related tasks.
Desired Results:
* Relevant Bugzilla statistics related to users and teams are exposed on their home pages
* Support for surveys within blogposts
* Users can join events
* Localization of static content

QMO 4.1

Purpose: Integrate statistics from automation efforts on per-user basis to better identify community member involvement around “pushes” for the Automation team.
Desired Results:
* Relevant Mercurial/GitHub statistics related to users and teams are exposed on their home pages
* Community moderation support

QMO 4.2

Purpose: Integrate statistics from our next-generation Test Case Manager to identify community member involvement around testcases ran, failed and invalidated.
Desired Results:
* Relevant TCM statistics related to users and teams are exposed on their home pages

There’s not too much to mention this time around. Input 1.9 was mostly to round out all of the dashboard’s features (i.e. Themes and Sites) for Mobile Firefox feedback as well as fix some security bugs before moving on to Input 2.0. Thanks again to Chris Howse, Frederic Wenzel, Dave Dash, Ryan Snyder, Michael Kurze, Stephen Donner and Justin Dow for making this happen.

Total List of Features

• Product Differentiation on Themes
• Product Differentiation on Sites
• Support for the “Submit Feedback” Firefox menu button

Finally, here’s a list of bugs fixed in this release.

The Input team ( i.e. the people behind input.mozilla.com ) definitely feel like we’re not getting the most bang for our buck in terms of the messages we have in our database. It’s pretty much the only publicly accessible database of user feedback on a major piece of software out there and we’re only processing the data through one form of text clustering. So, we’d like to break the bank here and get a slew of questions people would like to have answered (that makes our software/product better) with this data.

How can you offer us your questions? You can comment on this blogpost with the following format:

• Question you’d like answered:
• Why you’d like an answer to that question:
• How that answer would help make Firefox/Mobile Firefox better:
• BONUS – Suggested algorithms you’d like to see implemented to answer that question:

Some Inspiration:

• How do users commonly name features of Firefox?
• How happy/sad are messages submitted within the happy/sad forms?
• Is there a distinction in sentiment between messages sent with or without URLs across the happy/sad forms?
• How many users offer Input a message in another language, but on an en-US build, when there are no other locales available?

“Shh! And the best part is that he’s learning.” – Krieger, Archer

Input is now ready to go for Mobile Firefox Betas! If you want to see the system on the best open Mobile Browser in the world, look for the happy/sad buttons within the “β” pane in your browser controls once Beta 1 is out (Note: it’ll only be available on Maemo for Beta 1, but will also be on Android starting in Beta 2). Other notables in this release are a new Mobile Input Dashboard only for Mobile Firefox feedback (right now) and the ability to differentiate between products on the original Input Dashboard. A large thanks should go to Chris Howse, Frederic Wenzel, Dave Dash, Ryan Snyder, Michael Kurze, Stephen Donner and Shyam Mani for making this happen.

Total List of Features

• Input on Mobile Firefox
• Mobile Dashboard
• Messages Snippet shows total messages over the current beta
• Product Differentiation on “Feedback” page of our Desktop Dashboard
• Platform Differentiation on Sites

Finally, here’s a list of bugs fixed in this release.

As planned-out as we were for the destinations on our way to Seattle, we were just as much un-organized for the final destination. We started out at the visitor’s center (i.e. Seattle Visitor’s and Convention Bureau) which was hosting the Penny Arcade 2010 Expo at the time. Thankfully, it wasn’t hard to into the convention’s lobby and get some vital information toward Pike Place, the Space Needle and other such touristy areas. Though both tourist spots were like any other regular tourist spot: pricy and over-glamorized, they did open up the opportunity for several really great scenic and people-watching pictures around the 1st Starbucks, downtown Seattle, and the food/flower market.

After that, we ate some fantastic brunch at Tillikum Cafe. The egg and potato plate I got was particularly great. It came with seasoned eggs with some light cilantro, the potatoes were crisped, the ketchup was home-made, a thin sausage pattie, sun-dried tomato pesto on the side and italian bread. The next time I’m in Seattle, this is definitely going to be a stop.

The rest of the day consisted of going to the highest point in Seattle, the Columbia Center. Unfortunately, as the tourists we are, we ended up in the wrong building (trust me its confusing as it’s part of a number of buildings connected together!). Though the shots still ended up great of Qwest Field.

Lastly, don’t go to Aura nightclub.