S3.Ep2 - Open Source Strategy | My Open Source Experience Podcast 🔗 **Source:** [S3.Ep2 - Open Source Strategy | My Open Source Experience Podcast](https://www.youtube.com/watch?v=rqW7E1Z_Twk) > [!note]+ Document Notes > tags: [Open Source Strategy, OSPO, InnerSource] > author: [MISSING] > source: My Open Source Experience Podcast > reference: [https://www.youtube.com/watch?v=rqW7E1Z_Twk] > date created: > > # 🏷️ Title: S3.Ep2 - Open Source Strategy | My Open Source Experience Podcast > <!-- deep-read:sections start --> ## 🧰 Action Inbox - [H1] Draft OSPO-review board RACI — context/https://www.youtube.com/watch?v=rqW7E1Z_Twk&t=56 #articleseed - [H2] Write “inner source, then and now” brief — context/https://www.youtube.com/watch?v=rqW7E1Z_Twk&t=68 #xref - [H3] Propose OSS part-number tracking pattern — context/https://www.youtube.com/watch?v=rqW7E1Z_Twk&t=112 #articleseed - [H4] Document cross-line component reuse workflow — context/https://www.youtube.com/watch?v=rqW7E1Z_Twk&t=124 #xref - [H5] Summarize CEO-to-OSPO strategy linkage — context/https://www.youtube.com/watch?v=rqW7E1Z_Twk&t=40 #share - [H6] Prepare inner source culture playbook — context/https://www.youtube.com/watch?v=rqW7E1Z_Twk&t=78 #articleseed - [H7] Map printer-style BOM to SBOM process — context/https://www.youtube.com/watch?v=rqW7E1Z_Twk&t=112 #addendum ## 🧭 Table of Contents - [📝 Summary](#-summary) - [📖 Main Content](#-main-content) - [🗒️ Notes](#️-notes) - [📚 References](#-references) - [🗣️ Paraphrase](#️-paraphrase) - [📰 Newsletter](#-newsletter) - [✅ Action Items](#-action-items) - [🧪 Hypotheses](#-hypotheses) - [📊 Methodology](#-methodology) - [❓ Questions](#-questions) - [🔮 Future Research](#-future-research) - [💡 Implications](#-implications) - [🧠 Learning Styles Assessment](#-learning-styles-assessment) - [📊 Accessibility Assessment](#-accessibility-assessment) - [🌍 DEIB Assessment](#-deib-assessment) - [✅ Logical Validity](#-logical-validity) - [🛡️ DARVO Analysis](#-darvo-analysis) - [🎯 Conclusion](#-conclusion) ### 🔗 References - Episode video. https://www.youtube.com/watch?v=rqW7E1Z_Twk - TODO Group: OSPO definition. https://todogroup.org/ospo/ - InnerSource Commons: What is InnerSource? https://innersourcecommons.org/learn/what-is-innersource/ - SPDX Specification (for SBOMs). https://spdx.dev/specifications/ ## 📝 Summary - Speakers recount OSPO review board practice at a large firm. [Video](https://www.youtube.com/watch?v=rqW7E1Z_Twk) - Policies shaped what teams could do with open source. See [H1]. - Inner source emerged alongside cultural shifts and shared components. See [H2], [H4]. - Hardware groups assigned part numbers to open-source software. See [H3]. - Bottom line: governance and culture coevolve in successful OSPOs. ## 📖 Main Content - Review boards translate company goals into actionable open-source policy. This constrains risk while enabling reuse. [H1] - Inner source appears with cross-team component sharing and norms. It needs tooling and tracking. [H2], [H4] - Hardware-style tracking helped software governance. Part numbers mapped components to products. [H3] - Strategy broadcasting from leadership supports OSPO alignment. Communication matters for adoption. [H5] - Context: OSPOs coordinate policy, compliance, and community programs. See TODO Group overview. https://todogroup.org/ospo/ - Context: Inner source uses open practices inside companies. See ISC guide. https://innersourcecommons.org/learn/what-is-innersource/ - Uncertainties: exact timelines, metrics, and organizational names remain unclear in this excerpted transcript. ### 🗒️ Notes #### ⏱️ [00:40](https://www.youtube.com/watch?v=rqW7E1Z_Twk&t=40) Strategy communication ### [H5] Leadership shares strategy to drive alignment > [!quote] [S3.Ep2 - Open Source Strategy](https://www.youtube.com/watch?v=rqW7E1Z_Twk) by an unnamed author via [[YouTube]]. Published [MISSING]. Accessed . > “there was a trickle down effect and we all knew exactly what the strategy is” Clear strategy messages support governance execution. [view highlight](https://www.youtube.com/watch?v=rqW7E1Z_Twk&t=40) #share ID:rw_[MISSING] #### ⏱️ [00:56](https://www.youtube.com/watch?v=rqW7E1Z_Twk&t=56) Policy influence ### [H1] Review board policies constrain open-source choices > [!quote] [S3.Ep2 - Open Source Strategy](https://www.youtube.com/watch?v=rqW7E1Z_Twk) > “the open- source policies that the review board set very much influenced what you could and couldn't do.” Policies set guardrails for project and license decisions. [view highlight](https://www.youtube.com/watch?v=rqW7E1Z_Twk&t=56) #xref #articleseed ID:rw_[MISSING] #### ⏱️ [01:08](https://www.youtube.com/watch?v=rqW7E1Z_Twk&t=68) Inner source emergence ### [H2] Inner source practice rises with shared needs > [!quote] [S3.Ep2 - Open Source Strategy](https://www.youtube.com/watch?v=rqW7E1Z_Twk) > “we were doing some stuff around inner source and that was a time when that term started to come into existence” Name and practice matured together. [view highlight](https://www.youtube.com/watch?v=rqW7E1Z_Twk&t=68) #xref ID:rw_[MISSING] #### ⏱️ [01:18](https://www.youtube.com/watch?v=rqW7E1Z_Twk&t=78) Culture shift ### [H6] Inner source also requires cultural change > [!quote] [S3.Ep2 - Open Source Strategy](https://www.youtube.com/watch?v=rqW7E1Z_Twk) > “that was a cultural thing as well.” Culture enables code sharing and contribution norms. [view highlight](https://www.youtube.com/watch?v=rqW7E1Z_Twk&t=78) #articleseed ID:rw_[MISSING] #### ⏱️ [01:52](https://www.youtube.com/watch?v=rqW7E1Z_Twk&t=112) Tracking software like hardware ### [H3] Teams assign part numbers to OSS components > [!quote] [S3.Ep2 - Open Source Strategy](https://www.youtube.com/watch?v=rqW7E1Z_Twk) > “they wanted to give part numbers to these open-source software projects so that they could track them.” Tracking aligned software with existing BOM processes. [view highlight](https://www.youtube.com/watch?v=rqW7E1Z_Twk&t=112) #articleseed ID:rw_[MISSING] #### ⏱️ [02:04](https://www.youtube.com/watch?v=rqW7E1Z_Twk&t=124) Cross-line reuse ### [H4] Internal numbers reinforced cross-product reuse > [!quote] [S3.Ep2 - Open Source Strategy](https://www.youtube.com/watch?v=rqW7E1Z_Twk) > “those internal product numbers became you know a core set of functions that ran across multiple different product printer lines” Identifiers improved discoverability and reuse. [view highlight](https://www.youtube.com/watch?v=rqW7E1Z_Twk&t=124) #xref ID:rw_[MISSING] ## 📚 References - Episode video (primary source). https://www.youtube.com/watch?v=rqW7E1Z_Twk - TODO Group OSPO overview. https://todogroup.org/ospo/ - InnerSource Commons primer. https://innersourcecommons.org/learn/what-is-innersource/ - SPDX SBOM specification. https://spdx.dev/specifications/ ## 🔖 Zettel Candidates - **Review board policies constrain open-source choices.** Policies set boundaries that steer adoption and risk. https://www.youtube.com/watch?v=rqW7E1Z_Twk&t=56 - **Inner source practice rises with shared needs.** Practice and terminology matured in tandem. https://www.youtube.com/watch?v=rqW7E1Z_Twk&t=68 - **Inner source also requires cultural change.** Culture shifts enable sustained collaboration. https://www.youtube.com/watch?v=rqW7E1Z_Twk&t=78 - **Teams assign part numbers to OSS components.** Hardware-style tracking improved visibility. https://www.youtube.com/watch?v=rqW7E1Z_Twk&t=112 - **Internal numbers reinforced cross-product reuse.** Identifiers supported shared functions across lines. https://www.youtube.com/watch?v=rqW7E1Z_Twk&t=124 - **Leadership shares strategy to drive alignment.** Direction supports governance execution. https://www.youtube.com/watch?v=rqW7E1Z_Twk&t=40 ## 🗣️ Paraphrase - The review board shaped open-source behavior through policy and process. - Inner source appeared with culture work and tracking mechanisms across teams. ## 📰 Newsletter - This episode explores OSPO realities inside a large hardware-centric org. Policies shaped choices. Inner source needed culture change and tracking. A quirky detail stands out: assigning part numbers to OSS projects, which aided reuse across printer lines. Worth a listen if you run an OSPO or contribute to one. Links: [episode](https://www.youtube.com/watch?v=rqW7E1Z_Twk), [OSPO](https://todogroup.org/ospo/), [InnerSource](https://innersourcecommons.org/learn/what-is-innersource/). ## ✅ Action Items #### DevRel - Publish a primer on inner source benefits with examples. - Record a case study on part-number style tracking. - Create a short explainer on review board workflows. #### OSPO - Define a review board charter and RACI with SLAs. - Map BOM-style identifiers to SBOM fields (SPDX). - Pilot inner source contribution guidelines and templates. #### Community - Run a workshop on cross-team component reuse. - Share a checklist for cultural readiness and incentives. - Collect stories where identifiers improved reuse. #### WordPress - Documentation: add inner source patterns for .org teams. - Training: governance modules for working groups and mentors. - Accessibility: ensure contribution docs meet WCAG basics. #### The WPOCC - Fund microgrants for inner source starter kits. - Publish transparent reports on governance experiments. ### FAIR - Define provenance and signature expectations for shared code. - Produce operator agreements for cross-team components. ## 🧪 Hypotheses - Review board policies reduce license risk across releases. - Part-number style identifiers increase component reuse rates. - Inner source programs improve time-to-integration for shared code. - Leadership clarity increases OSPO policy adoption. ### 📊 Methodology - Audit releases for license findings pre/post policy updates. - Track reuse metrics per-component before and after identifiers. - Measure integration lead time across pilot teams. - Survey adoption and exception rates after strategy broadcasts. ### ❓ Questions - Which teams should own identifier assignment and lifecycle? - How do we sunset obsolete shared components safely? - What incentives sustain inner source contributions over time? ### 🔮 Future Research - Compare identifier schemes vs. pure SBOM discovery. - Evaluate governance patterns across hardware-heavy orgs. - Study inner source retention effects on contributors. ### 💡 Implications - Strong policy enables safe, faster open-source use. - Identifiers and SBOMs align software and hardware governance. - Culture and communication determine inner source durability. ### 🧠 Learning Styles Assessment - Reading level estimate: Flesch–Kincaid Grade ≈ 10–11. #### 👀 Visual learners - Present: schematic of identifier-to-SBOM mapping. - Improve: diagrams of review board workflows. #### 🔊 Aural learners - Present: podcast format aids comprehension. - Improve: short audio recaps per topic. #### 🗣️ Verbal learners - Present: clear terms for policy and culture. - Improve: glossary for OSPO and SBOM acronyms. #### 🧩 Kinesthetic learners - Present: runbook exercises for governance steps. - Improve: labs for SBOM generation and review. #### 🧠 Logical learners - Present: policy-to-outcome chains. - Improve: decision trees for exceptions and approvals. #### 🧑‍🤝‍🧑 Social learners - Present: cross-team collaboration stories. - Improve: cohort-based inner source pilots. #### 🧘‍♀️ Solitary learners - Present: transcripts and linked resources. - Improve: worksheets and self-paced templates. #### 🌿 Naturalistic learners - Present: not applicable here. - Improve: none needed. ### 📊 Accessibility Assessment #### Screen reader semantics - Present: YouTube player supports captions. - Improve: publish accessible transcript with headings. #### Keyboard navigation - Present: standard player controls. - Improve: clear focus order in linked resources. #### Contrast and readability - Present: varies by linked sites. - Improve: enforce 4.5:1 in any shared templates. #### Text resizing and reflow - Present: YouTube responsive UI. - Improve: provide downloadable text without layout issues. #### Media and captions - Present: captions likely available. - Improve: add corrected captions and full transcript. #### Forms and interactions - Present: n/a in episode. - Improve: accessible feedback form for show notes. #### Standards reference - Map any gaps to WCAG 2.2 AA. ### 🌍 DEIB Assessment #### Cultural breadth - Present: enterprise perspective predominates. - Improve: include SMEs and global contexts. #### Inclusive language - Present: neutral, professional tone. - Improve: define jargon for newcomers. #### Neurodiversity support - Present: structured timestamps aid navigation. - Improve: icon+text cues in show notes. #### Representation - Present: limited voices in excerpt. - Improve: feature diverse practitioners. #### Psychological safety - Present: reflective, non-blaming discussion. - Improve: share governance escalation paths. ### ✅ Logical Validity #### Strong reasoning - Policy influences behavior; quote supports causality. See [H1]. - Identifiers improve reuse by enabling tracking; evidence supports. See [H3], [H4]. #### Fallacies - “Term started to come into existence” is vague. Add dates or citations. See [H2]. - Cultural claims lack metrics. Propose surveys and retention data. See [H6]. #### Tone of voice - Reflective and pragmatic. Anecdotal but grounded in practice. ### 🛡️ DARVO Analysis - Deny: none observed. - Attack: none observed. - Reverse victim/offender: not present. - Messaging focuses on lessons and process. ## 🎯 Conclusion - Governance and culture shaped open-source success in this story. - Build clear policies, identifiers, and inner source practices. - Share strategy widely and measure adoption for credibility. - Tag Coverage — #articleseed: 4 • #xref: 3 • #share: 1 • #bmf: 0 • #addendum: 1 ## 🧱 Refactor Appendix (append after 🎯 Conclusion) ### 📚 Literature Split Pad - Purpose: Stage Konik CEE units that become per-source Literature notes. - Split level: **H3**. - Include verbatim quotes under 25 words and a [view highlight] link. ### [H1] Review board policies constrain open-source choices > [!quote] [S3.Ep2 - Open Source Strategy](https://www.youtube.com/watch?v=rqW7E1Z_Twk) by an unnamed author via [[YouTube]]. Published [MISSING]. Accessed . > “the open- source policies that the review board set very much influenced what you could and couldn't do.” Two lines: impact on licensing and approvals. Add RACI examples. [view highlight](https://www.youtube.com/watch?v=rqW7E1Z_Twk&t=56) #xref #articleseed ID:rw_[MISSING] ### [H2] Teams assign part numbers to OSS components > [!quote] [S3.Ep2 - Open Source Strategy](https://www.youtube.com/watch?v=rqW7E1Z_Twk) > “they wanted to give part numbers to these open-source software projects so that they could track them.” Two lines: relate to SBOMs and SPDX identifiers. [view highlight](https://www.youtube.com/watch?v=rqW7E1Z_Twk&t=112) #xref ID:rw_[MISSING] --- ### 🔖 Atomic Split Pad (Zettel Candidates) - Purpose: Promote reusable claims into Atomic notes. - Split level: **H4**. - Each item: one idea, present tense, specific, testable. #### [Z1] Review boards steer open-source adoption via policy - Holds when approvals gate shipping. - Pointer: 00:56. Links: [[OSPO-Charter]] [[License-Policy]] #### [Z2] Identifier schemes improve cross-team component reuse - Holds when identifiers surface in SBOM tooling. - Pointer: 02:04. Links: [[SPDX]] [[SBOM-Process]] --- ### ✏️ Fleeting Queue (Extract by Selection) - Purpose: Capture quick actions or sparks for Fleeting notes. - Extraction: **Select one line** → “Refactor: Extract selection to new note (content only).” - Keep each line short and self-contained. - [F1] Draft review board charter outline — context/https://www.youtube.com/watch?v=rqW7E1Z_Twk #fleeting #inbox - [F2] Map part numbers to SPDX fields — context/https://www.youtube.com/watch?v=rqW7E1Z_Twk #fleeting #inbox - [F3] Outline inner source culture workshop — context/https://www.youtube.com/watch?v=rqW7E1Z_Twk #fleeting #inbox --- <!-- deep-read:sections end -->