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.

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

Final Review for chapter 4 #500

Closed
wants to merge 8 commits into from
+77 −30
Closed

Final Review for chapter 4 #500

Changes from all commits
Commits
Show all changes
8 commits
Select commit Hold shift + click to select a range
4f6382a
Final Review for chapter 4
anajsana Jul 17, 2024
db75023
Update 04-chapter.md
anajsana Jul 17, 2024
69438dc
Update 04-chapter.md
anajsana Jul 17, 2024
755a5dd
Update 04-chapter.md
anajsana Jul 17, 2024
3ce77e3
Update 04-chapter.md
anajsana Jul 17, 2024
b6cbd25
Update 04-chapter.md
anajsana Jul 17, 2024
f238c01
Update 04-chapter.md
anajsana Jul 17, 2024
2098f59
typo in consumption
koozz Aug 12, 2024
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
Loading

Unchanged files with check annotations Beta

View file
ospo-book/content/en/references.md
* Additionally, the guide will highlight key organizations and initiatives that are leading the way in open source and OSPOs, providing organizations with a network of resources and support as they navigate their open source journey.
This section will provide organizations with a comprehensive list of the existing literature and resources available on open source and OSPOs, making it easy for them to access the information and support they need to create and implement an OSPO successfully.

Check failure on line 16 in ospo-book/content/en/references.md

GitHub Actions / Review docs

"alex.Condescending" 

Using 'easy' may come across as condescending.
## Adding resources: Required format
| Study | [The Evolution of the Open Source Program Office (OSPO)](https://www.linuxfoundation.org/research/the-evolution-of-the-open-source-program-office-ospo)
| Case Study | [Autodesk OSPO](https://todogroup.org/resources/case-studies/autodesk/)
| Case Study | [Capital One - OSPO in regulated environments](https://todogroup.org/resources/case-studies/capitalone/)
| Case Study | [Porsche - OSPOs in Automotiv](https://todogroup.org/resources/case-studies/porsche/)

Check failure on line 73 in ospo-book/content/en/references.md

GitHub Actions / Review docs

"Vale.Spelling" 

Did you really mean 'Automotiv'?
| Case Study | [Comcast](https://todogroup.org/resources/case-studies/comcast/)
| Case Study | [Dropbox](https://todogroup.org/resources/case-studies/dropbox/)
| Case Study | [Meta](https://todogroup.org/resources/case-studies/facebook/)
| Case Study | [Microsof](https://todogroup.org/resources/case-studies/microsoft/)

Check failure on line 77 in ospo-book/content/en/references.md

GitHub Actions / Review docs

"Vale.Spelling" 

Did you really mean 'Microsof'?
| Case Study | [National Instruments](https://todogroup.org/resources/case-studies/ni/)
| Case Study | [Porsche](https://todogroup.org/resources/case-studies/porsche/)
| Case Study | [Red Hat](https://todogroup.org/resources/case-studies/redhat/)
| Book | [The Open Source Way 2.0](https://www.theopensourceway.org/the_open_source_way-guidebook-2.0.html)
| Book | [VM (Vicky) Brasseur: Forge Your Future with Open Source](https://www.oreilly.com/library/view/forge-your-future/9781680506389/f_0000.xhtml)
| Book | [Eric S. Raymond: The Cathedral & the Bazaar](https://www.oreilly.com/library/view/the-cathedral/0596001088/)
| Book | [Open Source Law, Policy and Practice (2nd edn)](https://academic.oup.com/book/44727)

Check failure on line 97 in ospo-book/content/en/references.md

GitHub Actions / Review docs

"Vale.Spelling" 

Did you really mean 'edn'?
View file
ospo-book/content/en/01-chapter.md
* [OSPO 101 Module 1 - Open Source Introduction](https://github.com/todogroup/ospo-career-path/tree/main/OSPO-101/module1)
* [OSPO 101 Module 2 - Open Source Business Models](https://github.com/todogroup/ospo-career-path/tree/main/OSPO-101/module2)
* [OSPO 101 Module 3 - Open Source management & your organization](https://github.com/todogroup/ospo-career-path/tree/main/OSPO-101/module3)
* [OSPO easy FAQ - TODO Group and Open Chain Japan, Linux Foundation](https://todogroup.org/resources/guides/open-source-program-office-ospo-easy-faq/)

Check failure on line 168 in ospo-book/content/en/01-chapter.md

GitHub Actions / Review docs

"alex.Condescending" 

Using 'easy' may come across as condescending.
* [How to create an OSPO - TODO Group, Linux Foundation](https://todogroup.org/resources/guides/how-to-create-an-open-source-program-office/)
* [OSPO Definition - TODO Group, Linux Foundation](https://ospoglossary.todogroup.org/ospo-definition/)
* [The OSPO: A New Tool for Digital Government - Open Forum Europe](https://openforumeurope.org/wp-content/uploads/2022/06/The-OSPO-A-New-Tool-for-Digital-Government-2.pdf)
View file
ospo-book/content/en/03-chapter.md
* Industry Regulators: Many industries have their own regulatory bodies or professional associations that set guidelines and standards for organizations to follow.
* Consumer Protection Agencies: Consumer protection agencies ensure that organizations provide fair and safe products or services to consumers.
For open source to be successful and sustainable within an organization, it is crucial to collaborate not only with the open source community but also with external regulators. This collaboration ensures a clear understanding of open source principles when creating policies that affect the ecosystem. The primary objective is to work together and make informed decisions by fully grasping the implications of open source and its community. Thus, it is recommended that the OSPO consider ways to develop a plan for approaching and communicating with regulators, clearly defining the roles they will play in the policymaking process.

Check failure on line 100 in ospo-book/content/en/03-chapter.md

GitHub Actions / Review docs

"alex.Condescending" 

Using 'clearly' may come across as condescending.
## Assessing Maturity of Open Source Program Office
It helps identify the specific areas where they need to concentrate their efforts and improve their practices and its creation might come at any level of the open source journey of an organization.
### Simple checklist

Check failure on line 127 in ospo-book/content/en/03-chapter.md

GitHub Actions / Review docs

"alex.Condescending" 

Using 'Simple' may come across as condescending.
[This checklist](https://github.com/todogroup/ospology/blob/main/ospo-model/en/ospo-checklist.md) offers a simplified set of common milestones to both early-stage and seasoned OSPOs in navigating each stage of the previously mentioned OSPO maturity model. Please note that an OSPO might remove, add, or edit some content of this checklist to adapt it to their organization's needs.
#### Pre-stages
View file
ospo-book/content/en/02-chapter.md
![opensourceinvolvementmodel](https://user-images.githubusercontent.com/43671777/232468143-cde69525-7adb-4399-96d3-fa63f056b942.png)
## Step two: Identify and categorize the benefits of open source activities for your organization

Check failure on line 155 in ospo-book/content/en/02-chapter.md

GitHub Actions / Review docs

"Vale.Spelling" 

Did you really mean 'recomend'?
Once you have a certain familiarity with open source adoption models, the next natural question to ask is _What are the benefits of open source activities for the organization?_
The OSPO Japan Local Meetup Working Group, supported by the TODO Group and OpenChain, meets on the fourth Friday of every month. The group has been developing a simple frequently asked questions (FAQ) guide about OSPOs. This guide aims to answer questions at each step of the OSPO maturity model, which categorizes different open source activities from stage 0 to 4, and outlines the role of the OSPO at each level.