transform markdown files from this folder: https://github.com/todogroup/outbound-oss/tree/main/content into a g.doc

Find a suitable theme like https://themes.gohugo.io/doks/

https://github.com/todogroup/ospo101/blob/main/module3/README.md#comcast and it says

Working with an interdisciplinary team, Moore worked to set up an open source advisory council, which consisted of legal and technical subject matter experts. They reviewed contributions and created internal guidelines focused on good open source practices and community building. In 2013, when they started tracking these contributions, they had 13. This year, they plan to do almost 10x that.

The last sentence says "This year" and since the reader doesn't know when this was written it is impossible to know if the 10x is happening in 2014 or 2022 or some year between those years.

The Outbound OSS Wg is working to create a new OSPO course, specific to contributing to and releasing new open source projects based on the Outbound OSS Materials.

During our bi-weekly meetings, we discussed the idea of having a single or multiple repos where all existing, WIP and future OSPO courses could be stored. We agreed that the best approach is to keep it simple in one repo, instead of creating one for every new course.

Thus. The idea is to rename this repo to "OSPO Career Path" and put all OSPO 101 materials into a new folder. This way, the information architecture of this repo would look as follows:

OSPO Career Path

Beginner: OSPO 101

• Module 1
• Module 2
• Module 3
• Module N
• LICENSE
• LICENSE-DOCS
• README.md
• ospo101.svg

Intermediate: Outbound Open Source

• Module 1
• Module 2
• Module 3
• Module N
• LICENSE
• LICENSE-DOCS
• README.md

Define distribution channels to send the survey and create promotion campaign

Work on Q&A Knowledge check questions for the Outboud OSS Training course.

• For each module
• For the entire course

Hi,
To me it seems that module4 first image (image1.png) is not correct. The current module4/image1 is "Membership Life Cycle for Online Communities" and the text talks about:

As you can see from this graphic, ‘requirements’ generally come in the form of ‘feature requests’ from users or developers, and due to the more iterative/Agile nature of development (more on that shortly), there isn’t a long, protracted requirements phase for open source software development.

https://github.com/todogroup/ospo101/blob/main/module3/README.md#open-source-in-earnest

It says:

About three years ago, things began to change. Microsoft decided to make open source pervasive throughout the company and rolled open source into the main engineering groups.

Now it is impossible to know what this "About three years ago" means, because it is not clear when that was said. It would be better to put something like: "Around the year 201x things began to change" and change 201x to the correct year.

A simple division can be:

• (1) Open Source /OSPO managers shaping the process within an organization
• (2) Open Source /OSPO contributors within and organization (code and non-code contributors)
• (3) Open Source /OSPO managers executing the process

• @anajsana: Please submit a pull request (PR) in this repository with a markdown file that merges the different files containing the Outbound OSS Guide.

• After the PR is created, participants from the Working Group will be able to make changes to the format of the Outbound OSS Guide by commenting on the PR. Please use this PDF as a reference.

• @anajsana: Mirror the final output in this Google Doc for the LF training and certification team to review. If there's a different process available, we'll await an update from the LF training team.

Topics to work on while making changes to the PR:

Course Overview

• Learning Objectives
• Course Audience
• Knowledge Prerequisites
• System Requirements
• Course Lnght
• Course outline

Design a questionnaire for the survey to gather feedback that helps understand what the OSPO/ Open Source community is looking for or is missing in terms of training:

• What people expect from the different courses
• What structure would people like to see

At the moment the image https://github.com/todogroup/ospo101/blob/main/module5/incorporation.png has a small blue box on top left and this small blue box has an arrow pointing to the bigger blue box with a small green box inside. For me this is a bit confusing and I would change the small blue box on top left to small green box and here is my thinking:

• Small green box represents the open source code / component
• Big blue box represents the own (possibly proprietary) code
• Now the small green box (open source code / component) gets copy-pasted / integrated / embedded into the big blue box as the arrow indicates

(1) Came up with a list of existing courses designed for (1) OSPO managers

The format of this list should be as follow:

• Title as is in the LF Training Catalog and link
• What is its level of difficulty? please use beginner, intemediate, advanced tags
• Does it need to add a news section? please indicateYes or No
  • If yes, please include desired title, learning objectives and topics covered

(2) Came up with a list of existing courses designed for (2) employee open source contributors who collaborate with OSPO members

The format of this list should be as follow:

• Title as is in the LF Training Catalog and link
• What is its level of difficulty? please use beginner, intemediate, advanced tags
• Does it need to add a news section? please indicate Yes or No
  • If yes, please include desired title, learning objectives and topics covered

🎯 Please comment on this issue to send your proposals

It seems that Module 4, under The Role of Continuous Integration & Testing --> Why Continuous Integration? there are some markup errors as I see a couple of "** **" markups, e.g.

Linus Torvalds, invented the git** **system and 
Automated builds** **are run on as many variations of software
The repository must be monitored by a continuous integration server** **which runs scripted automation tests
The founding projects** **are:

Edit: Could not figure out how to get the asterisk signs to appear they do on the text, so I used insert "code" above.

Explain the differences and similarities for all three concepts.
in korean version
https://github.com/kenu/ospo101/blob/main/module1/README.md#%ED%95%99%EC%8A%B5-%EB%AA%A9%ED%91%9C-1

I wrote wrong issue board.
please close this.

Thank you for GOOD Contents.

The README file mentions a CC-BY license, but the LICENSE file has an Apache 2.0 license. I would guess that CC-BY is correct?

This is super minor thing, but I noticed that module 5 DYI audit picture (https://github.com/todogroup/ospo101/blob/main/module5/diy-audit.png) there is an asterisks (*) at Fingerprint collector tool -> digital signatures, but there is no "explanation" or "foot note" for this.
The previous picture (Traditional audit) also had an asterisks and it also provided the foot note.

LF Training & Cert team moves the content to their internal course directory and collaborates with the working group (WG) on the design

I wanted to let you know that the following links on the “Resources” page (https://ospoplusplus.org/resource/) are broken:

• How to Create an Open Source Program (https://todogroup.org/resources/guides/create-program/)
• Measuring Your Open Source Program (https://todogroup.org/resources/guides/measuring/)
• Tools for Managing Your Open Source Program (https://todogroup.org/resources/guides/management-tools/)
• Managing Career Development within OSPOs (https://todogroup.org/resources/guides/career-development/)

Collect all courses out there relevant to OSPO-related work and create a path. Review Career Path progression section and identify:

• Existing courses (outside TODO) that can be added
• Give an order to the list (from beginner to advance)
• Identify new courses that does not exist and the community would like to create

Send final g.doc content to LF Training & Cert Team to review and make suggestions /changes

The images under the headers are not visible. I am able to see them only when I download.

Define and design the modules.

• Do we want to keep the same ones as in outbound-oss repo or make changes for the course?
• What is the best sequence to use from a teaching point of view (e.g adding a test at the end of each module)?