Skip to content

todogroup/ospo-career-path

main
Switch branches/tags

Name already in use

A tag already exists with the provided branch name. Many Git commands accept both tag and branch names, so creating this branch may cause unexpected behavior. Are you sure you want to create this branch?
Code

Files

Permalink
Failed to load latest commit information.
Type
Name
Latest commit message
Commit time
 
 
 
 
 
 
 
 

👋 Welcome OSPO Career Path Repo

OSPO Career Path is a set of vendor-neutral, open source, and free courses created by folks from the TODO / OSPO community to support training inside the organization. Each course is intended to be modularized so the content is reusable in a piecemeal fashion.

The target audience of the OSPO Career path is intended to Open Source professionals that are in a role that manages, oversees, or guides the organization’s policies and/or contributions to open source projects. This includes:

  • Security, compliance, and licensing open source roles
  • Open Source developer relations, developer advocates, or community managers
  • Open Source project managers
  • Open Source leaders and general managers

📖 What defines an OSPO: Definition and characteristics

OSPO Definition

An open source program office (OSPO) is designed to (1) be the center of competency for an organization's open source operations and structure and (2) put a strategy and set of policies on top of an organization's open source efforts. This can include setting code use, distribution, selection, auditing, and other policies, training developers, ensuring legal compliance, and promoting and building community engagement that benefits the organization strategically. See the OSPO definition hosted by the TODO Group for more information. OSPO Characteristics

To a certain degree, any organization calling itself an OSPO likely indicates that the organization has reached a maturity stage, gained critical mass support with its enterprise, and manifests five key characteristics:

  • Employees are tasked with fostering and nurturing OSS usage.
  • The organization has a formal policy around the use and production of OSS.
  • Executives recognize that OSS and open source more broadly are important strategic assets.
  • Significant numbers of employees are contributing code to open source projects.
  • Processes, procedures, and tools are in place to streamline and facilitate open source consumption and participation
  • See the OSPO characteristics hosted by the TODO Group for more information.

📈 Career Path Progression

Courses are based on the different OSPO responsibilities established on the OSPO Mind Map. It provides key requirements that OSPO Teams or open source professionals should learn for quality implementation of an Open Source Program Office:

Description
Courses that already exist (either at TODO or other OS communities)
🆕 New Courses to be made
🤝 Courses provided by other OS Communities

Beginner Courses ⭐️

  • OSPO 101 Course (beginner) - TODO
  • 🤝 Introduction to OS license and compliance course (beginner) - OpenChain
  • 🤝 Developing Secure Software (beginner) - OpenSSF
  • 🤝 Software Package Data Exchange (beginner) - SPDX

Intermediate Courses ⭐️⭐️

Continuation fo OSPO 101 modules:

  • [🆕 Course] Effective OSPO policy & processes implementation for Users
  • [🆕 Course] Effective OSPO policy & processes implementation for Contributors
  • [🆕 Course] Effective OSPO policy & processes implementation for Partners

Advanced Courses ⭐️⭐️⭐️

TBT

🙋‍♀️ Contribute

Please open a new issue or PR to contribute to this repo adn help us improve the OSPO Career Path content!

👩‍⚖️ License

All code is offered under the Apache 2.0 and documentation is offered under the Creative Commons Attribution 4.0 International License: http://creativecommons.org/licenses/by/4.0/

About

OSPO 101 Training Modules

Topics

Resources

License

Apache-2.0, CC-BY-4.0 licenses found

Licenses found

Apache-2.0
LICENSE
CC-BY-4.0
LICENSE-DOCS

Code of conduct

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published