We're sorry but this page doesn't work properly without JavaScript enabled. Please enable it to continue.
Feedback

InnerSource and OSPOs: Institutionalizing Open Source Culture Change

Formal Metadata

Title
InnerSource and OSPOs: Institutionalizing Open Source Culture Change
Title of Series
Number of Parts
39
Author
Contributors
N. N.
License
CC Attribution 3.0 Unported:
You are free to use, adapt and copy, distribute and transmit the work or content in adapted or unchanged form for any legal purpose as long as the work is attributed to the author in the manner specified by the author or licensor.
Identifiers
Publisher
Release Date
Language

Content Metadata

Subject Area
Genre
Abstract
Many Open Source Program Offices are exploring InnerSource (using open source methods and practices internally in organizations to create proprietary code) as a step on the path to open source readiness. Some OSPOs find that they can overcome organizational resistance to open source by getting teams to first sharing code internally. Others go as far as to mandate that teams who plan to open source their projects first prove they can build and maintain a community using InnerSource. Some OSPOs are motivated to create InnerSource Programs as a way to bring in learnings from the open source communities into their organizations just because it is just a better way to build software. In this panel session we will examine the trend of InnerSource in OSPOs, why it’s happening and the ways in which OSPOs are using InnerSource as a tool in their toolbox to drive open source culture change.