Skip to content

change(ch0): Integrated v2 audience description #727

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
lenucksi wants to merge 3 commits into
base: main
Choose a base branch
from
Open

change(ch0): Integrated v2 audience description #727

Changes from 2 commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
bc774c7
change(ch0): Integrated v2 audience description
lenucksi Nov 26, 2025
25b8c3e
Update ospo-book/content/en/00-chapter.md
lenucksi Nov 28, 2025
00ea065
Refine introduction and target audience descriptions
semioticrobotic Nov 28, 2025
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
12 changes: 10 additions & 2 deletions ospo-book/content/en/00-chapter.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -8,7 +8,7 @@ weight: 20

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.

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.
One way to do open source management operations 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.

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:

Expand All @@ -25,7 +25,7 @@ It also doesn't provide step-by-step instructions for using, deploying, or contr

## 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 can be developed, integrated, and scaled within an organization—and who benefit from a structure that works both as a cover-to-cover reference and as targeted, chapter-based learning paths.

More specifically, it will be useful for:

Expand All @@ -34,3 +34,11 @@ More specifically, it will be useful for:
* **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.

In the second edition of this book, we aim to also make it useful for:

* **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** who need “pre-101” to intermediate material for 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.
Comment on lines +42 to +44
Copy link
Copy Markdown
Member

@semioticrobotic semioticrobotic Nov 28, 2025

Choose a reason for hiding this comment

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

These are noble goals, for sure, though achieving them would require a rather specific organizational structure. I would want to see how the discussion in #726 resolves before committing to something like this.

Copy link
Copy Markdown
Contributor Author

@lenucksi lenucksi Nov 29, 2025

Choose a reason for hiding this comment

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

Those just reflect the discussion as per the October call notes.
Please elaborate what you mean by "rather specific organizational structure".

On the educational use case: Usually higher-ed educators can mix, match and add/expose things if the basic content is good enough and useful in an isolated way - thus also the proposal of the #726 learning path path approach.

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.

Please elaborate what you mean by "rather specific organizational structure".

Sure. Sorry; I realize now my comment was vague.

What I mean is that when I see phrases like "modular curricula," "structured pathway," "bridging material," etc., I sense a rather specific organizational structure for the book—or, at the very least, for each chapter of the book (which can then be "sliced and diced" according to a readers' needs, if I understand your vision in #726). Creating a book that meets these goals for this audience might require, for example, all chapters to have clearly articulated learning objectives, review/comprehension questions, suggestions for discussion and learning activities, and so on—that is, the components that are most useful to educators. To be clear, I'm not saying this is impossible or even undesirable; I'm just saying that it's a significant advancement from the book's v1 version, and I would want to be sure the community is clear on what would be necessary for meeting that vision if we were to accept and merge it. I am probably just being my usual, too-pragmatic self. 😄

I get the sense, though, that the group assembled at the most recent meeting already agreed to this vision, and if that's the case then I do not mean to derail or override it. At any rate, I think this is something on which our technical editors (e.g., @alice-sowerby) should sign off before we commit.

At the very least, I would suggest editing these descriptions so they're perhaps a bit shorter and clearer, and so that they don't necessarily prescribe a structure for the book (just describe the goals of the reader). I'll offer some inline suggestions to show you what I mean.

Copy link
Copy Markdown
Member

@semioticrobotic semioticrobotic Nov 29, 2025 •
edited
Loading

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

@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.

This proposed change is in response to my earlier comment.