{"id":11448,"date":"2018-05-15T13:35:25","date_gmt":"2018-05-15T20:35:25","guid":{"rendered":"https:\/\/blog.mozilla.org\/?p=11448"},"modified":"2018-05-17T04:46:13","modified_gmt":"2018-05-17T11:46:13","slug":"whats-your-open-source-strategy-here-are-10-answers","status":"publish","type":"post","link":"https:\/\/blog.mozilla.org\/blogarchive\/blog\/2018\/05\/15\/whats-your-open-source-strategy-here-are-10-answers\/","title":{"rendered":"What\u2019s Your Open Source Strategy? Here Are 10 Answers\u2026"},"content":{"rendered":"

A research report from Mozilla and Open Tech Strategies provides new perspectives on framing open source strategy. The report builds on Mozilla\u2019s \u201cOpen by Design<\/a>\u201d strategy, which aims to increase the intent and impact of collaborative technology projects.<\/em><\/strong><\/p>\n

Mozilla is a radically open and participatory project<\/a>. As part of the research we compiled into turning openness into a consistent competitive advantage, we identified that the application of open practices<\/a> should always be paired with well-researched strategic intent. Without clarity of purpose, organizations will not (and nor should they) maintain long-term commitment to working with community. Indeed, we were not the first to observe this<\/a>.<\/p>\n

Mozilla benefits from many open practices, but open sourcing software is the foundation on which we build<\/a>. Open source takes many forms at Mozilla. We enjoy a great diversity among the community structures of different Mozilla-driven open source projects, from Rust<\/a> to Coral<\/a> to Firefox (there are actually multiple distinct Firefox communities<\/a>) and to others.<\/p>\n

The basic freedoms offered by Mozilla\u2019s open source projects\u200a\u2014\u200athe famous \u201cFour Freedoms\u201d<\/a> originally defined by the FSF\u200a\u2014\u200aare unambiguous. But they only define the rights conveyed by the software\u2019s license. People often have expectations that go well beyond that strict definition: expectations about development models, business models, community structure, even tool chains. It is even not uncommon for open source projects to be criticised<\/a> for failing to comply with those unspoken expectations.<\/p>\n

We recognize that there is no one true model. As Mozilla evolves more and more into a multi-product organization, there will be different models that suit different products and different environments. Structure, governance, and licensing policies should all be explicit choices based on the strategic goals of an open source project. A challenge for any organization is how to articulate these choices, or to put it simply, how do you answer the question, \u201cwhat kind of open source project is this?\u201d.<\/p>\n

To answer the question, we wanted to develop a set of basic models\u200a\u2014\u200a\u201carchetypes\u201d\u200a\u2014\u200athat projects could aim for, modifying them as needed, but providing a shared vocabulary for discussing how to think about any given project. We were delighted to be able to partner with one of the leading authorities in open source, Open Tech Strategies<\/a>, in defining these archetypes. Their depth of knowledge and fresh perspective has created something we believe offers unique value.<\/p>\n

The resulting framework consists of 10 common archetypes, covering things from business objectives to licensing, community standards, component coupling and project governance. It also contains some practical advice on how to use the framework and on how to set up your project.<\/p>\n

20 years after the Open Source Initiative was founded, open source is widespread (and has inspired methods of peer production beyond the realm of software). Although this report was tailored to advance open source strategies and project design within Mozilla, and with the organizations and communities we work with, we also believe that this challenge is not unique to us. We suspect there will be many other organizations, both commercial and non-commercial, who will benefit from the model.<\/p>\n