Announcing Raindrop

Standard

I’m thrilled to announce that we launched Raindrop today.  Raindrop is Mozilla Messaging’s experiment in messaging on the open web, hosted by Mozilla Labs.  You should definitely go over to the introductory post, and check out the first few pages we’ve put up describing the goal of the project, how we’ve built it so far, and how we’re hoping to engage designers as well as developers to participate in the ongoing effort.

It’s going to be fun to have both an experimental platform for next-generation experiments on messaging, which leverages the web of the future, as well as a Thunderbird client which provides both an awesome desktop experience today, and lets more people build interesting, fun, and useful add-ons as well.

I want to make sure to express my thanks to everyone who contributed to Raindrop thus far: Andrew Sutherland who did some initial experiments a long time ago; Chris Anderson, Jan Lenhardt, and Damien Katz of the CouchDB project, who’ve been super helpful in helping us understand their awesome database; Bryan Clark, who’se done a great job juggling Thunderbird and Raindrop design leadership; Mark Hammond, who took Andrew’s original draft and built a great backend infrastructure (it’s great to work with Mark again!); James Burke, for whom no UI requirement is too much; Andy Chung, who makes everyone else look great; and Chris Beard, Myk Melez and Pascal Finette, of Mozilla Labs, for their advice, hosting, and feedback.

2010 will be amazing.

Lightning Update

Standard

A week full of announcements:

I’ve been so busy working on the Thunderbird 3 release that I forgot to blog about this new development:  I’m pleased to announce that Mozilla Messaging has engaged Philipp Kewisch, lead of the Calendar project, to help drive the release of a version of the popular Lightning calendar add-on.  The plan so far is for Philipp (who’se in school, but somehow finds time to do Mozilla work after that) to help fix bugs, drive the release, and generally make sure that people who want to upgrade from Thunderbird 2 to Thunderbird 3 will find their favorite extension working there.

If you’re keen to help, let Philipp know, and participate in test days, help QA release candidates that will show up, and if you can, chip in with patches!

An update on Thunderbird’s support plan, Get Satisfaction and SUMO

Standard

Since my last blog post about a position being available for support, I’m pleased to announce (belatedly) that we’ve hired Roland Tanglao to lead Mozilla Messaging support. It’s not obvious being the only person on staff supporting millions of users around the world!  In order to learn how Thunderbird support is currently happening, he’s been busy immersing himself in that world.

Success for anything user-facing on the scale of Mozilla Thunderbird requires scalable approaches.  One person, no matter how well qualified and efficient, can’t help everyone who may have issues (especially as many people come to us with questions that are really about their mail provider).  So we need to look to systems and communities to help us help users.

Get Satisfaction

The first system that we’ve committed to is Get Satisfaction, an online website which is designed from the ground up for peer-to-peer support.  You go there to ask a question, and maybe you also help someone else who has a question you know the answer to.  The “take a penny, leave a penny” model.

There are two things that stand out for me with Get Satisfaction: their user experience, and their APIs:

Get Satisfaction clearly thought long and hard about what the user experience of a support site should be like, and it shows: Threads are categorized as being ideas, problems, and praise, and problems and idea threads can be marked appropriately when either there’s an solid answer of some sort, or to track the evolution of ideas.  This provides people who want to dive into a support role with great dashboards, which makes dealing with a high volume much easier.  It also provides users a way to communicate their input & mood effectively, which is an important part of a support interaction.

The second aspect of Get Satisfaction that was particularly compelling to me was that they have built their system with HTTP APIs in mind from the beginning.  This means that we can integrate it into our own websites, or even in future versions of Thunderbird, without anyone needing to rework the database.  We’re just starting to figure out how to use these APIs, but I’m hopeful it will allow us to streamline support interactions considerably.

You can find out more about Roland’s thoughts about Get Satisfaction in his blog post.

Knowledge Base

Even as we’re happy with the capabilities of Get Satisfaction, it’s clear we need to complement it with a knowledge base where we can build longer FAQs, helpful documents, etc. There, we got an unexpected assist from the Fennec (Mobile Firefox) project, as their need for a variant of SUMO for Mobile users made it so that the SUMO project had to refactor and “productize” SUMO.  Having more than one installation of SUMO supported by the core SUMO team made me feel that our use cases were likely to be supported well, which is great — we try to leverage as much of the Firefox infrastructure as we can, as efficiently as we can.  Thanks Fennec!  (For now, we’ll stick with Get Satisfaction, and won’t be using the SUMO forums or the Live Chat features).

SUMO will allow us to build a scalable, localizable document store — it’s been proven to scale (handling 22 million hits a day for Firefox!), and has a built-in localization system.  Given that Thunderbird 3 will likely be published in 40 languages, ignoring localization isn’t a realistic option.  (I should point out that while GetSatisfaction is currently only in English, that team is keen to explore internationalization and localization).

For English users, MozillaZine is the obvious alternative to both Get Satisfaction and SUMO.  And indeed MozillaZine currently has lots of great content, and a bunch of people who provide great support.  Unfortunately, it also lacks a bunch of features (APIs and RSS feeds), has an interface which we can’t improve upon, and is English-only.  An interesting observation is that with people relying on search engines ever more, it’s not really a problem to have multiple sources of information about a product.  I expect MozillaZine will continue to thrive, and we’ll definitely continue to work with the all existing knowledge bases on the web and link to them appropriately.

A web of communities

Going forward one of Roland’s tasks is to build or strengthen the bridges between Mozilla Messaging and the excellent Thunderbird related communities on the web. Mozillazine, of course, but also geckozone in France, and as many other support communities we can find.  Around the time of Thunderbird 3 launch (hopefully in November), Roland is planning some sort of worldwide support community online meeting. If you’re interested in participating, contact Roland.

One of my hopes is that better organization of support communities can lead not just to happier users, but to a better product.  One of Roland’s duties is to provide feedback to the product development team on frequent or emerging issues faced by users, or areas of Thunderbird that particularly please people.  That’s not something he can summarize accurately by himself — he’ll need your help.

Positive Feedback

Support is too often a one-way medium, with users complaining about problems.  That’s certainly an important function, but in a cooperative open source project, it’s equally critical that QA and developer contributors thank users for their input, and that users point out parts of the experience that they like, as positive feedback is the best motivator.  So take some time out and pick an open source project and generate some good karma!  For Thunderbird, it’s easy, go to getsatisfaction and click on “give praise”.  Roland will make sure that the people deserving of your praise get to see it.

An update on Thunderbird's support plan, Get Satisfaction and SUMO

Standard

Since my last blog post about a position being available for support, I’m pleased to announce (belatedly) that we’ve hired Roland Tanglao to lead Mozilla Messaging support. It’s not obvious being the only person on staff supporting millions of users around the world!  In order to learn how Thunderbird support is currently happening, he’s been busy immersing himself in that world.

Success for anything user-facing on the scale of Mozilla Thunderbird requires scalable approaches.  One person, no matter how well qualified and efficient, can’t help everyone who may have issues (especially as many people come to us with questions that are really about their mail provider).  So we need to look to systems and communities to help us help users.

Get Satisfaction

The first system that we’ve committed to is Get Satisfaction, an online website which is designed from the ground up for peer-to-peer support.  You go there to ask a question, and maybe you also help someone else who has a question you know the answer to.  The “take a penny, leave a penny” model.

There are two things that stand out for me with Get Satisfaction: their user experience, and their APIs:

Get Satisfaction clearly thought long and hard about what the user experience of a support site should be like, and it shows: Threads are categorized as being ideas, problems, and praise, and problems and idea threads can be marked appropriately when either there’s an solid answer of some sort, or to track the evolution of ideas.  This provides people who want to dive into a support role with great dashboards, which makes dealing with a high volume much easier.  It also provides users a way to communicate their input & mood effectively, which is an important part of a support interaction.

The second aspect of Get Satisfaction that was particularly compelling to me was that they have built their system with HTTP APIs in mind from the beginning.  This means that we can integrate it into our own websites, or even in future versions of Thunderbird, without anyone needing to rework the database.  We’re just starting to figure out how to use these APIs, but I’m hopeful it will allow us to streamline support interactions considerably.

You can find out more about Roland’s thoughts about Get Satisfaction in his blog post.

Knowledge Base

Even as we’re happy with the capabilities of Get Satisfaction, it’s clear we need to complement it with a knowledge base where we can build longer FAQs, helpful documents, etc. There, we got an unexpected assist from the Fennec (Mobile Firefox) project, as their need for a variant of SUMO for Mobile users made it so that the SUMO project had to refactor and “productize” SUMO.  Having more than one installation of SUMO supported by the core SUMO team made me feel that our use cases were likely to be supported well, which is great — we try to leverage as much of the Firefox infrastructure as we can, as efficiently as we can.  Thanks Fennec!  (For now, we’ll stick with Get Satisfaction, and won’t be using the SUMO forums or the Live Chat features).

SUMO will allow us to build a scalable, localizable document store — it’s been proven to scale (handling 22 million hits a day for Firefox!), and has a built-in localization system.  Given that Thunderbird 3 will likely be published in 40 languages, ignoring localization isn’t a realistic option.  (I should point out that while GetSatisfaction is currently only in English, that team is keen to explore internationalization and localization).

For English users, MozillaZine is the obvious alternative to both Get Satisfaction and SUMO.  And indeed MozillaZine currently has lots of great content, and a bunch of people who provide great support.  Unfortunately, it also lacks a bunch of features (APIs and RSS feeds), has an interface which we can’t improve upon, and is English-only.  An interesting observation is that with people relying on search engines ever more, it’s not really a problem to have multiple sources of information about a product.  I expect MozillaZine will continue to thrive, and we’ll definitely continue to work with the all existing knowledge bases on the web and link to them appropriately.

A web of communities

Going forward one of Roland’s tasks is to build or strengthen the bridges between Mozilla Messaging and the excellent Thunderbird related communities on the web. Mozillazine, of course, but also geckozone in France, and as many other support communities we can find.  Around the time of Thunderbird 3 launch (hopefully in November), Roland is planning some sort of worldwide support community online meeting. If you’re interested in participating, contact Roland.

One of my hopes is that better organization of support communities can lead not just to happier users, but to a better product.  One of Roland’s duties is to provide feedback to the product development team on frequent or emerging issues faced by users, or areas of Thunderbird that particularly please people.  That’s not something he can summarize accurately by himself — he’ll need your help.

Positive Feedback

Support is too often a one-way medium, with users complaining about problems.  That’s certainly an important function, but in a cooperative open source project, it’s equally critical that QA and developer contributors thank users for their input, and that users point out parts of the experience that they like, as positive feedback is the best motivator.  So take some time out and pick an open source project and generate some good karma!  For Thunderbird, it’s easy, go to getsatisfaction and click on “give praise”.  Roland will make sure that the people deserving of your praise get to see it.