2010 will be a big year for Thunderbird. Last year, we launched Thunderbird 3, which is a huge milestone for us. In this post, I’d like to give people a heads-up as to what the coming year will look like. I’ll focus on three topics: our plans for innovation through add-ons, Thunderbird 3.1, and our first steps towards making Thunderbird self-sustaining.
Innovation through Add-ons
We believe that Thunderbird is a much better development platform than ever. This means that building innovative experiences on top of Thunderbird is easier than ever. We’ll be building on that platform ourselves and helping others innovate as well. In particular, we’re going to be using add-ons in a few ways:
- If we have an idea for a change to an existing Thunderbird feature, we’d like to roll it out first as an add-on, so that we can get feedback on early versions of the idea without having to incur all of the up-front costs of landing that change into the “trunk” builds. This should allow us to validate (or reject) ideas much faster. A great example of how this can work is the Personas feature, which matured as an add-on, and is now a standard (and awesome) feature of Firefox 3.6.
- We sometimes think of features that “would be cool” (see e.g. conversation arcs, tagsoup), but don’t necessarily make sense to integrate into the core product. Making an add-on here makes sense because it lets us share those ideas with others who think they’re worthwhile. Sometimes “cool ideas” become “big ideas” over time (google calendar add-on.
Having core engineers develop add-ons is also one of the best ways to ensure that the add-on platform is as good as possible.
In parallel with some exciting innovations in add-ons, we’ll be pursuing more gradual change strategies within Thunderbird 3 itself.
Thunderbird 3.0 is getting security & bugfix releases (3.0.1 is out, 3.0.2 is coming soon).
Thunderbird 3.1 is also underway. We’ve already released the first alpha, and a first beta is getting defined. It will be focused on a couple of areas:
- Making the upgrade from Thunderbird 2 as painless as possible: Some of the features that we introduced in 3.0 were confusing to Thunderbird 2 users, and some of the defaults which we think made sense to new users were quite surprising to long-term Thunderbird users. We’re reviewing the upgrade process and making sure that users get to opt-in to the more radical changes. We realize it can be quite unpleasant to have your software change unexpectedly.
- Improving some of the new features in Thunderbird 3: The feedback for the new features has been both positive and constructive — look for refinements on the concepts introduced in Thunderbird 3.
Ensuring Economic Sustainability
Thunderbird deserves to be self-sustaining. Paying one’s way is a great validation of any effort, and it’s in the interest of Thunderbird users everywhere that we figure out a way to get there. As promised when we formed Mozilla Messaging, we’re starting to explore ways to make Thunderbird self-sustaining while at the same time promoting the Mozilla mission (as articulated by the Mozilla Manifesto). We’re specifically looking to identify business models that create economic value by improving the user experience of Thunderbird users. This is nothing new for Mozilla. The foundations of an open source codebase, the ability for users to opt-out of commercial relationships, and an architecture that allows plugging in alternative providers for whatever service or product we end up partnering with are non-negotiable requirements. With that as a foundation, we’re looking for ways to make the online life of our users better, and within those ways, identifying those which can help ensure Thunderbird’s long life.
This will happen through a set of public opt-in experiments. For each business model that we try, we’ll build a prototype, announce it, get data to evaluate it, solicit feedback from users, and evaluate whether it’s worth continuing. Anecdotal data suggests that plenty of Thunderbird users are happy to be offered commercial services which provide them value and help Mozilla too.
In addition, I’ll be actively soliciting input and help from what I’d like to call “business contributors”. Just like we encourage programmers and others to contributing to Mozilla through patches and other internet-mediated activities, I’m going to setup ways to “open source” the business model and business development activities. I’ve found in conversations with my peers that almost every business leader who’s aware of what we do would like to contribute, but we haven’t made it easy. Identifying and facilitating such contributions is one of my personal goals for the year.
To start, here are two possible ways for business folks to contribute:
- I’ll be in the Bay Area next week for a panel at MAAWG in San Francisco and other meetings, and will be organizing a dinner/drinks event for people who want to chat about Mozilla Messaging business models. Contact me by email if you’re interested (dascher at mozillamessaging.com).
- We’re hiring a business development lead to help drive this effort. If you know someone who you think understands business development and would be a great fit for Mozilla, point them to the job description.
I’m looking forward to the conversations!