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.

You can get anything from Mozilla Firefox-based themes to nature themes to your own photographs.

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.

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.

We’'ve broken the code base into logical chunks, called modules, and the foundation staff delegate authority for the modules to people with the most expertise.

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

Some people are really drawn to technology and I liken them to artists.