In early September we invited the wider community to develop concepts for the question “Visualizing your browser data – How can we provide intuitive and useful visual representations of your browser data (such as bookmarks, history, tabs, stored credentials etc.) on a web page?”

A total of 17 solutions were submitted in the first phase of the Design Challenge and analyzed by the Weave team. After an long round of discussion and carefully going through all submissions, the Weave team decided to return to the drawing board and better clarify the experiences Weave wants to enable, instead of moving this challenge to the second phase. The submissions significantly helped the team to identify potential interaction models and design directions.

The submitted concepts were (in order of submission date):
Luciano Lobato, Sridutt YS, David Little, Eshed Zachevsky, Shubham Sinha, Ely S, Silvio Fachinotti, Anil Chaudhry, Miyoung Yoon, Vijaya Ramanujam, J Newengland, Brennan Moore, Murray Thompson, Scott Fitchet, Maureen Hanratty, a mal.

You can view all entries with short explanations of the respective concept on the ChallengePost website.

Read more here!

- Suneel Gupta & Myk Melez on behalf of the Personas development team

What Has Changed?

Since Personas was launched earlier this year, over 10 million people around the globe have chosen to personalize their Firefox by downloading Personas. Here is a quick look at what else has happened since the launch:

• Nearly 35,000 designs were contributed from artists at all levels of experience from all parts of the world (over 1,000 designs / week).
• Over 450 community members have shared ideas and feedback on the Personas forum.
• Nearly 40 affinity brands, including Harry Potter, Bob Marley, Lady Gaga, and Greenpeace have added their content to the gallery.
• Using community feedback, the Personas development team has released 13 upgrades (4 add-on, 9 website releases) in order to add features like Favorites.
• Localization community has diligently translated the add-on into over 25 languages; Personas website will be localized by the end of the year.

Thanks!

Like all Mozilla projects, Personas is a collaboration between people who develop the product and people who use it. The following people (and many more) have been commited to this product’s success:

• NinaBella, Digital Blasphemy, MaDonna, and thousands of other artists around the globe that give millions of Firefox browsers a personalized look and feel. They are the heroes of this project.
• Shae Rivard, who has supported the resolution of over 200 issues on the Personas discussion forum, as well as over 450 other members, whose feedback, testing, and contributions continuously make the product better.
• Ryan Doherty, Myk Melez, Toby Elliot, and Zandr Milewski, with the support of Erik van Eykelen, and Jose Bolanos, for collaborating with community feedback to constantly improve on the product. Collaboratively, the development team has fixed over 300 issues since launch.
• Carsten Book (a.k.a. Tomcat), Stephen Donner, Tony Chung, Krupa Raj, and Vishal Kamdar, for assuring quality releases, and for doing so within incredibly tight deadlines.
• Amy Zehren, Sean Martell, Catherine Brady, and Julie Martin, with the support of Monique Johnson, who have reached out to countless brands around the globe to share the Mozilla story, and offer them the opportunity to participate in a growing movement.
• Tara Shahian, Mary Colvig, Melissa Shapiro, John Slater, Sarah Doherty, Jay Patel, and all the other members of the marketing community that helped build awareness around Personas.
• Seth Bindernagel, Staś Małolepszy, Pascal Chevrel, and all the Persona localizers on Babelzilla (AtteL, dogi, drry, Ersen Yoldac, fernph, Funkin2x, funTomas, Joergen, jojaba, jooliaan, kkemenczy, kustodian, Lisman, lois, loveleeyoungae, moZes, pia, SiiiE, spjutster, steekid, stoyan, Wareczek, and wtspout), who worked diligently to ensure that Personas is accessible in as many languages as possible.
• Rainer Cvillink who, on a shoestring budget, imaginatively developed the original Personas video:

Getting Started with Personas from Mozilla Labs on Vimeo.

What’s Next?

Between now and 20 million downloads, we’re looking to make this feature even better and easier to use. To continue to evolve Personas quickly, and in the right direction, we need your feedback and participation. Join the conversation in the discussion forum and add helpful hints to the support wiki. And stay tuned to this blog for updates!

- Suneel Gupta & Myk Melez on behalf of the Personas development team

With feedback from the Personas community, Labs recently released Personas 1.4. Watch the video below or go to the Personas blog for a detailed look at newly added features.

Introducing Personas 1.4 from Mozilla Labs on Vimeo.

- Suneel Gupta and Myk Melez on behalf of the Personas development team

Introducing Personas 1.4 from Mozilla Labs on Vimeo.

What you can Expect from 1.4

1. More From the Designer: Say you’re browsing through the Personas gallery and pick a design you like. The next day, you want to know whether the designer has created any other cool designs. Before, you would need to go to getpersonas.com and either search for the designer name or find the design you liked and click on the designer by-line. Now, you can simply click on your extension (the little fox on the bottom left corner of your screen), mouse to the top of the menu, and then mouse right to the submenu.

2. Favorites: In the last version of Personas, we enabled you to easily favorite any Persona design in the gallery and have it instantly accessible in the “my favorites” section of your menu (see more about the 1.3 release).

3. More From the Category: Say you’re in the mood for a Holiday persona design. Within the extension menu, you mouse through the Holiday category but can’t find anything you like. Before, you needed to navigate to the Holiday gallery by navigating to getpersonas.com and finding the Holiday gallery. Now you can get there in one step by clicking “More From Holiday” in the extension.

4. Undo: Personas gives you the ability to preview a design before you select it. But still, maybe you chose a design and instantly regret the decision. Before, to undo you would need to go to “recently selected” designs in your extension menu and click on the last design you were wearing. Now, an undo notification bar drops down every time you select a design that you haven’t used recently, or haven’t marked as a favorite.

Get Personas 1.4

If you are already using Personas 1.3, Firefox will automatically update it to Personas 1.4 the next time it checks for add-ons updates. If you aren’t using Personas yet, or you want to get the new version immediately, install it at getpersonas.com.

Thanks!

Many thanks to Erik van Eykelen, Jose Bolanos, Ryan Doherty, Carsten Book (a.k.a. Tomcat), Toby Elliott, Zandr Milewski, and all the Personas localizers on Babelzilla (AtteL, dogi, drry, Ersen Yoldac, fernph, Funkin2x, funTomas, Joergen, jojaba, jooliaan, kkemenczy, kustodian, Lisman, lois, loveleeyoungae, moZes, pia, SiiiE, spjutster, steekid, stoyan, Wareczek, and wtspout), who did great work to make this feature possible, along with all the folks in the discussion forum who suggested the feature, tested early versions of it, and reported problems!

What’s Next?

We’re looking to make this feature even better and easier to use. To continue to evolve Personas quickly, and in the right direction, we need your feedback and participation. Join the conversation in the discussion forum and add helpful hints to the support wiki. And stay tuned to this blog for updates!

- Suneel Gupta and Myk Melez on behalf of the Personas development team

– Ragavan Srinivasan, on behalf of the Weave team

This release marks a significant step towards making Weave Sync a production quality add-on. With this Beta release, we have tried to make Weave Sync:

• Faster – using heuristics, Weave Sync computes an interestingness score to get you the most relevant data first. We have more details below.
• Simpler – a user interface that allows regular users to get up and running in a matter of minutes, while being flexible to accommodate advanced users.
• Unobtrusive – once it has been setup, Weave Sync works mostly in the background and when your computer is idle, without interrupting your regular Firefox experience.

New to Weave Sync?

Check out the Getting Started section on the project page that describes what this addon is all about. You will also find links to help you get up and running quickly.

Currently using Weave Sync?

In case you didn’t catch our blog post from a week ago, we would like to reiterate the following to ensure a smooth upgrade.

• When you install the 1.0 beta sync add-on, all of your Firefox and Fennec instances will do a fresh upload of all your data. For the majority of our users, this should happen in a transparent manner. However, if you are using the Weave servers primarily as a back-up and do not have your data anywhere else, you should ensure you have at least one local copy before upgrading to 1.0 beta.
• If you are using the Weave Sync on multiple computers, you will need to upgrade to the 1.0 version on all of them to get sync functionality working correctly.
• The 1.0 beta sync add-on includes the incremental sync behavior. This helps in two ways:
  • Your data will be synchronized in chunks to improve performance. Among other things, it ensures that you can continue to use Firefox normally even when you are syncing hundreds of bookmarks in the background. That said, if you have a lot of data, it could take some time for all of it to be synchronized. Do not panic if you do not see all of your data immediately. Depending on the type of computer you have and the amount of data you have, this could take anywhere from a few minutes to a few hours.
  • Your data will be synchronized based on “Interestingness”. “Interestingness” is related to how the AwesomeBar works in Firefox where pages that you frequently and recently visit show up higher in the location bar results. Weave Sync basically stores that “frecency” value with the encrypted history data on the server, so clients can ask the server for the most interesting items first. For other data like bookmarks, frecency is combined with where the bookmark is shown, so items visible in the Bookmarks Toolbar are ranked as “more important.”
• Finally, if you are hosting your own Weave server, you’ll need to add an apache alias line for the 1.0 URL – your old server will still handle the same API.

Also, please be sure to check the release notes for any known issues. We also have a list of Frequently Asked Questions that might be helpful.

If you believe you have discovered a bug, please use the Filing Bugs link that provides easy instructions to file bugs.

And as always, if you have any questions/comments/feedback, please let us know on the forums.

One final point: If you have been using the auto-login features, you can download an early pre-alpha version here. We intend to develop it rapidly and have a bunch of new ideas/features lined up. See the wiki page for more details.

– Ragavan Srinivasan, on behalf of the Weave team

With the release of Jetpack 0.6 just days ago, we are happy to announce a contest in its honor. The contest starts today and ends on the 13th of December. For the developer who creates the most awesome Jetpack that uses less than 50 lines of code, we are offering a brand new netbook (the ASUS Eee PC 1000HE). We’ll be sending the runner-up a big package of Mozilla swag.

With so many neat Jetpacks on the Jetpack Gallery already, the competition should be fun and lively. And, naturally, you do get special bonus points for using the APIs debuted in Jetpack 0.6 APIs.

Get the details on the Jetpack blog ⟫

With the release of Jetpack 0.6 just days ago, we are happy to announce a contest in its honor. The contest starts today and ends on the 13th of December. For the developer who creates the most awesome Jetpack that uses less than 50 lines of code, we are offering a brand new netbook (the ASUS Eee PC 1000HE). We’ll be sending the runner-up a big package of Mozilla swag.

With so many neat Jetpacks on the Jetpack Gallery already, the competition should be fun and lively. And, naturally, you do get special bonus points for using the APIs debuted in Jetpack 0.6 APIs.

Here are the details:

• The contest ends lasts until the 13th of December.
• Your Jetpack should be less than 50-lines of code. White space, trailing brackets, and comments don’t count in your total line numbers. This is a loose rule (lines of code are hard to count) so play fair. Pulling in 3rd party libraries and services are par for the course. For an example of a 14-line Jetpack see Mozilla Labs’s Image Editor Jetpack.
• Win a netbook!
• See the contest details
• Submit your Jetpack

Get Involved in the development of Jetpack

Mozilla Labs is a virtual lab where people come together online to create, experiment and play with Web innovations for the public benefit. The easiest way to get involved, get the source code, and get creating is to visit the Jetpack homepage.

- Daniel Buchner, on behalf of the Jetpack team

<!DOCTYPE html>
<html><head> <link href="BespinEmbedded.css" type="text/css" rel="stylesheet"> <script type="text/javascript" src="BespinEmbedded.js"></script> <style> .bespin { margin: 0; padding: 0; border: 0; height: 300px; border: 10px solid #ddd; -moz-border-radius: 10px; -webkit-border-radius: 10px; } </style>
</head>
<body> <h1>Sample Editor as a Component</h1> <div id="editor" class="bespin" data-bespin-options='{ "stealFocus": true }'>
// The text of this div shows up in the editor.
var thisCode = "what shows up in the editor";
function editMe() { alert("and have fun!");
} </div> <script> window.onBespinLoad = function() { console.log("this is called when Bespin is loaded"); }; </script>
</body>
</html>

The Jetpack gallery, while still a beta, makes it easy to find new functionality that extends your Firefox experience with new abilities. You can browse Jetpacks by tag, author, and popularity, as well as vote on and review the ones you try. Jetpacks in the gallery have screenshots and video introductions, making it easy to get to know what you are getting before installing.

Read more on the Jetpack blog ⟫

The Jetpack gallery, while still a beta, makes it easy to find new functionality that extends your Firefox experience with new abilities. You can browse Jetpacks by tag, author, and popularity, as well as vote on and review the ones you try. Jetpacks in the gallery have screenshots and video introductions, making it easy to get to know what you are getting before installing.

For developers, the Jetpack gallery makes it easy to host and promote Jetpacks. Just like AMO, you’ll get a wealth of feedback and data on your Jetpack. And, because Jetpack is a runtime, every Jetpack but a user’s first will install without the need for a browser restart.

We hope to see your Jetpack there soon!

– Daniel Buchner, Nick Nguyen, and Aza Raskin on behalf of the Jetpack team.

In early September we challenged students from universities around the world to develop concepts and solutions to the question: “Browsing History — How can we make sense of this rich source of data and how do we best present this data to the user?” [read the full brief here]

Students from four schools took the challenge and worked intensively on their ideas – some in the form of a Design Jam next to their normal course work, other as part of their university assignments.

See all submitted concepts & mockups here.

In early September we challenged students from universities around the world to develop concepts and solutions to the question: “Browsing History — How can we make sense of this rich source of data and how do we best present this data to the user?” [read the full brief here]

[UPDATE] The students from the Interaction Design Studio at the University of Sydney, Australia, submitted their mockups and prototypes. See below for links to the individual submissions.

Students from four schools took the challenge and worked intensively on their ideas – some in the form of a Design Jam next to their normal course work, other as part of their university assignments.

In the last few weeks students from Parsons The New School for Design presented their concepts to an excited crowd of Mozillians during one of the Mozilla Design Lunches. The students presented their concepts and excellent mockups via video conference and received direct feedback from both the Mozilla Labs and Add-ons teams. The teams are now busy polishing their mockups, incorporating the feedback and submitting their final work in the next few weeks.

In the meantime the students engaged in the University of Michigan SOCHI student organization finished up their mockups and submitted a series of interesting concepts and very polished mockups:

• Natalia Fischer’s Snapshot History
• Tom Haynes’ Timeline
• Katie McCurdy and Kiran Jagadeesh’s Firefox Foresight
• Jose Jimenez’s Mozilla’s History Browsing

In Brazil the students at PUC Minas also got busy and created a whole series of amazing concepts:

• Marcello Cardoso’s Browse Back
• Harlley Oliveira’s My Web
• Humberto Massa and Marcelo Bruzzi’s Down the Memory Lane
• Diego CS, Leonardo Shibuya and Vitor Peçanha’s Memory Fox
• Danilo Strauss Neto and Charles Silva Lacerda’s HistorySearch
• Erika Goular, Nathália Massote, Olavo Xavier and Samuel Burlamaqui’s HistoryBrowse
• Flávio Cavalieri, Rodrigo Diniz and Tiago Rigoletto’s History 09

The students from the University of Sydney’s Interaction Design Studio submitted a series of excellent mockups and prototypes:

• Team cK: Cherry Chau and Qi Wu’s History Bubbles [Overview | Video | Prototype]
• Team Dr Poo: Jason Chan and Jimmy Lee’s 3D Rotating View [Overview | Video]
• Team Go! Aiden Benton and Ryo Yambe’s Web Tree [Overview | Video]
• Team JoC: Sze-Ming Yick and Joanna Chang’s UrStory [Overview | Video]
• Team Little Glass Vial: Anniese Josey and Arwen Whiting’s Hounded Fox [Overview]
• Team minimouse: Kristal Tang and Young-Long Kim’s Minimouse History [Overview | Video]
• Team PJ: Deanne Goard and Annabelle McGee’s PJ History [Overview | Video]
• Team PurpleMonkeyDishwasher: Sanjay Dutt and Scindya Datt’s Sidebar History [Overview | Video]
• Team StringPost: Ramon Rodrigo and Loan Myers’ StringPost [Overview | Video]
• Team Tamara feat Oliver: Tamara Chahine and Oliver Dawson’s Footsteps [Overview | Video]
• Team Awesome: Emily Allcock and Bernard Bucalon’s Kaleidoscope [Overview | Video]
• Team Teenage Mutant Ninja Turtles: Josh McInerheney and Jin Lim’s TMNT Browser History [Overview | Video]

Make sure you check out the concepts from all three schools – they are not only excellent ideas and concepts but also amazingly high quality mockups and prototypes..

What’s next?

We’ll post more concepts including the works from the students of Parsons The New School of Design. We’ll also provide direct feedback to the students and will make the results available to the wider Mozilla community.

Stay tuned!

Jetpack 0.6 adds two major APIs to the arsenal: a secure preferences system and the ability to add and modify menus. With these new APIs — and the numerous bug fixes since the last release — we hope to see even more innovative Jetpacks in addition to the hundreds already written.

Menu

An important part of many add-ons is creating menu items — both at a system level and for context menus. In Jetpack 0.6, we’ve tried to make this painless.

Jetpack Menu API Tutorial

For example, adding an item to the Tool’s menu requires just one line of code:

jetpack.menu.add("Hello World!");

For a fully useful example, check out the Pixlr Image Editor Jetpack, which lets you edit any photo you find on the web with a right-click.

If you want to dive in, you can read the Menu API documentation.

Settings

Most Jetpacks require a couple of persistent settings, like user names, passwords, and preferences. The Settings API tries to be unobtrusive — you tell Jetpack what kind of settings you want and Jetpack takes care of the interface.

For example, include the following code for settings in your Jetpack:

var manifest = { settings: [ {id:"username", type:"text", label:"Username"}, {id:"music", type:"boolean", label:"Music", default: true }, {id:"volume", type:"range", label:"Volume", min: 0, max: 10, default: 5 } ]
};

Jetpack will automatically build a UI for it:

And your Jetpack will be able to access the settings via:

jetpack.storage.settings.username
jetpack.storage.settings.music
jetpack.storage.settings.volume

This is a first iteration of a settings implementation, more will be coming soon. For more details, read the Settings API proposal document.

Download

If you already have Jetpack installed, update to 0.6 via the “Find Updates” button in the add-ons manager. If you’re new to Jetpack, you can get Jetpack automatically by installing any Jetpacks or by downloading it directly from addons.mozilla.org.

Participate

Mozilla Labs is a virtual lab where people come together online to create, experiment and play with Web innovations for the public benefit. There are many ways to join the team and get involved:

• Report a bug
• Grab the source code and fix a bug or add a feature
• Discuss, debate and add to the design in the Jetpack discussion group
• Join us in #jetpack on irc.mozilla.org

– Aza Raskin, Atul Varma, Daniel Buchner, and Nick Nguyen on behalf of the Jetpack development team.

We are happy to announce that we have a winner for the Jetpack 0.5 contest. Given the fantastic group of entrants, with Jetpacks that did everything from Twitter readers to a one-click text translators, it was hard to pick a winner.

The winner

Alexander Miltsev of Moscow created a prototype for allowing Jetpacks to process large amounts of data on your computer’s graphical co-processor. Alex’s work is both creative and unusual. It digs deep into what a potential future for Jetpack can be—allowing for high-performance computing that is accessible to casual developers.

In Alex’s words: “Large data processing is occurring everywhere today. Graphical co-processors are on computers everywhere [and are used in] computational science models, searching tasks, algorithms, statistics, and audio and video processing.” By giving webpages and add-ons easy access to the raw processing power available on most computers, the range of abilities that the web can have greatly increases.

Alex’s work is an alpha-prototype that shows the feasibility of the project and it requires a custom build of Firefox to use — it’s not easy to demo. However, the code sample below shows how the technology works. In this example, we are transposing a matrix at lightening speed:

jetpack.statusBar.append({ html: "Transpose!", onReady: function(widget){ $(widget).click(function(){ var myStorage = jetpack.cuda-storage; var matrix = new Array(); var size = 32; for(var i=0; i<size*size; ++i) array[i] = i; var transposedMatrix = myStorage.transpose(size, matrix); transposedMatrix.forEach(function (v) { console.log( v ); }) });
});

You can get more information about Alex's Jetpack on his website. For winning the Jetpack 0.5 competition, Alex is getting a brand new ASUS Eee PC netbook!

Check back in a couple days for the next Jetpack contest.

Runners Up

Elijah Grey wrote the GTranslatifier Jetpack, which lets you translate web pages and selections of text at the click of a button. He also wrote the Edit Page Jetpack, which lets you temporarily live-edit the contents of any page.

Francesco Strappini wrote a cute Jetpack called 3lyfic, which creates short links via http://3.ly and then lets you share them across your social networking site.

Panagiotis Astithas wrote the Jetstatus Jetpack, which not only gives you notifications of Twitter updates, but also lets your quickly read over past tweets in a slidebar.

— Aza Raskin on behalf of from the Jetpack Team

Jetpack 0.6 adds two major APIs to the arsenal: a secure preferences system and the ability to add and modify menus. With these new APIs — and the numerous bug fixes since the last release — we hope to see even more innovative Jetpacks in addition to the hundreds already written.

Read more about Jetpack 0.6 here.

We are happy to announce that we have a winner for the Jetpack 0.5 contest. Given the fantastic group of entrants, with Jetpacks that did everything from Twitter readers to a one-click text translators, it was hard to pick a winner.

Read more about the Jetpack 0.5 Contest here.

Next week, we expect to be able to release the first beta of the Weave sync add-on. To help you prepare for this release, we wanted to share some details on what to expect:

* When you install the 1.0 beta sync add-on, all of your firefox and fennec instances will do a fresh upload of all your data. For the majority of our users, this should happen in a transparent manner. However, if you are using the Weave servers primarily as a back-up and do not have your data anywhere else, you should ensure you have at least one local copy before upgrading to 1.0 beta.

* If you are using the sync add-on on multiple computers, you will need to upgrade to the 1.0 version on all of them to get sync functionality working correctly.

* If you have been using the auto-login features, you may have noticed them missing already starting with the 0.8 version. The weave sync 1.0 beta add-on will only have synchronization related functionality. The auto login feature is *not* dead. It is simply being moved into its own add-on. We hope to be able to release an early pre-alpha version soon (in a week or so). We fully intend to develop it rapidly and have a bunch of new ideas/features lined up. See the wiki page for more details.

* The 1.0 beta sync add-on includes the incremental sync behavior. This helps in two ways:

1. Your data will be synchronized in chunks to improve performance. Among other things, it ensures that you can continue to use firefox normally even when you are syncing hundreds of bookmarks in the background. That said, if you have a lot of data, it could take some time for all of it to be synchronized. Do not panic if you do not see all of your data immediately. Depending on the type of computer you have and the amount of data you have, this could take anywhere from a few minutes to a few hours.

2. Your data will be synchronized based on “Interestingness”. “Interestingness” is related to how the AwesomeBar works in Firefox where pages that you frequently and recently visit show up higher in the location bar results. Weave basically stores that “frecency” value with the encrypted history data on the server, so Weave clients can ask the server for the most interesting items first. For other data like bookmarks, frecency is combined with where the bookmark is shown, so items visible in the Bookmarks Toolbar are ranked as “more important.”

* Finally, if you are hosting your own weave server, you’ll need to add an apache alias line for the 1.0 URL – your old server will still handle the same API.

The weave team will be watching our servers and the forums very closely during and after the release to ensure everything happens smoothly. We are really excited about getting to this major milestone and look forward to building an awesome product for you.

As always, let us know if you have any questions/comments on the forums.

– Ragavan Srinivasan, on behalf of the Weave team

One of the problems with the Test Pilot extension so far has been that we’ve needed to release a new version of the extension every time we wanted to add a new experiment or survey, or even in order to fix a minor bug. And every time we released a new version, users had to download it, then restart Firefox; an annoyance that we’d rather not force on people. This new release of the Test Pilot extension, version 0.3, has been rewritten from the ground up to avoid this problem.

Download the latest Test Pilot extension!

Many pilots have asked what is the next study, and here it comes: A Week in the Life of a Browser!

For this study, which we will be launching at the beginning of December, we would like to explore what a browser does to facilitate its user using the Web through a year. We will periodically collect your usage information about the browser for a week and run the same study again every 60 days. The main goal is to explore if the browser has been used differently over time, which may help us design a better product that works adaptively.

For more detail about this release, please read the original blog post!

Since we announced the first study of Test Pilot, Tab Open/Close, about two months ago, we have received more than 7,000 data submissions from around the world, providing invaluable data into how you use tabs in your daily Web browsing. We’ve published some analysis we of this data. We’ve seen the thoughts you’ve shared about it via the discussion group and twitter . We’ve seen people use the aggregated data samples that we published to do their own analysis. The level of interest and participation in the Test Pilot community is very encouraging to us. We hope to continue delivering studies that are interesting and meaningful to both the product team and the public. Thanks for your participation, and keep it coming!

Test Pilot 0.3

Download!

One of the problems with the Test Pilot extension so far has been that we’ve needed to release a new version of the extension every time we wanted to add a new experiment or survey, or even in order to fix a minor bug. And every time we released a new version, users had to download it, then restart Firefox; an annoyance that we’d rather not force on people.

The new release of the Test Pilot extension, version 0.3, has been rewritten from the ground up to avoid this problem. It is now based on the same technology as Jetpack, which enables it to automatically retrieve new experiments and improvements to existing experiments, without asking you to download anything or restart Firefox.

Our policy of giving pilots control over their own data is the same as it has always been: You can still quit a study at any time, you can still review all collected data before you send it, and you can still choose not to submit the data when a study ends. The only thing that’s different is that we can now update an experiment already in progress.

A Week in the Life of a Browser

Many pilots have asked what is the next study, and here it comes: A Week in the Life of a Browser!

In recent years, people spend more and more time on the Web to work, to organize their daily lives, to entertain themselves and to socialize with friends. Is Firefox robust enough to support these activities smoothly all the time?

For this study, which we will be launching at the beginning of December, we would like to explore what a browser does to facilitate its user using the Web through a year. We will periodically collect your usage information about the browser for a week and run the same study again every 60 days. The main goal is to explore if the browser has been used differently over time, which may help us design a better product that works adaptively. This study is inspired by several test proposals that we received in the past months: proposals for tests of Overall Performance , Memory Usage, and Window Metrics.

This is a periodical study; pilots can choose to opt in or out of the study at any time. Each study phase is independent and equally important to us. Whether you choose to participate for the whole year, or only for a single week, the data that you share is extremely valuable. Please read the details about the study, and please visit the Test Pilot discussion group to share your thoughts if you have questions about this study.

Get Involved!

1. Install the latest “cuddlefish” version of Test Pilot, or become a Test Pilot if you haven’t join us!
2. Check the analysis or download the aggregated data samples from the Tab Open/Close study!
3. Share your questions and suggestions on Test Pilot discussion group or on Twitter .
4. Join the fun quiz: Tell us how long you normally stay on the Web everyday!

For more details about Weave 0.8, please check out the details over at the Weave blog!

Major Features

What is Weave Sync all about? In short, Weave Sync lets you securely take your Firefox experience with you to all your Firefox browsers — including our mobile browser, codenamed Fennec. It currently supports continuous synchronization of your bookmarks, browsing history, saved passwords and tabs, as well as form-field history and preferences. For example:

• Get the same results on the Smart Location Bar on each of your Firefox browsers, so you can get to your favorite sites with just a few keystrokes
• Continue what you were doing: have the ability to open any tab you have open on any of your Firefox browsers
• Keep the same list of bookmarks on all of your Firefox browsers
• If you use Personas, your currently selected Persona will be synchronized across your Firefox browsers
• Easily sign in to all your favorite sites using your saved passwords (this is especially handy on mobile phones, where it’s hard to type in complex passwords)
• Do it all securely: Weave Sync encrypts user data before uploading it to Mozilla’s servers, so that only you can access your data

What’s new in 0.8?

If you have not looked at Weave recently, now is a great time to jump in and try it out! In this last pre-beta release we have made a number of changes based on feedback from users:

• Incremental download support is much more aggressive at fetching data, with explicit priority given to your most important data first
• New preference and setup UI for both Firefox and Fennec, moving back to a much tighter integration with the applications
• Cut download size in half from 0.7
• Better feedback for sync progress and errors
• Many added bugfixes (see full changelog)

Getting Involved with Testing and Development

• Install Weave 0.8 (requires Firefox 3.5 or higher)
• Learn more about Weave
• Discuss, debate, and add to the design in the Weave forum
• Join us in #labs on irc.mozilla.org

– Mike Connor, on behalf of the Weave development team

We invite you to help turn the open Web into a rich learning environment and explore new possibilities for using Firefox add-ons to support learning online, by participating in the Jetpack for Learning Design Challenge sponsored by the Mozilla Foundation with support from the John D. and Catherine T. MacArthur Foundation as part of its digital media and learning initiative.

We are looking for designers, educators and software developers who want to turn their innovative ideas about learning online into working prototypes in the form of Firefox add-ons. We’ll help you refine your designs and teach you how to create Firefox add-ons using Jetpack and other Mozilla technologies. Participants creating the best prototpes will be invited to the Jetpack for Learning Design Camp and the SXSW Interactive conference in March 2010.

How does it work?

Come up with an innovative idea for a Firefox add-on that brings personal learning features to the open Web. Create a mock-up and submit it on the Jetpack for Learning Design Challenge web-site before midnight (US Pacific Time) on 27 November 2009. Based on the quality of submissions, up to 60 participants will be invited into a 6-week online course that covers design/UX and technical aspects of add-on development and will help you turn your mock-up into a working prototype. We’ll select the most promising prototypes and invite up to ten of their creators to further refine their add-ons at a face-to-face Jetpack for Learning Design Camp in March 2010 and to attend SXSW Interactive immediately following the Design Camp.

What kind of ideas are we looking for?

We are looking for your ideas on how Firefox add-ons, preferably add-ons created with Mozilla’s Jetpack technology, can turn the web browser into a platform for rich personal learning on the open web. You are not restricted to work on any particular type of application. Here are a few examples to get you started …

• Turn social bookmarking and page annotation into effective learning tools (for example by including peer-assessment features)
• Allow users to easily compile personal e-portfolios (for example, by combining their own works — photos, comments, articles—with testimonials others have written about them)
• Let the browser suggest relevant materials for learning (for example, by automatically identifying additional articles based on what sites a person visits or which topics they search for)
• Support social learning communities (for example, by making it easy to find and connect with others who share similar learning interests)

Who should apply?

Participation is open to individuals and teams, but we especially encourage submissions from inter-disciplinary groups (designers, educators, and software developers). You don’t need to be a computer geek, but participants are expected to implement their ideas as Firefox add-ons, which will require writing some software code.

You must be at least 18 years old in order to participate in the Jetpack for Learning Design Challenge. You must also make your submission and your add-ons available for public use under open licenses. See the Jetpack for Learning web site for complete rules.

Contact

You can find more information about the Jetpack for Learning Design Challenge, including how to apply, on our web site:

http://design-challenge.mozilla.org/jetpack-for-learning

See a design you particularly like in the Personas gallery? Click view details to see detailed information about the persona, then add it to your favorites by clicking the add to favorites star.

Once you’ve added some designs to your favorites, check out the little fox in the bottom left corner of your screen. All your favorites are there!

Want to see all your favorites at once? Go to the Personas gallery and click on All, then Favorites to view your favorites.

Get Personas 1.3

If you are already using Personas 1.2, Firefox will automatically update it to Personas 1.3 the next time it checks for add-ons updates. If you aren’t using Personas yet, or you want to get the new version immediately, install Personas 1.3 now.

Thanks!

Many thanks to Jose Bolanos, Ryan Doherty, Carsten Book (a.k.a. Tomcat), Toby Elliott, Zandr Milewski, and all the Personas localizers on Babelzilla (AtteL, dogi, drry, Ersen Yoldac, fernph, Funkin2x, funTomas, Joergen, jojaba, jooliaan, kkemenczy, kustodian, Lisman, lois, loveleeyoungae, moZes, pia, SiiiE, spjutster, steekid, stoyan, Wareczek, and wtspout), who did great work to make this feature possible, along with all the folks in the discussion forum who suggested the feature, tested early versions of it, and reported problems!

What’s Next?

We’re looking to make this feature even better and easier to use. To continue to evolve Personas quickly, and in the right direction, we need your feedback and participation. Join the conversation in the discussion forum and add helpful hints to the support wiki. And stay tuned to this blog for updates!

- Suneel Gupta & Myk Melez on behalf of the Personas development team

We should be cautious about drawing conclusions too quickly from this data. For instance, just because it’s very common for someone to have three tabs open doesn’t mean that we need to start optimizing the browser for the three-tabs use case. These visualizations are just a starting point. We hope that looking at them will spark some ideas which can be turned into hypotheses. The next step is not to jump into designing interfaces, but rather to design experiments to test our hypotheses.

Third-party researchers have already begun using the aggregated data samples that we published to do their own analysis. Andy Edmonds at Surfmind.com has created some very cool-looking visualizations. He looks at the relationship between average tabs and maximum tabs and proposes an interesting hypothesis about two different classes of heavy tab users. Take a look!

Please visit the Test Pilot discussion group and share your thoughts about these visualizations, or about what other visualizations you would like to see!

Major Features

What is Weave Sync all about? In short, Weave Sync lets you securely take your Firefox experience with you to all your Firefox browsers — including our mobile browser, codenamed Fennec. It currently supports continuous synchronization of your bookmarks, browsing history, saved passwords and tabs, as well as form-field history and preferences. For example:

• Get the same results on the Smart Location Bar on each of your Firefox browsers, so you can get to your favorite sites with just a few keystrokes
• Continue what you were doing: have the ability to open any tab you have open on any of your Firefox browsers
• Keep the same list of bookmarks on all of your Firefox browsers
• If you use Personas, your currently selected Persona can be synchronized across your Firefox browsers
• Easily sign in to all your favorite sites using your saved passwords (this is especially handy on mobile phones, where it’s hard to type in complex passwords)
• Do it all securely: Weave Sync encrypts user data before uploading it to Mozilla’s servers, so that only you can access your data

What’s new in 0.7?

If you have not looked at Weave recently, now is a great time to jump in and try it out! In this release we have continued work on scalability and reliability, user-facing performance, and continued our exploration of the new interface model that first appeared in 0.6.

• Major changes to improve sync reliability and performance for all users
• Incremental download support: when adding a new client, Weave will download your data in chunks to spread out and reduce memory and network usage
• Revamped setup and configuration UI, continuing the exploration we started with 0.6
• Many added bugfixes

Getting Involved with Testing and Development

• Install Weave 0.7 (requires Firefox 3.5 or higher)
• Learn more about Weave
• Discuss, debate, and add to the design in the Weave forum
• Join us in #labs on irc.mozilla.org

– Mike Connor, on behalf of the Weave development team

We’ve now completed our inaugural Test Pilot study, with more than 5,000 opt-in participants from around the world providing invaluable data into how they use tabs in their daily Web browsing, and today we’re making this data available under an open license for analysis by the wider research community.

With this first study our primary objective has been to provide a trial run of an end-to-end process while still maintaining user privacy. We believe that we’ve been able to gather enough information to answer the questions posed by the Tab Open/Close study while ensuring that we’re true to the privacy policy and guiding principles. All submitted test data is stored in anonymous form, none of it is directly associated with any potentially personally identifiable information, and no directly personally identifiable information was collected or stored.

Data from this study is being made available under the Creative Commons Attribution 3.0 United States License, with the additional requirement that you acknowledge that Mozilla cannot vouch for the quality or timeliness of any third-party analysis or work derived from the Mozilla Test Pilot Data.

We’re still working on the best way in which to license data from the Test Pilot program. Please do join us in the discussion group, especially if you are a researcher and help us better understand requirements for publication.

We encourage people to make creative use of this data, to conduct analysis and to perform research on these downloadable datasets. When you publish work derived from our test data, we ask that you cite Mozilla Test Pilot as the source. While it’s not required that you contribute back your analysis, we truly hope that you will join us in the spirit of shared exploration and research. Please do share your work back with us through the discussion group.

Tab Open/Close Study Test Data (9/3/2009-9/24/2009)

Get Involved

We invite you to participate in shaping the future of the Test Pilot program:

1. Install and play with the Test Pilot add-on .
2. Report a bug.
3. Suggest ways to better structure the program or improve the user experience of participating in tests.
4. Add your ideas for usability tests to the test proposals page on the Labs wiki.

Barring unforeseen issues, we plan to release this version in a couple of days. You can really help us out by trying it out and letting us know if you notice any problems with it!

To try it out, just follow this link to install Personas 1.3rc1.

Report any problems in the Personas discussion forum or by filing a bug report. You can also look at the list of reported bugs to see if the problem you notice has already been reported.]]> Uncategorized http://mozillalabs.com/conceptseries/2009/09/28/university-design-challenge-09-report-from-the-interaction-design-studio/ The students at the University of Sydney’s Interaction Design Studio took the Mozilla Labs Design Challenge and turned it into a semester long project – effectively going through the whole process from theoretical & concrete user research to ideation, concept development and prototype production (both lo-fi and hi-fi). The team progressed fast through this process and [...] http://mozillalabs.com/conceptseries/?p=59 Mon, 28 Sep 2009 15:07:38 -0700

The students at the University of Sydney’s Interaction Design Studio took the Mozilla Labs Design Challenge and turned it into a semester long project – effectively going through the whole process from theoretical & concrete user research to ideation, concept development and prototype production (both lo-fi and hi-fi).

The team progressed fast through this process and is currently in the prototyping stage in which the students will build prototypes using JavaScript and Python.

Martin Tomitsch, the group’s teacher and project coordinator posted two blog posts summarizing the amazing work the group has done so far:

• User research: results and findings
• Paper prototypes and user evaluation

You can also check out the Ning group which the students use for communication, idea exchange and collaboration.

Get your concepts in! The Weave Web UI Design Challenge is looking for your answer to the question:

“Visualizing your browser data – How can we provide intuitive and useful visual representations of your browser data (such as bookmarks, history, tabs, stored credentials etc.) on a web page?”.

This is your chance to get your ideas in front of a large audience, receive feedback from experts in the broader field of user experience design and directly influence the future design direction of Mozilla Labs’ Weave.

Read all about the Design Challenge on the landing page and submit your concept on our ChallengePost page.

You can read all about the event on the SOCHI blog and see pictures of the event on flickr. If you are interested in the overall process – the SOCHI team made their presentation describing the process available here.

Meanwhile the students at the University of Sydney finished up their research and started working on prototypes (after also having built a series of paper prototypes). For this purpose the students created a database schema which will form the basis of their work:

We are excited to see the results from all groups and will keep you updated on the progress.

[Update] The team at Parsons University met recently for a brainstorm/research exercise and published their results and findings on the Mozilla University Challenge Wiki. The students will continue their research this week with user stories and further exploration of existing or potentially interesting solutions.

When you click on the feed icon in Firefox’s location bar, Firefox normally shows you its feed preview page. If the page provides both RSS and Atom feeds, Firefox makes you pick between them first:

Snowl 0.3 replaces Firefox’s feed preview page with its river of news view, so once you click on the feed icon, you’ve subscribed to the feed in Snowl and can start following it immediately. It also detects identical RSS and Atom feeds and doesn’t make you pick between them.

The list view improvements include support for deleting messages, unread message counts, custom collections that you can define yourself, and collection filtering:

Try out Snowl 0.3 and let us know what you think! But don’t forget that this is a labs experiment, not a finished product, and there are bound to be bugs and other issues.

Post your thoughts on Snowl to the discussion group, and file bug reports on the problems you encounter. Or join us for discussion in the #labs IRC channel on irc.mozilla.org. And if you’re interesting in hacking on Snowl, check out the source code.

- Myk Melez on behalf of the Snowl team

Together with four universities from the US, Australia and Brazil we kicked off our Fall ‘09 University Design Challenge in the first week of September. The students are working on concepts around the question “Browsing History – How can we make sense of this rich source of data and how do we best present this data to the user?” [full brief]

Each university takes a different approach to tackle this challenge – from a semester-long course specifically around this challenge at the University of Sydney to a series of short Design Jams at the University of Michigan and week-long programs (PUC Minas and Parsons).

SOCHI, the student organization for computer-human interaction at the University of Michigan kicked off their Design Jams this week – you can read about their approach on their inaugural blog post.

The University of Sydney set up a Ning group to facilitate discussion, capture artefacts of their research & work and openly share their findings.

In the next few weeks the groups will work together with Grady Kelly, an experienced interaction designer from the wider community, who will provide help, feedback & guidance on prototyping.

We’ll present more information & updates on the process, results and findings as we go here. Stay tuned.

After our Summer ‘09 Design Challenge, which attracted 130 submissions and spurred great discussions within the wider community, we are getting ready to launch our next round of Design Challenges. And this time we’re back with two:

University Design Challenge Fall ‘09

For this challenge we work together with students from universities and schools specializing in User Experience and Human-Computer-Interaction studies around the world to find innovative concepts to the question: “Browsing and Search History — How can we make sense of this rich source of data and how do we best present this data to the user?”

Students will work together in teams, with each university deploying a different solution approach — from a semester-long integration of the Design Challenge into the course to shorter Design Sprints and high-energy 24 hour Design Jams.

The program will run over a course of 10 weeks and we will report back regularly not only results but also observations from the solution process under the different settings. We will make the results and observations fully open to the wider community, using open licenses as a basis, and want to initiate a dialog between the wider community, users, professors and students.

Participating schools (as of today) are: The University of Sydney (Australia), Parsons The New School of Design (USA), PUC Minas (Brazil) and Student Organization for Computer-Human Interaction at the University of Michigan (USA).

You’ll find more information about this challenge and the progress on our landing page. If your school interested in joining us please drop us an email.

Design Challenge Weave Web UI

For this Design Challenge, we are looking for innovative solutions to answer the question: “Visualizing your browser data – How can we provide intuitive and useful visual representations of your browser data (such as your contacts, bookmarks, browsing and search history, tabs, stored credentials etc.) on a web page?”

Together with IxDA, a network dedicated to the professional practice of Interaction Design and Johnny Holland, an open collective, talking, sharing and finding answers about all aspects of interaction design, we invite the wider community to join us in this challenge, develop concepts and submit them to our site. The full design brief and background information can be found here.

How It Works

The program starts in the first week of September and runs for 10 weeks. The Design Challenge is divided into two phases – each running for five weeks.

During the first phase we ask you to produce a concept, mockup and an explanation of your thinking behind it. The Mozilla Labs Weave team will provide feedback to participants at two check-in points in week three and four.

At the end of phase one the Weave team will select the most promising concepts, which will move forward into phase two. In this phase you will refine your mockup and turn it into an interactive HTML/CSS/JavaScript prototype. During phase two the Weave team will provide regular feedback, weekly check-ins and support via email/irc.

Participants are encouraged to share their ideas, approach and progress on their blogs – we will aggregate this information and provide a forum for open discussion, ideation and exchange.

At the end of phase two the Weave team will again select the most promising concepts and work with their respective creators on integrating them into Weave.

Get involved now – take the Weave Web UI Design Challenge and submit your concept here.

Important Dates for both Challenges

• First week of September 2009 – Launch of Design Challenges
• Last week of September 2009 – Selection of participants for phase 2 of the Weave Web UI Design Challenge
• First week of November 2009 – Challenges end, solutions will be presented on this site; for the Weave UI challenge the team will select the most promising concepts and work with their creator on integrating them into the Weave product

In the river view, you can now see a day, a week, or a month’s worth of messages via the time period picker in the toolbar:

In the list view, you can now see how many new/unread/total messages you have, and both messages and collections can have icons indicating various states (new, refreshing, error, etc.):

Other enhancements include performance improvements and better support for searching for messages in non-English languages.

This is the last preview before the final release of 0.3. From here until that release, the focus will be on bug fixes and polish.

Try out Snowl 0.3pre3 and let us know what you think! But don’t forget that this is a preview release of a labs experiment, not a stable release of a finished product, and there are bound to be bugs and other issues.

Post your thoughts on Snowl to the discussion group, and file bug reports on the problems you encounter. Or join us for discussion in the #labs IRC channel on irc.mozilla.org. And if you’re interesting in hacking on Snowl, check out the source code.

- Myk Melez on behalf of the Snowl team

Today we’re calling on industry, higher education and people from around the world to get involved and share their ideas and expertise as we collectively explore and design future directions for the Web.

You don’t have to be a software engineer to get involved, and you don’t have to program. Everyone is welcome to participate. We’re particularly interested in engaging with designers who have not typically been involved with open source projects. And we’re biasing towards broad participation, not finished implementations.

We’re hoping to lower the barrier to participation by providing a forum for surfacing, sharing, and collaborating on new ideas and concepts. Our goal is to bring even more people to the table and provoke thought, facilitate discussion, and inspire future design directions for Firefox, the Mozilla project, and the Web as a whole.

Concepts may take the form of Ideas, Mockups or Prototypes.

• Ideas
  It all begins with an idea. A sentence, paragraph, or even bullet-points kick-start the process. Ideas can be simple and non-technical. It should be easy for anyone and everyone to help shape the future of the Web. So throw your notions, inspirations, dreams and visions out to the community.
• Mockups
  Turn your idea (or someone else’s) into an image, sketch or video. Words are great, but you know what they say about pictures. Mockups offer up a visual and communicate ideas in terms that are just a bit more polished and real. They draw the next person in, tempting them to pick up the concept and run with it.
• Prototypes
  A prototype is interactive. Feel, touch and play with developing concepts. Prototypes get ideas across by showing off the moving parts. They aren’t always fully functional or pretty, but they’re more than a static image or two. They’re a dress rehearsal of sorts, with minimal programming. Make a prototype in HTML, Flash, or whatever puts things into action.

We only ask that all concepts and related source materials be freely redistributable and remixable under either a Creative Commons license (for Ideas and Mockups) or the Mozilla Public License (for Prototypes) so that we can all effectively collaborate on the exploration. Again, the intent is not for these concepts to evolve directly into new products but rather to provoke thought, facilitate discussion and provide inspiration.

Be bold. Be radical. The crazier, the better. Let’s explore the future together.

Inaugural Concepts

Aurora Concept (Part 1)
by Adaptive Path

Aurora explores new ways people could interact with the Web in the future based on projected technological trends and real-world scenarios. Learn More

Bookmarking & History Concept
by Wei Zhou

An investigation into a better way of visualizing and interacting with bookmarks, your history, and the browser in general. Learn More

Mobile Concept
by Aza Raskin

An experimental UI proposal for Firefox Mobile. Learn More

How to Get Involved
Join us on the Mozilla Labs site at http://labs.mozilla.com/projects/concept-series/.

Soon we’ll have a more structured way to contribute concepts. For now, all you have to do is use your favorite method of sharing an concept with the world. If it’s an idea, blog about it. If it’s a mockup, put it on Flickr. If it’s a prototype, host it on your web site. Tag it with “mozconcept” and then let us know about it by posting to the Concept Series discussion forum.

The second area of investigation is what we call verbifying the Web. More and more websites are things that you do rather than places that you go to. We Digg things, Tweet things, Google for things, blog things, map things, and so on. But in most cases, using one of these services requires copying some text, going to the appropriate website, and pasting it into a form. How about if the interface to the Web treated these services as tools that you can pick up and take with you, to use anywhere, instead of treating them as destinations?

Ubiquity commands are small chunks of javascript which can interface with web services. Any website can offer Ubiquity commands; any Ubiquity user who visits the site can see the commands and choose whether to subscribe to them. Once subscribed to, those commands can be used anywhere.

Today we’re launching Bespin as a project within our Developer Tools Lab to focus on this exploration.

Just as Mozilla enables massive innovation by making Firefox open on many levels, we hope to do the same with Bespin by developing an extensible framework for Open Web development. We’re particularly excited by the prospect of empowering Web developers to hack on the editor itself and make it their own.

Overview

Bespin proposes an open extensible web-based framework for code editing that aims to increase developer productivity, enable compelling user experiences, and promote the use of open standards.

Based upon discussions with hundreds of developers, and our own experience developing for the Open Web, we’ve come up with a proposed set of features along with some high-level goals:

• Ease of Use — the editor experience should not be intimidating and should facilitate quickly getting straight into the code
• Real-time Collaboration — sharing live coding sessions with colleagues should be easy and collaboratively coding with one or more partners should Just Work
• Integrated Command-Line — tools like vi and Emacs have demonstrated the power of integrating command-lines into editors; Bespin needs one, too
• Extensible and Self-Hosted — the interface and capabilities of Bespin should be highly extensible and easily accessible to users through Ubiquity-like commands or via the plug-in API
• Wicked Fast — the editor is just a toy unless it stays smooth and responsive editing files of very large sizes
• Accessible from Anywhere — the code editor should work from anywhere, and from any device, using any modern standards-compliant browser

Introducing Bespin from Dion Almaer on Vimeo.

View Introduction to Bespin

The Initial Prototype

As part of this announcement, we’re also releasing an early experimental prototype to demonstrate some of the concepts of Bespin and the possibilities that it opens up.

Bespin 0.1

• Initial prototype framework that includes support for basic editing features, such as syntax highlighting, large file sizes, undo/redo, previewing files in the browser, importing/exporting projects, etc.

Screenshots of Bespin 0.1 running in modern, standards-compliant browsers

All of the source code underlying the Bespin experiment is being released as open source software under the the MPL.

Get Involved

Mozilla Labs is a virtual lab where people come together online to create, experiment and play with Web innovations for the public benefit. The Bespin experiment is still in its infancy and just getting started. There are many ways to join the team and get involved:

• Play around with the demo and let us know what you think
• Report a bug
• Grab the source code and fix a bug or add a feature
• Discuss, debate and add to the design in the Bespin discussion group
• Join us in #bespin on irc.mozilla.org

– Ben Galbraith and Dion Almaer, on behalf of the Bespin development team