From a060b8efb300eb67149ee4639996af817569a3c9 Mon Sep 17 00:00:00 2001 From: Ana Jimenez Santamaria Date: Mon, 6 Mar 2023 13:40:41 +0100 Subject: [PATCH 01/36] [OSPO Book] add preface and chapter one draft for review Signed-off-by: Ana Jimenez Santamaria --- ospo-book/chapters/00-chapter.md | 27 +++++++++++++++++++++++++++ 1 file changed, 27 insertions(+) create mode 100644 ospo-book/chapters/00-chapter.md diff --git a/ospo-book/chapters/00-chapter.md b/ospo-book/chapters/00-chapter.md new file mode 100644 index 00000000..45f9439c --- /dev/null +++ b/ospo-book/chapters/00-chapter.md @@ -0,0 +1,27 @@ +# What is this book About? + +This book provides a guide to Open Source Programs Offices (OSPOs), to better understand their role in organizations, and the best practices for +establishing and managing an OSPO. The book covers a wide range of topics, including the reasons why organizations may need (or not) an OSPO, the +role of OSPOs in different types of organizations (public, private, small, medium, large), the challenges, antipatterns associated with OSPOs, and the +tools and processes required to establish and manage an effective OSPO. The book also does a brief introduction to assess an organization's readiness +for OSPO. As well as how to’s recommendations: from how to develop open source policies to how to engage with external open source communities. + +# What’s not in this book + +This book is not intended to be a guide to open source software development, nor does it cover the technical aspects of open source software development +in depth. Instead, the book focuses on the organizational and management aspects of open source dynamics within organizations by establishing OSPO roles. + +The book neither provide detailed technical guidance on specific open source software projects, nor does it provide guidance on how to write or contribute +code to open source projects as individuals. + +# Who should read this book? + +This book is intended for any person that wants to better understand the role of OSPOs within an organization. The book may be of interest to any role +in an organization that will be or is currently involved in open source at some level and has direct relationship with OSPO roles (or is in one) or is +likely to have a close relationship with an OSPO in the future. + +* Executives, policy-makers and decision-makers who are responsible for establishing, overseeing, funding or sponsoring an OSPO within an organization. +* Open source program managers and leaders who are responsible for coordinating and managing an organization's open source activities and engagement with external open source communities. +* Developers, researchers, students, professors and engineers who are interested in contributing to open source projects and want to better understand the role of OSPOs within their organization. +* Legal and compliance professionals who are responsible for managing legal issues related to open source software, including licensing and intellectual property. + From b62837467a3aee0c33dff2b3dfe13f42e30da7d7 Mon Sep 17 00:00:00 2001 From: Ana Jimenez Santamaria Date: Mon, 6 Mar 2023 14:05:48 +0100 Subject: [PATCH 02/36] add chapter one draft content for review Signed-off-by: Ana Jimenez Santamaria --- ospo-book/chapters/01-chapter.md | 79 ++++++++++++++++++++++++++++++++ 1 file changed, 79 insertions(+) diff --git a/ospo-book/chapters/01-chapter.md b/ospo-book/chapters/01-chapter.md index 5f23f1e3..64338216 100644 --- a/ospo-book/chapters/01-chapter.md +++ b/ospo-book/chapters/01-chapter.md @@ -1,5 +1,12 @@ # Chapter 1: Introduction to Open Source Program Offices +- [Introduction](#introduction) +- [Open Source and OSPO Readiness Assesment](#open-source-and-ospo-readiness-assesment) - `✅ Assesment` +- [Antipatterns](#antipatterns) - `🚫OSPO Antipatterns` +- [Resources](#resources) - `📚Continue Here` + +## Introduction + Open source technology has become an integral part of modern organizations, offering a range of benefits, including lower costs, increased collaboration, and access to a vast pool of talent and resources. However, with the growing importance of open source, organizations need to be equipped to manage their open source operations effectively, in order to realize these benefits. One solution to this challenge is the creation of an Open Source Program Office (OSPO). An OSPO is a dedicated team or department within an organization that is responsible for managing the organization's open source operations, including the development, distribution, and use of open source software. @@ -18,3 +25,75 @@ The book is structured in a user-friendly and practical manner, with a focus on Whether you're just starting out on your open source journey, or are looking to streamline your existing operations, this book will provide you with the knowledge and tools you need to create and implement a successful Open Source Program Office. In the following chapters, we will explore the key components of an OSPO, and provide practical guidance and best practices on how to create and implement an OSPO within your organization, regardless of your industry or sector. So let's get started! + +# Open Source and OSPO Readiness Assesment + +`✅ Assesment` + +The purpose of this section is to first identify the strengths, weaknesses, and opportunities for improvement within the organization, +and to help determine if an OSPO is the right solution for the organization's needs based on their existing open source engagement level, culture and understanding. + +## Where do Open Source and OSPO converge? + +In the past, open source software was primarily used by small groups of developers and enthusiasts, and there was little need for dedicated organizational units to manage open source activities. However, as open source software has become more prevalent and critical to the operation of many organizations, the need for dedicated OSPOs has become more apparent. + +### Understand existing and desired open source adoption + +Once an organization has assessed the level of open source used, contributed, or produced in the organization and why establishing an OSPO can help an organization manage the risks and opportunities of what open source, open works and collaboration brings, and ensure that its open source activities are effectively managed and aligned with the organization's strategic goals and objectives. + +While this is a book about Open Source Programs Offices (OSPOs), it is important to note that establishing an OSPO is not the starting point for open source operations. Before establishing an OSPO (and keep reading the content of the book), it is critical to assess your organization's level of open source adoption and readiness for open source operations. Open source software adoption varies widely across organizations, and it is important to understand your organization's current level of adoption and the level of knowledge and understanding of open source within your organization. + +Assessing open source adoption is critical because it sets the foundation for successful open source operations. Without proper understanding and adoption of open source, an OSPO may not be effective in achieving the desired outcomes. + +### ☑️ Open Source Software Usage + +Evaluate the level of open source software usage within your organization. Are there any specific open source projects that are widely used? Are there any projects that are critical to the organization's operations? + +### ☑️ Knowledge and Understanding of Open Source + +Evaluate the level of knowledge and understanding of open source within your organization. Are the different actors that will be or are currently involved in open source familiar with open source licensing models and requirements? Do they understand the benefits and risks of using open source software? + +### ☑️ Culture + +Evaluate the culture within your organization to determine if it is conducive to open source operations. Is there a culture of collaboration and sharing? Are the different actors that will be or are currently involved in open source willing to contribute to open source projects? + + +### ☑️ Tools and Processes + +Evaluate the tools and processes in place to support open source operations. Are there any existing tools or processes that can be leveraged for open source operations? Are there any gaps in tools or processes that need to be addressed? + +### ☑️ Addressing Gaps + +Determine if there are any gaps in open source adoption or readiness and develop a plan to address them. This may include training those actors that will be or are currently involved in open source on open source software usage and licensing, developing new tools and processes to support open source operations, or establishing an OSPO to coordinate open source activities. + +### ☑️ Overall, gather input from stakeholders on these areas by asking the folowing questions + +* What does open source means for the organization? +* Is there an open source culture within the organization? +* What are the organization's goals and objectives for using open source? +* How is open source software currently being used and /or created (contirbution) within the organization? +* If any, what are the current policies and procedures for managing open source software within the organization? +* What are the key legal and compliance considerations for using open source software within the organization? +* What are the challenges and opportunities for implementing an OSPO within the organization? +* What resources and support will be needed to successfully implement an OSPO within the organization? + +## Antipatterns + +`🚫OSPO Antipatterns` + +While Open Source Programs Offices (OSPOs) can provide significant benefits for organizations, there are also bad practices that organizations should avoid if they don't want to lead to negative consequences for both the organization and the open source ecosystem. Here is a set of examples that illustrates what an OSPO is not about, and how to avoid common pitfalts: + +* **Establishing an OSPO without proper alignment with organizational goals:** An OSPO should not be established just because it is a trend or because other organizations have them. Without proper alignment, an OSPO can become a waste of time, resources, and money + +* **Viewing an OSPO as a separate silo within the organization:** it should be integrated into the organization's existing structure and collaborate with other teams to achieve common goals + +* **Viewing an OSPO as a legal or compliance function only:** Instead, it should be recognized as a strategic entity within the organization that contributes to the organization's overall goals and objectives while keeping in mind the value and rights of the open source community. + +* **Viewing an OSPO as a one-size-fits-all solution:** It's important to evaluate the benefits and costs of establishing an OSPO and determine if it's the right fit for your organization's goals and objectives. + + +## Resources + +`📚Continue Here` + +Additional resources useful to continue evaluating open source usage, contribution, creation, and leadership: [provide a set of resources] From 82b11b8839d55a5eb4179b71da2345b98892391c Mon Sep 17 00:00:00 2001 From: Ana Jimenez Santamaria Date: Tue, 7 Mar 2023 22:45:54 +0100 Subject: [PATCH 03/36] add ospo definition section within intro Signed-off-by: Ana Jimenez Santamaria --- ospo-book/chapters/01-chapter.md | 61 +++++++++++++++----------------- 1 file changed, 29 insertions(+), 32 deletions(-) diff --git a/ospo-book/chapters/01-chapter.md b/ospo-book/chapters/01-chapter.md index 64338216..a2fc3687 100644 --- a/ospo-book/chapters/01-chapter.md +++ b/ospo-book/chapters/01-chapter.md @@ -1,11 +1,11 @@ # Chapter 1: Introduction to Open Source Program Offices - [Introduction](#introduction) -- [Open Source and OSPO Readiness Assesment](#open-source-and-ospo-readiness-assesment) - `✅ Assesment` -- [Antipatterns](#antipatterns) - `🚫OSPO Antipatterns` -- [Resources](#resources) - `📚Continue Here` +- [Assessing Readiness for Open Source and OSPO](#assessing-readiness-for-open-source-and-ospo) - `✅ Assesment` +- [Antipatterns](#antipatterns) - `🚫 OSPO Antipatterns` +- [Resources](#resources) - `📚 Continue Here` -## Introduction +# Introduction Open source technology has become an integral part of modern organizations, offering a range of benefits, including lower costs, increased collaboration, and access to a vast pool of talent and resources. However, with the growing importance of open source, organizations need to be equipped to manage their open source operations effectively, in order to realize these benefits. @@ -26,7 +26,15 @@ Whether you're just starting out on your open source journey, or are looking to In the following chapters, we will explore the key components of an OSPO, and provide practical guidance and best practices on how to create and implement an OSPO within your organization, regardless of your industry or sector. So let's get started! -# Open Source and OSPO Readiness Assesment +## OSPO Definition + +An Open Source Program Office (OSPO) is a center of expertise, either virtual or physical, that supports, nurtures, shares, explains, and grows open source within an organization. OSPOs are typically responsible for defining and implementing strategies and policies that guide open source efforts and provide tools, processes, and knowledge to organization teams and experts in navigating open source without harming the open source ecosystem. Instead, they help to sustain it while achieving organizational goals. + +OSPOs may set policies related to code use, distribution, selection, auditing, and other key areas. They may also provide education and training to internal and external stakeholders involved in open source activities, ensure legal compliance, and promote community engagement. + +> Important Considerations in Defining an Open Source Program Office (OSPO): OSPOs vary in Sector, Region, and Organizational Size; May Exclude the Term 'Program' to become 'Open Source Office'; and No Two OSPOs are Alike. + +# Assessing Readiness for Open Source and OSPO `✅ Assesment` @@ -45,41 +53,30 @@ While this is a book about Open Source Programs Offices (OSPOs), it is important Assessing open source adoption is critical because it sets the foundation for successful open source operations. Without proper understanding and adoption of open source, an OSPO may not be effective in achieving the desired outcomes. -### ☑️ Open Source Software Usage - -Evaluate the level of open source software usage within your organization. Are there any specific open source projects that are widely used? Are there any projects that are critical to the organization's operations? - -### ☑️ Knowledge and Understanding of Open Source - -Evaluate the level of knowledge and understanding of open source within your organization. Are the different actors that will be or are currently involved in open source familiar with open source licensing models and requirements? Do they understand the benefits and risks of using open source software? - -### ☑️ Culture - -Evaluate the culture within your organization to determine if it is conducive to open source operations. Is there a culture of collaboration and sharing? Are the different actors that will be or are currently involved in open source willing to contribute to open source projects? - +* **☑️ Open Source Software (or open works) Usage:** Evaluate the level of open source software usage within your organization. Are there any specific open source projects that are widely used? Are there any projects that are critical to the organization's operations? -### ☑️ Tools and Processes +* **☑️ Knowledge and Understanding of Open Source:** Evaluate the level of knowledge and understanding of open source within your organization. Are the different actors that will be or are currently involved in open source familiar with open source licensing models and requirements? Do they understand the benefits and risks of using open source software? -Evaluate the tools and processes in place to support open source operations. Are there any existing tools or processes that can be leveraged for open source operations? Are there any gaps in tools or processes that need to be addressed? +* **☑️ Culture:** Evaluate the culture within your organization to determine if it is conducive to open source operations. Is there a culture of collaboration and sharing? Are the different actors that will be or are currently involved in open source willing to contribute to open source projects? -### ☑️ Addressing Gaps +* **☑️ Tools and Processes:** Evaluate the tools and processes in place to support open source operations. Are there any existing tools or processes that can be leveraged for open source operations? Are there any gaps in tools or processes that need to be addressed? -Determine if there are any gaps in open source adoption or readiness and develop a plan to address them. This may include training those actors that will be or are currently involved in open source on open source software usage and licensing, developing new tools and processes to support open source operations, or establishing an OSPO to coordinate open source activities. +* **☑️ Addressing Gaps:** Determine if there are any gaps in open source adoption or readiness and develop a plan to address them. This may include training those actors that will be or are currently involved in open source on open source software usage and licensing, developing new tools and processes to support open source operations, or establishing an OSPO to coordinate open source activities. -### ☑️ Overall, gather input from stakeholders on these areas by asking the folowing questions +* **☑️ Overall, gather input from stakeholders on these areas** by asking the folowing questions -* What does open source means for the organization? -* Is there an open source culture within the organization? -* What are the organization's goals and objectives for using open source? -* How is open source software currently being used and /or created (contirbution) within the organization? -* If any, what are the current policies and procedures for managing open source software within the organization? -* What are the key legal and compliance considerations for using open source software within the organization? -* What are the challenges and opportunities for implementing an OSPO within the organization? -* What resources and support will be needed to successfully implement an OSPO within the organization? + * What does open source means for the organization? + * Is there an open source culture within the organization? + * What are the organization's goals and objectives for using open source? + * How is open source software currently being used and /or created (contirbution) within the organization? + * If any, what are the current policies and procedures for managing open source software within the organization? + * What are the key legal and compliance considerations for using open source software within the organization? + * What are the challenges and opportunities for implementing an OSPO within the organization? + * What resources and support will be needed to successfully implement an OSPO within the organization? ## Antipatterns -`🚫OSPO Antipatterns` +`🚫 OSPO Antipatterns` While Open Source Programs Offices (OSPOs) can provide significant benefits for organizations, there are also bad practices that organizations should avoid if they don't want to lead to negative consequences for both the organization and the open source ecosystem. Here is a set of examples that illustrates what an OSPO is not about, and how to avoid common pitfalts: @@ -94,6 +91,6 @@ While Open Source Programs Offices (OSPOs) can provide significant benefits for ## Resources -`📚Continue Here` +`📚 Continue Here` Additional resources useful to continue evaluating open source usage, contribution, creation, and leadership: [provide a set of resources] From 979e3f40ba717275f875a06ed486abc6935b45a4 Mon Sep 17 00:00:00 2001 From: Ana Jimenez Santamaria Date: Thu, 9 Mar 2023 08:58:45 +0100 Subject: [PATCH 04/36] include history, roots and impact section Signed-off-by: Ana Jimenez Santamaria --- ospo-book/chapters/01-chapter.md | 26 +++++++++++++++++++++++--- 1 file changed, 23 insertions(+), 3 deletions(-) diff --git a/ospo-book/chapters/01-chapter.md b/ospo-book/chapters/01-chapter.md index a2fc3687..c4441f82 100644 --- a/ospo-book/chapters/01-chapter.md +++ b/ospo-book/chapters/01-chapter.md @@ -14,7 +14,6 @@ In this book, we will guide organizations through the process of creating and im The book is structured in a user-friendly and practical manner, with a focus on providing actionable advice and steps that organizations can take to create and implement an OSPO. The book will cover a range of topics, including: -* Encouraging Organizations to treat Open Source as a commodity * Understanding the value of open source program offices within organizations * Learning how to be involved in open source program operations on a daily basis * Gathering the ingredients for a minimum viable OSPO @@ -28,9 +27,30 @@ In the following chapters, we will explore the key components of an OSPO, and pr ## OSPO Definition -An Open Source Program Office (OSPO) is a center of expertise, either virtual or physical, that supports, nurtures, shares, explains, and grows open source within an organization. OSPOs are typically responsible for defining and implementing strategies and policies that guide open source efforts and provide tools, processes, and knowledge to organization teams and experts in navigating open source without harming the open source ecosystem. Instead, they help to sustain it while achieving organizational goals. +An *Open Source Program Office (OSPO)* is a center of expertise, either virtual or physical, that supports, nurtures, shares, explains, and grows open source within an organization. An OSPO *role* can be conceived as an umbrella term, covering the responsibilities for defining and implementing strategies and policies that guide open source efforts and provide tools, processes, and knowledge to organization teams and experts in navigating open source without harming the open source ecosystem. Instead, they help to sustain it while achieving organizational goals. -OSPOs may set policies related to code use, distribution, selection, auditing, and other key areas. They may also provide education and training to internal and external stakeholders involved in open source activities, ensure legal compliance, and promote community engagement. + OSPOs (as center of expertise) may comprise a framework built around some or all of the following aspects: + +* Set policies related to code use, distribution, selection, auditing, and other key areas +* Provide education and training to internal and external stakeholders involved in open source activities +* Ensure legal compliance +* Promote community engagement + +The impacts of an OSPO role for an organization can include: + +* Open Source Enabler: OSPOs can help organizations navigate the cultural, process, and tool changes required to engage with the open source community effectively. This can involve educating employees, establishing new processes and workflows, and adopting new tools and technologies. + +* Open Source Counselor: OSPOs can provide guidance and advice on the latest open source trends, licensing issues, and how to engage with open source projects, foundations, and communities. This can help organizations stay up-to-date with the rapidly changing open source landscape and ensure they are making informed decisions. + +* Open Source Advocate: OSPOs can promote the use of open source software and best practices across different organizational units. This can help organizations realize the benefits of open source, such as increased collaboration, faster innovation, and reduced costs. + +* Open Source Environmentalist: OSPOs can help organizations support and sustain open source projects in the long term by addressing issues such as security, maintenance, and contributions. This can involve establishing policies and procedures for code review, security vulnerability management, and ongoing maintenance and support. By doing so, OSPOs can help ensure that open source projects remain healthy and continue to benefit the wider community. + +## History and Roots + +The OSPO concept initially started within the corporate world and is now about two decades old, but really started to accelerate in the last decade or so. Most prominent technology infrastructure firms (e.g., Amazon, VMware, Cisco) and consumer technology companies (e.g., Apple, Google, Facebook) ended up having an OSPOs or formal open source programs. All are encouraging their employees to contribute to open source projects that are strategic to their business and security. + +The term started becoming more mainstream and diverse in the last years, as more organizations from different sectors and regions included dedicated open source roles in their organization to manage open source operations and strategy. Nowadays, we can find OSPOs being formed in different regions (APAC, EMEA, AMER) and entities, such as Governments, Enterprises, NGOs, Universities and more. > Important Considerations in Defining an Open Source Program Office (OSPO): OSPOs vary in Sector, Region, and Organizational Size; May Exclude the Term 'Program' to become 'Open Source Office'; and No Two OSPOs are Alike. From 4bd2cbb450496a9fce2d2c48a90466faa77905d0 Mon Sep 17 00:00:00 2001 From: Ana Jimenez Santamaria Date: Thu, 9 Mar 2023 15:13:41 +0100 Subject: [PATCH 05/36] improve ospo as a role description Signed-off-by: Ana Jimenez Santamaria --- ospo-book/chapters/01-chapter.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/ospo-book/chapters/01-chapter.md b/ospo-book/chapters/01-chapter.md index c4441f82..4c29977f 100644 --- a/ospo-book/chapters/01-chapter.md +++ b/ospo-book/chapters/01-chapter.md @@ -36,15 +36,15 @@ An *Open Source Program Office (OSPO)* is a center of expertise, either virtual * Ensure legal compliance * Promote community engagement -The impacts of an OSPO role for an organization can include: +OSPO (as a role) can include: -* Open Source Enabler: OSPOs can help organizations navigate the cultural, process, and tool changes required to engage with the open source community effectively. This can involve educating employees, establishing new processes and workflows, and adopting new tools and technologies. +* Open Source Enabler: OSPOs can help organizations navigate the cultural, process, and tool changes required to engage with the open source community effectively. This can involve educating teams/ units, establishing new processes and workflows, and adopting new tools and technologies. * Open Source Counselor: OSPOs can provide guidance and advice on the latest open source trends, licensing issues, and how to engage with open source projects, foundations, and communities. This can help organizations stay up-to-date with the rapidly changing open source landscape and ensure they are making informed decisions. -* Open Source Advocate: OSPOs can promote the use of open source software and best practices across different organizational units. This can help organizations realize the benefits of open source, such as increased collaboration, faster innovation, and reduced costs. +* Open Source Advocate: OSPOs can promote the use and/or contribution of open source and best practices across different organizational units. This can help organizations realize the benefits of open source as well as engaging people to contribute to open source projects or start new ones. -* Open Source Environmentalist: OSPOs can help organizations support and sustain open source projects in the long term by addressing issues such as security, maintenance, and contributions. This can involve establishing policies and procedures for code review, security vulnerability management, and ongoing maintenance and support. By doing so, OSPOs can help ensure that open source projects remain healthy and continue to benefit the wider community. +* Open Source Environmentalist: OSPOs can help organizations support and sustain open source projects in the long term by addressing issues such as security, maintenance, and project health. This can involve establishing policies and procedures for code review, security vulnerability management, and ongoing maintenance and support through funding and/or contributions. By doing so, OSPOs can help ensure that open source projects remain healthy and continue to benefit the wider community. ## History and Roots From 56266d512c55e18979500fd04f331f3395ac0a78 Mon Sep 17 00:00:00 2001 From: Ana Jimenez Santamaria Date: Thu, 9 Mar 2023 20:25:52 +0100 Subject: [PATCH 06/36] include knowledge transmission topic in chapter one Signed-off-by: Ana Jimenez Santamaria --- ospo-book/chapters/01-chapter.md | 20 ++++++++++++++++++++ 1 file changed, 20 insertions(+) diff --git a/ospo-book/chapters/01-chapter.md b/ospo-book/chapters/01-chapter.md index 4c29977f..86288cab 100644 --- a/ospo-book/chapters/01-chapter.md +++ b/ospo-book/chapters/01-chapter.md @@ -93,6 +93,26 @@ Assessing open source adoption is critical because it sets the foundation for su * What are the key legal and compliance considerations for using open source software within the organization? * What are the challenges and opportunities for implementing an OSPO within the organization? * What resources and support will be needed to successfully implement an OSPO within the organization? + +### Understand knowledge transmission through the eyes of OSPO + +> RE ML disussion: https://lists.todogroup.org/g/ospo-book-project/message/5 + +If the organization decide to establish an OSPO (as entity) or integrate OSPO roles, it is crucial to assess the transmission of knowledge to different internal and external *open source players* that have a direct or indirect impact on the OSPO. This section examines the OSPO from four different perspectives: + +* Looking downward: as the head of an OSPO, managing the team's tasks is a fundamental responsibility. Depending on the OSPO's objectives, the team's responsibilities may vary, but effective management is essential. + +* Looking upward: if proposing the creation of an OSPO, managing expectations and aligning with executives' technology needs is necessary. + +* Looking sideways: collaboration with other teams is critical. For instance, in business-oriented OSPOs, collaborating with the dev tools and security teams is necessary. + +* Looking outside: representing the organization to external communities and foundations is crucial. The integration strategy must align with the organization's objectives and vision. + +As an example, the following [diagram](https://lists.todogroup.org/g/ospo-book-project/message/5) illustrates the various players in a business-oriented OSPO and the different methods of interaction, communication, and knowledge transmission. + +img2 + +In Chapters 3 and 6, we will delve deeper into how an OSPO can effectively address knowledge transmission across various open source players and highlight some best practices utilized by different organizations. ## Antipatterns From 8fe07ff43b51a5f801a13f4889f00d0a29b41458 Mon Sep 17 00:00:00 2001 From: Justin Dorfman Date: Wed, 15 Mar 2023 17:06:16 -0700 Subject: [PATCH 07/36] Update ospo-book/chapters/00-chapter.md Co-authored-by: Ildiko Vancsa Signed-off-by: Justin Dorfman --- ospo-book/chapters/00-chapter.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/ospo-book/chapters/00-chapter.md b/ospo-book/chapters/00-chapter.md index 45f9439c..a4259209 100644 --- a/ospo-book/chapters/00-chapter.md +++ b/ospo-book/chapters/00-chapter.md @@ -1,4 +1,4 @@ -# What is this book About? +# What is this book about? This book provides a guide to Open Source Programs Offices (OSPOs), to better understand their role in organizations, and the best practices for establishing and managing an OSPO. The book covers a wide range of topics, including the reasons why organizations may need (or not) an OSPO, the From 969a85b7ceb7f05219ffb739cbd010c98761c85a Mon Sep 17 00:00:00 2001 From: Ana Jimenez Santamaria Date: Thu, 16 Mar 2023 15:20:01 +0100 Subject: [PATCH 08/36] Update ospo-book/chapters/00-chapter.md Co-authored-by: Gergely Csatari Signed-off-by: Ana Jimenez Santamaria --- ospo-book/chapters/00-chapter.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/ospo-book/chapters/00-chapter.md b/ospo-book/chapters/00-chapter.md index a4259209..7c8bf933 100644 --- a/ospo-book/chapters/00-chapter.md +++ b/ospo-book/chapters/00-chapter.md @@ -4,7 +4,7 @@ This book provides a guide to Open Source Programs Offices (OSPOs), to better un establishing and managing an OSPO. The book covers a wide range of topics, including the reasons why organizations may need (or not) an OSPO, the role of OSPOs in different types of organizations (public, private, small, medium, large), the challenges, antipatterns associated with OSPOs, and the tools and processes required to establish and manage an effective OSPO. The book also does a brief introduction to assess an organization's readiness -for OSPO. As well as how to’s recommendations: from how to develop open source policies to how to engage with external open source communities. +for having an OSPO. As well as how to’s recommendations: from how to develop open source policies to how to engage with external open source communities. # What’s not in this book From 015dc87e912d734980f6943f95f42cad8305a878 Mon Sep 17 00:00:00 2001 From: Ana Jimenez Santamaria Date: Thu, 16 Mar 2023 15:21:49 +0100 Subject: [PATCH 09/36] Update ospo-book/chapters/00-chapter.md Co-authored-by: Ildiko Vancsa Signed-off-by: Ana Jimenez Santamaria --- ospo-book/chapters/00-chapter.md | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/ospo-book/chapters/00-chapter.md b/ospo-book/chapters/00-chapter.md index 7c8bf933..6a4cd079 100644 --- a/ospo-book/chapters/00-chapter.md +++ b/ospo-book/chapters/00-chapter.md @@ -11,8 +11,7 @@ for having an OSPO. As well as how to’s recommendations: from how to develop o This book is not intended to be a guide to open source software development, nor does it cover the technical aspects of open source software development in depth. Instead, the book focuses on the organizational and management aspects of open source dynamics within organizations by establishing OSPO roles. -The book neither provide detailed technical guidance on specific open source software projects, nor does it provide guidance on how to write or contribute -code to open source projects as individuals. +Providing guidance on how to deploy, use and contribute to specific open source software projects is also out of the scope of this book. # Who should read this book? From d182d61273f5bba0c97df51d271a5ed8e27dfa70 Mon Sep 17 00:00:00 2001 From: Ana Jimenez Santamaria Date: Thu, 16 Mar 2023 15:23:27 +0100 Subject: [PATCH 10/36] Update ospo-book/chapters/00-chapter.md Co-authored-by: Gergely Csatari Signed-off-by: Ana Jimenez Santamaria --- ospo-book/chapters/00-chapter.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/ospo-book/chapters/00-chapter.md b/ospo-book/chapters/00-chapter.md index 6a4cd079..cf91293f 100644 --- a/ospo-book/chapters/00-chapter.md +++ b/ospo-book/chapters/00-chapter.md @@ -20,7 +20,7 @@ in an organization that will be or is currently involved in open source at some likely to have a close relationship with an OSPO in the future. * Executives, policy-makers and decision-makers who are responsible for establishing, overseeing, funding or sponsoring an OSPO within an organization. -* Open source program managers and leaders who are responsible for coordinating and managing an organization's open source activities and engagement with external open source communities. +* Open source program managers and leaders who are responsible for coordinating and managing an organization's open source activities and engagement with open source communities. * Developers, researchers, students, professors and engineers who are interested in contributing to open source projects and want to better understand the role of OSPOs within their organization. * Legal and compliance professionals who are responsible for managing legal issues related to open source software, including licensing and intellectual property. From 4cb0a81ae5c5be308a8bb625cad3372f1f0af1f8 Mon Sep 17 00:00:00 2001 From: Ana Jimenez Santamaria Date: Thu, 16 Mar 2023 15:24:00 +0100 Subject: [PATCH 11/36] Update ospo-book/chapters/01-chapter.md Co-authored-by: Georg Kunz Signed-off-by: Ana Jimenez Santamaria --- ospo-book/chapters/01-chapter.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/ospo-book/chapters/01-chapter.md b/ospo-book/chapters/01-chapter.md index 86288cab..3e63192e 100644 --- a/ospo-book/chapters/01-chapter.md +++ b/ospo-book/chapters/01-chapter.md @@ -1,7 +1,7 @@ # Chapter 1: Introduction to Open Source Program Offices - [Introduction](#introduction) -- [Assessing Readiness for Open Source and OSPO](#assessing-readiness-for-open-source-and-ospo) - `✅ Assesment` +- [Assessing Readiness for Open Source and OSPO](#assessing-readiness-for-open-source-and-ospo) - `✅ Assessment` - [Antipatterns](#antipatterns) - `🚫 OSPO Antipatterns` - [Resources](#resources) - `📚 Continue Here` From 8ea3d27b1bad92b02f5647ab119c2a0db654dd51 Mon Sep 17 00:00:00 2001 From: Ana Jimenez Santamaria Date: Thu, 16 Mar 2023 15:25:19 +0100 Subject: [PATCH 12/36] Update ospo-book/chapters/01-chapter.md Co-authored-by: Ildiko Vancsa Signed-off-by: Ana Jimenez Santamaria --- ospo-book/chapters/01-chapter.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/ospo-book/chapters/01-chapter.md b/ospo-book/chapters/01-chapter.md index 3e63192e..4f04e8be 100644 --- a/ospo-book/chapters/01-chapter.md +++ b/ospo-book/chapters/01-chapter.md @@ -10,7 +10,7 @@ Open source technology has become an integral part of modern organizations, offering a range of benefits, including lower costs, increased collaboration, and access to a vast pool of talent and resources. However, with the growing importance of open source, organizations need to be equipped to manage their open source operations effectively, in order to realize these benefits. One solution to this challenge is the creation of an Open Source Program Office (OSPO). An OSPO is a dedicated team or department within an organization that is responsible for managing the organization's open source operations, including the development, distribution, and use of open source software. -In this book, we will guide organizations through the process of creating and implementing an OSPO, providing practical advice and best practices on how to streamline open source operations, and ensuring that organizations are able to maximize the benefits of open source technology. +In this book, we will guide organizations through the process of creating and implementing an OSPO. We will provide practical advice and best practices on how to streamline open source operations, and ensuring that organizations are able to maximize the benefits of open source technology, while being good open source citizens. The book is structured in a user-friendly and practical manner, with a focus on providing actionable advice and steps that organizations can take to create and implement an OSPO. The book will cover a range of topics, including: From 802f9bbd7e0002b91dbbc60ef25b1a28b0803fe4 Mon Sep 17 00:00:00 2001 From: Ana Jimenez Santamaria Date: Thu, 16 Mar 2023 15:26:35 +0100 Subject: [PATCH 13/36] Update ospo-book/chapters/01-chapter.md Co-authored-by: Gergely Csatari Signed-off-by: Ana Jimenez Santamaria --- ospo-book/chapters/01-chapter.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/ospo-book/chapters/01-chapter.md b/ospo-book/chapters/01-chapter.md index 4f04e8be..7393eee9 100644 --- a/ospo-book/chapters/01-chapter.md +++ b/ospo-book/chapters/01-chapter.md @@ -14,7 +14,7 @@ In this book, we will guide organizations through the process of creating and im The book is structured in a user-friendly and practical manner, with a focus on providing actionable advice and steps that organizations can take to create and implement an OSPO. The book will cover a range of topics, including: -* Understanding the value of open source program offices within organizations +* Understanding the value of OSPOs within organizations * Learning how to be involved in open source program operations on a daily basis * Gathering the ingredients for a minimum viable OSPO * Best practices for creating and implementing an open source strategy From 82cfd08c1c7c5e014351193ca69c7f2716daafbc Mon Sep 17 00:00:00 2001 From: Ana Jimenez Santamaria Date: Thu, 16 Mar 2023 15:27:51 +0100 Subject: [PATCH 14/36] Update ospo-book/chapters/01-chapter.md Co-authored-by: Georg Kunz Signed-off-by: Ana Jimenez Santamaria --- ospo-book/chapters/01-chapter.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/ospo-book/chapters/01-chapter.md b/ospo-book/chapters/01-chapter.md index 7393eee9..a07993d2 100644 --- a/ospo-book/chapters/01-chapter.md +++ b/ospo-book/chapters/01-chapter.md @@ -48,7 +48,7 @@ OSPO (as a role) can include: ## History and Roots -The OSPO concept initially started within the corporate world and is now about two decades old, but really started to accelerate in the last decade or so. Most prominent technology infrastructure firms (e.g., Amazon, VMware, Cisco) and consumer technology companies (e.g., Apple, Google, Facebook) ended up having an OSPOs or formal open source programs. All are encouraging their employees to contribute to open source projects that are strategic to their business and security. +The OSPO concept initially started within the corporate world about two decades ago, but adoption accelerated signficantly in the last decade. Most prominent technology infrastructure firms (e.g., Amazon, VMware, Cisco) and consumer technology companies (e.g., Apple, Google, Facebook) created OSPOs or formal open source programs. All are encouraging their employees to contribute to open source projects that are strategic to their business and security. The term started becoming more mainstream and diverse in the last years, as more organizations from different sectors and regions included dedicated open source roles in their organization to manage open source operations and strategy. Nowadays, we can find OSPOs being formed in different regions (APAC, EMEA, AMER) and entities, such as Governments, Enterprises, NGOs, Universities and more. From b13a6eb867933f08a11a68f11b97c64486b50697 Mon Sep 17 00:00:00 2001 From: Ana Jimenez Santamaria Date: Thu, 16 Mar 2023 15:28:10 +0100 Subject: [PATCH 15/36] Update ospo-book/chapters/01-chapter.md Co-authored-by: Georg Kunz Signed-off-by: Ana Jimenez Santamaria --- ospo-book/chapters/01-chapter.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/ospo-book/chapters/01-chapter.md b/ospo-book/chapters/01-chapter.md index a07993d2..fe05b86c 100644 --- a/ospo-book/chapters/01-chapter.md +++ b/ospo-book/chapters/01-chapter.md @@ -56,7 +56,7 @@ The term started becoming more mainstream and diverse in the last years, as more # Assessing Readiness for Open Source and OSPO -`✅ Assesment` +`✅ Assessment` The purpose of this section is to first identify the strengths, weaknesses, and opportunities for improvement within the organization, and to help determine if an OSPO is the right solution for the organization's needs based on their existing open source engagement level, culture and understanding. From 267c30d432b4f1d48f731524586d4794e01c9386 Mon Sep 17 00:00:00 2001 From: Ana Jimenez Santamaria Date: Thu, 16 Mar 2023 15:36:29 +0100 Subject: [PATCH 16/36] Update ospo-book/chapters/01-chapter.md Co-authored-by: Ildiko Vancsa Signed-off-by: Ana Jimenez Santamaria --- ospo-book/chapters/01-chapter.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/ospo-book/chapters/01-chapter.md b/ospo-book/chapters/01-chapter.md index fe05b86c..474a8e5e 100644 --- a/ospo-book/chapters/01-chapter.md +++ b/ospo-book/chapters/01-chapter.md @@ -118,7 +118,7 @@ In Chapters 3 and 6, we will delve deeper into how an OSPO can effectively addre `🚫 OSPO Antipatterns` -While Open Source Programs Offices (OSPOs) can provide significant benefits for organizations, there are also bad practices that organizations should avoid if they don't want to lead to negative consequences for both the organization and the open source ecosystem. Here is a set of examples that illustrates what an OSPO is not about, and how to avoid common pitfalts: +While Open Source Programs Offices (OSPOs) can provide significant benefits for organizations, there are also bad practices that organizations should avoid if they don't want to lead to negative consequences for both the organization and the open source ecosystem. Here is a set of examples that illustrates what an OSPO is not about, and how to avoid common pitfalls: * **Establishing an OSPO without proper alignment with organizational goals:** An OSPO should not be established just because it is a trend or because other organizations have them. Without proper alignment, an OSPO can become a waste of time, resources, and money From fe42490c586c4cdcb7d823c4ed323994c0724ffc Mon Sep 17 00:00:00 2001 From: Ana Jimenez Santamaria Date: Wed, 22 Mar 2023 10:47:47 +0100 Subject: [PATCH 17/36] Update ospo-book/chapters/00-chapter.md Signed-off-by: Ana Jimenez Santamaria --- ospo-book/chapters/00-chapter.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/ospo-book/chapters/00-chapter.md b/ospo-book/chapters/00-chapter.md index cf91293f..f7e905f2 100644 --- a/ospo-book/chapters/00-chapter.md +++ b/ospo-book/chapters/00-chapter.md @@ -9,7 +9,7 @@ for having an OSPO. As well as how to’s recommendations: from how to develop o # What’s not in this book This book is not intended to be a guide to open source software development, nor does it cover the technical aspects of open source software development -in depth. Instead, the book focuses on the organizational and management aspects of open source dynamics within organizations by establishing OSPO roles. +in depth. Providing guidance on how to deploy, use and contribute to specific open source software projects is also out of the scope of this book. From 4058307ce07191d7e7d46dbeebf929566817a3c8 Mon Sep 17 00:00:00 2001 From: Ana Jimenez Santamaria Date: Wed, 22 Mar 2023 10:50:19 +0100 Subject: [PATCH 18/36] Update ospo-book/chapters/01-chapter.md Co-authored-by: Ildiko Vancsa Signed-off-by: Ana Jimenez Santamaria --- ospo-book/chapters/01-chapter.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/ospo-book/chapters/01-chapter.md b/ospo-book/chapters/01-chapter.md index 474a8e5e..30b07100 100644 --- a/ospo-book/chapters/01-chapter.md +++ b/ospo-book/chapters/01-chapter.md @@ -9,7 +9,7 @@ Open source technology has become an integral part of modern organizations, offering a range of benefits, including lower costs, increased collaboration, and access to a vast pool of talent and resources. However, with the growing importance of open source, organizations need to be equipped to manage their open source operations effectively, in order to realize these benefits. -One solution to this challenge is the creation of an Open Source Program Office (OSPO). An OSPO is a dedicated team or department within an organization that is responsible for managing the organization's open source operations, including the development, distribution, and use of open source software. +Creating an Open Source Program Office (OSPO) can accelerate a company's or organization's open source journey from mindset change to efficient policies and workflows. An OSPO is a dedicated team or department within an organization that is responsible for managing the organization's open source operations, including the development, distribution, and use of open source software, and harmonizing and integrating these with product development. In this book, we will guide organizations through the process of creating and implementing an OSPO. We will provide practical advice and best practices on how to streamline open source operations, and ensuring that organizations are able to maximize the benefits of open source technology, while being good open source citizens. The book is structured in a user-friendly and practical manner, with a focus on providing actionable advice and steps that organizations can take to create and implement an OSPO. The book will cover a range of topics, including: From b523f4b26ec8c42e33b56e70843cbca6cc08048a Mon Sep 17 00:00:00 2001 From: Ana Jimenez Santamaria Date: Wed, 22 Mar 2023 10:50:44 +0100 Subject: [PATCH 19/36] Update ospo-book/chapters/01-chapter.md Co-authored-by: Ildiko Vancsa Signed-off-by: Ana Jimenez Santamaria --- ospo-book/chapters/01-chapter.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/ospo-book/chapters/01-chapter.md b/ospo-book/chapters/01-chapter.md index 30b07100..adf3c229 100644 --- a/ospo-book/chapters/01-chapter.md +++ b/ospo-book/chapters/01-chapter.md @@ -122,7 +122,7 @@ While Open Source Programs Offices (OSPOs) can provide significant benefits for * **Establishing an OSPO without proper alignment with organizational goals:** An OSPO should not be established just because it is a trend or because other organizations have them. Without proper alignment, an OSPO can become a waste of time, resources, and money -* **Viewing an OSPO as a separate silo within the organization:** it should be integrated into the organization's existing structure and collaborate with other teams to achieve common goals +* **Viewing an OSPO as a separate silo within the organization:** It should be integrated into the organization's existing structure and collaborate with other teams to achieve common goals. * **Viewing an OSPO as a legal or compliance function only:** Instead, it should be recognized as a strategic entity within the organization that contributes to the organization's overall goals and objectives while keeping in mind the value and rights of the open source community. From c0b57c15455ded8938a488a988c073570cc7cdaa Mon Sep 17 00:00:00 2001 From: Ana Jimenez Santamaria Date: Wed, 22 Mar 2023 10:52:09 +0100 Subject: [PATCH 20/36] Update ospo-book/chapters/01-chapter.md Co-authored-by: Ildiko Vancsa Signed-off-by: Ana Jimenez Santamaria --- ospo-book/chapters/01-chapter.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/ospo-book/chapters/01-chapter.md b/ospo-book/chapters/01-chapter.md index adf3c229..d0e5afab 100644 --- a/ospo-book/chapters/01-chapter.md +++ b/ospo-book/chapters/01-chapter.md @@ -63,7 +63,7 @@ and to help determine if an OSPO is the right solution for the organization's ne ## Where do Open Source and OSPO converge? -In the past, open source software was primarily used by small groups of developers and enthusiasts, and there was little need for dedicated organizational units to manage open source activities. However, as open source software has become more prevalent and critical to the operation of many organizations, the need for dedicated OSPOs has become more apparent. +In the past, collaborative open source software development was primarily adopted by small groups of developers and enthusiasts, and there was little need for dedicated organizational units to manage open source activities. However, as this method has become more prevalent and critical to the operation of many organizations, the need for dedicated OSPOs has become more apparent. ### Understand existing and desired open source adoption From c4ab43c36b761d6800402d8515de20d2f0123897 Mon Sep 17 00:00:00 2001 From: Ana Jimenez Santamaria Date: Wed, 22 Mar 2023 11:08:55 +0100 Subject: [PATCH 21/36] Update ospo-book/chapters/01-chapter.md Co-authored-by: Ildiko Vancsa Signed-off-by: Ana Jimenez Santamaria --- ospo-book/chapters/01-chapter.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/ospo-book/chapters/01-chapter.md b/ospo-book/chapters/01-chapter.md index d0e5afab..7a50848f 100644 --- a/ospo-book/chapters/01-chapter.md +++ b/ospo-book/chapters/01-chapter.md @@ -120,7 +120,7 @@ In Chapters 3 and 6, we will delve deeper into how an OSPO can effectively addre While Open Source Programs Offices (OSPOs) can provide significant benefits for organizations, there are also bad practices that organizations should avoid if they don't want to lead to negative consequences for both the organization and the open source ecosystem. Here is a set of examples that illustrates what an OSPO is not about, and how to avoid common pitfalls: -* **Establishing an OSPO without proper alignment with organizational goals:** An OSPO should not be established just because it is a trend or because other organizations have them. Without proper alignment, an OSPO can become a waste of time, resources, and money +* **Establishing an OSPO without proper alignment with organizational goals:** An OSPO should not be established just because it is a trend or because other organizations have them. Without proper alignment, an OSPO can become a waste of time, resources, and money. * **Viewing an OSPO as a separate silo within the organization:** It should be integrated into the organization's existing structure and collaborate with other teams to achieve common goals. From 9c35d9d5864029e3662dbb04c09c6555db44a11f Mon Sep 17 00:00:00 2001 From: Ana Jimenez Santamaria Date: Wed, 22 Mar 2023 11:09:51 +0100 Subject: [PATCH 22/36] Update ospo-book/chapters/01-chapter.md Signed-off-by: Ana Jimenez Santamaria --- ospo-book/chapters/01-chapter.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/ospo-book/chapters/01-chapter.md b/ospo-book/chapters/01-chapter.md index 7a50848f..0f1ba2fd 100644 --- a/ospo-book/chapters/01-chapter.md +++ b/ospo-book/chapters/01-chapter.md @@ -85,7 +85,8 @@ Assessing open source adoption is critical because it sets the foundation for su * **☑️ Overall, gather input from stakeholders on these areas** by asking the folowing questions - * What does open source means for the organization? + * How would you define 'open source'? + * What does 'open source' mean for you and your organization? * Is there an open source culture within the organization? * What are the organization's goals and objectives for using open source? * How is open source software currently being used and /or created (contirbution) within the organization? From 2fd59638915b53c93e6c5337d539c1974281fe9f Mon Sep 17 00:00:00 2001 From: Ana Jimenez Santamaria Date: Wed, 22 Mar 2023 11:10:08 +0100 Subject: [PATCH 23/36] Update ospo-book/chapters/01-chapter.md Signed-off-by: Ana Jimenez Santamaria --- ospo-book/chapters/01-chapter.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/ospo-book/chapters/01-chapter.md b/ospo-book/chapters/01-chapter.md index 0f1ba2fd..3e1acd8e 100644 --- a/ospo-book/chapters/01-chapter.md +++ b/ospo-book/chapters/01-chapter.md @@ -87,7 +87,7 @@ Assessing open source adoption is critical because it sets the foundation for su * How would you define 'open source'? * What does 'open source' mean for you and your organization? - * Is there an open source culture within the organization? + * How would you define the 'open source culture' within your organization? * What are the organization's goals and objectives for using open source? * How is open source software currently being used and /or created (contirbution) within the organization? * If any, what are the current policies and procedures for managing open source software within the organization? From 815e35757d8cc14cb234cf81a5a9de9b1213c5c0 Mon Sep 17 00:00:00 2001 From: Ana Jimenez Santamaria Date: Wed, 22 Mar 2023 11:10:21 +0100 Subject: [PATCH 24/36] Update ospo-book/chapters/01-chapter.md Signed-off-by: Ana Jimenez Santamaria --- ospo-book/chapters/01-chapter.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/ospo-book/chapters/01-chapter.md b/ospo-book/chapters/01-chapter.md index 3e1acd8e..fc2a4093 100644 --- a/ospo-book/chapters/01-chapter.md +++ b/ospo-book/chapters/01-chapter.md @@ -92,7 +92,8 @@ Assessing open source adoption is critical because it sets the foundation for su * How is open source software currently being used and /or created (contirbution) within the organization? * If any, what are the current policies and procedures for managing open source software within the organization? * What are the key legal and compliance considerations for using open source software within the organization? - * What are the challenges and opportunities for implementing an OSPO within the organization? + * What are the motivations for implementing an OSPO within the organization? + * What are the challenges of implementing an OSPO within the organization? * What resources and support will be needed to successfully implement an OSPO within the organization? ### Understand knowledge transmission through the eyes of OSPO From 6775a95dd5532ee26fb51a20636840584ef3843d Mon Sep 17 00:00:00 2001 From: Ana Jimenez Santamaria Date: Wed, 22 Mar 2023 12:30:05 +0100 Subject: [PATCH 25/36] Update ospo-book/chapters/01-chapter.md Signed-off-by: Ana Jimenez Santamaria --- ospo-book/chapters/01-chapter.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/ospo-book/chapters/01-chapter.md b/ospo-book/chapters/01-chapter.md index fc2a4093..233d3c78 100644 --- a/ospo-book/chapters/01-chapter.md +++ b/ospo-book/chapters/01-chapter.md @@ -69,7 +69,9 @@ In the past, collaborative open source software development was primarily adopte Once an organization has assessed the level of open source used, contributed, or produced in the organization and why establishing an OSPO can help an organization manage the risks and opportunities of what open source, open works and collaboration brings, and ensure that its open source activities are effectively managed and aligned with the organization's strategic goals and objectives. -While this is a book about Open Source Programs Offices (OSPOs), it is important to note that establishing an OSPO is not the starting point for open source operations. Before establishing an OSPO (and keep reading the content of the book), it is critical to assess your organization's level of open source adoption and readiness for open source operations. Open source software adoption varies widely across organizations, and it is important to understand your organization's current level of adoption and the level of knowledge and understanding of open source within your organization. +While this is a book about Open Source Programs Offices (OSPOs), it is important to note that establishing an OSPO might not the starting point for open source operations. Before establishing an OSPO (and keep reading the content of the book), companies and organizations need to assess their current goals and relationship with using and collaborating to open source software projects. + +Below, people will find a checklist to assess and better understand their possible current stage and potential next steps. Assessing open source adoption is critical because it sets the foundation for successful open source operations. Without proper understanding and adoption of open source, an OSPO may not be effective in achieving the desired outcomes. From 052cb0a6f325a42a73c2e97f695492d79d205a19 Mon Sep 17 00:00:00 2001 From: Ana Jimenez Santamaria Date: Wed, 22 Mar 2023 12:34:17 +0100 Subject: [PATCH 26/36] Update ospo-book/chapters/01-chapter.md Signed-off-by: Ana Jimenez Santamaria --- ospo-book/chapters/01-chapter.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/ospo-book/chapters/01-chapter.md b/ospo-book/chapters/01-chapter.md index 233d3c78..4e21968f 100644 --- a/ospo-book/chapters/01-chapter.md +++ b/ospo-book/chapters/01-chapter.md @@ -7,7 +7,7 @@ # Introduction -Open source technology has become an integral part of modern organizations, offering a range of benefits, including lower costs, increased collaboration, and access to a vast pool of talent and resources. However, with the growing importance of open source, organizations need to be equipped to manage their open source operations effectively, in order to realize these benefits. +Open source has become an integral part of modern organizations, offering a range of benefits, including lower costs, increased collaboration, and access to a vast pool of talent and resources. However, with the growing importance of open source, organizations need to be equipped to manage their open source operations effectively, in order to realize these benefits. Creating an Open Source Program Office (OSPO) can accelerate a company's or organization's open source journey from mindset change to efficient policies and workflows. An OSPO is a dedicated team or department within an organization that is responsible for managing the organization's open source operations, including the development, distribution, and use of open source software, and harmonizing and integrating these with product development. In this book, we will guide organizations through the process of creating and implementing an OSPO. We will provide practical advice and best practices on how to streamline open source operations, and ensuring that organizations are able to maximize the benefits of open source technology, while being good open source citizens. From b49b89414860b07771ab3b20a3137e9de0a4644b Mon Sep 17 00:00:00 2001 From: Ana Jimenez Santamaria Date: Fri, 31 Mar 2023 15:23:29 +0200 Subject: [PATCH 27/36] Update ospo-book/chapters/00-chapter.md Signed-off-by: Ana Jimenez Santamaria --- ospo-book/chapters/00-chapter.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/ospo-book/chapters/00-chapter.md b/ospo-book/chapters/00-chapter.md index f7e905f2..400bc2fa 100644 --- a/ospo-book/chapters/00-chapter.md +++ b/ospo-book/chapters/00-chapter.md @@ -16,7 +16,7 @@ Providing guidance on how to deploy, use and contribute to specific open source # Who should read this book? This book is intended for any person that wants to better understand the role of OSPOs within an organization. The book may be of interest to any role -in an organization that will be or is currently involved in open source at some level and has direct relationship with OSPO roles (or is in one) or is +More specific examples include: likely to have a close relationship with an OSPO in the future. * Executives, policy-makers and decision-makers who are responsible for establishing, overseeing, funding or sponsoring an OSPO within an organization. From 09229e4f2afea04ac9ff3348921a97522f9abf08 Mon Sep 17 00:00:00 2001 From: Ana Jimenez Santamaria Date: Fri, 31 Mar 2023 15:23:40 +0200 Subject: [PATCH 28/36] Update ospo-book/chapters/00-chapter.md Signed-off-by: Ana Jimenez Santamaria --- ospo-book/chapters/00-chapter.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/ospo-book/chapters/00-chapter.md b/ospo-book/chapters/00-chapter.md index 400bc2fa..5be3f18b 100644 --- a/ospo-book/chapters/00-chapter.md +++ b/ospo-book/chapters/00-chapter.md @@ -15,7 +15,7 @@ Providing guidance on how to deploy, use and contribute to specific open source # Who should read this book? -This book is intended for any person that wants to better understand the role of OSPOs within an organization. The book may be of interest to any role +This book is intended for any person that wants to better understand the role of OSPOs within an organization. More specific examples include: likely to have a close relationship with an OSPO in the future. From 88c753a6e9dd2ecd9bfd6146cc22e8f14dbe6541 Mon Sep 17 00:00:00 2001 From: Ana Jimenez Santamaria Date: Fri, 31 Mar 2023 15:23:48 +0200 Subject: [PATCH 29/36] Update ospo-book/chapters/00-chapter.md Signed-off-by: Ana Jimenez Santamaria --- ospo-book/chapters/00-chapter.md | 1 - 1 file changed, 1 deletion(-) diff --git a/ospo-book/chapters/00-chapter.md b/ospo-book/chapters/00-chapter.md index 5be3f18b..4eb2001f 100644 --- a/ospo-book/chapters/00-chapter.md +++ b/ospo-book/chapters/00-chapter.md @@ -17,7 +17,6 @@ Providing guidance on how to deploy, use and contribute to specific open source This book is intended for any person that wants to better understand the role of OSPOs within an organization. More specific examples include: -likely to have a close relationship with an OSPO in the future. * Executives, policy-makers and decision-makers who are responsible for establishing, overseeing, funding or sponsoring an OSPO within an organization. * Open source program managers and leaders who are responsible for coordinating and managing an organization's open source activities and engagement with open source communities. From 4bfc71065755ab029638af097aa45dbcb4307cda Mon Sep 17 00:00:00 2001 From: Ana Jimenez Santamaria Date: Fri, 31 Mar 2023 15:23:57 +0200 Subject: [PATCH 30/36] Update ospo-book/chapters/00-chapter.md Signed-off-by: Ana Jimenez Santamaria --- ospo-book/chapters/00-chapter.md | 1 - 1 file changed, 1 deletion(-) diff --git a/ospo-book/chapters/00-chapter.md b/ospo-book/chapters/00-chapter.md index 4eb2001f..c1d3ce32 100644 --- a/ospo-book/chapters/00-chapter.md +++ b/ospo-book/chapters/00-chapter.md @@ -20,6 +20,5 @@ More specific examples include: * Executives, policy-makers and decision-makers who are responsible for establishing, overseeing, funding or sponsoring an OSPO within an organization. * Open source program managers and leaders who are responsible for coordinating and managing an organization's open source activities and engagement with open source communities. -* Developers, researchers, students, professors and engineers who are interested in contributing to open source projects and want to better understand the role of OSPOs within their organization. * Legal and compliance professionals who are responsible for managing legal issues related to open source software, including licensing and intellectual property. From f9fd905f0134625255808af4b0aecab786703cf0 Mon Sep 17 00:00:00 2001 From: Ana Jimenez Santamaria Date: Fri, 31 Mar 2023 15:24:09 +0200 Subject: [PATCH 31/36] Update ospo-book/chapters/01-chapter.md Signed-off-by: Ana Jimenez Santamaria --- ospo-book/chapters/01-chapter.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/ospo-book/chapters/01-chapter.md b/ospo-book/chapters/01-chapter.md index 4e21968f..51d253b1 100644 --- a/ospo-book/chapters/01-chapter.md +++ b/ospo-book/chapters/01-chapter.md @@ -10,7 +10,9 @@ Open source has become an integral part of modern organizations, offering a range of benefits, including lower costs, increased collaboration, and access to a vast pool of talent and resources. However, with the growing importance of open source, organizations need to be equipped to manage their open source operations effectively, in order to realize these benefits. Creating an Open Source Program Office (OSPO) can accelerate a company's or organization's open source journey from mindset change to efficient policies and workflows. An OSPO is a dedicated team or department within an organization that is responsible for managing the organization's open source operations, including the development, distribution, and use of open source software, and harmonizing and integrating these with product development. -In this book, we will guide organizations through the process of creating and implementing an OSPO. We will provide practical advice and best practices on how to streamline open source operations, and ensuring that organizations are able to maximize the benefits of open source technology, while being good open source citizens. +In this book, we will guide organizations through the process of creating and implementing an OSPO. The book provides: +* Practical advice and best practices on how to streamline open source operations +* Recommendations to ensure that organizations are able to maximize the benefits of open source technology while being good open source citizens. The book is structured in a user-friendly and practical manner, with a focus on providing actionable advice and steps that organizations can take to create and implement an OSPO. The book will cover a range of topics, including: From b48285d8ae59424648102eb4a5a618a15c69c7a7 Mon Sep 17 00:00:00 2001 From: Ana Jimenez Santamaria Date: Fri, 31 Mar 2023 15:24:21 +0200 Subject: [PATCH 32/36] Update ospo-book/chapters/01-chapter.md Signed-off-by: Ana Jimenez Santamaria --- ospo-book/chapters/01-chapter.md | 1 + 1 file changed, 1 insertion(+) diff --git a/ospo-book/chapters/01-chapter.md b/ospo-book/chapters/01-chapter.md index 51d253b1..b6326bb3 100644 --- a/ospo-book/chapters/01-chapter.md +++ b/ospo-book/chapters/01-chapter.md @@ -91,6 +91,7 @@ Assessing open source adoption is critical because it sets the foundation for su * How would you define 'open source'? * What does 'open source' mean for you and your organization? + * How much open-source software is already being used in the organization? * How would you define the 'open source culture' within your organization? * What are the organization's goals and objectives for using open source? * How is open source software currently being used and /or created (contirbution) within the organization? From 5261c7e3236c16ad4b7d1d4523d0ad496b600bce Mon Sep 17 00:00:00 2001 From: Ana Jimenez Santamaria Date: Fri, 31 Mar 2023 15:24:30 +0200 Subject: [PATCH 33/36] Update ospo-book/chapters/01-chapter.md Signed-off-by: Ana Jimenez Santamaria --- ospo-book/chapters/01-chapter.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/ospo-book/chapters/01-chapter.md b/ospo-book/chapters/01-chapter.md index b6326bb3..3079bdb2 100644 --- a/ospo-book/chapters/01-chapter.md +++ b/ospo-book/chapters/01-chapter.md @@ -94,7 +94,8 @@ Assessing open source adoption is critical because it sets the foundation for su * How much open-source software is already being used in the organization? * How would you define the 'open source culture' within your organization? * What are the organization's goals and objectives for using open source? - * How is open source software currently being used and /or created (contirbution) within the organization? + * How is open source software currently being used (usage) within the organization? + * How is open source software currently being created (contribution) within the organization? * If any, what are the current policies and procedures for managing open source software within the organization? * What are the key legal and compliance considerations for using open source software within the organization? * What are the motivations for implementing an OSPO within the organization? From 5af27ff412d8274a6d88399cc4b221cbaa4af238 Mon Sep 17 00:00:00 2001 From: Ana Jimenez Santamaria Date: Fri, 31 Mar 2023 15:24:40 +0200 Subject: [PATCH 34/36] Update ospo-book/chapters/01-chapter.md Signed-off-by: Ana Jimenez Santamaria --- ospo-book/chapters/01-chapter.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/ospo-book/chapters/01-chapter.md b/ospo-book/chapters/01-chapter.md index 3079bdb2..4d28abf6 100644 --- a/ospo-book/chapters/01-chapter.md +++ b/ospo-book/chapters/01-chapter.md @@ -102,7 +102,7 @@ Assessing open source adoption is critical because it sets the foundation for su * What are the challenges of implementing an OSPO within the organization? * What resources and support will be needed to successfully implement an OSPO within the organization? -### Understand knowledge transmission through the eyes of OSPO +### Understand knowledge sharing through the eyes of OSPO > RE ML disussion: https://lists.todogroup.org/g/ospo-book-project/message/5 From 4785545335e4ff9eb8b5657636589ab4b5be19a8 Mon Sep 17 00:00:00 2001 From: Ana Jimenez Santamaria Date: Fri, 31 Mar 2023 15:38:49 +0200 Subject: [PATCH 35/36] Update ospo-book/chapters/01-chapter.md Signed-off-by: Ana Jimenez Santamaria --- ospo-book/chapters/01-chapter.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/ospo-book/chapters/01-chapter.md b/ospo-book/chapters/01-chapter.md index 4d28abf6..615b7d89 100644 --- a/ospo-book/chapters/01-chapter.md +++ b/ospo-book/chapters/01-chapter.md @@ -12,7 +12,7 @@ Open source has become an integral part of modern organizations, offering a rang Creating an Open Source Program Office (OSPO) can accelerate a company's or organization's open source journey from mindset change to efficient policies and workflows. An OSPO is a dedicated team or department within an organization that is responsible for managing the organization's open source operations, including the development, distribution, and use of open source software, and harmonizing and integrating these with product development. In this book, we will guide organizations through the process of creating and implementing an OSPO. The book provides: * Practical advice and best practices on how to streamline open source operations -* Recommendations to ensure that organizations are able to maximize the benefits of open source technology while being good open source citizens. +* Recommendations to ensure that organizations can maximize the benefits of open source while being good open source citizens. The book is structured in a user-friendly and practical manner, with a focus on providing actionable advice and steps that organizations can take to create and implement an OSPO. The book will cover a range of topics, including: From c23f403366d5f4f731ff27c994c3a6f26850f157 Mon Sep 17 00:00:00 2001 From: Ana Jimenez Santamaria Date: Wed, 5 Apr 2023 10:48:56 +0200 Subject: [PATCH 36/36] Update ospo-book/chapters/01-chapter.md Signed-off-by: Ana Jimenez Santamaria --- ospo-book/chapters/01-chapter.md | 17 ++++++++++++++++- 1 file changed, 16 insertions(+), 1 deletion(-) diff --git a/ospo-book/chapters/01-chapter.md b/ospo-book/chapters/01-chapter.md index 615b7d89..bcc2edc9 100644 --- a/ospo-book/chapters/01-chapter.md +++ b/ospo-book/chapters/01-chapter.md @@ -29,7 +29,22 @@ In the following chapters, we will explore the key components of an OSPO, and pr ## OSPO Definition -An *Open Source Program Office (OSPO)* is a center of expertise, either virtual or physical, that supports, nurtures, shares, explains, and grows open source within an organization. An OSPO *role* can be conceived as an umbrella term, covering the responsibilities for defining and implementing strategies and policies that guide open source efforts and provide tools, processes, and knowledge to organization teams and experts in navigating open source without harming the open source ecosystem. Instead, they help to sustain it while achieving organizational goals. + +[WHAT] An Open Source Program Office (OSPO) is a center of expertise, either virtual or physical, whose people support, nurture, share, explain, and promote the growth of open source within an organization. + +[WHO] OSPOs are composed of people (open source specialists) wearing different hats: + +* Open Source Enabler: OSPOs can help organizations navigate the cultural, process, and tool changes required to engage with the open source community effectively. This can involve educating teams/ units, establishing new processes and workflows, and adopting new tools and technologies. + +* Open Source Counselor: OSPOs can provide guidance and advice on the latest open source trends, licensing issues, and how to engage with open source projects, foundations, and communities. This can help organizations stay up-to-date with the rapidly changing open source landscape and ensure they are making informed decisions. + +* Open Source Advocate: OSPOs can promote the use and/or contribution of open source and best practices across different organizational units. This can help organizations realize the benefits of open source as well as engaging people to contribute to open source projects or start new ones. + +* Open Source Environmentalist: OSPOs can help organizations support and sustain open source projects in the long term by addressing issues such as security, maintenance, and project health. This can involve establishing policies and procedures for code review, security vulnerability management, and ongoing maintenance and support through funding and/or contributions. By doing so, OSPOs can help ensure that open source projects remain healthy and continue to benefit the wider community. + +[HOW] The way the people behind an OSPO achieve this is by creating and maintaining a framework covering the following aspects: strategy, governance, compliance, and community engagement. The OSPO's strategy focuses on aligning the organization's open source goals with its overall organization objectives. + +[WHY] An OSPO serves as a vital bridge between an organization and the open source community, helping to ensure that the organization is a good steward of open source software and can reap the benefits of open source adoption while minimizing risks. OSPOs (as center of expertise) may comprise a framework built around some or all of the following aspects: