We have a very active testing community which people don't often think about when you have open source.

What's been most helpful to me is realizing that those times when all the heads in the room turn and look at me as if I was crazy, reinforce my own leadership capability. Because I've been in a number of those settings where I've been right. And I've been right often enough that now when it happens I don't automatically think, "Oh, my, what's wrong with me?" or "Ohhh, I must not be ready for this role," or "They know so much more than I do."

But I think it's always difficult when a product that you're using and accustomed to changes.

We're also looking a lot at graphics and video. We've done a lot on a deep technical level to make sure that the next version of Firefox will have all sorts of new graphics capabilities. And the move from audio to video is just exploding. So those areas in particular, mobile and graphics and video, are really important to making the Web today and tomorrow as open as it can be.

We should probably figure out a new word for this. For us, "open" means transparent, as in "open source" - you're not locked in to what the original creator did. And in our case "open" also means distributed decision making.

The Mozilla project is big in terms of lines of code and complexity.

Money tends to make people suspicious, if there's any money floating around.