Canmove, confirm
1,953
edits
Changes
→Definition: Added definitions based on https://blog.mozilla.org/privacy/2014/03/05/user-data-you-privacy-for-programmers-2/
<em>Frequently Asked Questions and helpful resources for when, why and how to work open at Mozilla</em>. Got a question? Please add it below! This is a work in progress we're going to tackle together at the 2013 Mozilla Summit.<br>
http://farm9.staticflickr.com/8204/8175049476_798ea876ca_z.jpg
===DefinitionDefinitions===
* What does "working in the open" mean at Mozilla?
* Why does Mozilla do it?
* How has it changed? ====Open vs. Transparent====; transparent : Public, but not necessarily enabling participation.; passively transparent : Not private; decisions aren’t actively hidden, but are difficult to locate. They may not even be documented. This is usually not done intentionally.; actively transparent : Everything is written down, is easily searchable and is locatable by interested parties. This requires intentional, sustained effort.; open : Public ''and'' participatory. This requires structuring efforts so that "outsiders" can meaningfully participate (and become "insiders" as appropriate).
===Successes===
