Russ Rutledge – Welcome address #InnerSourceSummit2025

Russ Rutledge – Welcome address #InnerSourceSummit2025 🔗 **Source:** [Russ Rutledge – Welcome address #InnerSourceSummit2025](https://www.youtube.com/watch?v=51C_FyiZdxk) > [!note]+ Document Notes > tags: [inner-source, open-source, software-development] > author: Russ Rutledge > source: InnerSource Commons > reference: https://www.youtube.com/watch?v=51C_FyiZdxk > date created: 2025-01-11 15:30 > > # 🏷️ Title: Russ Rutledge – Welcome address #InnerSourceSummit2025 >  ## 🧰 Action Inbox - [H1] Join InnerSource Commons Slack community — QR code provided/website link #community - [H2] Check out InnerSource patterns book for implementation guidance — foundational resource #documentation - [H3] Share event learnings on social media with #InnerSourceSummit2025 tag — community engagement #networking ## 🧭 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 - [InnerSource Commons Website](https://innersourcecommons.org) - [InnerSource Patterns Book](https://patterns.innersourcecommons.org/) ## 📝 Summary - Russ Rutledge, Executive Director of InnerSource Commons, delivered the welcome address for the New York leg of InnerSource Summit 2025 - The event celebrates the 10-year anniversary of the InnerSource Commons Foundation as a global 24-hour summit - InnerSource adopts open source practices internally within organizations for internal code sharing and collaboration - Four key motivations for InnerSource: open source mastery, engineering efficiency, innovation catalyst, and people development - AI era makes InnerSource more relevant than ever as AI becomes both consumer and contributor to internal code ## 📖 Main Content InnerSource represents the adoption of open source software practices within organizations for internal code sharing. Unlike traditional siloed development, InnerSource makes internal projects visible to everyone in the organization, inviting both usage and contribution through pull requests and issue reporting—similar to open source projects but contained within company boundaries. The InnerSource Commons Foundation, celebrating its 10-year anniversary, serves as the global steward for InnerSource practices. With over 4,000 participants in their Slack community representing 1,000+ organizations, the foundation has produced the InnerSource Patterns book and hosted 30+ in-person events. Organizations pursue InnerSource for four primary reasons: developing open source mastery skills in a safe internal environment, improving engineering efficiency by breaking down silos and avoiding duplicated work, catalyzing innovation through cross-team collaboration, and enhancing developer happiness by removing roadblocks to getting work done. The emergence of AI amplifies InnerSource's relevance. AI serves as both the ultimate InnerSource consumer and contributor, benefiting from the discoverability and contribution ease that InnerSource promotes. As AI lowers technical barriers to code creation, human and social collaboration barriers—InnerSource's specialty—become the primary bottleneck in software development. ## 🗒️ Notes #### ⏱️ [00:00](https://youtu.be/51C_FyiZdxk?t=0) — [H1] Welcome and Event Introduction - Key idea: InnerSource Summit 2025 celebrates 10-year anniversary with 24-hour global event - Evidence: "We're celebrating today with 24 hours of inner source summit... 10 years ago the organization started" #### ⏱️ [02:30](https://youtu.be/51C_FyiZdxk?t=150) — [H2] Event Sponsors and Community - Key idea: Multiple global sponsors enable worldwide InnerSource community events - Evidence: "Event started about 16 hours ago in Japan, hosted in Yokohama at Mitsubishi Electric and then we just received the handoff from SAP hosted in Berlin" #### ⏱️ [04:15](https://youtu.be/51C_FyiZdxk?t=255) — [H1] What is InnerSource Definition - Key idea: InnerSource adopts open source practices internally within organizations - Evidence: "Innersource is adopting the practices of open source software internally within an organization for code that will only ever be shared internally" #### ⏱️ [05:45](https://youtu.be/51C_FyiZdxk?t=345) — [H2] InnerSource Core Principles - Key idea: InnerSource follows open source principles of openness, transparency, and voluntary contribution - Evidence: "Inner source follows and adapts many of the principles of open source openness, transparency prioritizing mentorship and encouraging voluntary code contribution" #### ⏱️ [06:30](https://youtu.be/51C_FyiZdxk?t=390) — [H1] Four Categories of Why InnerSource - Key idea: Organizations pursue InnerSource for mastery, efficiency, innovation, and developer happiness - Evidence: "As we speak with and listen to organizations throughout the world these four categories of why inner source come out" #### ⏱️ [07:00](https://youtu.be/51C_FyiZdxk?t=420) — [H2] Path to Open Source Mastery - Key idea: InnerSource provides safe internal practice for open source skills - Evidence: "Inner source gives a safe internal chance for individuals and companies to practice and learn the skills that will then aid them in successful involvement with open source" #### ⏱️ [08:00](https://youtu.be/51C_FyiZdxk?t=480) — [H2] Engineering Efficiency Benefits - Key idea: InnerSource breaks down silos and eliminates duplicate work across teams - Evidence: "Inner sources a path to engineering efficiency. It breaks down engineering silos. Avoids duplicated work" #### ⏱️ [08:45](https://youtu.be/51C_FyiZdxk?t=525) — [H2] Innovation Through Cross-Contamination - Key idea: InnerSource enables serendipitous innovation like Fleming's penicillin discovery - Evidence: "Project Fleming... Alexander Fleming who invented penicillin... happened completely as a happy accident of people working close to each other and sharing the things they're working on" #### ⏱️ [10:30](https://youtu.be/51C_FyiZdxk?t=630) — [H2] People Development and Happiness - Key idea: InnerSource removes roadblocks by enabling self-service through pull requests - Evidence: "Inner source is an incredibly enabling methodology... it enables anyone when needing something from a project to get what they want by their own effort only by opening a poll request" #### ⏱️ [11:45](https://youtu.be/51C_FyiZdxk?t=705) — [H1] InnerSource Commons Foundation Overview - Key idea: Global community of 4,000+ participants representing 1,000+ organizations - Evidence: "Over 4,000 participants in the inner source commons representing at least a thousand organizations" #### ⏱️ [13:00](https://youtu.be/51C_FyiZdxk?t=780) — [H2] Foundation Mission and Assets - Key idea: Educational nonprofit stewarding worldwide InnerSource knowledge through patterns and events - Evidence: "The stated mission of the charity is education education around inner source in the technical industry" #### ⏱️ [16:15](https://youtu.be/51C_FyiZdxk?t=975) — [H1] InnerSource History and Timeline - Key idea: InnerSource term coined 25 years ago by Tim O'Reilly, foundation started 10 years ago - Evidence: "Inner source started in the US with Tim O'Reilly actually coined the term way back in 2000 25 years ago" #### ⏱️ [19:30](https://youtu.be/51C_FyiZdxk?t=1170) — [H2] Government and Industry Recognition - Key idea: US government mandates code sharing through SHARE IT Act, UN panels discuss InnerSource - Evidence: "The share it act requires US agencies to share custom source code with each other... 15 billion dollars of software development that they believe could be impacted" #### ⏱️ [21:00](https://youtu.be/51C_FyiZdxk?t=1260) — [H1] AI Era and InnerSource Relevance - Key idea: AI makes InnerSource more relevant as ultimate consumer and contributor - Evidence: "In the AI era, inner source is more relevant than ever... AI is the ultimate inner source consumer, the ultimate inner source contributor" #### ⏱️ [22:30](https://youtu.be/51C_FyiZdxk?t=1350) — [H2] AI as Collaboration Bottleneck Solution - Key idea: AI lowers technical barriers, making human collaboration the primary bottleneck - Evidence: "As AI lowers the technical barrier to in the creation of code, the human and social barriers to effective code creation are going to become the bottleneck" #### ⏱️ [24:00](https://youtu.be/51C_FyiZdxk?t=1440) — [H1] Future Vision for InnerSource - Key idea: InnerSource will become industry standard within 10 years with local chapters and training - Evidence: "After 10 years inner source as the industry standard... robust and pervasive inner source is just the normal way that software development happens in organizations worldwide" ## 📚 References - [InnerSource Commons](https://innersourcecommons.org/) - [InnerSource Patterns Book](https://patterns.innersourcecommons.org/) - [InnerSource Commons Slack Community](https://innersourcecommons.org/slack) - [SHARE IT Act Information](https://code.gov/) ## 🗣️ Paraphrase - InnerSource applies open source development practices within organizations, making internal code projects visible and contributable to all employees rather than keeping them in departmental silos - The practice serves four main organizational goals: building open source skills safely, eliminating duplicate engineering work, fostering innovation through collaboration, and improving developer satisfaction by removing bureaucratic barriers - The emergence of AI amplifies InnerSource's importance because AI functions as both a consumer and contributor to code repositories, while human collaboration challenges become the primary constraint as technical code generation becomes easier ## 📰 Newsletter 🎉 **InnerSource Commons Celebrates 10 Years of Breaking Down Silos** The InnerSource movement just marked a major milestone with a 24-hour global summit celebrating a decade of bringing open source practices inside organizations. For WordPress professionals, this approach offers valuable lessons for internal development workflows. **Key Takeaway:** InnerSource treats internal company code like open source projects—visible to all employees, welcoming contributions via pull requests, and prioritizing documentation and mentorship. This eliminates the "not invented here" syndrome and reduces duplicate work across teams. **WordPress Connection:** Many agencies and large WordPress installations could benefit from InnerSource principles when developing internal tools, custom plugins, or client solutions that could be reused across projects. **AI Advantage:** As AI tools make code generation easier, human collaboration becomes the bottleneck. InnerSource practices that emphasize discoverability and contribution ease position teams well for AI-assisted development. Resources: [InnerSource Commons](https://innersourcecommons.org/), [Patterns Book](https://patterns.innersourcecommons.org/), [Learning Paths](https://innersourcecommons.org/learn/) ## ✅ Action Items #### DevRel - Developer advocacy: Create InnerSource awareness talks for WordPress conferences and meetups - Education: Develop learning paths connecting WordPress development with InnerSource practices - Developer experience: Document internal tool contribution processes using InnerSource patterns - Developer marketing: Share case studies of WordPress agencies using InnerSource approaches - Community management: Foster internal contribution culture in WordPress organizations #### OSPO - Policy & Governance: Adapt InnerSource contribution policies for internal WordPress development - License Compliance: Apply InnerSource patterns to internal GPL-licensed WordPress projects - Software Inventory: Track internal WordPress tools and plugins using InnerSource discoverability - Developer Support: Train WordPress teams on InnerSource collaboration practices - Community Engagement: Bridge internal InnerSource practices with WordPress.org contributions - Strategic Alignment: Measure InnerSource adoption impact on WordPress development velocity #### Community - Maintainers: Apply InnerSource mentorship patterns to WordPress core contribution onboarding - Contributors: Use InnerSource practices for cross-team WordPress plugin collaboration - Sponsors: Support InnerSource adoption in WordPress organizations through funding and resources - Ecosystem: Coordinate InnerSource best practices across WordPress agencies and enterprises #### WordPress - Core: Implement InnerSource-inspired processes for cross-team contributions - Community: Create InnerSource local chapters for WordPress developers - Training: Develop InnerSource learning paths specific to WordPress development workflows - Documentation: Apply InnerSource patterns to improve internal WordPress project documentation - Meta: Use InnerSource practices for .org tool development and collaboration ## 🧪 Hypotheses - Organizations adopting InnerSource practices will see 30-50% reduction in duplicate code development within 12 months - AI-assisted development will accelerate InnerSource adoption as collaboration barriers become more visible bottlenecks - WordPress agencies implementing InnerSource will demonstrate measurable improvements in cross-project code reuse - InnerSource adoption correlates with increased employee satisfaction and reduced development frustration ### 📊 Methodology - Survey WordPress agencies before/after InnerSource adoption measuring code reuse metrics - A/B test AI coding assistance with/without InnerSource-structured codebases for efficiency gains - Longitudinal study tracking developer satisfaction scores in organizations implementing InnerSource - Case study analysis comparing WordPress development velocity across InnerSource vs. traditional siloed approaches ### ❓ Questions - How can WordPress-specific development patterns be adapted for InnerSource implementation in agencies? - What metrics best demonstrate InnerSource ROI for WordPress organizations considering adoption? - How do InnerSource practices intersect with WordPress.org contribution workflows and GPL compliance? ### 🔮 Future Research - InnerSource pattern development specifically for WordPress multisite and plugin architectures - Integration studies between InnerSource practices and WordPress contribution processes - AI-assisted InnerSource implementation frameworks for non-technical WordPress organization leaders ### 💡 Implications - Practice: WordPress developers should learn InnerSource patterns for improved internal collaboration - Policy: Organizations need contribution guidelines that bridge internal InnerSource and external WordPress.org practices - Security: InnerSource visibility requirements must balance with WordPress security considerations - Education: WordPress training programs should incorporate InnerSource collaboration methodologies - Funding: Investment in InnerSource tooling and processes may accelerate WordPress development ROI ### 🧠 Learning Styles Assessment Reading level estimate: 12th grade (Flesch-Kincaid) #### 👀 Visual learners - Present: Organization logos, timeline graphics, community photos - Improve: InnerSource workflow diagrams, before/after collaboration visualizations #### 🔊 Aural learners - Present: Full video presentation with clear narration - Improve: Podcast-style summary, discussion questions for group learning #### 🗣️ Verbal learners - Present: Clear definitions, analogies (Fleming/penicillin story), examples - Improve: More case study narratives, step-by-step implementation stories #### 🧩 Kinesthetic learners - Present: QR codes for immediate action, Slack community joining - Improve: Hands-on InnerSource implementation workshop materials #### 🧠 Logical learners - Present: Clear timeline, structured four-category framework, cause-effect relationships - Improve: Decision trees for InnerSource adoption, ROI calculation templates #### 🧑‍🤝‍🧑 Social learners - Present: Community emphasis, Slack channels, global summit format - Improve: Local meetup organizing guides, peer mentoring frameworks #### 🧘‍♀️ Solitary learners - Present: Self-directed learning paths mentioned, patterns book reference - Improve: Individual assessment tools, self-paced implementation guides #### 🌿 Naturalistic learners - Present: Organic community growth analog --- ## Full Transcript [00:06] We'll get started uh here in the room in [00:09] New York. And uh also uh welcome to any [00:13] people online who are just joining uh or [00:15] more likely who have stayed over and are [00:17] continuing to watch the the broadcast. I [00:20] think we've got a little over a hundred [00:21] people online also joining in for this [00:23] leg of Inner Source Summit. Well, my [00:26] name is Russ Rutled. I'm the executive [00:28] director of the Inner Source Commons uh [00:31] that is co-sponsoring [00:33] uh this event. It's my pleasure to give [00:35] the welcome to our uh New York leg of [00:39] Inner Source Summit 2025. Uh so this [00:42] event today is a special one. Well, I [00:45] think an inner source day is always [00:47] special. Uh we have a a saying uh in the [00:50] inner source comments, happy innersource [00:52] day. uh any day that we're doing inner [00:54] source is a day of happiness for [00:55] ourselves and a chance to give happiness [00:57] to others and uh this event is [01:00] especially happy because we're [01:01] celebrating the 10-year anniversary of [01:04] the Interceource Commons Foundation as [01:07] an organization. So 10 years ago the [01:10] organization started and it's been a [01:12] long and storied journey to this point [01:14] where there's a global community and [01:16] we're celebrating today with 24 hours of [01:20] inner source uh summit. We're here on [01:22] the last leg of it here in New York. So [01:26] uh for the event today uh we want to [01:28] start by thanking our event sponsors. Uh [01:32] we're all sitting here in this wonder [01:34] wonderful facility here at IBM. I want [01:37] to thank IBM for hosting uh also our [01:41] other location sponsors. This event [01:44] started uh about 16 hours ago in Japan, [01:47] hosted in Yokohama at Mitsubishi [01:50] Electric and then we just received the [01:52] handoff from SC SAP hosted in Berlin. So [01:56] thanks to our uh host sponsors. Uh in [02:00] addition uh we have other SP others that [02:02] have helped with uh Inner Source Summit. [02:05] uh thanks to GitH uh Git Lab, Red Hat [02:09] and then uh Bera solutions which are [02:11] also some Summit sponsors. [02:14] Um in addition to sponsors for this [02:17] particular event, we're thankful for our [02:18] general sponsors of the Inner Source [02:21] Commons whose support also goes into [02:23] putting on events like these. Um the [02:26] support of these organizations are what [02:28] allows this community to thrive and for [02:30] us to be meeting here together today. [02:32] Thank you for our partners, sponsors, [02:35] our supporting sponsors. Uh I'll call [02:37] out here since we're at the uh IBM [02:39] headquarters, IBM is also a general [02:41] sponsor of the Inner Source Commons for [02:43] which we're very thankful and really [02:45] helps the work of Inner Source [02:46] throughout the world. [02:49] So for those who are uh just joining [02:52] whether online or in person, we want you [02:55] to post and share about what you're [02:58] learning here, about what you're excited [03:00] about. put it on your favorite social [03:03] media platform. Uh we're watching [03:06] encouraging the use of the Inner Source [03:07] Summit 2025 tag. Uh also uh for in [03:13] person and uh online, we want to invite [03:16] you to join the Inner Source Commons [03:18] Slack. I know that many of you are on [03:20] the Slack already. Some of you, it's [03:22] probably how you found out about the [03:23] event, but if you're not there, you can [03:26] find the link very easily on the Inner [03:28] Source Commons website. uh or you can [03:31] take out your mobile device and scan [03:33] this QR code. That'll put you in the [03:35] Slack. For the event today, if you have [03:39] questions for the speakers, we're going [03:41] to be using the Slack as our location [03:45] for Q&A. So, just right there in the [03:48] general channel of Slack, you can post [03:50] your questions. And if you're online, [03:52] there'll be people watching for those [03:54] and making sure that your question gets [03:56] asked of the in-person speaker. [03:59] All right. Well, today we got a [04:01] fantastic program lined up with inner [04:05] sorcerers uh from uh around the world [04:08] and around the Americas here in our New [04:12] York lake. Uh the way things are going [04:15] to go today is for those watching [04:17] online, there's a continuous schedule of [04:20] inner source content. Uh this schedule [04:24] is also available on the event page on [04:26] the website where you can follow it [04:27] there. Now, uh, for those of us who are [04:30] here in person, there will be a chance [04:33] to take a few breaks, uh, morning break, [04:36] afternoon break, a lunch break. So, we [04:39] will not be going as part of the 24 [04:41] hours uh, here in person, but we'll have [04:43] some breaks. And while the in-person [04:46] crowd is on break time, uh, there'll be [04:48] online virtual speakers that continue to [04:51] share about innersource so that the [04:53] online stream has a continuous feed of [04:55] speakers. Okay. [04:58] All right. Uh I'm just get started with [05:00] a little bit of background for anyone [05:02] who's new to inner source, new to the [05:05] inner source commons community with a [05:07] little bit of history and level setting [05:10] as we get started learning more about [05:11] inner source. Uh first of all, what is [05:14] inner source? Innersource is adopting [05:18] the practices of open source software [05:20] internally within an organization for [05:23] code that will only ever be shared [05:27] internally running it as if it were an [05:30] open source project uh within the [05:32] company. That means it's visible to [05:34] everyone at the organization. Everyone [05:36] is invited to use it and everyone is [05:39] invited to contribute to it to open a [05:41] poll request or open an issue just like [05:44] you would see with an open source [05:45] project except for a company internal [05:48] project. Uh inner source follows and [05:52] adapts many of the principles of open [05:54] source uh openness, transparency uh [05:59] prioritizing mentorship and encouraging [06:01] voluntary code contribution. These [06:04] principles are outlined on the inner [06:06] source commons website. Uh there's a [06:08] series of learning path videos that give [06:10] more information example on the [06:12] importance of these principles in making [06:14] inner source work and give training [06:16] ideas of how to implement them at your [06:18] organization. So definitely check that [06:19] out. Um so why inner source? I find this [06:23] is so connected with um with what is [06:27] inner source is what do we hope to gain [06:30] by it? Uh as we speak with and listen to [06:34] uh organizations throughout the world [06:36] these four categories of why inner [06:40] source come out. Uh so you might [06:43] identify uh with some of these and not [06:45] with others and that's okay. Many [06:47] organizations maybe have just one of [06:48] these that's a motivation for inner [06:50] source. Sometimes the way that we pursue [06:52] or think about inner source in our [06:54] organizations is different based on the [06:56] results that we want to see. So I want [06:59] to share these so that as you listen to [07:00] speakers and have conversations uh you [07:03] can identify what is your why for inner [07:07] source and uh look through it in that [07:09] lens as you learn about inner source [07:10] today. Uh so briefly uh inner source is [07:14] a path at a personal or professional [07:16] level uh or at an individual or [07:18] organization level to open source [07:20] mastery. Inner source gives a safe [07:23] internal chance for individuals and [07:25] companies to practice and learn the [07:28] skills uh that will then aid them in [07:30] successful involvement with open source [07:32] without having to learn in in public and [07:36] have those learnings be something that [07:37] are visible outside the organization. [07:40] Um, next one. Inner sources. A path to [07:42] engineering efficiency. It breaks down [07:45] engineering silos. Avoids duplicated [07:48] work. Allows teams to build on the [07:51] successes of others to stop reinventing [07:54] the wheel and move forward with work on [07:57] the team that is specific to their [07:59] product domain instead of uh doing work [08:02] that's already been discovered elsewhere [08:04] inside the organization. [08:07] Inner source is a path and a catalyst [08:09] for innovation. Um there's a neat um [08:13] innersource enablement project that I [08:15] heard about uh that called itself [08:17] project Fleming and as a a story about [08:20] the way this works. The reason why it [08:22] had this uh this name is Alexander [08:25] Fleming who invented penicellin was a [08:28] researcher working in a lab and uh in [08:31] the samples of uh that he was working [08:34] with there was some crosscontamination [08:36] from an adjacent lab that was completely [08:38] by accident and as he saw the results of [08:41] this contamination had in his experience [08:43] it put him on the path where eventually [08:45] discovered penicellin which is just a uh [08:47] you know an amazing thing in the medical [08:49] field today and it happened completely [08:50] as a as a happy accident of people [08:53] working close to each other and sharing [08:54] the things they're working on. Uh in [08:56] this case inadvertently uh inner source [08:58] is the same way as we bring together [09:00] people from different parts of the [09:02] organization. The thing that gets [09:03] produced is better than anything that [09:05] could have done by any single team. Uh [09:08] even a central team mandated to solve a [09:10] problem once for the company can never [09:12] have all the insights that could come by [09:15] inviting consumers from around the [09:16] organization. [09:18] Um and lastly, uh people development [09:20] happiness. Uh inner source is an [09:23] incredibly enabling methodology to adopt [09:27] internally. Uh it enables anyone when [09:30] needing something from a project to get [09:32] what they want by their own effort only [09:35] by opening a poll request. We're taking [09:38] away roadblocks and silos that are [09:40] frustrating to our engineering and [09:42] development teams that have to spend [09:44] time on the non-engineering [09:46] non-productive task of negotiating [09:48] across projects uh and uh vying for [09:52] features to get in. Uh with inner source [09:54] you can just open a pull request and and [09:56] move on with writing more code. Okay. So [09:59] that's a little bit about inner source. [10:01] So the inner source commons foundation [10:04] is a separate entity that is stewarding [10:07] the practice of inner source in the [10:09] industry throughout the world. Uh as we [10:12] look at our online Slack community [10:14] there's over 4,000 participants in the [10:16] inner source commons representing at [10:18] least a thousand organizations. [10:21] uh over the past 10 years there've been [10:23] over 30 in-person events and beyond talk [10:27] many of the best practices of [10:29] innersource are documented and probably [10:31] is in what is the foundation's most [10:34] durable long-lasting asset which is the [10:36] inner source patterns book you can find [10:38] that linked on the inner source commons [10:40] website uh we continually receive [10:42] feedback that it's a very uh valuable [10:44] tool for capturing patterns of how to do [10:47] inner source at your organization so the [10:49] innersource commons is a nonprofit [10:53] organization uh uh founded uh 10 years [10:56] ago as we say and incorporated uh 5 [10:59] years ago as a public charity in the [11:01] United States. The stated mission of the [11:04] charity is education education around [11:07] inner source in the technical technical [11:10] industry. So it's been a long a long [11:14] journey for the innersource commons. Oh, [11:16] here's our our mission. Uh, educating [11:18] and supporting innersource throughout [11:20] the industry and throughout the world, [11:21] especially stewarding the worldwide body [11:24] of inner source knowledge. We do that [11:26] through assets like the patterns or [11:28] conferences like we're here in today. [11:30] All right, there's some logos of [11:33] organizations [11:34] um the the dozens I think we're over a [11:36] hundred now organizations that have [11:38] publicly shared their practice of [11:40] innersource online. You can find links [11:42] to case studies for all these [11:43] organizations on our website and [11:47] uh and people the inner commons is [11:50] extremely uh welcoming community with uh [11:54] and it's a place where people really [11:56] want to be. Uh it's a a unique community [11:59] among tech communities uh where [12:01] interpersonal interaction is such a key [12:04] part of pe people feeling welcomed in [12:06] addition to the practice of inner [12:08] source. So you see here uh some of the [12:10] happy gatherings that folks have had and [12:12] since we're here in New York I gathered [12:14] here some pictures. Uh there's a [12:16] wonderful tradition in the inner source [12:17] commons whenever two inner sourcers are [12:20] together at a conference whether an [12:22] inner source summit or some other event [12:24] uh they're always friends and always [12:26] taking pictures. So these are some that [12:27] have been shared in our Slack before. Uh [12:29] I want to call out as Innersource grows [12:31] throughout the world you can see in the [12:33] bottom right it's a picture of an [12:35] innersource gathering in Brazil. So, [12:37] Innersource in the Americas is more than [12:40] just uh US and Canada. We're seeing that [12:42] regional interource group in South [12:43] America come which is really exciting. [12:46] Um the leadership of the Inner Source [12:49] Commons board of directors uh myself as [12:51] a director um Addie who's here I don't [12:54] see her in the room uh is also on the [12:57] board of directors. Katie who's here in [12:58] the room as a former member of the [13:00] board. Uh these are all volunteers, [13:02] people who believe in inner source and [13:05] want to put time into seeing the [13:06] practice spread throughout the world. Uh [13:08] so last uh 10 years uh inner source uh [13:12] kind of has a start about 25 years ago [13:15] when the term was coined. I'm not going [13:17] to go through and read everything here [13:18] but just touch on a few highlights and [13:20] it's grown from that beginning uh here [13:22] in the United States all the way until [13:24] now where it's a worldwide movement. So [13:26] just some of the highlights uh inner [13:27] source started uh in the in the US uh [13:31] with Tim O'Reilly actually coined the [13:33] term way back in 2000 uh 25 years ago uh [13:38] bringing open source practices [13:40] techniques uh development techniques [13:42] within the corporation and Tim was [13:44] advocating for this uh this was like [13:47] kind of the formal start to the name [13:49] innersource uh at the time the battle in [13:51] the industry was really around open [13:53] source at this time will open source [13:54] come out on top open source hadn't won [13:57] yet. So there wasn't a wide adoption and [13:59] recognition of inner source at the time. [14:02] But after uh over the next 10 years [14:04] after it was clear open source was the [14:05] winner uh things turned to innersource [14:08] and and bringing that together. So [14:10] Denise Cooper who was involved in the [14:12] handoff from Berlin that you just saw uh [14:15] started and founded the innersource [14:17] comments 10 years ago in 2015. That's [14:19] the 10 years that we're we're [14:20] celebrating. This was generously [14:22] supported by her employer at the time uh [14:25] which was uh PayPal which sponsored some [14:28] of the first inner source events uh [14:30] which led to the foundation being [14:32] incorporated as a public charity five [14:34] years ago. Um so since that time in 2015 [14:39] uh there's been over a dozen in-person [14:41] events uh regional gatherings associated [14:44] with conferences mostly in the United [14:46] States but also also appearing uh in [14:49] Europe uh in Asia as well. Um inner [14:53] source patterns book we talked about [14:54] that one uh continually is the asset of [14:57] the inner source commons that people [14:59] call out as one of the most helpful [15:00] things for starting inner source at your [15:02] organization. And then besides these [15:05] large um global summits uh the program [15:10] of local gatherings has popped up where [15:13] there's uh regional events a little bit [15:15] like a Kubernetes community day or a [15:17] DevOps days where particular hosts in a [15:20] city will sponsor a smaller inner source [15:22] gathering. We've seen a growth of these [15:24] with a dozen in the past uh 12 to 15 [15:28] months in 2024 and 2025 uh including [15:33] several in in Tokyo, one in China. So [15:35] it's exciting to see inner source [15:37] expanding in Asia. Uh and with the [15:40] interest we're really excited last year, [15:43] actually two years ago when inner source [15:45] first popped up on the Gartner hype [15:46] cycle for software engineering uh moving [15:49] up uh moving up the peak showing up in [15:52] 2023 uh extending further on 2024 and uh [15:57] now in their reports in 2025 it's moving [15:59] forward. Um, and our our task now is to [16:03] uh get up that uh to the plateau of of [16:06] productivity there on the right. It's [16:08] exciting to see major outlets like [16:10] Gartner acknowledging Interceource and [16:11] its place in the in the industry. All [16:14] right, here for the New York audience, I [16:17] wanted to call out some more local [16:19] exciting things we see around [16:21] Innersource. Uh, Innersource showed up [16:23] in the United Nations uh this past year. [16:26] Uh I think in the picture I see uh Addie [16:28] who's also in the back here today as [16:31] part of the UN panel on inner source uh [16:34] right here in New York. Uh in the middle [16:36] uh there's Daniel the chair of the inner [16:39] source commons uh who was also there at [16:42] that UN panel. So exciting to see the [16:44] concept uh recognized in other [16:46] international organizations uh like the [16:48] UN. Uh we almost had a a UN [16:50] representative or UN person at the UN [16:52] here today ended up not being able to [16:54] make it but interest there in inner [16:56] source. Uh also did you know that inner [16:59] source is required uh by the US [17:02] government the share it act requires US [17:06] agencies to share custom source code [17:08] with each other. Now they don't use the [17:10] term inner source uh but I'm co-opting [17:12] and saying uh the US government has [17:14] mandated inner source because when you [17:16] look at some of the text there it's [17:18] mandated that agencies share with one [17:20] another. Uh what are their goals? Uh [17:22] we're going to prevent uh duplicative [17:24] software development. Um and it's even [17:28] the the act they always do these cute [17:30] acronyms for the bills to get passed. [17:32] This is the share it act and they came [17:34] up with a letter uh for each of them. [17:36] But in my mind, it's kind of the inner [17:37] source act as well. But look at the [17:39] impact that they're expecting. You have [17:41] 15 billion dollars of software [17:43] development that they believe could be [17:45] impacted through inner source practices. [17:48] So inner source uh is alive. It's [17:51] growing growing in the industry. As we [17:54] look forward uh now toward the future [17:57] and what it means for innours [18:01] uh this is the way I see things. I know [18:03] that there's others that do as well. Um [18:05] there's a question in the AI area. What [18:07] does that mean for innersource? I'll [18:09] stand and say that in the AI era, inner [18:13] source is more relevant than ever. Uh [18:15] think about it. AI is the ultimate inner [18:19] source consumer, the ultimate inner [18:21] source contributor. and everything that [18:24] we do that you've done uh in your in [18:27] your organizations to make software [18:29] discoverable, understandable and easy to [18:32] contribute to is the exact things that's [18:34] going to help AI to do the same. Okay, [18:37] so inner source uh makes sense. Think of [18:40] AI as a consumer and potential inner [18:42] source contributor and also inner source [18:46] is helpful to AI. Inner source projects [18:49] at your organization provide an [18:51] abstraction layer over details that are [18:53] solved problems that are already done [18:55] your company way so that AI can just use [18:58] the inner source projects that already [18:59] exist at your organization and get it [19:02] done right by your company's security [19:04] and coding standards without having to [19:07] figure out how to fit all of that into a [19:09] prompt. the prompt and context window [19:11] for AI can focus on the partic [19:14] particular business problem that you're [19:16] trying to solve rather than also having [19:18] to spin up the underlying infrastructure [19:21] uh and code and platform that need to be [19:23] done in a specific way. Uh thirdly, as [19:27] AI lowers the technical barrier to in [19:30] the creation of code, the human and [19:33] social barriers to effective code [19:36] creation are going to become the [19:37] bottleneck. In the software industry in [19:40] general, we don't collaborate within our [19:42] organizations as we should. That's why [19:44] there's a need for inner source. We've [19:46] been able to get by with this somewhat [19:48] in the past because collaboration was [19:51] only part of the problem in software [19:52] development. Effective code generation [19:55] was also a really time consuming and [19:57] really expensive task. With inner [20:00] source, the amount of time and resources [20:03] that need to go into generating code are [20:05] lowered quite a bit. And what's [20:07] happening is we're all going to come [20:08] against the point where the human and [20:10] social barriers and collaboration [20:12] barriers end up becoming the bigger [20:15] bottleneck rather than code generation [20:17] itself. So the AI area and all AI era in [20:21] all these ways accelerates the need uh [20:23] for innersource. All right. So looking [20:26] forward uh we've had 10 years of [20:28] innersource awesomeness. What is there [20:31] to come in the future? Uh what I see for [20:36] the inner source commons and innersource [20:38] in general I see more local gatherings [20:41] and chapters of the inner source [20:43] commons. Inner source started in the [20:45] United States. It spread throughout the [20:47] world. I think there's more to go and [20:48] strengthening local organizations [20:50] throughout the world that have sprung [20:52] up, many of them in just the past year [20:54] will be an ongoing theme. Uh more [20:57] published training guides and handbooks. [20:59] I think in general there's a general [21:02] knowledge and direction for inner [21:04] source, but a lot of the how even the [21:07] specific patterns uh sometimes there's [21:09] things still left to interpretation. We [21:11] see companies and organizations creating [21:13] internal uh guide books and trainings. I [21:16] think more of those can be brought into [21:17] the open and shared. So not every [21:19] company has to figure things out uh [21:22] completely from where things are at now [21:23] to having a functioning inner source [21:25] program. Uh and uh I think we'll see [21:28] after 10 years inner source as the [21:31] industry industry standard. It's for [21:34] software development. It's on the trend. [21:36] It's on the hype cycle. uh within 10 [21:38] years uh we're looking back and uh like [21:42] like agile development it's the industry [21:45] standard that people know is is going to [21:47] happen. The tagline I have for that I [21:49] have for this is we'll see robust and [21:51] pervasive inner source is just the [21:53] normal way that software development [21:55] happens in organizations worldwide. [21:59] All right. Well, that's my summary here. [22:02] 10 years of awesomeness in the inner [22:04] source commons. I'm so excited to uh [22:07] kick off our uh New York. Thanks for [22:10] having us here today. Again, a special [22:12] thanks for IBM for hosting all of us and [22:14] hosting the Inner Source Commons uh in [22:16] that venue. Let's have a great day today [22:18] here with Innersource. Thank you.  ## 📺 Video ![](https://www.youtube.com/watch?v=51C_FyiZdxk) --- # 📝 Full Notes (Deep-Read Analysis) # 🏷️ Title: Russ Rutledge – Welcome address #InnerSourceSummit2025 ## 🧰 Action Inbox - [H1] Join InnerSource Commons Slack community — QR code provided/website link #community - [H2] Check out InnerSource patterns book for implementation guidance — foundational resource #documentation - [H3] Share event learnings on social media with #InnerSourceSummit2025 tag — community engagement #networking ## 🧭 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 - [InnerSource Commons Website](https://innersourcecommons.org) - [InnerSource Patterns Book](https://patterns.innersourcecommons.org/) ## 📝 Summary - Russ Rutledge, Executive Director of InnerSource Commons, delivered the welcome address for the New York leg of InnerSource Summit 2025 - The event celebrates the 10-year anniversary of the InnerSource Commons Foundation as a global 24-hour summit - InnerSource adopts open source practices internally within organizations for internal code sharing and collaboration - Four key motivations for InnerSource: open source mastery, engineering efficiency, innovation catalyst, and people development - AI era makes InnerSource more relevant than ever as AI becomes both consumer and contributor to internal code ## 📖 Main Content InnerSource represents the adoption of open source software practices within organizations for internal code sharing. Unlike traditional siloed development, InnerSource makes internal projects visible to everyone in the organization, inviting both usage and contribution through pull requests and issue reporting—similar to open source projects but contained within company boundaries. The InnerSource Commons Foundation, celebrating its 10-year anniversary, serves as the global steward for InnerSource practices. With over 4,000 participants in their Slack community representing 1,000+ organizations, the foundation has produced the InnerSource Patterns book and hosted 30+ in-person events. Organizations pursue InnerSource for four primary reasons: developing open source mastery skills in a safe internal environment, improving engineering efficiency by breaking down silos and avoiding duplicated work, catalyzing innovation through cross-team collaboration, and enhancing developer happiness by removing roadblocks to getting work done. The emergence of AI amplifies InnerSource's relevance. AI serves as both the ultimate InnerSource consumer and contributor, benefiting from the discoverability and contribution ease that InnerSource promotes. As AI lowers technical barriers to code creation, human and social collaboration barriers—InnerSource's specialty—become the primary bottleneck in software development. ## 🗒️ Notes #### ⏱️ [00:00](https://youtu.be/51C_FyiZdxk?t=0) — [H1] Welcome and Event Introduction - Key idea: InnerSource Summit 2025 celebrates 10-year anniversary with 24-hour global event - Evidence: "We're celebrating today with 24 hours of inner source summit... 10 years ago the organization started" #### ⏱️ [02:30](https://youtu.be/51C_FyiZdxk?t=150) — [H2] Event Sponsors and Community - Key idea: Multiple global sponsors enable worldwide InnerSource community events - Evidence: "Event started about 16 hours ago in Japan, hosted in Yokohama at Mitsubishi Electric and then we just received the handoff from SAP hosted in Berlin" #### ⏱️ [04:15](https://youtu.be/51C_FyiZdxk?t=255) — [H1] What is InnerSource Definition - Key idea: InnerSource adopts open source practices internally within organizations - Evidence: "Innersource is adopting the practices of open source software internally within an organization for code that will only ever be shared internally" #### ⏱️ [05:45](https://youtu.be/51C_FyiZdxk?t=345) — [H2] InnerSource Core Principles - Key idea: InnerSource follows open source principles of openness, transparency, and voluntary contribution - Evidence: "Inner source follows and adapts many of the principles of open source openness, transparency prioritizing mentorship and encouraging voluntary code contribution" #### ⏱️ [06:30](https://youtu.be/51C_FyiZdxk?t=390) — [H1] Four Categories of Why InnerSource - Key idea: Organizations pursue InnerSource for mastery, efficiency, innovation, and developer happiness - Evidence: "As we speak with and listen to organizations throughout the world these four categories of why inner source come out" #### ⏱️ [07:00](https://youtu.be/51C_FyiZdxk?t=420) — [H2] Path to Open Source Mastery - Key idea: InnerSource provides safe internal practice for open source skills - Evidence: "Inner source gives a safe internal chance for individuals and companies to practice and learn the skills that will then aid them in successful involvement with open source" #### ⏱️ [08:00](https://youtu.be/51C_FyiZdxk?t=480) — [H2] Engineering Efficiency Benefits - Key idea: InnerSource breaks down silos and eliminates duplicate work across teams - Evidence: "Inner sources a path to engineering efficiency. It breaks down engineering silos. Avoids duplicated work" #### ⏱️ [08:45](https://youtu.be/51C_FyiZdxk?t=525) — [H2] Innovation Through Cross-Contamination - Key idea: InnerSource enables serendipitous innovation like Fleming's penicillin discovery - Evidence: "Project Fleming... Alexander Fleming who invented penicillin... happened completely as a happy accident of people working close to each other and sharing the things they're working on" #### ⏱️ [10:30](https://youtu.be/51C_FyiZdxk?t=630) — [H2] People Development and Happiness - Key idea: InnerSource removes roadblocks by enabling self-service through pull requests - Evidence: "Inner source is an incredibly enabling methodology... it enables anyone when needing something from a project to get what they want by their own effort only by opening a poll request" #### ⏱️ [11:45](https://youtu.be/51C_FyiZdxk?t=705) — [H1] InnerSource Commons Foundation Overview - Key idea: Global community of 4,000+ participants representing 1,000+ organizations - Evidence: "Over 4,000 participants in the inner source commons representing at least a thousand organizations" #### ⏱️ [13:00](https://youtu.be/51C_FyiZdxk?t=780) — [H2] Foundation Mission and Assets - Key idea: Educational nonprofit stewarding worldwide InnerSource knowledge through patterns and events - Evidence: "The stated mission of the charity is education education around inner source in the technical industry" #### ⏱️ [16:15](https://youtu.be/51C_FyiZdxk?t=975) — [H1] InnerSource History and Timeline - Key idea: InnerSource term coined 25 years ago by Tim O'Reilly, foundation started 10 years ago - Evidence: "Inner source started in the US with Tim O'Reilly actually coined the term way back in 2000 25 years ago" #### ⏱️ [19:30](https://youtu.be/51C_FyiZdxk?t=1170) — [H2] Government and Industry Recognition - Key idea: US government mandates code sharing through SHARE IT Act, UN panels discuss InnerSource - Evidence: "The share it act requires US agencies to share custom source code with each other... 15 billion dollars of software development that they believe could be impacted" #### ⏱️ [21:00](https://youtu.be/51C_FyiZdxk?t=1260) — [H1] AI Era and InnerSource Relevance - Key idea: AI makes InnerSource more relevant as ultimate consumer and contributor - Evidence: "In the AI era, inner source is more relevant than ever... AI is the ultimate inner source consumer, the ultimate inner source contributor" #### ⏱️ [22:30](https://youtu.be/51C_FyiZdxk?t=1350) — [H2] AI as Collaboration Bottleneck Solution - Key idea: AI lowers technical barriers, making human collaboration the primary bottleneck - Evidence: "As AI lowers the technical barrier to in the creation of code, the human and social barriers to effective code creation are going to become the bottleneck" #### ⏱️ [24:00](https://youtu.be/51C_FyiZdxk?t=1440) — [H1] Future Vision for InnerSource - Key idea: InnerSource will become industry standard within 10 years with local chapters and training - Evidence: "After 10 years inner source as the industry standard... robust and pervasive inner source is just the normal way that software development happens in organizations worldwide" ## 📚 References - [InnerSource Commons](https://innersourcecommons.org/) - [InnerSource Patterns Book](https://patterns.innersourcecommons.org/) - [InnerSource Commons Slack Community](https://innersourcecommons.org/slack) - [SHARE IT Act Information](https://code.gov/) ## 🗣️ Paraphrase - InnerSource applies open source development practices within organizations, making internal code projects visible and contributable to all employees rather than keeping them in departmental silos - The practice serves four main organizational goals: building open source skills safely, eliminating duplicate engineering work, fostering innovation through collaboration, and improving developer satisfaction by removing bureaucratic barriers - The emergence of AI amplifies InnerSource's importance because AI functions as both a consumer and contributor to code repositories, while human collaboration challenges become the primary constraint as technical code generation becomes easier ## 📰 Newsletter 🎉 **InnerSource Commons Celebrates 10 Years of Breaking Down Silos** The InnerSource movement just marked a major milestone with a 24-hour global summit celebrating a decade of bringing open source practices inside organizations. For WordPress professionals, this approach offers valuable lessons for internal development workflows. **Key Takeaway:** InnerSource treats internal company code like open source projects—visible to all employees, welcoming contributions via pull requests, and prioritizing documentation and mentorship. This eliminates the "not invented here" syndrome and reduces duplicate work across teams. **WordPress Connection:** Many agencies and large WordPress installations could benefit from InnerSource principles when developing internal tools, custom plugins, or client solutions that could be reused across projects. **AI Advantage:** As AI tools make code generation easier, human collaboration becomes the bottleneck. InnerSource practices that emphasize discoverability and contribution ease position teams well for AI-assisted development. Resources: [InnerSource Commons](https://innersourcecommons.org/), [Patterns Book](https://patterns.innersourcecommons.org/), [Learning Paths](https://innersourcecommons.org/learn/) ## ✅ Action Items #### DevRel - Developer advocacy: Create InnerSource awareness talks for WordPress conferences and meetups - Education: Develop learning paths connecting WordPress development with InnerSource practices - Developer experience: Document internal tool contribution processes using InnerSource patterns - Developer marketing: Share case studies of WordPress agencies using InnerSource approaches - Community management: Foster internal contribution culture in WordPress organizations #### OSPO - Policy & Governance: Adapt InnerSource contribution policies for internal WordPress development - License Compliance: Apply InnerSource patterns to internal GPL-licensed WordPress projects - Software Inventory: Track internal WordPress tools and plugins using InnerSource discoverability - Developer Support: Train WordPress teams on InnerSource collaboration practices - Community Engagement: Bridge internal InnerSource practices with WordPress.org contributions - Strategic Alignment: Measure InnerSource adoption impact on WordPress development velocity #### Community - Maintainers: Apply InnerSource mentorship patterns to WordPress core contribution onboarding - Contributors: Use InnerSource practices for cross-team WordPress plugin collaboration - Sponsors: Support InnerSource adoption in WordPress organizations through funding and resources - Ecosystem: Coordinate InnerSource best practices across WordPress agencies and enterprises #### WordPress - Core: Implement InnerSource-inspired processes for cross-team contributions - Community: Create InnerSource local chapters for WordPress developers - Training: Develop InnerSource learning paths specific to WordPress development workflows - Documentation: Apply InnerSource patterns to improve internal WordPress project documentation - Meta: Use InnerSource practices for .org tool development and collaboration ## 🧪 Hypotheses - Organizations adopting InnerSource practices will see 30-50% reduction in duplicate code development within 12 months - AI-assisted development will accelerate InnerSource adoption as collaboration barriers become more visible bottlenecks - WordPress agencies implementing InnerSource will demonstrate measurable improvements in cross-project code reuse - InnerSource adoption correlates with increased employee satisfaction and reduced development frustration ### 📊 Methodology - Survey WordPress agencies before/after InnerSource adoption measuring code reuse metrics - A/B test AI coding assistance with/without InnerSource-structured codebases for efficiency gains - Longitudinal study tracking developer satisfaction scores in organizations implementing InnerSource - Case study analysis comparing WordPress development velocity across InnerSource vs. traditional siloed approaches ### ❓ Questions - How can WordPress-specific development patterns be adapted for InnerSource implementation in agencies? - What metrics best demonstrate InnerSource ROI for WordPress organizations considering adoption? - How do InnerSource practices intersect with WordPress.org contribution workflows and GPL compliance? ### 🔮 Future Research - InnerSource pattern development specifically for WordPress multisite and plugin architectures - Integration studies between InnerSource practices and WordPress contribution processes - AI-assisted InnerSource implementation frameworks for non-technical WordPress organization leaders ### 💡 Implications - Practice: WordPress developers should learn InnerSource patterns for improved internal collaboration - Policy: Organizations need contribution guidelines that bridge internal InnerSource and external WordPress.org practices - Security: InnerSource visibility requirements must balance with WordPress security considerations - Education: WordPress training programs should incorporate InnerSource collaboration methodologies - Funding: Investment in InnerSource tooling and processes may accelerate WordPress development ROI ### 🧠 Learning Styles Assessment Reading level estimate: 12th grade (Flesch-Kincaid) #### 👀 Visual learners - Present: Organization logos, timeline graphics, community photos - Improve: InnerSource workflow diagrams, before/after collaboration visualizations #### 🔊 Aural learners - Present: Full video presentation with clear narration - Improve: Podcast-style summary, discussion questions for group learning #### 🗣️ Verbal learners - Present: Clear definitions, analogies (Fleming/penicillin story), examples - Improve: More case study narratives, step-by-step implementation stories #### 🧩 Kinesthetic learners - Present: QR codes for immediate action, Slack community joining - Improve: Hands-on InnerSource implementation workshop materials #### 🧠 Logical learners - Present: Clear timeline, structured four-category framework, cause-effect relationships - Improve: Decision trees for InnerSource adoption, ROI calculation templates #### 🧑‍🤝‍🧑 Social learners - Present: Community emphasis, Slack channels, global summit format - Improve: Local meetup organizing guides, peer mentoring frameworks #### 🧘‍♀️ Solitary learners - Present: Self-directed learning paths mentioned, patterns book reference - Improve: Individual assessment tools, self-paced implementation guides #### 🌿 Naturalistic learners - Present: Organic community growth analog --- # 📄 Full Transcript *Auto-generated from YouTube captions · timestamps roughly every 30 seconds · [watch on YouTube](https://www.youtube.com/watch?v=51C_FyiZdxk)* **[00:06]** We'll get started uh here in the room in New York. And uh also uh welcome to any people online who are just joining uh or more likely who have stayed over and are continuing to watch the the broadcast. I think we've got a little over a hundred people online also joining in for this leg of Inner Source Summit. Well, my name is Russ Rutled. I'm the executive director of the Inner Source Commons uh that is co-sponsoring uh this event. It's my pleasure to give the welcome to our uh New York leg of **[00:39]** Inner Source Summit 2025. Uh so this event today is a special one. Well, I think an inner source day is always special. Uh we have a a saying uh in the inner source comments, happy innersource day. uh any day that we're doing inner source is a day of happiness for ourselves and a chance to give happiness to others and uh this event is especially happy because we're celebrating the 10-year anniversary of the Interceource Commons Foundation as an organization. So 10 years ago the **[01:10]** organization started and it's been a long and storied journey to this point where there's a global community and we're celebrating today with 24 hours of inner source uh summit. We're here on the last leg of it here in New York. So uh for the event today uh we want to start by thanking our event sponsors. Uh we're all sitting here in this wonder wonderful facility here at IBM. I want to thank IBM for hosting uh also our **[01:41]** other location sponsors. This event started uh about 16 hours ago in Japan, hosted in Yokohama at Mitsubishi Electric and then we just received the handoff from SC SAP hosted in Berlin. So thanks to our uh host sponsors. Uh in addition uh we have other SP others that have helped with uh Inner Source Summit. uh thanks to GitH uh Git Lab, Red Hat and then uh Bera solutions which are **[02:11]** also some Summit sponsors. Um in addition to sponsors for this particular event, we're thankful for our general sponsors of the Inner Source Commons whose support also goes into putting on events like these. Um the support of these organizations are what allows this community to thrive and for us to be meeting here together today. Thank you for our partners, sponsors, our supporting sponsors. Uh I'll call out here since we're at the uh IBM headquarters, IBM is also a general **[02:41]** sponsor of the Inner Source Commons for which we're very thankful and really helps the work of Inner Source throughout the world. So for those who are uh just joining whether online or in person, we want you to post and share about what you're learning here, about what you're excited about. put it on your favorite social media platform. Uh we're watching encouraging the use of the Inner Source Summit 2025 tag. Uh also uh for in **[03:13]** person and uh online, we want to invite you to join the Inner Source Commons Slack. I know that many of you are on the Slack already. Some of you, it's probably how you found out about the event, but if you're not there, you can find the link very easily on the Inner Source Commons website. uh or you can take out your mobile device and scan this QR code. That'll put you in the Slack. For the event today, if you have questions for the speakers, we're going to be using the Slack as our location **[03:45]** for Q&A. So, just right there in the general channel of Slack, you can post your questions. And if you're online, there'll be people watching for those and making sure that your question gets asked of the in-person speaker. All right. Well, today we got a fantastic program lined up with inner sorcerers uh from uh around the world and around the Americas here in our New York lake. Uh the way things are going to go today is for those watching **[04:17]** online, there's a continuous schedule of inner source content. Uh this schedule is also available on the event page on the website where you can follow it there. Now, uh, for those of us who are here in person, there will be a chance to take a few breaks, uh, morning break, afternoon break, a lunch break. So, we will not be going as part of the 24 hours uh, here in person, but we'll have some breaks. And while the in-person crowd is on break time, uh, there'll be **[04:48]** online virtual speakers that continue to share about innersource so that the online stream has a continuous feed of speakers. Okay. All right. Uh I'm just get started with a little bit of background for anyone who's new to inner source, new to the inner source commons community with a little bit of history and level setting as we get started learning more about inner source. Uh first of all, what is inner source? Innersource is adopting the practices of open source software **[05:20]** internally within an organization for code that will only ever be shared internally running it as if it were an open source project uh within the company. That means it's visible to everyone at the organization. Everyone is invited to use it and everyone is invited to contribute to it to open a poll request or open an issue just like you would see with an open source project except for a company internal project. Uh inner source follows and **[05:52]** adapts many of the principles of open source uh openness, transparency uh prioritizing mentorship and encouraging voluntary code contribution. These principles are outlined on the inner source commons website. Uh there's a series of learning path videos that give more information example on the importance of these principles in making inner source work and give training ideas of how to implement them at your organization. So definitely check that out. Um so why inner source? I find this **[06:23]** is so connected with um with what is inner source is what do we hope to gain by it? Uh as we speak with and listen to uh organizations throughout the world these four categories of why inner source come out. Uh so you might identify uh with some of these and not with others and that's okay. Many organizations maybe have just one of these that's a motivation for inner source. Sometimes the way that we pursue or think about inner source in our **[06:54]** organizations is different based on the results that we want to see. So I want to share these so that as you listen to speakers and have conversations uh you can identify what is your why for inner source and uh look through it in that lens as you learn about inner source today. Uh so briefly uh inner source is a path at a personal or professional level uh or at an individual or organization level to open source mastery. Inner source gives a safe internal chance for individuals and **[07:25]** companies to practice and learn the skills uh that will then aid them in successful involvement with open source without having to learn in in public and have those learnings be something that are visible outside the organization. Um, next one. Inner sources. A path to engineering efficiency. It breaks down engineering silos. Avoids duplicated work. Allows teams to build on the successes of others to stop reinventing the wheel and move forward with work on **[07:57]** the team that is specific to their product domain instead of uh doing work that's already been discovered elsewhere inside the organization. Inner source is a path and a catalyst for innovation. Um there's a neat um innersource enablement project that I heard about uh that called itself project Fleming and as a a story about the way this works. The reason why it had this uh this name is Alexander Fleming who invented penicellin was a **[08:28]** researcher working in a lab and uh in the samples of uh that he was working with there was some crosscontamination from an adjacent lab that was completely by accident and as he saw the results of this contamination had in his experience it put him on the path where eventually discovered penicellin which is just a uh you know an amazing thing in the medical field today and it happened completely as a as a happy accident of people working close to each other and sharing the things they're working on. Uh in this case inadvertently uh inner source **[08:58]** is the same way as we bring together people from different parts of the organization. The thing that gets produced is better than anything that could have done by any single team. Uh even a central team mandated to solve a problem once for the company can never have all the insights that could come by inviting consumers from around the organization. Um and lastly, uh people development happiness. Uh inner source is an incredibly enabling methodology to adopt internally. Uh it enables anyone when **[09:30]** needing something from a project to get what they want by their own effort only by opening a poll request. We're taking away roadblocks and silos that are frustrating to our engineering and development teams that have to spend time on the non-engineering non-productive task of negotiating across projects uh and uh vying for features to get in. Uh with inner source you can just open a pull request and and move on with writing more code. Okay. So that's a little bit about inner source. **[10:01]** So the inner source commons foundation is a separate entity that is stewarding the practice of inner source in the industry throughout the world. Uh as we look at our online Slack community there's over 4,000 participants in the inner source commons representing at least a thousand organizations. uh over the past 10 years there've been over 30 in-person events and beyond talk many of the best practices of innersource are documented and probably is in what is the foundation's most **[10:34]** durable long-lasting asset which is the inner source patterns book you can find that linked on the inner source commons website uh we continually receive feedback that it's a very uh valuable tool for capturing patterns of how to do inner source at your organization so the innersource commons is a nonprofit organization uh uh founded uh 10 years ago as we say and incorporated uh 5 years ago as a public charity in the United States. The stated mission of the **[11:04]** charity is education education around inner source in the technical technical industry. So it's been a long a long journey for the innersource commons. Oh, here's our our mission. Uh, educating and supporting innersource throughout the industry and throughout the world, especially stewarding the worldwide body of inner source knowledge. We do that through assets like the patterns or conferences like we're here in today. All right, there's some logos of organizations um the the dozens I think we're over a **[11:36]** hundred now organizations that have publicly shared their practice of innersource online. You can find links to case studies for all these organizations on our website and uh and people the inner commons is extremely uh welcoming community with uh and it's a place where people really want to be. Uh it's a a unique community among tech communities uh where interpersonal interaction is such a key part of pe people feeling welcomed in **[12:06]** addition to the practice of inner source. So you see here uh some of the happy gatherings that folks have had and since we're here in New York I gathered here some pictures. Uh there's a wonderful tradition in the inner source commons whenever two inner sourcers are together at a conference whether an inner source summit or some other event uh they're always friends and always taking pictures. So these are some that have been shared in our Slack before. Uh I want to call out as Innersource grows throughout the world you can see in the bottom right it's a picture of an innersource gathering in Brazil. So, **[12:37]** Innersource in the Americas is more than just uh US and Canada. We're seeing that regional interource group in South America come which is really exciting. Um the leadership of the Inner Source Commons board of directors uh myself as a director um Addie who's here I don't see her in the room uh is also on the board of directors. Katie who's here in the room as a former member of the board. Uh these are all volunteers, people who believe in inner source and want to put time into seeing the practice spread throughout the world. Uh **[13:08]** so last uh 10 years uh inner source uh kind of has a start about 25 years ago when the term was coined. I'm not going to go through and read everything here but just touch on a few highlights and it's grown from that beginning uh here in the United States all the way until now where it's a worldwide movement. So just some of the highlights uh inner source started uh in the in the US uh with Tim O'Reilly actually coined the term way back in 2000 uh 25 years ago uh bringing open source practices **[13:40]** techniques uh development techniques within the corporation and Tim was advocating for this uh this was like kind of the formal start to the name innersource uh at the time the battle in the industry was really around open source at this time will open source come out on top open source hadn't won yet. So there wasn't a wide adoption and recognition of inner source at the time. But after uh over the next 10 years after it was clear open source was the winner uh things turned to innersource and and bringing that together. So **[14:10]** Denise Cooper who was involved in the handoff from Berlin that you just saw uh started and founded the innersource comments 10 years ago in 2015. That's the 10 years that we're we're celebrating. This was generously supported by her employer at the time uh which was uh PayPal which sponsored some of the first inner source events uh which led to the foundation being incorporated as a public charity five years ago. Um so since that time in 2015 uh there's been over a dozen in-person **[14:41]** events uh regional gatherings associated with conferences mostly in the United States but also also appearing uh in Europe uh in Asia as well. Um inner source patterns book we talked about that one uh continually is the asset of the inner source commons that people call out as one of the most helpful things for starting inner source at your organization. And then besides these large um global summits uh the program of local gatherings has popped up where **[15:13]** there's uh regional events a little bit like a Kubernetes community day or a DevOps days where particular hosts in a city will sponsor a smaller inner source gathering. We've seen a growth of these with a dozen in the past uh 12 to 15 months in 2024 and 2025 uh including several in in Tokyo, one in China. So it's exciting to see inner source expanding in Asia. Uh and with the interest we're really excited last year, actually two years ago when inner source **[15:45]** first popped up on the Gartner hype cycle for software engineering uh moving up uh moving up the peak showing up in 2023 uh extending further on 2024 and uh now in their reports in 2025 it's moving forward. Um, and our our task now is to uh get up that uh to the plateau of of productivity there on the right. It's exciting to see major outlets like Gartner acknowledging Interceource and its place in the in the industry. All right, here for the New York audience, I **[16:17]** wanted to call out some more local exciting things we see around Innersource. Uh, Innersource showed up in the United Nations uh this past year. Uh I think in the picture I see uh Addie who's also in the back here today as part of the UN panel on inner source uh right here in New York. Uh in the middle uh there's Daniel the chair of the inner source commons uh who was also there at that UN panel. So exciting to see the concept uh recognized in other international organizations uh like the **[16:48]** UN. Uh we almost had a a UN representative or UN person at the UN here today ended up not being able to make it but interest there in inner source. Uh also did you know that inner source is required uh by the US government the share it act requires US agencies to share custom source code with each other. Now they don't use the term inner source uh but I'm co-opting and saying uh the US government has mandated inner source because when you look at some of the text there it's mandated that agencies share with one **[17:20]** another. Uh what are their goals? Uh we're going to prevent uh duplicative software development. Um and it's even the the act they always do these cute acronyms for the bills to get passed. This is the share it act and they came up with a letter uh for each of them. But in my mind, it's kind of the inner source act as well. But look at the impact that they're expecting. You have 15 billion dollars of software development that they believe could be impacted through inner source practices. So inner source uh is alive. It's **[17:51]** growing growing in the industry. As we look forward uh now toward the future and what it means for innours uh this is the way I see things. I know that there's others that do as well. Um there's a question in the AI area. What does that mean for innersource? I'll stand and say that in the AI era, inner source is more relevant than ever. Uh think about it. AI is the ultimate inner source consumer, the ultimate inner **[18:21]** source contributor. and everything that we do that you've done uh in your in your organizations to make software discoverable, understandable and easy to contribute to is the exact things that's going to help AI to do the same. Okay, so inner source uh makes sense. Think of AI as a consumer and potential inner source contributor and also inner source is helpful to AI. Inner source projects at your organization provide an abstraction layer over details that are **[18:53]** solved problems that are already done your company way so that AI can just use the inner source projects that already exist at your organization and get it done right by your company's security and coding standards without having to figure out how to fit all of that into a prompt. the prompt and context window for AI can focus on the partic particular business problem that you're trying to solve rather than also having to spin up the underlying infrastructure uh and code and platform that need to be done in a specific way. Uh thirdly, as **[19:27]** AI lowers the technical barrier to in the creation of code, the human and social barriers to effective code creation are going to become the bottleneck. In the software industry in general, we don't collaborate within our organizations as we should. That's why there's a need for inner source. We've been able to get by with this somewhat in the past because collaboration was only part of the problem in software development. Effective code generation was also a really time consuming and **[19:57]** really expensive task. With inner source, the amount of time and resources that need to go into generating code are lowered quite a bit. And what's happening is we're all going to come against the point where the human and social barriers and collaboration barriers end up becoming the bigger bottleneck rather than code generation itself. So the AI area and all AI era in all these ways accelerates the need uh for innersource. All right. So looking forward uh we've had 10 years of **[20:28]** innersource awesomeness. What is there to come in the future? Uh what I see for the inner source commons and innersource in general I see more local gatherings and chapters of the inner source commons. Inner source started in the United States. It spread throughout the world. I think there's more to go and strengthening local organizations throughout the world that have sprung up, many of them in just the past year will be an ongoing theme. Uh more published training guides and handbooks. **[20:59]** I think in general there's a general knowledge and direction for inner source, but a lot of the how even the specific patterns uh sometimes there's things still left to interpretation. We see companies and organizations creating internal uh guide books and trainings. I think more of those can be brought into the open and shared. So not every company has to figure things out uh completely from where things are at now to having a functioning inner source program. Uh and uh I think we'll see after 10 years inner source as the **[21:31]** industry industry standard. It's for software development. It's on the trend. It's on the hype cycle. uh within 10 years uh we're looking back and uh like like agile development it's the industry standard that people know is is going to happen. The tagline I have for that I have for this is we'll see robust and pervasive inner source is just the normal way that software development happens in organizations worldwide. All right. Well, that's my summary here. **[22:02]** 10 years of awesomeness in the inner source commons. I'm so excited to uh kick off our uh New York. Thanks for having us here today. Again, a special thanks for IBM for hosting all of us and hosting the Inner Source Commons uh in that venue. Let's have a great day today here with Innersource. Thank you.