S3.Ep2 - Stop Re-implementing Everything! | My Open Source Experience Podcast 🔗 **Source:** [S3.Ep2 - Stop Re-implementing Everything! | My Open Source Experience Podcast](https://www.youtube.com/watch?v=FTc22U8A8d8) > [!note]+ Document Notes > tags: [Open Source, OSPO, Collaboration] > author: [MISSING] > source: My Open Source Experience Podcast > reference: [https://www.youtube.com/watch?v=FTc22U8A8d8] > date created: > > # 🏷️ Title: S3.Ep2 - Stop Re-implementing Everything! | My Open Source Experience Podcast > <!-- deep-read:sections start --> ## 🧰 Action Inbox - [H1] Draft a “stop re-implementing” explainer — context/https://www.youtube.com/watch?v=FTc22U8A8d8&t=36 #articleseed - [H2] Create “adopt upstream UI” guidelines — context/https://www.youtube.com/watch?v=FTc22U8A8d8&t=109 #xref - [H3] Build “waste→innovation” pitch deck — context/https://www.youtube.com/watch?v=FTc22U8A8d8&t=155 #share - [H4] Document early GNOME vendor partnerships — context/https://www.youtube.com/watch?v=FTc22U8A8d8&t=238 #addendum - [H5] Add DEIB notes to OSPO onboarding — context/https://www.youtube.com/watch?v=FTc22U8A8d8&t=335 #articleseed - [H6] Capture origin stories for culture playbook — context/https://www.youtube.com/watch?v=FTc22U8A8d8&t=437 #share - [H7] Propose “peer hiring via community” SOP — context/https://www.youtube.com/watch?v=FTc22U8A8d8&t=439 #articleseed - [H8] Publish glossary: CDE, GNOME, KDE — context/https://www.youtube.com/watch?v=FTc22U8A8d8 #xref ## 🧭 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 - Include links cited in or relevant to the article. ## 📝 Summary - The episode argues against redundant engineering. Source: [video](https://www.youtube.com/watch?v=FTc22U8A8d8). - The speaker describes learning open source via CDE, GNOME, and KDE. - Collaboration reduces waste and unlocks higher-value work. - Early GNOME vendor work seeded commercial participation. - Bottom line: join upstream rather than duplicating efforts internally. ## 📖 Main Content - Many firms fixed the same bugs in private forks. - Shared upstream work reduces duplicated maintenance costs. - Linux desktops offered GNOME and KDE as open alternatives. See [GNOME](https://en.wikipedia.org/wiki/GNOME) and [KDE](https://en.wikipedia.org/wiki/KDE). - CDE showed the proprietary baseline. See [CDE](https://en.wikipedia.org/wiki/Common_Desktop_Environment). - Partnering with GNOME aligned vendors and community incentives. - Personal stories highlight DEIB challenges in early events. - Networks enabled hiring and OSPO talent pipelines. - Some specifics lack dates; YouTube metadata is limited. ### 🗒️ Notes #### ⏱️ [00:36](https://www.youtube.com/watch?v=FTc22U8A8d8&t=36) Duplicative effort realization ### [H1] Companies re-implement identical fixes in parallel > [!quote] [S3.Ep2 - Stop Re-implementing Everything!](https://www.youtube.com/watch?v=FTc22U8A8d8) by an unnamed author via [[My Open Source Experience Podcast]]. Published [MISSING]. Accessed . > “all of the companies in the room had teams that were working on the exact same thing.” This motivates upstream collaboration policies. [view highlight](https://www.youtube.com/watch?v=FTc22U8A8d8&t=36) #xref #articleseed ID:rw_[MISSING] #### ⏱️ [01:09](https://www.youtube.com/watch?v=FTc22U8A8d8&t=69) Choose upstream over forks ### [H2] Linux desktops invite vendor collaboration upstream > [!quote] [S3.Ep2 - Stop Re-implementing Everything!](https://www.youtube.com/watch?v=FTc22U8A8d8) > “they had Gnome and KDE … why can't we work with them … why can't we just use that” Adopt community UIs instead of private copies. [view highlight](https://www.youtube.com/watch?v=FTc22U8A8d8&t=109) #xref ID:rw_[MISSING] #### ⏱️ [01:55](https://www.youtube.com/watch?v=FTc22U8A8d8&t=115) Waste blocks innovation ### [H3] Reducing waste frees teams for higher-value work > [!quote] [S3.Ep2 - Stop Re-implementing Everything!](https://www.youtube.com/watch?v=FTc22U8A8d8) > “It wasn't just to reduce waste. It was like to inspire all the other things we could be doing.” Use shared maintenance to fund innovation. [view highlight](https://www.youtube.com/watch?v=FTc22U8A8d8&t=155) #articleseed ID:rw_[MISSING] #### ⏱️ [02:38](https://www.youtube.com/watch?v=FTc22U8A8d8&t=158) Early vendor-community ties ### [H4] Vendors engage GNOME to bridge enterprise and OSS > [!quote] [S3.Ep2 - Stop Re-implementing Everything!](https://www.youtube.com/watch?v=FTc22U8A8d8) > “I met with Helix Code … they were the primary drivers behind the Gnome … project.” Capture lessons for OSPO partnership playbooks. [view highlight](https://www.youtube.com/watch?v=FTc22U8A8d8&t=238) #addendum ID:rw_[MISSING] #### ⏱️ [03:35](https://www.youtube.com/watch?v=FTc22U8A8d8&t=215) Representation at events ### [H5] Early conferences reveal gender representation gaps > [!quote] [S3.Ep2 - Stop Re-implementing Everything!](https://www.youtube.com/watch?v=FTc22U8A8d8) > “You're a girl.” Include DEIB guidance in community programs. [view highlight](https://www.youtube.com/watch?v=FTc22U8A8d8&t=335) #articleseed ID:rw_[MISSING] #### ⏱️ [04:37](https://www.youtube.com/watch?v=FTc22U8A8d8&t=277) Culture stories matter ### [H6] Anecdotes transmit norms and operating principles > [!quote] [S3.Ep2 - Stop Re-implementing Everything!](https://www.youtube.com/watch?v=FTc22U8A8d8) > “it made the Windows bootup sound in the middle of the conference.” Use stories to teach etiquette and empathy. [view highlight](https://www.youtube.com/watch?v=FTc22U8A8d8&t=277) #share ID:rw_[MISSING] #### ⏱️ [04:41](https://www.youtube.com/watch?v=FTc22U8A8d8&t=281) Community→jobs pipeline ### [H7] Community networks enable resilient hiring paths > [!quote] [S3.Ep2 - Stop Re-implementing Everything!](https://www.youtube.com/watch?v=FTc22U8A8d8) > “she … introduced me to an opportunity … at … Linux and open source lab … in 2001.” Formalize referral programs that respect fairness. [view highlight](https://www.youtube.com/watch?v=FTc22U8A8d8&t=439) #articleseed ID:rw_[MISSING] #### ⏱️ [05:09](https://www.youtube.com/watch?v=FTc22U8A8d8&t=309) Repeated bias cues ### [H8] Recurrent surprise at women in OSS signals bias > [!quote] [S3.Ep2 - Stop Re-implementing Everything!](https://www.youtube.com/watch?v=FTc22U8A8d8) > “Oh, you're a girl.” Add bias training and reporting routes. [view highlight](https://www.youtube.com/watch?v=FTc22U8A8d8&t=309) #articleseed ID:rw_[MISSING] ## 📚 References - Episode video: S3.Ep2 - Stop Re-implementing Everything! — https://www.youtube.com/watch?v=FTc22U8A8d8 - Common Desktop Environment (CDE) — https://en.wikipedia.org/wiki/Common_Desktop_Environment - GNOME — https://en.wikipedia.org/wiki/GNOME - KDE — https://en.wikipedia.org/wiki/KDE ## 🗣️ Paraphrase - Many companies fixed identical issues alone, wasting effort and time. - Working upstream redirected energy toward innovation and user value. ## 📰 Newsletter - Tired of fixing the same bugs twice? This episode argues for upstream-first collaboration. GNOME and KDE show how shared platforms cut waste and speed progress. We also discuss representation and hiring through community networks. Watch and compare with your governance stack: https://www.youtube.com/watch?v=FTc22U8A8d8 ## ✅ Action Items #### DevRel - Publish a blog on “why upstream first” with WordPress parallels. - Demo a fork→upstream contribution workflow in a live stream. - Run office hours on evaluating upstream adoption risks. #### OSPO - Adopt an upstream-first policy with exception handling. - Maintain a UI adoption guideline for GNOME/KDE analogs. - Track duplicated bug-fix rates across teams quarterly. #### Community - Launch DEIB workshop series for event organizers. - Set up fair referral programs with transparency safeguards. #### WordPress - Document when to upstream fixes to Core or Gutenberg. - Create theme/plugin example repos showing upstream-first practice. #### The WPOCC - Fund microgrants for upstream mentorship cohorts. - Support DEIB speaker stipends and safety protocols. ### FAIR - Add a “no-duplicate-work” covenant to project charters. - Provide scorecards for upstream engagement and waste reduction. ## 🧪 Hypotheses - Upstream-first policies reduce duplicated fixes by 30% within two quarters. - DEIB training improves event satisfaction scores by 15%. - Referral programs increase diverse hiring by 10% year over year. - Story-based onboarding improves policy recall by 20%. ### 📊 Methodology - Compare bug-fix duplication rates pre/post policy. - Survey event participants before and after DEIB sessions. - Track hiring demographics with privacy safeguards. - Run controlled onboarding quizzes on policy retention. ### ❓ Questions - Which metrics best capture duplicated effort in practice? - Where does WordPress fork code unnecessarily today? - How can OSPOs measure partnership health with upstreams? - What safeguards keep referrals equitable and transparent? ### 🔮 Future Research - Study long-term ROI of upstream-first mandates. - Analyze DEIB interventions across OSS events. - Map talent pipelines from community to enterprise roles. ### 💡 Implications - Collaboration shifts budgets from maintenance to innovation. - Clear policies reduce friction during product decisions. - DEIB improves retention and community trust at events. ### 🧠 Learning Styles Assessment - Reading level estimate: Flesch-Kincaid Grade ≈ 11. #### 👀 Visual learners - Present: diagrams comparing fork vs upstream workflows. - Improve: swimlane of fix lifecycle from issue to merge. #### 🔊 Aural learners - Present: podcast narrative. - Improve: 3-minute audio summary with key takeaways. #### 🗣️ Verbal learners - Present: definitions of CDE, GNOME, KDE. - Improve: glossary with enterprise analogies. #### 🧩 Kinesthetic learners - Present: hands-on upstream contribution lab. - Improve: reproducible exercises with PR templates. #### 🧠 Logical learners - Present: cost model for duplicated fixes. - Improve: decision tree for adopt vs build choices. #### 🧑‍🤝‍🧑 Social learners - Present: office hours and mentorship. - Improve: cohort learning with peer reviews. #### 🧘‍♀️ Solitary learners - Present: written guides. - Improve: self-paced checklists and quizzes. #### 🌿 Naturalistic learners - Present: not applicable here. - Improve: sustainability lens on compute and travel. ### 📊 Accessibility Assessment #### Screen reader semantics - Present: standard YouTube semantics. - Improve: descriptive captions and a cleaned transcript. #### Keyboard navigation - Present: focusable player controls. - Improve: document hotkeys and provide skip links in notes. #### Contrast and readability - Present: platform defaults. - Improve: ensure 4.5:1 contrast in shared slides. #### Text resizing and reflow - Present: responsive player. - Improve: verify 200% zoom for shared resources. #### Media and captions - Present: auto-captions. - Improve: human-edited captions and downloadable transcript. #### Forms and interactions - Present: N/A for the video. - Improve: accessible feedback forms for events. #### Standards reference - Map gaps to WCAG 2.2 AA: https://www.w3.org/TR/WCAG22/ ### 🌍 DEIB Assessment #### Cultural breadth - Present: Western corporate examples. - Improve: add multi-region case studies. #### Inclusive language - Present: mostly neutral phrasing. - Improve: define jargon and acronyms consistently. #### Neurodiversity support - Present: chunked topics by timecodes. - Improve: icon+text cues and predictable navigation. #### Representation - Present: gender imbalance noted. - Improve: diversify panels and mentorship. #### Psychological safety - Present: respectful tone. - Improve: publish clear CoC reporting paths. ### ✅ Logical Validity #### Strong reasoning - Causal link: duplicated work reduces innovation ([H3]). The claim fits observed constraints. - Policy claim: upstream-first reduces parallel fixes ([H1], [H2]). It follows from shared maintenance economies. - Social claim: networks aid hiring ([H7]). Evidence matches typical OSS practice. #### Fallacies - Possible selection bias in anecdotes ([H5], [H8]). Mitigate with broader survey data. - Survivorship bias in partnership success ([H4]). Include failed attempts for balance. #### Tone of voice - Pragmatic and reflective. Personal stories ground arguments. ### 🛡️ DARVO Analysis - Deny: none observed. - Attack: none observed. - Reverse victim/offender: none observed. - The conversation remains constructive and historical. **Tag Coverage — #articleseed: 4 • #xref: 3 • #share: 2 • #bmf: 0 • #addendum: 1** ## 🎯 Conclusion - Stop re-implementing the same fixes in private forks. - Work upstream to cut waste and grow innovation. - Pair policy with DEIB and hiring pathways for durable culture. ## 🧱 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] Companies re-implement identical fixes in parallel > [!quote] [S3.Ep2 - Stop Re-implementing Everything!](https://www.youtube.com/watch?v=FTc22U8A8d8) by an unnamed author via [[My Open Source Experience Podcast]]. Published [MISSING]. Accessed . > “all of the companies in the room had teams that were working on the exact same thing.” Two lines: quantify duplicated fixes; set upstream-first guardrails. [view highlight](https://www.youtube.com/watch?v=FTc22U8A8d8&t=36) #xref #articleseed ID:rw_[MISSING] ### [H2] Linux desktops invite vendor collaboration upstream > [!quote] [S3.Ep2 - Stop Re-implementing Everything!](https://www.youtube.com/watch?v=FTc22U8A8d8) > “they had Gnome and KDE … why can't we work with them … why can't we just use that” Two lines: define adopt-vs-build decision points with examples. [view highlight](https://www.youtube.com/watch?v=FTc22U8A8d8&t=109) #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] Upstream-first reduces duplicated enterprise fixes - Scope: product teams with active OSS dependencies. - Links: [[OSPO Policy]] [[Collaboration Economics]] #### [Z2] Waste reduction enables measurable innovation time - Scope: track reclaimed hours post-policy. - Links: [[Metrics]] [[Engineering Productivity]] #### [Z3] Vendor-community partnerships accelerate UI progress - Scope: when governance and roadmaps align. - Links: [[GNOME]] [[Partnership Playbooks]] #### [Z4] DEIB practices improve event participation quality - Scope: conferences and meetups with clear CoC. - Links: [[DEIB]] [[Community Health]] #### [Z5] Community networks strengthen hiring resilience - Scope: transparent referrals with fair process. - Links: [[Talent Pipelines]] [[OSPO Roles]] --- ### ✏️ 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 upstream-first policy one-pager — context/https://www.youtube.com/watch?v=FTc22U8A8d8 #fleeting #inbox - [F2] Build a DEIB checklist for event hosts — context/https://www.youtube.com/watch?v=FTc22U8A8d8 #fleeting #inbox - [F3] Outline WordPress upstream contribution examples — context/https://www.youtube.com/watch?v=FTc22U8A8d8 #fleeting #inbox --- <!-- deep-read:sections end --> ## 📺 Video  --- # 📄 Full Transcript *Auto-generated from YouTube captions · timestamps roughly every 30 seconds · [watch on YouTube](https://www.youtube.com/watch?v=FTc22U8A8d8)* **[00:02]** [Music] Do you remember when you first learned about the concept of open source? >> Yeah, so I first got involved in in open source at when I was at Hulip Packard um first heard about it. I was managing the the CDE team which is the user interface for Unix. I was in the Unix lab um on the CDE team and I had about 30 people working on CDE and we weren't adding a lot of new features because technology had been around for a long time. Um so we were mostly just fixing bugs and **[00:32]** making it work on new hardware and advancing things. Um and I went to a standards meeting and I discovered that all of the companies in the room had teams that were working on the exact same thing. And not only did we have our own separate code bases, but we would agree on which bugs we were going to fix first. like we would have these meetings where we would vote on which bugs got fixed. And I thought they were all going to go back to our separate companies and you know have our engineers all redo this work. So it was very much like my college experience of having people all work on the same projects and write **[01:03]** their own individual solutions to it. Um and it it just felt like a waste of effort. Um so at that was at the time that Linux was first starting to come out um and you know come out in a big way that lots of people were using it and there was not just one user interface um like so we had CD on on HPX on all the Unixes um but on on Linux they had Gnome and KDE so they even had competing solutions to it and I thought why can't we work with them like they know how to work in the open why can't we just use that um so that that was my **[01:34]** my first experience with open source software It sounds like that that your main drive to keep exploring open source was this opportunity to reduce duplicative effort um like kind of industrywide. It it wasn't just to reduce waste. It was like to inspire all the other things we could be doing. Like if if you're if you're fixing the same bug somebody else **[02:04]** is, that means both of you are not doing, you haven't gotten to the part that you really wanted to do, right? You're just you're taking care of like the the basics. Um, so I really wanted to see what we could build together if we worked together on it as opposed to each of us individually having to get there. >> When did you first get involved on with with open source? like after learning about what the what the concept was. >> So this was around the year 2000 wasn't **[02:35]** 2000 some somewhere in that time frame. Um and I actually I met with Helix Code um which then became Zimeian which then got acquired by Susay. Um they they they were the primary drivers behind the Gnome um project. And so that that was my first experience. I actually remember meeting with Natt Freriedman in a restaurant where he had even those Blackberries that had little keyboards and the whole time he was talking to us, he was also like keying in text messages or they were emails because we didn't really have text messages then, emails **[03:07]** to other people. Um, and then I went out to visit them and I was I was in my 20s and I came back and told my manager I think I was the oldest person there. Um, so it was a very young very new effort to bring this open source into the commercial space. Um, and then I went to Guadecophagen. Um, that was my very first open-source conference to go to. Um, it was still relatively small. Um, the experience I really remember was walking in the door and as I walked in the door, there was **[03:37]** like a just a a table that you signed in at with one person behind the table. And when I told her my name, she was like, "You're a girl." And she had been trying to decide based on my name whether I was a woman or a man. and there weren't a lot of women in the field at the time. Um, I think a lot of women at that conference was the marketing team from from Helix Code. Um, and then I also had an embarrassing moment. I was sitting it was a one room conference, you know, maybe I don't know 100 people. I I actually don't know what the size was. Um, and I had this really cute HP **[04:09]** laptop. Um, they don't make them anymore. There was like it was much smaller than any laptop we have now. Is an HP800. Um, but it was running Windows and of course it made the Windows bootup sound in the middle of the conference. >> Yes, that can be embarrassing indeed. Particularly back then. >> Yes. Yes. But I couldn't get the the modem drivers to run on Linux and I needed to be able to dial it in for work. >> And Stormmy, you were my introduction into open source. **[04:40]** >> Oh, was I? >> So, yes, Stormmy and I were on a roller hockey team together. and I was in need for a job because the dotcom I had been working for had recently imploded. And so, uh, yes, through that connection, she, uh, actually introduced me to an opportunity that was in the Linux and open source lab, the fledgling Linux and open source lab at Cula Packard in 2001. >> That's pretty cool. >> And we got to work together. [Music] I can only share the experience of uh **[05:11]** stepping into a room where people look at me like, "Oh, you're a girl." They were they were telling me the same thing that they saw the name in the emails and they were like, "This looks like a I don't know in some language. I think my first name resembles more I think that's more like a name that they they give to uh men as opposed to women." And so they they were surprised and I'm like, "Yep, I'm a girl." >> Well, a lot of the Latin languages probably assume an O at the end is Yeah. **[05:41]** masculine.