Skip to content

Commit

Permalink
Update _index.md
Browse files Browse the repository at this point in the history
Signed-off-by: Ana Jimenez Santamaria <ana@todogroup.org>
  • Loading branch information
anajsana authored Jan 3, 2024
1 parent 5ee9a3e commit b87c1ca
Showing 1 changed file with 8 additions and 8 deletions.
16 changes: 8 additions & 8 deletions ospo-book/content/en/_index.md
Original file line number Diff line number Diff line change
Expand Up @@ -5,14 +5,14 @@ status: Completed

# Welcome to the <br/>OSPO Book

This book serves as a source of knowledge for Open Source Program Office (OSPO) teams, aiding them in gaining a better understanding of their role within organizations and providing resources built in the open across different organizations for effectively managing an OSPO.
The book covers a wide range of topics, including:

* Why organizations may or may not need an OSPO
* Assessing an organization's readiness for implementing an OSPO
* The role of OSPOs in different types of organizations
* Challenges and common antipatterns associated with OSPOs
* Practical recommendations in day-to-day tasks, ranging from formulating open source policies to effectively engaging with external open source communities
The book serves as a source of knowledge for organizations developing strategies to use, contribute to, and/or create open source projects through professionals working in Open Source Program Offices (OSPOs). It aids in gaining a better understanding of the OSPO's role and provides resources [developed openly by a group of contributors](https://ospobook.todogroup.org/07-chapter/) with deep knowledge in open source strategy, community and management. This includes setting up policies, processes, and strategies on how to use, contribute to, and create open source projects critical to the organization's infrastructure, as well as overseeing day-to-day operations.

Check failure on line 8 in ospo-book/content/en/_index.md

View workflow job for this annotation

GitHub Actions / Review docs

"Vale.Spelling"

Did you really mean 'OSPO's'?


* Why organizations may or may not need an OSPO.
* Assessing an organization's readiness for implementing an OSPO.
* The role of OSPOs in different types of organizations.
* Common difficult scenarios and recommendations.
* Practical recommendations in day-to-day operations, ranging from formulating open source policies to effectively engaging with external open source communities.

<p><img class="mt-3 mb-3" src="/images/homepage/colorful-houses.jpg" alt="Colorful houses with people"></p>

Expand Down

0 comments on commit b87c1ca

Please sign in to comment.