todogroup / ospo-career-path Goto Github PK
View Code? Open in Web Editor NEW📖 OSPO Career Path - Training Courses
Home Page: https://todogroup.org
License: Apache License 2.0
📖 OSPO Career Path - Training Courses
Home Page: https://todogroup.org
License: Apache License 2.0
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:
Collect all courses out there relevant to OSPO-related work and create a path. Review Career Path progression
section and identify:
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.
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:
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.
(1) Came up with a list of existing courses designed for (1) OSPO managers
The format of this list should be as follow:
beginner
, intemediate
, advanced
tagsYes
or No
(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:
beginner
, intemediate
, advanced
tagsYes
or No
🎯 Please comment on this issue to send your proposals
Define and design the modules.
outbound-oss
repo or make changes for the course?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.
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.
A simple division can be:
Work on Q&A Knowledge check questions for the Outboud OSS Training course.
Send final g.doc content to LF Training & Cert Team to review and make suggestions /changes
@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.
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.
transform markdown files from this folder: https://github.com/todogroup/outbound-oss/tree/main/content into a g.doc
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?
Find a suitable theme like https://themes.gohugo.io/doks/
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 images under the headers are not visible. I am able to see them only when I download.
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:
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:
Define distribution channels to send the survey and create promotion campaign
A declarative, efficient, and flexible JavaScript library for building user interfaces.
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google ❤️ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.