Skip to content
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.

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

[OSPO Book] minor edits in chapter 2 and 3 #435

Merged
merged 4 commits into from
Mar 7, 2024
Merged
Show file tree
Hide file tree
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: 21 additions & 9 deletions ospo-book/content/en/02-chapter.md
Original file line number Diff line number Diff line change
Expand Up @@ -4,19 +4,25 @@
weight: 40
---

- [Introduction](#introduction)
- [Open Source is All About Integration](#open-source-is-all-about-integration)
- The Value of an OSPO
- Reasons Behind Starting an OSPO
- Reasons Behind Sustaining an OSPO
- [Assessing Value of Open Source Activity](#assessing-value-of-open-source-activity) - `✅ Assessment`
- [Recommendations](#recommendations) - `💡 Recommendations`
- [Resources](#resources) - `📚 Continue Here`

## Introduction
## Open Source is all about Integration

Organizations of various types, including end-user companies, software companies, universities, and public administrations, all have a relationship with open source. To handle not only software responsibly but also hardware, content, and other various aspects of technology, organizations need to engage with open source. Establishing an organizational structure is an initial step to consolidate commitment, which is where an OSPO comes into play, as it acts as a means for organizations to support their objectives and address challenges when it comes to open source.
Organizations of various typesincluding end-user companies, software vendors, universities, and public administrations—maintain a relationship with open source. To responsibly manage not only software but also hardware, content, and other aspects of technology, organizations must engage with open source. This involves finding ways to integrate such culture and operations into their IT strategy and technology and AI stacks. Establishing an organizational structure is a crucial first step to solidify commitment. This is where an Open Source Program Office (OSPO) becomes key. It serves as a means for organizations to support their objectives and address challenges related to open source.

Below are common situations where an organization, which needs to manage open source integral to its digital/IT strategy and infrastructure, can encounter issues. When ignored or neglected, these issues can lead to mid-term to long-term innovation bottlenecks and security vulnerabilities.
> 💡 OSPOs are all about Integration, not Isolation

### Supply Chain and Open Source

Sometimes, organizational stakeholders may assume that they do not use open source projects because their end product is proprietary. However, a closer examination of the [entire software supply chain](https://opensource.com/article/16/12/open-source-software-supply-chain) often reveals that such proprietary software contains open source dependencies or other artifacts that form the baseline. If the contributors working on those open source projects were to leave, the project could become obsolete or a target for security vulnerabilities. This, in turn, would affect the proprietary software the organization uses or sells, directly impacting its reputation, performance, or revenue

Below are common situations where an organization, aiming to manage open source for integration into its digital/IT strategy and technology infrastructure, may encounter issues. If ignored or neglected, these issues can lead to mid-term and long-term innovation bottlenecks and security vulnerabilities.

- **Vulnerability Management:** keeping track of the open source usage (software, hardware, etc) by the organization and performing risk assessments on the identified projects. By identifying key projects within the organization, they can prioritize securing them by tracking common vulnerabilities and exposures.

Expand All @@ -33,13 +39,15 @@

To fully overcome these and other challenges, organizations must be equipped to manage open source operations on both cultural and practical levels. The *how* of accomplishing this is often through the OSPO, as it fosters committed, cross-functional collaboration within the organization to address open source issues encountered by various teams or departments.

> 💡 OSPOs foster cross-functional collaboration

But how exactly can an OSPO enable cross-functional collaboration? Why and how does this cross-functional collaboration aid in achieving the organization's goals? Additionally, why is this cross-functional collaboration essential for the creation and long-term sustainability of an OSPO within the organization?

### The value of an OSPO

To understand the value of an [OSPO](https://ospoglossary.todogroup.org/ospo-definition/), it is important for the reader to understand the reasons for (1) Establishing an OSPO and (2) Sustaining it over the long term.

In this book, the section on _Starting an OSPO_ is aimed at organizations that are taking their first steps toward creating an OSPO. This means that even if they already have personnel dedicated to dealing with open source tasks from time to time, they still lack a structured and specialized unit (or units) within their organization. On the other hand, the section on _Sustaining an OSPO_ is more relevant to individuals in organizations that have already established specialized units, covering aspects such as strategy, compliance, community involvement, and governance
In this book, the section on _starting an OSPO_ is aimed at organizations that are taking their first steps toward creating an OSPO. This means that even if they already have personnel dedicated to dealing with open source tasks from time to time, they still lack a structured and specialized unit (or units) within their organization. On the other hand, the section on _sustaining an open source through an OSPO_ is more relevant to individuals in organizations that have already established specialized units, covering aspects such as strategy, compliance, community involvement, and governance

> In both sections, the emphasis is on the different responsibilities of an OSPO to help manage open source as an ongoing activity and be well integrated into all organization's units. This responsibility may evolve and become more complex over time, but it is definitely not a temporary task with a predetermined completion point.

Expand All @@ -49,7 +57,7 @@

### The reasons behind starting an OSPO

The [business value of the OSPO report](https://www.linuxfoundation.org/research/business-value-of-ospo) explains some of the reasons shared by Open Source leaders across different industries and organization sizes.
Integrating open source into an organization's infrastructure and operations is a vast field that encompasses various angles and objectives. The [business value of the OSPO report](https://www.linuxfoundation.org/research/business-value-of-ospo) explains some of the reasons shared by Open Source leaders across different industries and organization sizes.

- Building standardized processes around open source
- Learn how to approach the open source community
Expand All @@ -59,9 +67,11 @@
- Improving development velocity
- Mitigating Security Risks

### The reasons behind sustaining an OSPO
### The reasons behind sustaining open source operations through an OSPO

Stopping the work of an OSPO could have significant negative impacts on those organizations that use open source (directly or indirectly) at any level, including loss of open source expertise, increased security and legal risks, reduced community engagement, and damage to reputation.

Stopping the work of an OSPO could have significant negative impacts on those organizations that use open source at any level, including loss of open source expertise, increased security and legal risks, reduced community engagement, and damage to reputation.
> 💡 _Open Source is a silent critical need_

An OSPO needs to be an ongoing initiative within an organization in order to evolve its culture and open source knowledge, helping the organization to contribute to and build more secure open-source software, as well as improving the sustainability of open-source projects.

Expand Down Expand Up @@ -99,12 +109,12 @@

By extending the concept of _open_ to encompass (for instance) open research, design, or access, we can identify additional benefits that these practices bring to organizations. This broader view of openness is gaining traction in academic and public sectors, where terms other than open source are sometimes used instead, such as [open technology](https://www.researchgate.net/publication/254920512_Open_Technology#pf7) or open work. However, since these terms are not as well-known among organizations, many of them still use open source as a term to indicate activities beyond software.

![opensourceswiss-knife](https://github.com/todogroup/ospology/assets/43671777/402151df-1c98-42e3-99cc-c1377ff8ca60)

Check warning on line 112 in ospo-book/content/en/02-chapter.md

View workflow job for this annotation

GitHub Actions / Review docs

"alex.ProfanityUnlikely"

Be careful with 'knife', it’s profane in some cases.
Source: Khalil Khalaf - The Pros and Cons of Open Source Software

Check warning on line 113 in ospo-book/content/en/02-chapter.md

View workflow job for this annotation

GitHub Actions / Review docs

"alex.ProfanityUnlikely"

Be careful with 'Pros', it’s profane in some cases.

> Note: You may have noticed that in this book, when referring to open source, we also include other kinds of open initiatives beyond software, such as hardware, data, etc.

## Assessing value of open source usage (also called consumption)
## Assessing the value of open source usage (also called consumption)

`✅ Assessment`

Expand Down Expand Up @@ -151,7 +161,7 @@

![ospo-role](https://github.com/todogroup/ospology/assets/43671777/8dbcf056-446c-489d-9b40-07fc2a8c331c)

> You can find a summary of their work in both Japanese and English [in this Qiita article written by one of its members](https://qiita.com/owada-k/items/017d1b98d0e437766bd0)

Check warning on line 164 in ospo-book/content/en/02-chapter.md

View workflow job for this annotation

GitHub Actions / Review docs

"alex.ProfanityUnlikely"

Be careful with 'Japanese', it’s profane in some cases.


## Step three: Initiate conversations and define unique motivators
Expand Down Expand Up @@ -201,6 +211,8 @@

`📚 Continue Here`

- [Open source and the software supply chain - John Mark Walker](https://opensource.com/article/16/12/open-source-software-supply-chain)
- [Strategy: End Game for FINOS Maturity Model - Victor Lu](https://docs.google.com/presentation/d/1jJtR6-fvU-dCrGq_gTm4P1Awv90oCu4RClj1919970A/edit#slide=id.g1ed9ae7029f_0_29)
- [Securing the Software Supply Chain: The Role of OSPOs - Jessica Marz](https://www.intel.com/content/www/us/en/developer/articles/community/securing-software-supply-chain-the-role-of-ospo.html)
- [Simple Frequently Asked Questions OSPO Guide - OSPO SWG Japan](https://qiita.com/owada-k/items/017d1b98d0e437766bd0)
- [The Business Value of the OSPO Report - Linux Foundation](https://www.linuxfoundation.org/research/business-value-of-ospo)
Expand All @@ -209,4 +221,4 @@
- [How Governments Want to Use OSPOs to Transform Themselves - Sivan Pätsch](https://joinup.ec.europa.eu/collection/open-source-observatory-osor/news/growing-case-ospos-government)
- [Open Source Security and Risk Analysis Report 2022 - Synopsys](https://www.synopsys.com/software-integrity/resources/analyst-reports/open-source-security-risk-analysis.html)
- [Open Technology - Scheerder, Jeroen & Koymans](https://www.researchgate.net/publication/254920512_Open_Technology#pf7)
- [The Pros and Cons of Open Source Software - Khalil Khalaf](https://medium.com/@kylekhalaf/the-pros-and-cons-of-open-source-software-d498304f2a95)

Check warning on line 224 in ospo-book/content/en/02-chapter.md

View workflow job for this annotation

GitHub Actions / Review docs

"alex.ProfanityUnlikely"

Be careful with 'Pros', it’s profane in some cases.
21 changes: 12 additions & 9 deletions ospo-book/content/en/03-chapter.md
Original file line number Diff line number Diff line change
Expand Up @@ -59,6 +59,10 @@

#### Creating and Implementing an Open Source Strategy

> If an organization's primary objective is profitability, customer satisfaction becomes a linchpin in the corporate strategy – a focal point for both CEOs and CFOs. For individuals in Open Source Program Offices, effectively communicating the open source strategy to C-level executives demands a keen understanding of the industry landscape and alignment with the key considerations of CEOs and CFOs. This alignment necessitates a clear comprehension of the overarching corporate strategy and identifying technologies within the open-source realm that can propel the organization toward its strategic objectives
>
> Victor Lu and Rob Moffat Presentation - [Strategy - End Game for FINOS Maturity Model](https://osr.finos.org/docs/presentations/strategy)

The people behind an OSPO achieve this 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 usage (consumption) and contributions across its projects, products, services, or internal infrastructure to its overall organization objectives.

Expand All @@ -68,7 +72,7 @@

### Fostering open source integration within the organization

Effectively executed OSPO work takes into account the elements of an organization's architecture, as understanding the organization's goals is fundamental for making

Check warning on line 75 in ospo-book/content/en/03-chapter.md

View workflow job for this annotation

GitHub Actions / Review docs

"alex.ProfanityUnlikely"

Be careful with 'executed', it’s profane in some cases.
informed open source-forward decisions. For instance, in a corporate field, an OSPO might look into the following areas and identify the role that open source plays on each situation:

![organization-architecture](https://github.com/todogroup/ospology/assets/43671777/e722d9b0-04f7-4f0a-b645-fd369a2b56f9)
Expand Down Expand Up @@ -173,13 +177,12 @@

`📚 Continue Here`

* [FINOS open source maturity model](https://www.finos.org/blog/open-source-maturity-model-launch)
* [Porsche Open Source Website](https://opensource.porsche.com/)
* [OSPO maturity model](https://linuxfoundation.org/tools/the-evolution-of-the-open-source-program-office-ospo/)
* [OSPO 101 training module - OSPO and your organization](https://github.com/todogroup/ospo-career-path/tree/main/OSPO-101/module3)
* [Setting up an open source strategy](https://todogroup.org/resources/guides/setting-an-open-source-strategy/).
* [Participating in open source communities](https://todogroup.org/resources/guides/participating-in-open-source-communities/)
* [A guide to outbound open source software](https://todogroup.org/resources/guides/a-guide-to-outbound-open-source-software/)
* [A deep dive into OSPO](https://www.linuxfoundation.org/research/a-deep-dive-into-open-source-program-offices)
* [Open Source maturity model](https://www.finos.org/blog/open-source-maturity-model-launch)
- [FINOS open source maturity model](https://www.finos.org/blog/open-source-maturity-model-launch)
- [Porsche Open Source Website](https://opensource.porsche.com/)
- [OSPO maturity model](https://linuxfoundation.org/tools/the-evolution-of-the-open-source-program-office-ospo/)
- [OSPO 101 training module - OSPO and your organization](https://github.com/todogroup/ospo-career-path/tree/main/OSPO-101/module3)
- [Setting up an open source strategy](https://todogroup.org/resources/guides/setting-an-open-source-strategy/).
- [Participating in open source communities](https://todogroup.org/resources/guides/participating-in-open-source-communities/)
- [A guide to outbound open source software](https://todogroup.org/resources/guides/a-guide-to-outbound-open-source-software/)
- [A deep dive into OSPO](https://www.linuxfoundation.org/research/a-deep-dive-into-open-source-program-offices)

Loading