Our sense of "open" is that the authority to make decisions about that gets distributed based on merit and understanding and participation and leadership, not solely on employment or a title or a business plan. Technical colleagues will define "open" as "open standards," "interoperable" - you can find it, search it, cut and paste it, view source, mix and match - all those things that we associate with text on the Web, that you can continue to do that with audio and video and whatever's next.

The average consumer does not know the difference between browser, Internet and search box.

Of course, it's hard to support full-time programmers, so we do get funds from a set of companies that are interested in the health of the Mozilla project and so are willing to support the people working for the Foundation as well.

I guess my other advice is that it's really good to be comfortable among groups of men! It's just a very common work setting and I don't actually think about it too much, but there must be some comfort level that I've developed over the years.

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

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.