The InnerSource Commons Roundtable - CourtneyR.dev's 2nd Brain

The InnerSource Commons Roundtable ![rw-book-cover](https://img.youtube.com/vi/Y3QQssEnG8o/maxresdefault.jpg) 🔗 **Source:** [The InnerSource Commons Roundtable](https://www.youtube.com/watch?v=Y3QQssEnG8o) > [!note]+ Document Notes > tags: #inner-source #community #open-source #devrel #ospo > author: InnerSource Commons > source: YouTube > reference: https://www.youtube.com/watch?v=Y3QQssEnG8o > date created: 2025-01-27 12:00 > > # 🏷️ Title: The InnerSource Commons Roundtable >  ## 🧰 Action Inbox - [H1] Join inner source gatherings or start local community — visit gatherings.innersource.org #community - [H2] Attend ISPO working group bi-weekly meetings — DM Jeff Bailey, Russ, or Kier for guidance #ospo - [H3] Explore patterns and playbooks for enterprise inner source programs — managing inner source projects book #governance ## 🧭 Table of Contents - [[#📝 Summary]] - [[#📖 Main Content]] - [[#🗒️ Notes]] - [[#📚 References]] - [[#🗣️ Paraphrase]] - [[#📰 Newsletter]] - [[#✅ Action Items]] - [[#🧪 Hypotheses]] - [[#📊 Methodology]] - [[#❓ Questions]] - [[#🔮 Future Research]] - [[#💡 Implications]] - [[#🧠 Learning Styles Assessment]] - [[#📊 Accessibility Assessment]] - [[#🌍 DEIB Assessment]] - [[#✅ Logical Validity]] - [[#🛡️ DARVO Analysis]] - [[#🎯 Conclusion]] ### 🔗 References - [InnerSource Commons](https://innersource.org) - [Gatherings Portal](https://gatherings.innersource.org) ## 📝 Summary - **What happened**: Four leaders from InnerSource Commons presented community growth, local chapters, program office strategies, and global vision - **Why it matters**: Inner source adoption is accelerating globally, appearing on Gartner hype cycles and in government mandates - **Key stakeholders**: Developers, open source program offices, enterprise engineering teams, community organizers - **Risks and tradeoffs**: Need to maintain central hub role while scaling locally; AI era requires new patterns for collaboration - **Bottom line**: InnerSource Commons provides the collaborative infrastructure for enterprises to adopt open source practices internally ## 📖 Main Content The InnerSource Commons has evolved from a small US-based group in 2015 to a global community spanning Japan, Europe, China, and the Americas. The roundtable covered four perspectives on community building and program implementation. **Local Community Development**: Yuki Hattori demonstrated how Japan built from translation efforts in 2020 to active corporate adoption by 2024, including creative content like "InnerSource Hero" music videos. The community model includes micro-gatherings, meetups, and summit-style conferences adaptable to regional needs. **Inner Source Program Offices (ISPOs)**: Jeff Bailey outlined how ISPOs organize around building reusable software projects and documentation. The working group publishes practical resources like goals/questions/metrics frameworks and playbooks integrated with the managing inner source projects book. **Event Organization**: Sebastian Spier shared lessons from coordinating the tri-city summit across Berlin, Yokohama, and New York. The Berlin event hosted 67 attendees from 29 organizations with seamless hybrid broadcasting and cross-timezone handovers. **Strategic Vision**: Russ Rutledge positioned inner source as more critical in the AI era, not less. While AI lowers technical barriers to code creation, team-to-team collaboration becomes the limiting factor. Inner source practices that break down engineering silos become essential competitive advantages. ## 🗒️ Notes #### ⏱️ [00:00](https://youtu.be/Y3QQssEnG8o?t=0) — [H1] Global community spans seven countries with structured programs - Key idea: InnerSource Commons operates local gatherings in Tokyo, Berlin, Vienna, Dublin, Shenzhen, Paris, São Paulo, and London - Evidence: "In 2024 there are seven gatherings... in 2025 there are six gatherings" #### ⏱️ [03:45](https://youtu.be/Y3QQssEnG8o?t=225) — [H2] Japan's organic growth from translations to corporate adoption - Key idea: Community started with translation efforts in 2020, achieved corporate adoption by 2024 - Evidence: "Out of blue actually some company started to practice inner source... I found some blogs writing about inner source" #### ⏱️ [06:30](https://youtu.be/Y3QQssEnG8o?t=390) — [H3] Creative community expression through InnerSource Hero music - Key idea: KDDI telecommunications created enthusiastic promotional songs for inner source practices - Evidence: "He created a song for inner source... about the readme and contributing.md to attract people" #### ⏱️ [08:15](https://youtu.be/Y3QQssEnG8o?t=495) — [H2] Three gathering styles support different community needs - Key idea: Micro-gathering, community meetup, and summit conference formats provide flexibility - Evidence: "Three styles for gatherings micro gathering and community meetup summit conference" #### ⏱️ [10:00](https://youtu.be/Y3QQssEnG8o?t=600) — [H1] ISPO working group builds reusable program artifacts - Key idea: Inner Source Program Offices organize around building communities and high-impact software projects - Evidence: "We intentionally organize around building communities and stitching people together" #### ⏱️ [12:30](https://youtu.be/Y3QQssEnG8o?t=750) — [H2] Goals-questions-metrics framework measures inner source value - Key idea: Systematic measurement helps find and track inner source projects across enterprises - Evidence: "Who uses the inner source projects? You can count how many times a project is used across the enterprise" #### ⏱️ [15:45](https://youtu.be/Y3QQssEnG8o?t=945) — [H3] Interactive documentation integrates community feedback - Key idea: Managing inner source projects book includes GitHub-integrated commenting for real-time questions - Evidence: "Integrated comment section... you sign in with GitHub and have questions... everyone in the community will see that" #### ⏱️ [18:20](https://youtu.be/Y3QQssEnG8o?t=1100) — [H2] Trusted committer pattern ensures community sustainability - Key idea: Working groups follow inner source patterns themselves as a community practice - Evidence: "We're drinking our own wine here... using the patterns themselves as we work as a community" #### ⏱️ [22:00](https://youtu.be/Y3QQssEnG8o?t=1320) — [H1] Tri-city summit required interface standardization - Key idea: Berlin coordinated with Yokohama and New York through shared ticketing, broadcasting, and handover protocols - Evidence: "Implement the right interfaces so we could plug this local event into this global event" #### ⏱️ [25:15](https://youtu.be/Y3QQssEnG8o?t=1515) — [H2] Community building strengthens organizational inner source adoption - Key idea: Hosting events sends internal message that inner source is prioritized and supported - Evidence: "Strengthen the message that inner source is something we want at SAP... constantly remind people" #### ⏱️ [28:30](https://youtu.be/Y3QQssEnG8o?t=1710) — [H3] Vision of universal inner source within organizational boundaries - Key idea: If everything can't be open source, at least make internal projects operate with open source practices - Evidence: "What if we could live in a world where things that cannot be open source were like if they were but in limited scope" #### ⏱️ [32:00](https://youtu.be/Y3QQssEnG8o?t=1920) — [H1] Inner source appears on Gartner hype cycle for software engineering - Key idea: Industry recognition shows inner source climbing toward plateau of productivity - Evidence: "Gartner publication put inner source on the hype cycle for software engineering... at the top of the list" #### ⏱️ [35:45](https://youtu.be/Y3QQssEnG8o?t=2145) — [H2] Government mandates and UN recognition validate approach - Key idea: US Share It Act requires inner source practices within federal government - Evidence: "US government passed a bill basically requiring inner source... the Share It Act to mandate sharing between government organizations" #### ⏱️ [38:20](https://youtu.be/Y3QQssEnG8o?t=2300) — [H1] AI era increases importance of collaboration patterns - Key idea: Code generation makes team-to-team collaboration the primary bottleneck, not technical implementation - Evidence: "As code generation becomes cheaper, the percentage impact of team-to-team bottlenecks will become greater inhibitor" #### ⏱️ [41:00](https://youtu.be/Y3QQssEnG8o?t=2460) — [H2] Working groups tackle emerging challenges like transfer pricing - Key idea: Community collaboration needed on topics like AI integration, transfer pricing, and regulatory compliance - Evidence: "Topic of transfer pricing I've heard for several years... we still don't have anything published" ## 📚 References - [InnerSource Commons Foundation](https://innersource.org) - [InnerSource Gatherings](https://gatherings.innersource.org) - [Managing InnerSource Projects Book](https://innersourcecommons.org/documents/managing-inner-source-projects/) - [InnerSource Patterns](https://patterns.innersource.org) ## 🗣️ Paraphrase - InnerSource Commons has grown from a small US group to a global community with local chapters, structured programs, and government recognition, demonstrating the scalability of open source practices within enterprises - Inner Source Program Offices provide systematic approaches to building reusable software and documentation, with working groups creating shared resources like metrics frameworks and playbooks that prevent organizations from solving the same problems in isolation - The AI era makes inner source more critical rather than obsolete, as code generation shifts bottlenecks from technical implementation to team collaboration and organizational silos that inner source practices are designed to address ## 📰 Newsletter The InnerSource Commons community is experiencing remarkable global growth, with active chapters across seven countries and increasing enterprise adoption. Recent highlights include Japan's creative community engagement (including promotional music videos!), successful tri-city summit coordination, and recognition from Gartner and government mandates. **Key Development**: Inner Source Program Offices (ISPOs) are providing structured approaches to internal open source adoption, with working groups publishing practical frameworks for goals, metrics, and project management. **WordPress Connection**: The collaborative patterns and community-building strategies demonstrated by InnerSource Commons offer valuable lessons for WordPress's own global community coordination and contributor onboarding efforts. **Action Opportunity**: Consider attending an InnerSource gathering or joining the ISPO working group if your organization is exploring internal open source practices or contributor experience improvements. Resources: [InnerSource Commons](https://innersource.org), [Gatherings Portal](https://gatherings.innersource.org), [Learn WordPress](https://learn.wordpress.org/) ## ✅ Action Items #### DevRel - Developer advocacy: Study inner source community building patterns for WordPress contributor onboarding, explore inner source-to-open source pipeline presentations - Education: Develop workshops on collaborative development patterns, create curricula around contribution workflows - Developer experience: Research inner source documentation patterns, implement GitHub-integrated feedback systems like managing inner source projects book - Community management: Apply gathering formats (micro/meetup/summit) to WordPress meetup organization, implement cross-timezone event coordination #### OSPO - Policy & Governance: Examine inner source governance patterns for WordPress project application, develop contribution policy templates - Community Engagement: Explore working group models for WordPress working groups, implement systematic feedback collection - Strategic Alignment: Develop goals-questions-metrics frameworks for WordPress community impact measurement - Developer Support: Create playbooks for inner source adoption that could inform WordPress enterprise adoption #### Community - Maintainers: Apply trusted committer patterns to WordPress core team coordination, implement "drinking our own wine" principle - Contributors: Study inner source onboarding flows for WordPress contributor experience improvements - Ecosystem: Research cross-project collaboration patterns from inner source community coordination #### WordPress - Community: Apply gathering format diversity to WordCamp organization, explore tri-city coordination for global events - Training: Integrate inner source collaboration patterns into WordPress contributor training materials - Design: Study community-driven creative expression (InnerSource Hero) for WordPress community engagement - Documentation: Implement integrated feedback systems for WordPress documentation, explore GitHub-integrated commenting #### The WPCC - Programs: Research fellowship models from inner source working groups, explore systematic mentorship approaches - Projects: Apply collaborative development patterns to WordPress governance projects ## 🧪 Hypotheses - Inner source practices provide successful models for improving WordPress contributor experience and reducing organizational silos - Working group structures with dedicated channels and regular meetings could enhance WordPress working group effectiveness - AI-assisted development will increase the importance of collaboration patterns that WordPress community already emphasizes - Local gathering formats could improve WordPress meetup engagement and global community coordination ### 📊 Methodology - Survey comparison of inner source vs WordPress contributor onboarding experiences to identify transferable practices - Pilot working group format with GitHub-integrated documentation and bi-weekly meetings for specific WordPress initiatives - Analysis of team collaboration bottlenecks in WordPress development to validate AI-era collaboration importance - Experimental application of micro-gathering format to WordPress local communities ### ❓ Questions - How could WordPress working groups adopt the systematic resource publication model demonstrated by ISPO working group? - What elements of inner source community building could enhance WordPress's global community coordination? - How might inner source program office frameworks apply to WordPress enterprise adoption strategies? ### 🔮 Future Research - Comparative analysis of inner source governance patterns vs WordPress governance for cross-pollination opportunities - Investigation of transfer pricing and compliance patterns from inner source for WordPress enterprise considerations - Exploration of AI integration patterns from inner source community for WordPress AI strategy ### 💡 Implications - Practice: Inner source collaboration patterns could improve WordPress team coordination and contributor experience - Policy: Working group governance models provide templates for WordPress working group effectiveness - Security: Inner source program office security patterns could inform WordPress enterprise security guidance - Education: Systematic resource publication models could enhance WordPress training material development - Funding: Inner source working group sustainability models could inform WordPress working group resource allocation ### 🧠 Learning Styles Assessment Reading level estimate: 12th Grade (technical content with clear explanations) #### 👀 Visual learners - Present: Community photos, event imagery, organizational diagrams - Improve: Process flow diagrams for inner source adoption, community structure visualizations #### 🔊 Aural learners - Present: Full video presentation with clear speakers and varied voices - Improve: Audio-only versions, podcast-style discussion summaries #### 🗣️ Verbal learners - Present: Clear definitions, analogies to open source, concrete examples - Improve: Glossary of inner source terminology, comparison matrices with open source #### 🧩 Kinesthetic learners - Present: Step-by-step community building guidance, working group participation instructions - Improve: Interactive checklists for starting local communities, hands-on workshop formats #### 🧠 Logical learners - Present: Goals-questions-metrics framework, systematic progression from micro to summit gatherings - Improve: Decision trees for community formats, ROI calculations for inner source programs #### 🧑‍🤝‍🧑 Social learners - Present: Community photos, collaborative working groups, cross-timezone coordination examples - Improve: Peer mentorship programs, buddy systems for new community members #### 🧘‍♀️ Solitary learners - Present: Individual role descriptions, self-directed resource exploration - Improve: Self-assessment tools for community readiness, independent learning paths #### 🌿 Naturalistic learners - Present: Organic community growth examples, ecosystem thinking about global coordination - Improve: Community lifecycle analogies, sustainable growth pattern descriptions ### 📊 Accessibility Assessment #### Screen reader semantics - Present: Clear heading structure, descriptive speaker introductions - Improve: Image descriptions for community photos, slide content descriptions #### Keyboard navigation - Present: Standard video player controls, accessible presentation format - Improve: Timestamped navigation, keyboard shortcuts for section jumping #### Contrast and readability - Present: Clear audio quality, well-lit video presentation - Improve: High-contrast slide versions, adjustable playback speed #### Text resizing and reflow - Present: Video scales appropriately, transcript available - Improve: Responsive transcript formatting, adjustable text size #### Media and captions - Present: Full transcript provided, clear audio - Improve: Professional captions, downloadable transcript formats #### Forms and interactions - Present: Standard video interaction patterns - Improve: Accessible feedback forms for community interest, clear error handling ### 🌍 DEIB Assessment #### Cultural bread --- ## Full Transcript [00:09] So um in this I mean 10-minut session [00:11] I'd like to introduce about the inner [00:13] source community. So uh no local [00:16] community more specifically. [00:20] So actually insource stories are [00:23] everywhere. So you can find some case [00:26] studies in your region and it means [00:30] inner source local community or maybe [00:32] the practitioners are also everywhere [00:35] across the world. So we are [00:38] collaborating to learn more and practice [00:40] more on inner source and then grow more. [00:43] So actually uh this is all about local [00:46] community but actually innosource [00:48] commons and know inner source community [00:50] itself is I mean essentially global [00:53] community. So it started in the United [00:56] States but in in Oscon uh in 2015 [01:01] actually uh we our first summit is I [01:04] mean including the private one uh is [01:06] started in 2015 but actually for I mean [01:10] more public one we started our I mean [01:12] global conference in 2016. [01:16] Thor and uh we did so many summits on uh [01:21] the United in the United States and then [01:23] in addition to the United States uh we [01:26] had a uh Switzerland, Germany and [01:28] Ireland and summit and then yeah [01:31] probably some of you who join us uh [01:34] today joined the Innosource summit this [01:36] year in maybe in Yokohama uh Berlin or [01:40] uh New York. [01:43] And apart from uh inner source summit [01:46] there is a specific program called inner [01:49] source gatherings. [01:51] So, Inosource gathering the very first [01:54] one was I mean initiated in Dublin and [01:58] then modeled uh after Dublin actually we [02:02] uh officially started the program in [02:04] Tokyo from Tokyo and then actually in [02:07] 2024 there are uh seven gatherings uh in [02:11] Tokyo, Berlin, Vienna, D uh Dublin, [02:14] Shenchen uh Paris and then Tokyo again [02:17] and in 2025 there are six uh gatherings [02:21] So Berlin, Paris, uh Tokyo twice, London [02:24] and S. Paulo. So this is our community [02:27] and then actually you can also start [02:29] your community. Um [02:33] if you are uh interested in building [02:36] your community, so please visit [02:38] gatherings.inosource.org. [02:41] You can find uh some uh records of the [02:44] event. For instance, uh Innosource [02:48] gathering. Yes. So in the inosource [02:50] gathering page uh there are event [02:52] reports available for each gatherings. [02:55] For instance in Tokyo gatherings [02:58] there are so many um speakers speak [03:01] about shared some inner source case [03:03] studies right. So you can start your own [03:08] community or just you can start I mean [03:11] if you are not interested in uh being [03:12] the community leader but you you are [03:14] still okay to I mean uh build some [03:17] conferences or have some meetups in your [03:20] region of course. So yeah then actually [03:24] there are several types of event in this [03:26] foundation. So the first one probably [03:29] the biggest one is the summit. So it's [03:31] the global conference and then [03:33] gatherings is a local conference. So [03:37] actually in between gatherings and [03:39] community calls there must be some local [03:42] uh meetups which is more smaller or [03:45] midsize uh meetups which is not um I [03:48] mean what we call conference. However, I [03:50] mean you have flexibility to align your [03:53] community or maybe align your market uh [03:57] industry size because um uh typically uh [04:01] some of the uh specifically more I mean [04:04] smaller industry or maybe countries uh [04:08] it's inner source term uh might be not [04:12] that popular. So actually you can start [04:14] small and then expand your community. [04:18] So um let me introduce some I mean cases [04:21] uh about uh our community. So I'm the uh [04:25] Japan community initiator. So actually I [04:27] will share some uh what happened in [04:31] Japan. [04:32] So I will switch my slide. [04:36] So [04:38] technically Japanese community I mean [04:40] has started in 2022. So our translation [04:44] project has uh had been started from [04:47] maybe 2020. However, I mean comm when it [04:51] comes to the community program [04:52] perspective our community has uh started [04:56] in 2022. [04:57] So in actually 2016 innosource the term [05:02] innosource is not that popular is has [05:05] just landed in Japan without any [05:07] context. So and then Yoshiake who is the [05:12] I mean translator of the innosource [05:13] learning path and also I started the I [05:16] mean initial activities on innource on [05:20] evangel uh evangelizing inner source and [05:23] then actually there are several [05:24] presentation from me and also other [05:27] people but actually in 2021 um inner [05:31] source if you search on inner source in [05:34] Japanese actually it shows only inner [05:36] soul I [05:38] result. So, but actually uh we [05:41] translated Inosource patterns as the [05:44] community effort and then we uh did some [05:47] online meetup because um it's still um I [05:51] mean uh there there are some sense of I [05:54] mean community is not that big. So [05:57] actually we started to record some [05:59] videos uh for Inosource and then we as a [06:03] again as a community effort uh we [06:06] started to translate uh some books into [06:09] Japanese and then we try to I mean we [06:12] did some uh edit on uh Wikipedia on [06:16] Inosaurus. So we are we uh built some [06:22] Japanese informations. [06:24] So in 2023 so something amazing [06:27] happened. So out of blue actually some [06:30] company started to practice inner [06:33] source. So it was an kind of amazing [06:36] thing for me. So actually I didn't even [06:40] realize that but actually I found uh [06:42] some blogs who uh write writing about [06:47] inner source. So and then actually in [06:50] 2024 we uh did the first Inosource [06:54] gathering in Tokyo. So this is the story [06:57] of Inosource gathering and then [07:00] something more interesting happened. So [07:04] uh I will share stop share and also [07:06] actually I will start um sharing again [07:10] uh with sound. So [07:13] this is insource hero. [07:16] So um probably you can feel enthusiasm [07:20] by this music. [07:24] So actually this is from KDDDI [07:28] which is a telecommunication company [07:32] and then he created a song for inner [07:34] source. So about the readme and then [07:38] contributing MD and to attract people to [07:42] and to let them start in the source. So [07:46] this is the brief introduction and also [07:48] there is an uh another English version [07:50] of the song. So uh you can also search [07:52] Inosource man. So initially Inosour Hero [07:55] was called Inosource man. However um [07:58] when it comes to DEI actually we renamed [08:01] uh to Inosour [08:04] but um anyways so this is the enthusiasm [08:08] of this I mean Japanese community. So [08:11] there are other uh community available. [08:13] So I only listed some active and also um [08:17] active Inosource community programs for [08:20] each oh sorry about that for each [08:22] region. So they they are the point of [08:24] contact. However of course there are so [08:26] many community activities in Germany and [08:29] then probably Thailand and other [08:31] communities. So I did haven't listed [08:34] because um uh when it comes to uh yeah [08:37] community program local community [08:39] program so there are specific name [08:41] available. So but actually if you can't [08:45] find your name or maybe if you can't [08:47] find your regions in this list of course [08:50] there must be there must be so many [08:53] practitioners uh of inner source in your [08:56] region. So we can probably connect you [08:59] to the maybe point of contact or maybe [09:02] the leader in this comm in the region or [09:05] maybe potential practitioners of inner [09:07] source. But um yeah feel free to ask us [09:10] about the community and our local [09:12] community. You can start your own [09:13] community and then again if you are not [09:16] interested in I mean leading community [09:19] or having gatherings you can still um [09:22] build uh create your I mean regional [09:24] slack channel in inner source commission [09:27] and then actually you can uh of course [09:30] start translating your um the resources [09:33] of inner source or you can just start [09:35] blogging on inner source but um it's up [09:38] to you. So um we have flexibility on [09:41] that and um if you have some ideas uh [09:44] for your region please ping us and then [09:47] please let us know about your idea. So [09:51] your idea and your activity and your I [09:54] mean opinion must be heard and then [09:57] actually uh we are looking forward to [09:59] receiving it. So and then more [10:02] specifically uh there are some um style [10:05] for gatherings. So there are uh three [10:07] styles for gatherings micro gathering [10:10] and then community meetup summit [10:12] conference. So typically we call like [10:14] gatherings for uh when it comes to um I [10:17] mean event program perspective from [10:20] event program perspective we uh treat [10:23] summit conference as a gatherings. [10:25] However yeah you can freely start your I [10:28] mean micro gathering or micro meetup in [10:30] your region of course. Yep. So let's [10:33] build inner source together in your [10:35] region. Thank you very much. [10:41] >> Okay, so hello everyone. I'm uh Jeff [10:43] Bailey. I work over at Nike. Uh I'm a [10:46] principal engineer there. What I do is a [10:49] focus on open an open source program [10:52] office there. And I'll talk to you a [10:53] little bit about that. Um, I probably [10:55] won't be as exciting as Yuki, but uh, [10:58] see, I'm more of a brass tax type of [11:00] person and I like to, uh, get into the [11:02] weeds of working on artifacts and, uh, [11:06] guidance for inner source program [11:09] offices, which I will introduce to you [11:12] briefly here. [11:14] So, uh, if you're not familiar with an [11:17] inner source program office, it's a lot [11:20] like an open-source program office, but [11:23] it's focused on inner source. And what [11:26] we do is we in a intentional way uh [11:30] organize around building uh communities [11:34] and uh stitching people together and [11:38] pushing them toward building reusable [11:41] and high impact software projects and [11:44] sometimes documentation. There's no [11:47] boundary there in terms of how you can [11:49] contribute to an inner source program. [11:52] Um and so in this group what we do is we [11:54] work together uh to build the content [11:58] that will help you drive your inner [12:00] source program office. Uh so Russ Rutled [12:04] and Kier are trusted committers in [12:07] there. We're all leaders that are [12:09] pushing forward uh inner source program [12:12] offices together. So if you need any [12:14] help with any of that then please DM any [12:17] of us. I'm just signing them up right [12:19] now for that uh cuz I think they'll be [12:22] happy to help. Um there's a channel, a [12:25] Slack channel that we join and I'll show [12:26] you more about that in a little while. [12:28] Um and feel free to stop me at any [12:30] moment if you have particular questions. [12:33] I like to do interactive presentations [12:35] instead of just talking uh a lot. Uh so [12:40] next here uh what do we do? Uh we build [12:43] inner source resources together. So you [12:46] may hear about patterns and practices [12:48] from Russ or uh Sebastian if he shows [12:51] up. There's another book that we adopt a [12:54] kindly adopted uh called the managing [12:56] inners source projects book which helps [12:58] you manage inner source projects within [13:01] your inner source program. Uh they can [13:04] also be used on the side without an [13:05] inner source program. There's people [13:06] that have come in here that just are [13:09] interested in inner source and have [13:11] benefited from these materials. So the [13:14] learning materials we teach you how to [13:16] do all those things. The inner source [13:18] hero helps you mostly uh tools and [13:21] templates uh you know we build uh [13:24] metrics. So there's goals questions and [13:27] metrics I'll show you a little while [13:28] that we use uh to measure the value of [13:31] inner source as we know the industry [13:33] wants us to show value. Uh and so how do [13:37] we do that? We attend bi-weekly [13:39] meetings. Highly encourage you uh to [13:42] join those meetings. It's a good place [13:44] to learn from other experts in the [13:46] industry and uh bring your problems, [13:49] bring your challenges and I'll speak to [13:51] that in a little while here. [13:55] So, how do you get involved? You join [13:57] the Slack channel, ESPO working group in [13:59] the inner source comments and I will [14:02] show you our calendar a little while [14:03] where you can attend a meeting. you just [14:05] add that to your calendar. And if you [14:07] have a challenge uh you are having [14:09] difficulty getting people to adopt inner [14:12] source in your company, then I encourage [14:15] you to join the ISPO working group and [14:18] learn how you can get past some of those [14:20] hurdles. [14:22] So I'm going to show you a little bit [14:23] about the OSPO book. So I was working in [14:26] the past with Yuki on this. We are [14:28] planning on adding a chapter on the [14:31] inner source program offices. So this is [14:34] a good place to jump in directly to [14:37] start learning about an OSPO and then as [14:39] an extension the ISPO. So you can take a [14:43] look there [14:45] and the ISPO working group. This is [14:48] again an overview. We have a inviting [14:52] contributing MD here. So if you want to [14:54] join that uh go to that URL you can [14:58] learn how you can contribute. So you are [15:00] going to come in, propose your challenge [15:02] to the ISPO working group, review some [15:04] contributions, maybe you see some [15:06] contributions you have expertise on or [15:09] you want to learn more about just by [15:10] leaning in and again participate in the [15:13] meetings and we publish content to the [15:15] managing inner source projects book and [15:17] the inner source patterns and there's [15:19] plenty of information on how to attend [15:21] the meeting and our board etc. [15:26] And so there's another, you know, [15:28] there's a nice documented page here if [15:30] you want don't like markdown, you don't [15:32] like uh poking around. And I want to [15:34] show you a little bit about Russ here. [15:35] So Russ has another presentation. So if [15:37] you don't like my presentation, you can [15:39] go look at Russ's presentation. I really [15:42] like uh how he put it together. So [15:45] there's a particular section where he [15:48] says, "No two companies are the same, [15:51] but not every company is wholly [15:53] different either." And so if we work [15:55] together uh in this community to sol to [15:59] to meet our challenges and to build [16:01] content for uh together in an open [16:05] source fashion then we we all win. We [16:08] all win in that uh that scenario. And so [16:11] I want to show you a little bit of the [16:13] work products that we have here. So we [16:15] have uh goals uh goals questions and [16:19] metrics was something we worked on. This [16:21] is in the managing inner source projects [16:23] book. Another thing we worked on you'll [16:26] see at the bottom here is [16:30] there's a integrated comment section. So [16:32] you sign in with GitHub and you have [16:34] questions about goals, questions, and [16:36] metrics. You can jump in there and ask [16:38] questions directly within the book. So [16:41] as you're learning, you can you're going [16:43] to get messages on that. Everyone in the [16:44] community will see that. This is super [16:47] helpful. [16:48] Uh there's a goals here. So you're [16:51] trying to find inner source projects in [16:53] your company. This is a challenge I had [16:55] when I came in Nike. I was like where [16:57] are the uh inner source projects? Where [16:59] are the projects I should use as a [17:01] template to start building my first [17:03] back-end service for example? That right [17:06] there is high value in terms of [17:09] understanding where your software is and [17:11] where the reuse lies within your [17:13] company. So that goal can be met uh [17:17] through [17:19] metrics. So who uses the inner source [17:22] projects? You can count [17:25] how many times a project is used across [17:27] the enterprise and other details like [17:31] where it's used etc. [17:33] So then the patterns uh this one also [17:36] speak to this I hope later but patterns [17:38] is where we contribute as well and some [17:41] of these key patterns are for example [17:45] inner source before open source. This is [17:47] something that we continually [17:49] see coming in our community. So, we [17:52] worked on some of this uh pattern here [17:55] trying to expand the value of it and [17:58] eventually get it published in the book [18:01] here [18:03] on the lefth hand nav to be able to get [18:06] more information. So, speaking quickly [18:09] to [18:11] where is it? Um [18:14] trusted committer. This is a pattern we [18:16] follow as well. We're drinking our own [18:18] wine here. We are trying to make sure [18:20] that we are using the patterns [18:22] themselves uh as we work as a community [18:25] in the inner source comments. [18:29] So this is another work product that we [18:31] uh contributed to. It's a we a lot of [18:34] times people are like what is my [18:36] playbook? How do I get from point A to [18:40] point Z in my inner source program? Uh [18:43] this is a good place to come in and see [18:46] how do I scale inner source at my [18:48] company and get an overview. You can [18:50] interactively click on these expand [18:52] details. If you go into some of these [18:55] nodes, you'll see uh direct links to [18:59] patterns etc that are applicable to the [19:03] journey that you're the part of the [19:05] journey you're in within your inner [19:06] source program office. [19:09] And so this is how you can contribute. [19:11] You can come to our board here. We have [19:14] many challenges that we just talk about [19:16] in this meeting typically or comes [19:19] through Slack. Someone says, "How do I [19:20] do this?" or "I'm having a challenge of [19:23] that." Um Michaela has been focusing on [19:26] creating an ISPO playbook. It's [19:29] something [19:29] >> and I have I have it pulled up if [19:31] anybody wants to see it. [19:33] >> Yeah, it's it's more of a micro uh jump [19:36] into inner source. A lot of people get [19:38] overwhelmed with the amount of [19:39] information that comes through uh their [19:42] company and I I completely empathize [19:44] with that. Uh we are all information [19:47] overloaded today uh in the current age. [19:50] So that's always welcome simplified uh [19:52] ways of of working. And so the the [19:55] calendar is where you can find uh [19:57] details about the next meeting. So today [20:01] is the 4th. It looks like our next [20:04] working group meeting is here. So you [20:06] can just go into this calendar and go to [20:08] copy my calendar and add yourself to the [20:12] next meeting. [20:15] There you go. And then the channel uh [20:18] there are bookmarks in the channel. You [20:20] can see all the things we just talked [20:22] about here. So this is a really good [20:23] place to just jump in and then ask [20:25] questions if you are in the channel. I [20:29] do an at here. I try not to do at [20:31] channel because I don't like to make [20:32] people mad. Uh we we let everyone know [20:35] that's online that there's another [20:37] meeting coming up about 24 hours before [20:39] the meeting and it's a great way to just [20:43] be become part of the community itself [20:46] is just to join the meeting even just [20:48] listen in understand a little bit about [20:51] what's going on in the inner source [20:53] world. Uh highly recommend uh jumping in [20:56] there. Uh so with that um are there any [21:00] questions? [21:05] Thank you everybody for being here and [21:07] thank you for the opportunity to speak. [21:10] Uh well uh Olive already introduced me a [21:13] little bit before. I will introduce [21:14] myself again and at some point in my [21:17] talk here uh first so what was the [21:20] mission that I was given today? Uh [21:23] prepare 10 minutes chat on uh these two [21:26] topics. my role as the local inner [21:28] source summit lead for Berlin and uh [21:32] also what inner source and inner source [21:34] commons means to me uh three slides were [21:37] mentioned but I guess that was not a [21:39] formal constraint I think that the time [21:41] and the 10 minutes are were the actual [21:43] constraint yeah so because I I went over [21:46] three slides cannot do anything with [21:48] three slides I guess don't have that [21:50] power uh so first of all about me I [21:54] joined SAP in uh 2010 as a developer. [21:59] Before that I had already uh around nine [22:02] years of experience in software [22:03] development but a different realm. [22:06] So I I am a former developer. Um I don't [22:10] develop software anymore although I [22:12] think I will always be a developer. It's [22:15] kind of a state of mind, right? And um I [22:18] am a long-term open-source enthusiast. [22:21] Uh I would uh use the word enthusiast [22:24] here because to be honest I don't have a [22:27] lot of contributions like source code [22:29] contributions to to open source. I have [22:32] like uh one uh big one and uh and some [22:36] other small ones. Uh but now I am [22:38] involved more on communities around open [22:41] source uh projects like this one and so [22:43] on and even with the topic of inner [22:45] source. Uh talking about that uh I have [22:49] become an inner source officer at SAP. [22:51] This is not like uh chief something or [22:54] anything like that. It's just a job [22:56] title. Uh that means uh one of my main [23:00] assignments is to uh spread uh the inner [23:04] source culture at SAP, grow the [23:07] awareness and grow the adoption of inner [23:09] source at at SAP where I am uh also a [23:13] member of the open source program office [23:15] that's actually my team since uh 2022. [23:20] So about my role in the inner source [23:23] summit as you know we recently had this [23:26] uh crazy idea of doing an event that [23:29] runs across uh three different locations [23:32] hosted or co-hosted by three different [23:34] companies and I was the one that was [23:38] responsible to make this happening uh in [23:40] Berlin and that is where it was hosted [23:43] by SAP. So uh to describe a little bit [23:47] about what does my role entail, I would [23:50] say it's about making sure that [23:53] everything happens well uh locally in in [23:56] my own subvent. say so things like uh [24:01] helping select the talks and the [24:04] speakers uh helping u uh let's say [24:07] ensure that we have a smooth check-in [24:10] experience that the speakers have a good [24:12] experience that they know what the the [24:14] conditions will be that they know when [24:16] uh to be where and all that kind of [24:19] stuff during the day. also the catering [24:22] or all the details like the technical [24:26] things that have to happen at the event [24:28] to ensure that the slides are showing up [24:30] that the that everything else is [24:31] working. So all that those things I was [24:34] uh responsible for uh securing the venue [24:38] the budget. So all that and on top of [24:40] that what uh we have to do when now to [24:43] use a software engineering u uh term I [24:46] would say is implement the right [24:48] interfaces so that we could plug this [24:52] local event into this global event and [24:54] that is stuff like ensuring that we use [24:57] the same ticketing system as everybody [24:59] uh keeping in contact with the global [25:01] event organization that means olive uh [25:03] all the time to be sure that things are [25:05] on track and uh be sure that we are [25:08] broadcasting the right way because this [25:10] was a hybrid event that's broadcast all [25:13] uh across the the world. So people could [25:16] join virtually and have a smooth [25:18] experience as if it was one big event. [25:21] And as part as of that experience we [25:24] also had this uh idea that the events [25:27] they should not just coexist but they [25:29] should be connected to each other. So we [25:31] did this handovers that we also had like [25:34] onsite we saw uh what was happening in [25:37] Yokohama and then we said hello and then [25:39] they handed over the torch to us and [25:41] then after that in the afternoon we did [25:43] the same uh for IBM. So these are the [25:46] kind of interfaces that I am uh talking [25:48] about. Yeah. So this was uh a very [25:52] interesting experience and I think it's [25:54] important to say uh why uh did we did do [25:58] this or personally why did I want to do [26:02] this and why did I want SAP to host uh [26:05] this event so there are thing I think [26:08] it's two main reasons one I wanted to [26:11] give back to the community I have been a [26:13] member of inner source commons for quite [26:16] some time I have been attending the the [26:19] events that we had until now virtually. [26:22] I have participated on great on-site [26:25] events and gatherings organized by other [26:27] people and uh I was feeling like it's uh [26:31] I should do something like that too. Now [26:33] it's my turn to get people to my home [26:37] and and welcome them and give them a [26:39] good time. So this is something that I [26:41] wanted to do and I also wanted then [26:44] what's in for SAP I wanted to strengthen [26:48] the message that uh inner source is [26:51] something that we want at SAP that's [26:53] very important uh we have to constantly [26:56] remind people mainly uh our own people [26:59] that hey this is something that you can [27:02] do you should do and you should [27:04] prioritize this. So we wanted to send [27:06] that message too and of course associate [27:10] the brand of SAP with this topic of [27:13] inner source that I consider so [27:15] important uh in the tech community and [27:18] well uh for the world I would say. Yeah. [27:21] And what were the results? Uh this is a [27:25] very nice picture that we took at the [27:27] end of the event. It doesn't even show [27:29] everybody who was there at this point in [27:31] the event. Some people had already left. [27:34] Uh but I like this picture very much. It [27:36] show that everybody's having a great [27:38] time there. And uh we did at the end [27:41] have 11 presentations and many more [27:45] presenters uh because it's we had many [27:48] occasions where we had more than one [27:49] presenter uh for each presentation. In [27:52] one occasion I think it was even three [27:53] people uh doing a presentation together. [27:56] We had uh 3 hours uh more or less of [27:59] space for people to network like at the [28:02] at the check-in, at the breaks, at the [28:05] lunch and all that. And I think that [28:06] went very well. I saw a lot of people [28:08] interacting and talking to each other. [28:11] And we did have an aftervent get [28:13] together that was also a great [28:17] opportunity for people to to network. So [28:19] that's not part of those 3 hours and not [28:22] everybody was available to go there but [28:24] I think we had maybe around 30 to 240 [28:28] people at the get together. Yeah. Uh in [28:31] total we had seven uh 67 on-site [28:34] attendees coming from 29 different [28:38] organizations and I think 26 more or [28:40] less of those were SAP employees. So we [28:43] also provided great content internally [28:46] to our uh employees and I like to say [28:49] this uh for me it was like a great inner [28:52] source party after thinking a little bit [28:54] it felt like my inner source birthday in [28:57] terms of like having a party where [28:58] everybody's coming to my home and I have [29:01] like this opportunity to re receive all [29:03] these nice people that I know from the [29:05] community and engage with them which is [29:07] something that it's not so often that we [29:10] can do that on site and tons of positive [29:13] uh feedback which was uh also great. [29:17] So the last part what inner source [29:19] commons means to me and what inner [29:21] source means to me. I think that's a [29:23] very interesting question to answer [29:25] that. Uh I think I I have to say like [29:27] what is my vision for the world? I would [29:30] like to be able to live in a world where [29:32] everything is open source. Yeah. Not not [29:34] everybody shares that vision. uh it's a [29:37] bit complicated and I know that we will [29:39] probably not uh get going to get there [29:42] easily. There's a lot of constraints and [29:44] so on. So why not then aim for something [29:48] a little bit uh easier that is what if [29:52] we could live in a world that at least [29:54] the things that cannot be open source [29:56] were were like if they were but in a [29:59] limited scope like within the [30:01] organizations that are handling those [30:03] things and this is inner source for me [30:05] once I had the first experience more [30:08] than 10 years ago where I contributed to [30:11] a project it was not my first [30:13] contribution to another project But it's [30:14] the first that looking back felt like [30:17] open source. Uh then everything where I [30:21] could not do that became extremely [30:23] frustrating because I knew another world [30:25] was possible. One that empowered me to [30:28] be the one participating in the solution [30:30] of my own problems. So that is inner [30:33] source for me. And what is inner source [30:36] commons where it's it's uh the place [30:39] where it feels like an inner source [30:41] home. It's this community. is this great [30:43] place of like-minded people that not [30:46] necessarily share my vision that [30:48] everything has to be open source but [30:50] they do share this other vision that [30:52] whatever cannot be open source should be [30:55] inner sourced and that is where I feel [30:58] the sense of belonging in this community [31:00] where I know I will find other people to [31:02] collaborate with and to learn from and [31:04] to share experiences [31:06] yeah with that a little bit over 10 [31:09] minutes uh let's build inner source [31:11] together and thank Thank you everybody [31:13] for hearing me out. [31:19] >> So I I'll share my slides in a minute [31:22] here. What I wanted to go over. So my [31:24] role now is as the executive director of [31:26] the inner source commons and also I'm a [31:30] very longtime member of the inner source [31:33] community. So what I wanted to share is [31:35] a little bit of perspective from both of [31:38] these roles. um both uh thinking about [31:41] the inner source and the inner source [31:43] commons foundation uh uh worldwide and [31:47] what uh what is our role what are we [31:49] trying to accomplish together where are [31:51] things going and then I also want to [31:53] reflect a little bit and share some of [31:55] the history from the beginnings of inner [31:57] source and the inner source commons [31:59] until now um so I'll I do have a few [32:02] slides it's way more than uh than three [32:07] slides let me share my screen here. Uh, [32:10] just a second. [32:13] All right. And I'm going to just use [32:16] these are some slides that Yuki made. [32:18] So, some of them you can see already. [32:20] Uh, and [32:23] oh, hold on a second. Okay. Let me try [32:25] to reshare. [32:27] Here it is. Okay. All right. So, I'll go [32:30] through some of these fast. Some of them [32:31] you've seen before. It's really just a [32:33] chance to for to put my memory to some [32:36] talking points. So, we're here in 2025 [32:40] uh talking about inner source. Uh some [32:42] of these I went over at the New York [32:44] event. I won't go through in in detail, [32:46] but yeah, a little history. So, inner [32:49] source, the concept uh at least as a [32:52] term started in the US in the year 2000 [32:56] with Tim O'Reilly, the O'Reilly from [32:59] O'Reilly Media, who was attempting to [33:01] start a business actually around inner [33:02] source consulting at the time. Uh so uh [33:06] from there things went dormant for a [33:08] while until [33:10] here the year 2015 Denise Cooper who was [33:14] the founder of inners source comments uh [33:17] decided that she wanted to make inner [33:19] source a worldwide move it and the [33:22] purpose was and I heard a question about [33:23] this earlier was to teach more people [33:26] how to do open source and open source [33:29] development and in these early years uh [33:32] 2015 and 2016 the inner source common [33:35] started and there were a few summits. Um [33:38] I joined the worldwide inner source [33:40] movement in 2017 at a summit that was [33:44] happening in Chicago in the US and that [33:47] was where I got the chance to meet [33:48] Denise for the first time and a little [33:51] bit about what inner source meant to me. [33:53] Uh I was uh working at Nike where Jeff [33:56] is located now. I think Jeff wasn't at [33:59] the company yet but he and I got the [34:00] chance to meet there anyway. I was [34:02] working at Nike and without knowing it, [34:04] I was doing inner source. I had an [34:06] innersource project. Um I didn't call it [34:08] inner source at the time, but it was uh [34:11] around running continuous deployment of [34:15] uh Nike's websites. We had like every [34:17] website at the company on the same [34:19] deployment pipeline and everyone was [34:20] doing inner source contributions to it. [34:22] So I was looking for a I realized the [34:25] problems I'm solving, they weren't [34:27] unique to me and having the mindset of [34:30] collaboration and sharing. I wanted to [34:32] go out and find others that were trying [34:35] to solve these same problems in their [34:37] company. I thought I can't be the only [34:38] one having these issues. I want to work [34:40] together. And so I found the [34:42] Interceource Commons which was really in [34:44] its infas in infancy and had the chance [34:47] to meet Denise there in in 2017. And uh [34:52] the whole thing I wanted to do which I'm [34:54] still trying to do today is to [34:56] collaborate as much as possible around [34:58] how to run inner source in our [34:59] organizations. Uh as Jeff shared [35:01] earlier, I started the ISPO working [35:04] group. Uh I think that was around 2020 [35:07] or so with the idea that we shouldn't [35:10] all go and try to figure out how to do [35:12] inner source at our own organizations. [35:15] There should be some type of open-source [35:17] tooling, training, documentation that we [35:20] can all create, all submit to some [35:22] common location and then all reuse [35:25] within our companies. And uh so I I got [35:28] involved actually here 2020 in creating [35:31] the inner source learning path that's on [35:33] the website. I was the the project [35:36] leader gathered an open source group of [35:37] people and we co-created the learning [35:40] path together that we could all use [35:41] within our within our companies. And [35:44] this really is still the vision I have. [35:46] We all need source. As Jeff shared, I I [35:49] put that presentation not all of our [35:51] companies is different. We need a common [35:53] place where we can come together and [35:54] work on inner source. Uh so really the [35:58] inner source comments to me was an open- [36:00] source location to do inner source. So [36:02] we're we're open sourcing our inner [36:04] source some tooling but mostly open- [36:06] source uh documentation. And I I [36:09] remember in the in the early days here [36:12] in um 2017 2018 it felt like worldwide [36:18] there was only a handful of [36:19] organizations that were doing inner [36:21] source by name. Uh and we all knew each [36:23] other. Uh it was a a a tight-knit group [36:27] and I remember kind of around 2018 [36:30] getting into 2019 all of a sudden we [36:33] started seeing people have uh blogs. I [36:36] remember the first time I saw a blog [36:37] that was on inner source that was from [36:39] someone I've never met before. Uh I've [36:41] been working I think for 2 years and [36:43] kind of aware of everyone that was [36:44] talking about inner source. So seeing [36:47] the way that started with a few US and [36:50] European participants until now uh just [36:53] completely completely blows my mind. [36:56] Let's see if we go uh forward here. I [36:58] think Yuki talked about this or not this [37:01] one the yeah the the gatherings. I mean [37:04] I I never seeing the way that things [37:07] have come worldwide from where they [37:09] started where we had a close group in [37:11] the US and Americas and everyone knew [37:14] each other. It's amazing all the Tokyo [37:16] gatherings. There's a robust uh China [37:19] inner source community. They're having a [37:20] gathering uh next week uh by the way [37:23] that are very highly attended by uh by [37:26] the most influential uh organizations uh [37:29] and companies in China. Uh yeah, seeing [37:32] that inner source hero in that video [37:34] that Michaela called out is is simply [37:36] simply amazing to me to think of the the [37:39] worldwide community that we have today. [37:42] So, uh let me just go forward from here. [37:44] Um so that's uh recognized uh from kind [37:48] of the late uh 2010s whereas this close [37:52] group uh things have really exploded as [37:54] far as awareness of inners source. Uh [37:58] here I'm familiar with uh a lot of these [38:01] US uh centric touch points for inner [38:02] source. I think just the global [38:04] community is a is a great example of the [38:06] growth. Uh also the uh Gartner [38:10] publication uh put inner source on the [38:13] hype cycle for software engineering. [38:15] Actually in 2023 it was among the uh the [38:18] top uh trends for software engineering [38:22] that was released at their Gartner [38:24] London conference. Uh inner source was [38:26] at the top of the list. It's showing up [38:28] here on the uh Gartner hype cycle for [38:31] software engineering. Uh here two years [38:33] ago was the last time they released this [38:35] publicly. Uh we've confirmed from [38:38] contacts at Gartner that inner source [38:39] continues to show up on the 2024 2025 [38:43] hype hype cycle uh going up the peak of [38:46] inflated expectations as people are uh [38:49] seeing the um uh the the uh uh [38:53] challenges and opportunities with [38:55] integrating into organization. uh [38:57] there's like a crossing of this peak and [39:00] now where we're at I think with inner [39:01] source worldwide is needing to get as [39:05] fast as we can up this slope of [39:07] enlightenment and to the plateau of [39:09] productivity around around inner source [39:12] and my vision what I'd like to see is [39:14] the innersource commons is occupying a [39:17] leading spot and being the hub where [39:20] companies and organizations can work [39:22] through the challenges that they have [39:24] with innersource and publish those [39:26] results holds publicly to help other [39:28] companies to get through these [39:30] challenges faster. I think later on I [39:33] have a slide about a few of those. Let [39:34] me go forward and see what's next here. [39:37] Um oh yeah so the inner source comments [39:41] foundation I think this was shared [39:43] before uh a ton of companies and [39:45] organizations and now uh have we've [39:48] collected and shared stories about [39:50] what's happening with inner source. Um [39:52] the people I think is one of the [39:55] strongest assets of the innersource uh [39:58] commons. Uh look at all these people [40:00] that are just having a great time with [40:03] inner source. Uh they love inners source [40:05] and they love being with each other. The [40:07] Inner Source Commons has a concept of [40:10] membership for uh community participants [40:13] that are continually involved in moving [40:17] inner source forward uh at a foundation [40:20] level and across the world. And there's [40:22] a wonderful tradition that just started [40:24] on its own where every time there's two [40:27] members that are together uh they take a [40:29] picture and share it. So here's a few [40:31] that I had access to uh from people in [40:34] the Americas. Um, this wasn't something [40:35] we had to tell people to do, but people [40:37] love being with each other so much that [40:39] there's always a picture uh taken and [40:41] shared. Um, I think uh this watercolor [40:45] from the Berlin Summit is an interesting [40:47] aspect that captures how people feel [40:50] about Inner Source and the Inner Source [40:52] community. The fact that an attendee uh [40:56] would decide to make a watercolor I [40:58] think expresses a depth of feeling and [41:01] connection uh that's had in the inner [41:04] source commons throughout the world. As [41:05] Germe said the summit just in Berlin [41:08] just gave a place where that uh where [41:10] that could be reflected and expressed. [41:13] So it's really an amazing community. Um [41:16] you know some tangible wins here. Inner [41:18] Source showed up uh at the United [41:21] Nations uh open source event uh [41:24] happening uh last summer. I've been in [41:26] touch with the organizers. They're [41:27] having an innource focus to part of the [41:30] UN open source event uh in the upcoming [41:32] year as well uh more local to me. The US [41:36] government passed a bill basically [41:38] requiring inner source to happen uh [41:42] within federal government. It's the [41:44] Share It Act uh to mandate sharing [41:47] between government organizations. So [41:49] really they're reaching for inner [41:50] source. So it's amazing to see these [41:53] worldwide strides that are being to [41:55] taken and there's probably stories like [41:56] this other parts of the world that I'm [41:58] not quite as close and connected to. So [42:00] really the community and inner source is [42:03] in a strong position and reaching to [42:06] expand even further. What I want to see [42:09] let me go ahead a little bit here [42:11] because I think I'm running out of time. [42:12] uh our leadership really what what I [42:15] want to see and what I think needs to [42:17] happen for the benefits of inner source [42:19] to reach across the world as soon as [42:22] possible is for the innersource commons [42:24] to uh focus and maintain itself as the [42:29] hub and central collaboration space for [42:31] inner source knowledge. This works out [42:34] as in the gatherings that Yuki talked [42:36] about in the summit uh in uh the [42:40] publishing that we do in the patterns [42:42] and other books that Jeff talked about. [42:45] Um I think that we need to have more uh [42:48] written work and publishing because that [42:51] can endure and become uh a part of AI [42:55] knowledge uh on on the internet. And we [42:57] do this through building a strong [42:59] inclusive community. And in the inner [43:01] source commons, we work open-source [43:04] style to share knowledge about about [43:08] inner source. Uh so let me go ahead [43:10] because I'm getting started. So I think [43:14] I'm running slower on time here. Um so [43:16] we talked about how one way we do this [43:19] is through working groups in the inner [43:21] source comments. Um there's some working [43:24] groups that are active today. Jeff [43:25] talked about the ISPO working group. A [43:27] working group is a set of folks in the [43:31] inner source commons community that want [43:33] to get together to tackle a common [43:36] challenge or a common need and hopefully [43:38] to produce something that can be shared [43:40] within the inner source commons. The [43:42] working groups have a dedicated slack [43:44] channel and a regular me meeting series [43:46] to meet share knowledge and work on [43:49] publishing information about a specific [43:51] topic. The working groups that are there [43:54] is f flexible. These are some working [43:56] groups that are here today, but anyone [43:58] who has an idea for a working group, uh, [44:00] please reach out to me. We'll see if [44:02] there's a way if your topic is not [44:04] covered by an existing working group to [44:06] start a new one and collaborate with [44:08] others in the industry around particular [44:11] challenge or aspect of innersource. [44:14] So a few um a few ideas uh these I took [44:18] from the Berlin summit where a working [44:22] group or other publishing or [44:23] collaboration is needed. Uh the topic of [44:26] transfer pricing I've heard for several [44:29] years uh we still don't have anything [44:31] published in the inner source commons [44:32] about this. I think these and the other [44:34] topics are uh AI uh also of course is [44:37] the top of the list is a good [44:39] opportunity for the community to come [44:42] together in future gathering summits and [44:44] working groups to publish and share more [44:46] information. Uh we have to do it in [44:49] order to continue to be the central hub [44:52] and the central collaboration space for [44:55] inner source knowledge in the industry. [44:57] Uh let me see what else I have here. [45:00] Yeah, a few other few other ideas. I [45:03] think this is from the uh Berlin area as [45:06] well that show topics that can be worked [45:07] on in the inner source commons. Let's [45:09] see. We talked about the United Nations [45:11] and share it act. A little bit about [45:13] inner source and AI. This is where I [45:16] think we have opportunity and really we [45:18] need to as a community to uh come [45:21] together and lead in defining what does [45:24] inner source mean and why is it relevant [45:26] in the age of AI. uh I'll give my [45:28] opinion which I also uh shared at the [45:31] summit is that uh in the AI area era [45:35] inner source is more relevant than ever. [45:38] Um I I've heard some people say like [45:40] well maybe inner source isn't needed [45:41] because generating code is easy and [45:43] cheap. Uh so it doesn't matter if [45:46] there's duplicated work. Um but we're [45:49] finding that's not uh true. uh first of [45:52] all AI is the ultimate inner source [45:54] consumer and everything that needs to be [45:56] done to enable project discovery and [45:58] contribution for a human is also needed [46:01] for AI clear documentation clear readme [46:05] uh also um AI can code generation can do [46:10] quick prototypes but need so much [46:12] guidance it's far easier for company to [46:16] encapsulate its best practices in inner [46:19] source projects that are been shared and [46:21] AI leverages instead of AI having to [46:25] write everything in in Scratch. And also [46:28] AI and code generation will lower the [46:31] technical barrier to create new code. [46:35] And increasingly the difficult part of [46:37] software development is teamtote team [46:40] and persontoperson collaboration which [46:42] is a big part of what inner source is [46:44] meant to solve to break down those [46:46] engineering silos. In the past, uh [46:49] because code took longer to create, uh [46:53] maybe it was okay or not as never, it's [46:56] never okay, but not as damaging to have [46:58] the collaboration between teams go [47:00] slower. But as code generation becomes [47:03] cheaper, the percentage impact of of [47:07] teamtoteam and persontoperson [47:09] bottlenecks will become a greater uh [47:12] inhibitor to effective software [47:14] development. So we can't afford to um to [47:18] have our teamtote team silos continue. [47:22] They will quickly become the limiting [47:24] factor in company effectiveness and all [47:26] the inner source practices that break [47:28] those down are more needed than ever. [47:31] All right, I think I've got about 15 [47:33] minutes here, so I want to stop. I know [47:35] we're on the time. I see some things [47:36] have shown up in the chat. I haven't [47:38] looked at them yet, but um I guess just [47:40] in closing, I'll say the reason I'm here [47:43] and the reason I I actually just went [47:45] and looked before this meeting at my [47:46] application for executive director of [47:48] the inner source commons and what I [47:50] wrote there, I'll share with you about [47:52] about what inner source means to me. Uh [47:54] when I think about the world today and [47:57] the problems that exist worldwide, I [47:59] know there's so much in software that [48:02] could help uh problems that are in the [48:04] world and individuals that are in the [48:06] world. And I also I believe there's more [48:09] to do than as a a worldwide and [48:13] companies collective that we're able to [48:14] do. And so inner source to me is a gift [48:18] to give to the world to make everyone in [48:21] it as effective as possible at helping [48:23] each other with the software they're [48:24] making. At the same time like Germe my [48:27] background is in software development [48:29] and I know the enobling power that comes [48:32] from the ability and autonomy to work in [48:35] an inner source manner. It's a gift that [48:37] I've received and I would be happy if I [48:40] could spend the rest of my life working [48:43] to give that to the world and all the [48:46] engineers in it. It's uh it will always [48:49] be I guess my tribe is the the [48:52] engineering and development population [48:54] and I know Inner Source is a gift to [48:55] them. So I'd be happy if I could find a [48:57] way to work on that uh for the rest of [49:00] my life and I know I have a home for [49:03] that and I'm glad to be here in the [49:04] inner source commons. All right, I'll [49:07] stop.  📄 **Full text:** ![[Full Document Contents/Articles/The InnerSource Commons Roundtable|The InnerSource Commons Roundtable, YouTube]] ## Highlights - inner source local community or maybe the practitioners are also everywhere across the world. So we are collaborating to learn more and practice more on inner source and then grow more. So actually uh this is all about local community but actually innosource commons and know inner source community itself is I mean essentially global community. So it started in the United States but in in Oscon uh in 2015 ([View Highlight](https://read.readwise.io/read/01km124s26rsd75ezh4rff23f8)) - Tags: 👻 ai highlighted - organize around building uh communities and uh stitching people together and pushing them toward building reusable and high impact software projects and sometimes documentation. There's no boundary there in terms of how you can contribute to an inner source program. Um and so in this group what we do is we work together uh to build the content that will help you drive your inner ([View Highlight](https://read.readwise.io/read/01km124s3aakapt5914kckde0c)) - Tags: 👻 ai highlighted - inner source as we know the industry wants us to show value. Uh and so how do we do that? We attend bi-weekly meetings. Highly encourage you uh to join those meetings. It's a good place to learn from other experts in the industry and uh bring your problems, bring your challenges and I'll speak to that in a little while here. So, how do you get involved? You join the Slack channel, ESPO working group in the inner source comments and I will ([View Highlight](https://read.readwise.io/read/01km124s4p376g607pgyjm9kex)) - Tags: 👻 ai highlighted - where I know I will find other people to collaborate with and to learn from and to share experiences yeah with that a little bit over 10 minutes uh let's build inner source together and thank Thank you everybody for hearing me out. >> So I I'll share my slides in a minute here. What I wanted to go over. So my role now is as the executive director of the inner source commons and also I'm a very longtime member of the inner source ([View Highlight](https://read.readwise.io/read/01km124s7n4qkp9vy00ejsw03y)) - Tags: 👻 ai highlighted - collaboration and sharing. I wanted to go out and find others that were trying to solve these same problems in their company. I thought I can't be the only one having these issues. I want to work together. And so I found the Interceource Commons which was really in its infas in infancy and had the chance to meet Denise there in in 2017. And uh the whole thing I wanted to do which I'm still trying to do today is to collaborate as much as possible around how to run inner source in our organizations. Uh as Jeff shared ([View Highlight](https://read.readwise.io/read/01km124sca8skgrh3grg69dd5e)) - Tags: 👻 ai highlighted - the inner source learning path that's on the website. I was the the project leader gathered an open source group of people and we co-created the learning path together that we could all use within our within our companies. And this really is still the vision I have. We all need source. As Jeff shared, I I put that presentation not all of our companies is different. We need a common place where we can come together and work on inner source. Uh so really the inner source comments to me was an open- ([View Highlight](https://read.readwise.io/read/01km124skcv9bapp531z7rzyd5)) - Tags: 👻 ai highlighted - source location to do inner source. So we're we're open sourcing our inner source some tooling but mostly open- source uh documentation. And I I remember in the in the early days here in um 2017 2018 it felt like worldwide there was only a handful of organizations that were doing inner source by name. Uh and we all knew each other. Uh it was a a a tight-knit group and I remember kind of around 2018 getting into 2019 all of a sudden we ([View Highlight](https://read.readwise.io/read/01km124ssbbxp88r61nnhts7n5)) - Tags: 👻 ai highlighted - really the community and inner source is in a strong position and reaching to expand even further. What I want to see let me go ahead a little bit here because I think I'm running out of time. uh our leadership really what what I want to see and what I think needs to happen for the benefits of inner source to reach across the world as soon as possible is for the innersource commons to uh focus and maintain itself as the hub and central collaboration space for ([View Highlight](https://read.readwise.io/read/01km124t1smbpf3g7s4q01gyr6)) - Tags: 👻 ai highlighted