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 ] Update title of intro section #531

Merged
merged 1 commit into from
Jan 2, 2025
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
4 changes: 2 additions & 2 deletions ospo-book/content/en/02-chapter.md
Original file line number Diff line number Diff line change
Expand Up @@ -4,15 +4,15 @@ status: Completed
weight: 40
---

- [Open Source is All About Integration](#open-source-is-all-about-integration)
- [Introduction](#introduction)
- 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`

## Open Source is all about Integration
## Introduction

Organizations of various types – including end-user companies, software vendors, universities, and public administrations – maintain a relationship with open source. To responsibly manage software and 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 important. It helps organizations to achieve their objectives and overcome challenges related to open source.

Expand Down
Loading