GH-900 practice question 7 of 15

Which of the following is an Innersource development practice?

Full set: 144 questions
Answer options
A: Adopting open source code into the organization
B: Sharing code between teams within the organization Correct answer
C: Removing open source code from the organization
D: Making all repositories publicly accessible
Correct Answer:
B. Sharing code between teams within the organization
Explanation

Innersource is the practice of applying open-source software development principles and methodologies to proprietary projects within a single organization. The core goal is to break down organizational silos, improve code quality, and foster a culture of internal collaboration. This is achieved by making code visible and accessible across different teams or business units, allowing for contributions, peer review, and code reuse from anyone within the company. Therefore, sharing code between teams is a fundamental Innersource practice.

Why Incorrect

A. Adopting open source code into the organization is known as OSS (Open Source Software) consumption, which is distinct from the internal development methodology of Innersource.
C. Removing open source code is a security or licensing compliance activity, not a collaborative development practice related to Innersource.
D. Making all repositories publicly accessible describes the practice of Open Source, where code is shared with the world, not Innersource, which is confined within an organization. ---

References

1. Riehle, D., et al. (2016). "What is InnerSource?" IEEE Software, 33(2), pp. 6-9. This foundational article defines InnerSource as "the use of open source software development practices...within organizations for the development of its proprietary software," emphasizing internal collaboration over public release. (DOI: https://doi.org/10.1109/MS.2016.42)

2. Stol, K. J., & Fitzgerald, B. (2014). "Inner-sourcing: A new model of software development." In Proceedings of the 3rd International Workshop on Software Engineering for Systems-of-Systems, p. 3. The paper describes Inner-sourcing as a model where "development is opened up to a wider group of people within the organization," directly supporting the concept of sharing code between internal teams. (DOI: https://doi.org/10.1145/2593738.2593742)

3. Wagstrom, P., & Jergensen, N. (2010). "The InnerSource-Process for Internal Software Reuse." Carnegie Mellon University, Institute for Software Research, Technical Report CMU-ISR-10-121, Section 2.1. This report details how InnerSource facilitates collaboration and reuse "between business units" by creating a marketplace for software assets inside the company.

Scroll to Top