We've always been the development project that lived in a time pressured setting and always where commercial entities were relying heavily on releases in a certain time frame.

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

I've learned that for many people, change is uncomfortable. Maybe they want to go through it, and they can see the benefit of it, but at a gut level, change is uncomfortable.

So many commercial orgs have software where you can come and modify it but they still control everything. And what's controlled is very clearly what's good for their business, or if they're more progressive, their view of what's good for the Internet.

People notice it and they help you participate and see your work included in this project and when we ship our browser, you and millions of other people get to see the fruits of your efforts.

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.

Some period of time later you look up and say, "That concern was right on the mark; it happened exactly as I thought it would." So that's been really helpful to recognize.