872 bytes added,
19:46, 1 October 2013 =How to Work Open at Mozilla: a FAQ=
===Definition===
* What does "working in the open" mean at Mozilla?
* Why does Mozilla do it?
* How has it changed?
===Successes===
* What are examples of how working open has made Mozilla successful?
===Challenges===
* What's hard about working open?
* What if I don't believe in the benefits?
* When there's a conflict between openness and business requirements, how should we navigate that?
* What are some examples of failures / areas we've done badly?
===Strategies and Tactics===
* How do you work open? What are some specific strategies, tactics and best practices?
===Different approaches===
* How do different parts of Mozilla take up working open differently? (e.g., design vs. communications vs. QA) What can we learn from each other?
===Resources====
* What resources do we have available for guidance and help?