Skip to content

Commit

Permalink
Update ospo-book/content/en/05-chapter.md
Browse files Browse the repository at this point in the history
Signed-off-by: Matt Germonprez <germonprez@gmai.com>

Co-authored-by: Alice Sowerby <acsowerby@hotmail.com>
Signed-off-by: Matt Germonprez <germonprez@gmail.com>
  • Loading branch information
germonprez and alice-sowerby authored Nov 18, 2024
1 parent 9dfcac2 commit 5d01b8f
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion ospo-book/content/en/05-chapter.md
Original file line number Diff line number Diff line change
Expand Up @@ -55,7 +55,7 @@ Working with open source is never easy as rival corporations may dominate upstre

#### Goal 4: Organizational Impact

Engagement with open source communities includes working in the upstream to effectively use open source software in organizational products. In this, there is a need to monitor the intake of open source software for infosec, legal, and engineering reasons. Companies can establish software intake processes, working with teams to either technically track or socially consider issues related to open source intake. organization impact can also include working downstream with projects and companies that rely on your organizational products. This can include working to gain a clearer picture of the open source that is in your shipped products. Organizations can work in securing and regulating their own internal open source processes in an effort to improve product development activities. Key questions to consider regarding organization impact include:
Engagement with open source communities includes working in the upstream to effectively use open source software in organizational products. In this, there is a need to monitor the intake of open source software for infosec, legal, and engineering reasons. Companies can establish software intake processes, working with teams to either technically track or socially consider issues related to open source intake. Organization impact can also include working downstream with projects and companies that rely on your organizational products. This can include working to gain a clearer picture of the open source that is in your shipped products. Organizations can work in securing and regulating their own internal open source processes in an effort to improve product development activities. Key questions to consider regarding organization impact include:

Check failure on line 58 in ospo-book/content/en/05-chapter.md

View workflow job for this annotation

GitHub Actions / Review docs

"Vale.Spelling"

Did you really mean 'infosec'?

* What characteristics does an organization inspect related to inbound open source software?
* What product-level software and infrastructure contains open source software dependencies?
Expand Down

0 comments on commit 5d01b8f

Please sign in to comment.