Nothing Special   »   [go: up one dir, main page]
Jump to content

Inner source

From Wikipedia, the free encyclopedia

InnerSource is the use of open source software development best practices and the establishment of an open source-like culture within organizations[1] for the development of its non-open-source and/or proprietary software. The term was coined by Tim O'Reilly in 2000[2] in his column.[3]

Motivation

[edit]

Open source is recognized to be capable of delivering high quality software.[4] Furthermore, the open collaboration in open source enables collaboration even between competitors (e.g. ARM and Intel working on Linux kernel on merit-based decisions).

Consequently, software developing organizations want to benefit from its outcomes (the software components and tools), but also from the development practices exercised and established in the open source world.[5]

Used open source practices

[edit]

Besides several practices established in foundations such as Apache Software Foundation, Linux Foundation, and Eclipse Foundation, InnerSource and open source projects require open collaboration, open communication, and a proper quality assurance.

Open collaboration

[edit]

All required development artifacts (e.g. code, documentation, issue tracker, etc.) have to be accessible for all employees of a company leveraging InnerSource. Central software forges are an essential tool for implementing open collaboration.

Based on the principles of open collaboration (egalitarian, meritocratic, and self-organizing) every contributor who is willing to help an InnerSource project is typically welcome. Contributions to InnerSource projects are typically judged meritocratically based on the value they bring to the project. Meritocracy can also be enabled by open communication as decisions are discussed publicly. Although an organization does not necessarily become completely self-organizing to adopt InnerSource, InnerSource allows individuals, organizational units, and project communities a higher degree of self-organization.

Open communication

[edit]

InnerSource projects and programs rely on open communication to make all communication openly accessible for all employees. Open communication is communication that is public (within the company), written, archived, and complete. As consequence of this property, the communication is asynchronous. The goal is to allow any individual or party that has stake or interest in an InnerSource project to participate in the communication. As open communication discussions are archived, a detailed documentation of the software is passively gathered that allows one to go back and revisit historic discussions and decisions.

Quality assurance through separation of contribution from integration

[edit]

A dedicated code review and the separation of contributors and committers (integrators, developers with write access) assures the quality of an open source project, and, therefore, also for an InnerSource project.

Benefits

[edit]

Beyond the quality attributes of open source software the following benefits are reported:[6][7]

More efficient and effective development
Overcoming organizational unit boundaries
  • Cost and risk sharing among organizational units
  • Collaboration across organizational unit boundaries
  • Program-wide information exchange
More successful reuse
  • Use of competences missing at component providers
  • Independence between reusers and providers
  • Relief of component providers
Better software product
More flexible utilization of developers
  • Simplified developer deployment
  • Collaboration of detached developers
Enhanced knowledge management
  • Community-based learning
  • Openness and availability of knowledge
Higher employee motivation

Prevalence

[edit]

Among others the following companies are known for adopting InnerSource:[6]

Key factors for adopting InnerSource

[edit]

InnerSource can be a promising approach for large organizations that develop software. However, it may not be appropriate in all settings. The following nine factors, grouped in three categories, can be consulted to gauge the extent to which InnerSource may be appropriate.[13]

Product factors

[edit]
  • Seed product to attract a community
  • Multiple stakeholders for a variety of contributions
  • Modularity to attract contributors and users

Process and Tools factors

[edit]
  • Practices that support "Bazaar-style" development
  • Practices that support "Bazaar-style" quality assurance
  • Standardization of tools to facilitate collaboration

Organization and Community factors

[edit]
  • Coordination and leadership to support the emergence of an internal meritocracy
  • Transparency to open up the organization
  • Management support and motivation to involve people

References

[edit]
  1. ^ Capraro, Maximilian; Riehle, Dirk (2017-02-06). "InnerSource Definition, Benefits, and Challenges" (PDF). ACM Computing Surveys. 49 (4): 1–36. doi:10.1145/2856821. ISSN 0360-0300. S2CID 5385511. InnerSource (IS) is the use of open source software development practices and the establishment of an open source-like culture within organizations. The organization may still develop proprietary software but internally opens up its development.
  2. ^ ben van 't ende (2016-05-09). "InnerSource: An Open Source Approach to Community Culture". Tim O'Reilly, the founder of O'Reilly Media, coined the term "inner-sourcing" in 2000, describing it as: "the use of open source development techniques within the corporation."
  3. ^ O'Reilly, Tim (2000-12-01). "Open Source and OpenGL". oreilly.com. O'Reilly and Associates. Archived from the original on 2015-02-15. Retrieved 2017-02-22. [W]e've also worked with companies on what we call "inner sourcing" — that is, helping them to use open source development techniques within the corporation.
  4. ^ Kevin Crowston, Kangning Wei, James Howison, Andrea Wiggins (2012), ACM (ed.), "Free/Libre open-source software development: What we know and what we do not know", ACM Computing Surveys (in German), 44 (2): 1–35, doi:10.1145/2089125.2089127, S2CID 2246943{{citation}}: CS1 maint: multiple names: authors list (link)
  5. ^ Stol, Klaas-Jan; Fitzgerald, Brian (2014). "InnerSource—adopting open source development practices within organizations: a tutorial" (PDF). IEEE Software. doi:10.1109/MS.2014.77. hdl:10344/4443. S2CID 1965218. [...] a number of organizations have adopted open source practices to develop their software. [...] Unlike traditional approaches, developers of an InnerSource project do not belong to a single team or department. Instead, anybody within the confines of the organization can become a contributing member of this internal community, either as a user or contributor.
  6. ^ a b Capraro, Maximilian; Riehle, Dirk (2016-12-01). "InnerSource Definition, Benefits, and Challenges". ACM Comput. Surv. 49 (4): 67:1–67:36. doi:10.1145/2856821. ISSN 0360-0300. S2CID 5385511.
  7. ^ Stol, Klaas-Jan; Fitzgerald, Brian (2015-07-01). "InnerSource - Adopting Open Source Development Practices within Organizations: A tutorial" (PDF). IEEE Software. 32 (4): 60–67. doi:10.1109/MS.2014.77. hdl:10344/4443. ISSN 0740-7459. S2CID 1965218.
  8. ^ Microsoft Internal Solorigate Investigation Update.
  9. ^ Oram, Andy (2015). Getting Started with InnerSource. O’Reilly Media, Inc. ISBN 978-1-491-93758-7.
  10. ^ Smith, Jared (2016). Using open source methods for internal software projects. O’Reilly Media, Inc.
  11. ^ Archived at Ghostarchive and the Wayback Machine: Commit San Francisco 2020: Shucking Corporate Oysters-Kickstarting an Innersource Culture @ T-Mobile. YouTube.
  12. ^ "Watch: Creating an InnerSource Hub at Siemens". JFrog. 2020-07-28. Retrieved 2020-12-09.
  13. ^ Stol, K. J.; Avgeriou, P.; Babar, M. A.; Lucas, Y.; Fitzgerald, B. (2014). "Key factors for adopting InnerSource". ACM Transactions on Software Engineering and Methodology. 23 (2): 1. doi:10.1145/2533685. hdl:10344/3897. S2CID 6995068.
Retrieved from "https://en.wikipedia.org/w/index.php?title=Inner_source&oldid=1220236410"