-
Notifications
You must be signed in to change notification settings - Fork 136
Expand file tree
/
Copy pathEmilysTOC
More file actions
67 lines (51 loc) · 2.8 KB
/
EmilysTOC
File metadata and controls
67 lines (51 loc) · 2.8 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
---
title: Table of Contents
weight: 5
---
## Definition of Open Source
- The legal definition, plus background on the open source movement
- Permissive licenses and copyleft licenses
- The difference between 'legally' open source and the open source philosophy
- Desciption of common practices in open source development
- Misconceptions about open source
## Open source glossary
- Glossary of terms
## [Background - Existing frameworks and models]({{< relref "glossary" >}})
- Guide's purpose and audience
- Open source in modern software engineering
- Open source in modern businesses
- Engagement levels in open source
- Using open source software
- Contributing to open source software
- Publishing and maintaining open source software
- Carl-Eric Mols' "Principles for Industrial Open Source"
- Magnus presentation at FOSSNorth
- Mozilla archetypes and Heather Meeker's frameworks
## Business benefits of open source software
- Engineering benefits
- Marketing + sales benefits
- Other business benefits (recruiting, retention, reputation)
- Difference in business benefits depending on the engagement level (user, contributor, editor)
- Strategies for maximizing the business benefits of open source
## [Open source has downsides, too]({{< relref "misconceptions_challenges" >}})
- Risks and challenges from using open source software
- Risks and challenges from contributing to open source software
- Risks and challenges from publishing and maintaining open source software
- Cyber Resilience Act (CRA) when publishing software
- Legislative risks related to open source software
- How to properly budget or allocate resources for OSPOs?
- Strategies for minimizing the risks and downsides from open source
## [Communicating open source's value with business stakeholders]({{< relref "communication_of_benefits_to_business_value" >}})
- Adjusting your message according to your audience - not all business stakeholders are the same
- Focus on the 2 or 3 primary benefits you think this particular project will have; all projects are different
- Don't hide the drawbacks of open source; be frank about the potential risks and downsides
## [Case Studies and Success Stories]({{< relref "case_studies_and_stories" >}})
- Neutral collaboration: Stories from organizations like LF Energy's OpenSTEF or from Open Telemetry
- Case study from open source 'user' organizations
- Case study from organizations who are engaged contributors
- Case study from publishers of open source software
## Should I open source this software?
- Framework for deciding whether your organization should release an internal project as an open source project
## [Future work and conclusion]({{< relref "living_guide_for_business" >}})
- Creating a living document that evolves with community input
- Recap of the guide's key points