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] small update in chapter 2 #404

Merged
merged 1 commit into from
Jan 2, 2024
Merged
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
11 changes: 6 additions & 5 deletions ospo-book/content/en/02-chapter.md
Original file line number Diff line number Diff line change
Expand Up @@ -99,8 +99,8 @@

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 102 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 103 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.

Expand Down Expand Up @@ -151,16 +151,17 @@

![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 154 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

Have 1:1 conversations with managers, high-level executives, and workers/contractors from different teams that use open source in their day-to-day operations, or whose strategy involves dealing with open source projects (in terms of licenses, security vulnerabilities). Use the insights from these conversations to define the organization's unique motivators and map them to areas within the organization where open source brings value

## Step four
## Step four: Map motivators with different activity types across the organization

Create a secondary division that categorizes each of these unique motivators according to the different stages within the previously mentioned OSPO model, or a similar model as referenced in step 2.
Create a second division that categorizes each of these unique motivators according to the different stages within the previously mentioned OSPO model, or a similar model as referenced in step 2.
As an example, below is a possible categorization, proposed by one of the contributors to this book

<img width="942" alt="activityparticipationcategorization" src="https://user-images.githubusercontent.com/43671777/232468402-bb4a4d49-a6d6-4c74-8d21-88c6be3c2c13.png">

Expand Down Expand Up @@ -202,10 +203,10 @@

- [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)
- [The Business Value of the OSPO Report - Linux Foundation](https://www.linuxfoundation.org/research/business-value-of-ospo)
- [EC Open Source Programme Office - European Commission Joinup](https://joinup.ec.europa.eu/collection/ec-ospo)
- [Public services should sustain Critical open source software - FOSSEPS](https://joinup.ec.europa.eu/collection/ec-ospo)
- [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)
- [Public Services Should Sustain Critical Open Source Software - FOSSEPS](https://joinup.ec.europa.eu/collection/ec-ospo)
- [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 212 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.
Loading