What does it mean when a project or event is “open?” What is “working open?” There are many definitions, but the one that we often use at Mozilla highlights three open principles:
- Understanding: You aim to make the work you do clear and easy for anyone to comprehend. Examples of how you might design for understanding: avoid jargon or insider terminology when communicating about your work; document processes or outcomes clearly; make decision-making practices transparent and public.
- Sharing: You make the work easy to adapt, reproduce, and spread. Examples of how you might design for sharing: make code, content, or process info from your project available online so others can benefit from it; add an open license so it’s clear exactly how others can reuse or adapt your work.
- Participation & inclusion: You create many ways for others (we call them participants or contributors) to be involved in your work, and welcome a broad diversity of people to do so. Examples of how you might design for participation and inclusion: create clear participation guidelines or codes of conduct so potential contributors know how to engage and what to expect; share leadership by inviting contributors to co-design your event or provide meaningful feedback on a project’s direction; do intentional outreach to invite diverse perspectives and voices into your work.
Why work open? There are so many reasons! By working open, you can:
- improve your outcomes by bringing new, diverse skills and perspectives to your project
- grow a community of enthusiastic supporters of your project
- get more done with the help of contributors
- increase your reach, influence, and impact of your project
What are your reasons for working open? We'd love to know. Tell us here.