aakashd

The Mozilla project has grown to support many products and projects over the past year: Firefox (Desktop and Mobile), Thunderbird, Boot2Gecko, Apps and Identity. These products arrived in quick succession making it difficult to organize, grow, and direct the project’s communities to support them. To ramp-up our organically-created and modestly-supported community to meet the needs of this situation, the Engagement and People teams have begun driving an initiative called “Grow Mozilla”. It aims to build, develop and enable a global community of paid and volunteer Mozillians to propel our mission and build great products for the web.

Both teams are doing great work in building programs that helps to on-board new contributors, retain them and develop them to become leaders. We’re becoming more organized in how we approach contributor engagement. The Mozilla Reps and Stewards programs have robust infrastructure and people in place to help on-ramp and advise Mozillians at a level we haven’t had before. Contributors are finding people responding to their inquiries to get involved and being directed to tasks available via many of our functional areas.

I think we can do better. For the thousands of requests we receive to get involved per month, about 20 end up as contributors. Further, these Stewards and Reps have limited tools at their disposal that come standard in many community-based organizations: they don’t know who does what, how much they do it or when they do it across all of our communities. We need to do more to help grow our community’s size and involvement that can propel our mission to support our current and future endeavors.

How do we do this?

We can’t manage what we don’t know. We currently have un-organized on-ramps with many obstacles to get involved across the project. Further, many of our communities do not have access to tools to share contributor activity, achievements, and privileges.

For 2012, we plan to build tools and platforms that add that necessary layer of abstraction that augment our current community platforms, programs and product pages to support Mozilla’s ability to on-ramp, retain and easily organize contributors in the Mozilla Project.

12-Month Goals

• Getting involved in the Mozilla project only takes 2-steps from any place in our community.
• Mozillians will be able to know what and how they’re contributing to the project.
• Mozillians will be able to recognize and reward someone’s contributions to the project in real-time.
• Community Managers will be able to track and measure the effectiveness of their communities.

Tools & Platforms

1. Phonebook: A platform to share, identify and communicate with Mozillians in our community. Active/Core Mozillians will be able to use their profile as a resume and passport for who they are and what they do in our community. For Reps & Stewards, they’ll be able to better manage and show-off who is in their communities. New/potential contributors that come across it will be served up ways to get involved.
2. TaskBoard: A platform to uplift and share all contributor-facing tasks in our community into one easy to find app. It will act as the basis for contributors to easily find (2-steps!) a task or job available to finish in the project. The app will help Mozillians increase participation across their projects, areas and teams by offering ways to embed relevant tasks on any on-ramp across the community.
3. Events Manager: A platform to uplift and share all contributor-facing events in our community into one easy to find app. It’s purpose is for contributors to easily find and participate in any event happening in our community anywhere in the world at any given time.

Looking Forward

If we are successful, the community will feel like an expansive, closely-knit swarm of individuals dedicated toward bettering the Web. Specifically, Mozillians will be able to know who, where and what volunteers are doing around the project. Community managers will know how much and where contributors are participating in the community, measure the efficiency and effectiveness of that involvement as well as who should be rewarded for it in real-time. For contributors, they’ll be able to improve their professional skills and feel a part of a global movement in bettering the Internet.

Note: To learn more about “Grow Mozilla”, there will be a brownbag hosted by the Contributor Engagement team on Monday, 3/26 at 2pm Pacific, and another specific to the Community Tools & Platforms Roadmap for 2012 on April 3rd at 12pm Pacific as well. Both will be available on Air Mozilla.

When I first proposed a plan for what we’re now calling the Community Tools & Platforms initiative, there were a lot of issues that we needed to solve in the Mozilla community. Contributors couldn’t easily find ways to get involved in our community. The organization and community didn’t know who or how many Mozillians were in our community and what they did within it. Though, as we got deeper into analyzing the situation, it was worse than that. We simply couldn’t get bootstrapped into determining how to set strategy. The priorities were fuzzy. A few times the priority was contributor-focused to allow social networks to be created; other times an all-in-one Community CRM solution. Yet, none of these were ever finalized; our Community Managers were left with little help build their programs. In my opinion, the biggest problem to solve for a an initial Phonebook release was to simply just get bootstrapped.

A product goal like getting to a “.1″ or prototype stage is generally an odd one; especially for those with such an extensive history. You can’t really call it a product because it’s in such an infant stage of what it will become. Time and communication are far from perfect. Very useful features need to be ruthlessly cut and the “product” ends up not as useful as users expect it to be.

Don’t get me wrong, there’s no doubt in my mind that the community phonebook helped Mozilla, as an organization, get a lot of necessary data about our community (specifically our core and active contributors). On the other hand, we ended up delivering a webapp that was rather confusing to a large set out of userbase (e.g. non-vouched users), lacked features and was rather buggy. We’re getting past the haze now and look to fix a lot of these issues very soon and I’m freaking excited about its prospects of what we have planned. Mozillians are going to start seeing the application get a whole lot better in a hurry.

So, how? To do this, we’ve stripped our understanding of the Phonebook’s current strategy (i.e. one focused more internally and towards active/core contributors). It’s being re-jigged towards one that is more new/potential contributor focused and about growing our community from where it is now. This will mean a lot of changes on the app front. Namely:

1. Completely Overhauling the User Experience on the Phonebook: We’re starting from scratch for the user experience of the site and building from new/potential contributor focused and up. The biggest change will include a easier flow for new/potential contributors connecting Mozilla Stewards and Reps with new/potential contributors signing up to the site and in a non-vouched state. The other big change will be moving to connect.mozilla.org and away from Mozillians.org.
2. Contributor Web Services: We’re planning to build web services that help mozilla.org properties and contributors alike. We’ll allow for simpler authentication/authorization of contributors (with the help of BrowserId). Further, we want to make it simple to auto-populate Mozillian Phonebook profile data onto any mozilla.org site account. The ultimate goal is to be insanely easy to get around the community with as little work as possible.
3. Recognition for your Contributions and Involvement: The one cool we’re looking to do by the end of 2012 is to show the amount of contributions you’ve performed around the Mozilla project (and find partners such as LinkedIn to plug-in to with that data). Display recommendations made by other Mozillians! Link to your Linkedin profile.
4. Public Profiles: Phonebook users are going to get a whole lot of control over the publicity of their profile. Our end goal is going to be allowing folks to show their profiles publicly and show off their contributions to Mozilla.
5. More Ways to Find and Contact Mozillians: Expect additions to profiles such as Location & timezones, Multiple e-mail addresses on profiles and many other things!

I seriously can’t wait for these changes to land during the course of the year. There’s going to rainbows, unicorns and nyan cats and everyone should be ecstatic for those possibilities on what this means. We’re going to kill it in 2012.

Hello, Mozilla Community!

I am proud to announce Mozillians.org has re-worked it’s login and registration flow using BrowserId. You’ll need to register an account with the new service Browserid.org and add your primary e-mail address used for Mozillians.org onto the account there. for more details and a step-by-step walkthrough of how to sign-in and/or register, make sure to read through BrowserId’s about page.

For those users who aren’t sure why we did it, here’s some context on why we did it and what its been replaced with:

Mozillians.org, a community directory, required a login and password in order to register and log-in to the site. That’s not really a problem, right? Actually, not true. One of the things you learn after use using more than a single site in our community is that we’re pretty bad at identity management in general. We end up using different services not knowing how each is connected to the other and end up many different username and passwords for a lot of services that all should be tied to a single identity (i.e. you, as a Mozillian).

That’s terrible. Mozillians shouldn’t have to accidentally manage their way into multiple identity hell when its unnecessary. It becomes painful to move around the community as a contributor. What’s the benefit of having multiple accounts, each with a different password, yet all within the same public-benefit organization?

Thankfully, Mozilla is already working on fixing a superset of this problem; of which can be applied here using their first solution called BrowserId. Rather than have too many accounts with different Mozilla web sites, users need only one BrowserID account, which will let them partake in any site they choose at Mozilla. This helps the phonebook’s aims as we’re looking to develop web services and APIs that help make it as easy and simple as possible for contributors to move around and help contribute around the project too.

So, without further ado, please take go to Mozilla’s favorite community directory and log-in using BrowserId!

For a list of bugs fixed in this release, please take a look at our Bugzilla query.

A big thank you to tofumatt, ozten, ednapiranha, cbeasley, davedash, badida, lloyd, Jason, Jabba, mbrandt, rbillings and Milos for their fantastic contributions and making this release a success!

P.S. I know location was mentioned as a feature for this release, but we’re holding off on it due to the holidays. It will be out shortly.

Hello there, Mozilla Community!

When Mozillians.org (i.e. Phonebook 1.0) went live last month, we offered a way for Mozillians find each other through a simple directory application. It had a minimal set of features and what we were looking for was a way to determine how many Mozillians were in our overall community as well as how to make it easy to find anyone in the community. One of the major problems we face is that its still hard to find Mozillians within specific sub-communities and groups. Well, Mozillians.org 1.1 aims to fix that particular problem.

The team has landed a new major feature called “Groups” where Mozillians can list themselves as part of specific sub-communities such as “Quality Assurance” or “Firefox”. Here’s an example of my profile:

Also, vouched Mozillians will be able to search for who and how many contributors list themselves as a part of specific groups [1]. So, what can do you with this new feature? Well, here’s a small list of useful use cases:

• Find the contact e-mails for Mozillians within a specific group for closer communications within other active/core set of contributors.
• Put a face and name to a IRC handle to all the folks that seem to hang around your team or project’s channel.
• Get to know a little more about the details of each contributor within your sub-community in their bios!

For you Mozillians out there who want to host a Testday in the QA community, a SUMO day in Support or even mix and match contributors from separate sub-communities (but not spam everyone), this’ll will help save a lot of time and effort to get that information! So, go to the “Edit Profile” page after logging-in to Mozillians.org and help yourself and the Mozilla project to better communicate with each other!

Major Features

• Tag Yourself to Groups – Mozillians can now add themselves and search for other Mozillians within groups/sub-communities that are known and unknown. To use it, simply go to the “Edit Profile” and add/remove groups on the bottom left of the edit panel.
• Search via Firefox – Ever met a Mozillian at an Event or on a Mozilla IRC channel, but didn’t know who they were or what they worked on? Well, we made the act of searching for a Mozillian even easier with a Firefox Search plugin! To find it, go to Mozillians.org and add it via the Firefox search plugin drop down list. A special thank you to Antoine Turmel and Leslie Orchard for this completely contributor-made feature!

For a list of bugs fixed in this release, please take a look at our Bugzilla query.

A big thank you to tofumatt, malexis, ednapiranha, lorchard, davedash, Andrew Findlay, Tobbi, stephend, mbrandt, Jason and Milos for their fantastic contributions and making this release a success!

We’re looking to add in Location information to Mozillian profiles and have BrowserID hooked up with Mozillians.org next. There’s plenty more things we want to do after that though. So, if you’re interested in following what the team is planning to work on, take a look at our roadmap, planned releases and how to contact us (or get involved!).

[1] There are two caveats in this release: Phonebook users can only perform a search for a single group per search in this release. Also, searches within groups with more than 20 Mozillians will only show the first 20 Mozillians in that group.

Firefox Input currently offers a set of feedback options that have a very low-bar to submission, anonymity and constraints that help frame feedback into actionable items. One of the drawbacks of such an approach is the loss of detailed information (ala a bug report) and a point of contact to further investigate the issue. Well, we’ve seen this in the wild: we have seen our Nightly and Aurora users, who comprise of early adopters, submit bug reports disguised as feedback submission even though they should be filing a bug.

To fix this issue, the Input team is building a method to supplement the sad feedback form with an option for Firefox Nightly and Aurora users to submit a bug report into Mozilla’s bug tracking system. We believe the lasting benefits of such a tool will garner greater contributor participation in the project and Bugzilla as well as improve efforts to find Firefox bugs before they get into the Beta and Release channels.

How will it Work?

Firefox users on Nightly and Aurora builds who go to submit a piece of sad feedback on input.mozilla.com will be able to click a button on the form that will direct them to a simplified bug reporting form. On completion of that form, the service will file a bug onto bugzilla.mozilla.org after a simple e-mail validation step.

How will this change things in Bugzilla?

• Bugzilla user accounts will be created, if not found in Bugzilla, after their e-mail address is verified.
• Bugs filed into a new Product called “Un-Triaged Bugs” with Component, “Firefox”.

Some of you may have seen Mozilla QA contributor Tyler Downer’s blog post on the current state of the triage system and we’ve been chatting to see how efforts could be better. We hope this will lead to a cleaner triage system in Bugzilla and will closely view the component when this app does release to ensure that happens.

How can you Help?

We’ll need eyes on these bugs in order to triage into their proper products and components. If you’d like to learn more on how you can help, please visit #qa or #input on irc.mozilla.org and chat with the folks there in regards to bug triage (#qa) or delivering this app (#input).

When can you expect it out?

We are looking to release this by the end of the 2011 calendar year. If you feel you can help with this effort in terms of code contribution to help release this earlier, feel free to head over to #input on irc.mozilla.org and mention so!