Skip to content
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
30 changes: 15 additions & 15 deletions ospo-book/content/en/00-chapter.md
Original file line number Diff line number Diff line change
Expand Up @@ -6,31 +6,31 @@ weight: 20

## What's This Book About?

Open source is a reality for all organizations that work with software — not just for software companies. Because of this, actively managing open source is becoming increasingly important for many organizations.
For any organization working with software—not just software companies—open source software has become unavoidable. So learning to work with, manage, and contribute to open source software is becoming increasingly important for many organizations. One way to manage open source operations is by setting up an Open Source Program Office (OSPO). And as more organizations adopt this approach, they generate experience and knowledge about how to do it successfully.

One way to manage open source is by setting up an Open Source Program Office (OSPO). Many companies and organizations have adopted this approach, and there is now a lot of shared experience and knowledge about how to do it successfully. In the open source spirit, much of this knowledge is openly available in the community.
In the open source spirit, this book aims to make that knowledge available to that growing commuity of open source program management practitioners. It provides a clear introduction for anyone who wants to understand how OSPOs help organizations manage open source. It's also a helpful resource for people already working in OSPOs who want to strengthen their role in shaping and managing open source strategy and operations. The book offers practical advice on topics such as:

This book provides a clear introduction for anyone who wants to understand how OSPOs help organizations manage open source. It's also a helpful resource for people already working in OSPOs who want to strengthen their role in shaping and managing open source strategy and operations. The book offers practical advice on topics such as:
* building an open source strategy,
* setting up an OSPO,
* managing day-to-day operations, and
* collaborating effectively with external open source communities

* Building an open source strategy.
* Setting up an OSPO.
* Managing day-to-day operations.
* Collaborating effectively with external open source communities.
## What's Not in This Book

## What’s Not in This Book

This book doesn't focus on how to develop open source software or explain technical details in depth.

It also doesn't provide step-by-step instructions for using, deploying, or contributing to specific open source software projects.
This book doesn't focus on how to develop open source software, nor does it explain technical details in much depth. It also doesn't provide step-by-step instructions for using, deploying, or contributing to specific open source software projects.

## Who Should Read This Book?

This book is for anyone who wants to understand the role of OSPOs within an organization.
This book is for readers who need clear, actionable guidance on how open source governance, risk management, and community engagement. It discusses ways practitioners can develope, integrate, and scale these processes in their organizations, and who might benefit from a structured guidebook for implementing best practices.

More specifically, it will be useful for:

* **Executives, policymakers, and decision-makers** who are responsible for setting up, supporting, or funding an OSPO.
* **Open source program managers and team leads** who coordinate open source activities and build relationships with open source communities.
* **Legal and compliance professionals** who handle legal matters related to open source, such as licensing and intellectual property.

* **Open Source Program Managers and team leads** who coordinate open source activities and build relationships with open source communities.
The second edition of this book aims to make it useful for additional audiences, including:

* **Legal and compliance professionals** who handle legal matters related to open source, such as licensing and intellectual property.
* **Leaders and practitioners** who are establishing or refining open-source-related processes, aligning them with existing management, compliance, and risk frameworks, or evaluating how an OSPO contributes to broader organizational objectives.
* **Educators and trainers** introducing open source program management to students and professionals across fields such as computer science, business, law, and engineering, including those designing modular curricula or standalone teaching units.
* **New and experienced contributors to open source programs** who require a structured pathway—assembled from focused chapters and supported with bridging material—to build organizational capability, upstream engagement, and supply-chain awareness.
Copy link
Copy Markdown
Member

@semioticrobotic semioticrobotic Nov 29, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
* **New and experienced contributors to open source programs** who require a structured pathway—assembled from focused chapters and supported with bridging material—to build organizational capability, upstream engagement, and supply-chain awareness.
This book is for readers who need clear, actionable guidance on open source governance practices, risk management, and community engagement. It discusses ways practitioners can develop, integrate, and scale these processes in their organizations, and explains who might benefit from a structured guidebook for implementing best practices.
More specifically, it will be useful for:
* **Executives, policymakers, and organizational decision makers** responsible for setting up, supporting, or funding an OSPO.
* **Open source program managers** who coordinate open source activities, advance an organization's open source capabilities, and build relationships with open source communities.
* **Organizational leaders** establishing or refining open source-related processes (aligning them with existing management, compliance, and risk frameworks) and ensuring an OSPO contributes to broader organizational objectives.
* **Legal and compliance professionals** who handle legal matters related to open source software licensing and compliance.
* **Educators and trainers** introducing open source program management to students and professionals across fields such as computer science, business, law, and engineering.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This proposed change is in response to my earlier comment.

Loading