Building InnerSource Foundations Through InnerSource Patterns #InnerSourceSummit2025

Building InnerSource Foundations Through InnerSource Patterns #InnerSourceSummit2025 🔗 **Source:** [Building InnerSource Foundations Through InnerSource Patterns #InnerSourceSummit2025](https://www.youtube.com/watch?v=oDuMuh-wxs0) > [!note]+ Document Notes > tags: [innersource, patterns, enterprise-transformation, collaboration] > author: InnerSource Commons > source: YouTube > reference: https://www.youtube.com/watch?v=oDuMuh-wxs0 > date created: 2025-01-03 10:30 > > # 🏷️ Title: Building InnerSource Foundations Through InnerSource Patterns at AXA >  ## 🧰 Action Inbox - [H1] Establish inner source portal and knowledge repository — 00:00-05:23 #infrastructure - [H2] Create standard documentation templates for all projects — 12:45-15:30 #standardization - [H3] Implement governance model with core teams and trusted contributors — 08:15-10:45 #governance ## 🧭 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 Patterns](https://patterns.innersourcecommons.org/) - [AXA Group](https://www.axa.com/) ## 📝 Summary - AXA, a global insurance company with 95M customers across 50 countries, implemented InnerSource patterns to break down silos and accelerate innovation - Their journey began in 2016 with internal summits and evolved into a structured program using proven InnerSource Commons patterns rather than reinventing solutions - Key implementation includes inner source portals, standardized documentation templates, governance structures with core teams, and measurement systems - The initiative combines Red Hat's open expertise with InnerSource Commons patterns, creating a "secret equation" for scaled collaboration - Bottom line: Large enterprises can successfully implement inner source by leveraging existing community patterns and adapting them to their federated organizational structure ## 📖 Main Content AXA's inner source transformation represents a systematic approach to applying proven community patterns within a large, federated organization. The company serves over 95 million customers globally with 150,000+ employees, making collaboration and code reuse essential rather than optional. Their implementation strategy centers on four key principles: collaboration, transparency, recognition, and compliance. Rather than developing new methodologies, AXA deliberately chose to build upon existing InnerSource Commons patterns, working with Red Hat's Open Innovation Lab to adapt these patterns to their enterprise context. The technical foundation includes multiple portal systems - an onboarding portal for newcomers, a knowledge portal documenting guidance and governance, and project visibility portals. All projects use standardized documentation templates that include codes of conduct, contribution guidelines, licenses, and security protocols in a single repository. Their governance model implements trusted contributor patterns with clear roles and responsibilities. The organization has grown their internal community to 2,500 developers through annual engineering summits, with the most recent event hosting 3,000 engineers in Sevilla. ## 🗒️ Notes #### ⏱️ [00:00](https://youtu.be/oDuMuh-wxs0?t=0) — [H1] Introduction and Team Presentation - Key idea: Three-person team from AXA and Red Hat presenting their inner source journey - Evidence: "Carlos Navarro, principal engineer at AXA leading boarding staff, governance architecture" #### ⏱️ [02:30](https://youtu.be/oDuMuh-wxs0?t=150) — [H2] AXA Company Overview and Scale - Key idea: AXA serves 95 million customers across 50 countries with significant collaboration needs - Evidence: "Over 100 billion in annual revenues which means collaboration and reuse of solutions are not just beneficial, is essential" #### ⏱️ [04:45](https://youtu.be/oDuMuh-wxs0?t=285) — [H3] Four Key Inner Source Principles - Key idea: AXA's inner source foundation built on collaboration, transparency, recognition, and compliance - Evidence: "These pillars create a safe and open environment where teams can share ideas and innovate efficiently" #### ⏱️ [06:15](https://youtu.be/oDuMuh-wxs0?t=375) — [H2] Timeline of Open Culture Development - Key idea: Nine-year journey starting with internal summits in 2016, growing to 2,500 developer community - Evidence: "Last week we've been in Sevilla with 3,000 engineers sharing again" #### ⏱️ [08:30](https://youtu.be/oDuMuh-wxs0?t=510) — [H1] Secret Equation: Red Hat + InnerSource Patterns - Key idea: Combination of Red Hat open expertise with InnerSource Commons proven patterns - Evidence: "We didn't reinvent the wheel. We stood on your shoulders of community and proven patterns to fit our reality at AXA" #### ⏱️ [10:15](https://youtu.be/oDuMuh-wxs0?t=615) — [H3] Current Pattern Implementation Status - Key idea: Multiple patterns already adopted including legal framework, documentation standards, and governance - Evidence: "Every project include a standard documentation from our inner source template" #### ⏱️ [12:45](https://youtu.be/oDuMuh-wxs0?t=765) — [H2] Inner Source Portal Implementation - Key idea: Multiple portal systems for onboarding, knowledge sharing, and project visibility - Evidence: "We implemented different kind of inner source portal. One is just this kind of onboarding but also we created some learning paths" #### ⏱️ [15:30](https://youtu.be/oDuMuh-wxs0?t=930) — [H1] Standard Documentation Template System - Key idea: Comprehensive template repository providing all necessary assets for project startup - Evidence: "Inner source template repository that basically provides you all the things that you need to start from the beginning" #### ⏱️ [17:00](https://youtu.be/oDuMuh-wxs0?t=1020) — [H3] Self-Service Approach to Inner Source - Key idea: Documentation and portals designed for independent developer onboarding without requiring assistance - Evidence: "You have everything described. You don't need to ask anyone. You can jump into the different inner source portals" #### ⏱️ [18:45](https://youtu.be/oDuMuh-wxs0?t=1125) — [H2] Future Pattern Adoption Plans - Key idea: Next phase includes dedicated community leaders, explicit governance levels, and decision documentation - Evidence: "Dedicated community leader or set the split explicit governance levels. Also the project valuation" #### ⏱️ [19:30](https://youtu.be/oDuMuh-wxs0?t=1170) — [H3] Community Gratitude and Pattern Attribution - Key idea: Acknowledgment that success built upon existing community wisdom rather than original innovation - Evidence: "We want to thank you all of you because these are your patterns these are thing that you have learned with your experience" ## 📚 References - [InnerSource Commons Patterns](https://patterns.innersourcecommons.org/) - [Red Hat Open Innovation Labs](https://www.redhat.com/en/services/consulting/open-innovation-labs) - [FINOS Foundation](https://www.finos.org/) - [Linux Foundation](https://www.linuxfoundation.org/) ## 🗣️ Paraphrase - AXA transformed their internal collaboration by systematically implementing proven InnerSource Commons patterns rather than creating new methodologies from scratch - Their approach combines multiple portal systems, standardized documentation templates, and clear governance structures to enable self-service developer onboarding - The nine-year journey from informal engineering summits to a structured 2,500-developer community demonstrates how large enterprises can scale inner source practices ## 📰 Newsletter 🚀 **Enterprise Inner Source Success: AXA's Pattern-Driven Transformation** Great news for large organizations considering inner source adoption! AXA just shared their nine-year journey implementing inner source at enterprise scale, serving as a blueprint for other federated organizations. **Key Learning**: Don't reinvent the wheel. AXA's "secret equation" combines Red Hat's open source expertise with proven InnerSource Commons patterns, creating a self-service developer experience that scales to thousands of engineers. **Practical Benefits**: - Standardized documentation templates eliminate project setup friction - Multiple portal systems support different learning paths and use cases - Clear governance with trusted contributors ensures quality and compliance - Community growth from internal summits to 2,500+ developer ecosystem **Helpful Resources**: Check out the [InnerSource Commons Patterns](https://patterns.innersourcecommons.org/) for proven templates you can adapt to your organization's needs. **Community Connection**: AXA's success demonstrates how enterprise adoption strengthens the broader inner source community - their implementations feed back improvements to shared patterns. Resources: [InnerSource Commons](https://innersourcecommons.org/), [Pattern Library](https://patterns.innersourcecommons.org/), [Enterprise Adoption Guide](https://innersourcecommons.org/learn/) ## ✅ Action Items #### DevRel - Developer advocacy: Create case studies showing enterprise inner source adoption patterns and ROI metrics - Education: Develop workshops on adapting InnerSource Commons patterns for large federated organizations - Developer experience: Improve pattern documentation with enterprise-scale implementation examples - Developer marketing: Highlight AXA's journey in conference talks and community presentations - Community management: Facilitate connections between enterprises implementing similar pattern combinations #### OSPO - Policy & Governance: Create template governance models for federated organizations adopting inner source - License Compliance: Document inner source licensing patterns for multi-entity corporate structures - Software Inventory: Develop SBOM strategies that work across federated inner source repositories - Developer Support: Provide consultation on scaling inner source communities within large enterprises - Community Engagement: Support InnerSource Commons pattern development and maintenance funding - Strategic Alignment: Establish KPIs for measuring inner source adoption and community growth #### Community - Maintainers: Support InnerSource Commons pattern library with enterprise-validated improvements - Contributors: Create onboarding programs specifically for enterprise inner source practitioners - Sponsors: Provide transparent impact reports showing how enterprise adoption strengthens pattern quality - Ecosystem: Coordinate cross-enterprise pattern sharing and collaboration initiatives ## 🧪 Hypotheses - Large enterprises can successfully implement inner source by adapting existing community patterns rather than developing custom solutions - Self-service developer onboarding through standardized templates and portals reduces inner source adoption friction at scale - Federated organizations require specific governance patterns that balance autonomy with consistency across entities - Community-grown inner source patterns become more robust through enterprise-scale validation and feedback ### 📊 Methodology - Longitudinal case study tracking AXA's nine-year inner source journey from informal summits to structured community - Pattern effectiveness analysis comparing standardized vs. custom implementation approaches across enterprise contexts - Developer productivity measurements before and after self-service portal and template implementations ### ❓ Questions - How do inner source success metrics differ between federated vs. centralized organizational structures? - What specific adaptations do InnerSource Commons patterns require for compliance-heavy industries like insurance? - How can enterprises contribute pattern improvements back to the community without revealing competitive information? ### 🔮 Future Research - Comparative analysis of inner source adoption patterns across different enterprise verticals (insurance, banking, healthcare) - Investigation of optimal community size thresholds and growth patterns for enterprise inner source programs - Development of industry-specific pattern variants for highly regulated environments ### 💡 Implications - Practice: Enterprises can accelerate inner source adoption by leveraging existing community patterns instead of building from scratch - Policy: Federated organizations need governance frameworks that balance entity autonomy with collaborative consistency - Security: Inner source implementations must address IP management across multiple legal entities within single corporations - Education: Enterprise adoption creates feedback loops that improve pattern quality for the broader community - Funding: Large-scale enterprise implementations can provide sustainable funding models for community pattern development ### 🧠 Learning Styles Assessment Reading level estimate: 12th Grade (technical business presentation) #### 👀 Visual learners - Present: Portal screenshots, organizational diagrams, timeline visualizations - Improve: Architecture diagrams showing pattern relationships, visual governance models #### 🔊 Aural learners - Present: Conference presentation format with multiple speakers - Improve: Podcast interview format exploring detailed implementation challenges #### 🗣️ Verbal learners - Present: Clear definitions of patterns, analogies like "secret equation" and "standing on shoulders" - Improve: Story-driven case studies from other enterprise implementations #### 🧩 Kinesthetic learners - Present: Demo walkthrough of actual portals and templates - Improve: Hands-on workshops using AXA's open-sourced templates and patterns #### 🧠 Logical learners - Present: Timeline progression, pattern-to-outcome relationships, structured governance models - Improve: Decision trees for pattern selection, ROI calculations, success metrics dashboards #### 🧑‍🤝‍🧑 Social learners - Present: Community summit examples, collaborative pattern development - Improve: Facilitated enterprise inner source cohorts, peer mentoring programs #### 🧘‍♀️ Solitary learners - Present: Self-service portal design, independent developer onboarding paths - Improve: Self-assessment tools for pattern readiness, individual learning tracks #### 🌿 Naturalistic learners - Present: Organic community growth analogies, ecosystem thinking - Improve: Sustainability considerations for long-term community health ### 📊 Accessibility Assessment #### Screen reader semantics - Present: Basic presentation structure with speaker identification - Improve: Detailed alt text for diagrams, semantic markup for pattern relationships #### Keyboard navigation - Present: Standard video controls - Improve: Keyboard-accessible interactive demos, skip links for long presentations #### Contrast and readability - Present: Standard presentation slides - Improve: High-contrast mode for technical diagrams, larger fonts for code examples #### Text resizing and reflow - Present: Video format limits resizing options - Improve: Responsive transcript layout, scalable diagram versions #### Media and captions - Present: Audio presentation available - Improve: Professional captions, downloadable transcript with speaker attribution #### Forms and interactions - Present: Basic video interaction - Improve: Accessible demo interfaces, keyboard-navigable portal examples ### 🌍 DEIB Assessment #### Cultural breadth - Present: Multi-national company (50 countries) with global perspective - Improve: More diverse geographic case studies, localization considerations #### Inclusive language - Present: Technical jargon clearly defined, professional tone - Improve: Plain-language executive summaries, avoid cultural idioms #### Neurodiversity support - Present: Structured presentation with clear sections - Improve: Content warnings for fast-paced demos, processing time between concepts #### Representation - Present: Mixed-gender presentation team, international perspectives - Improve: Diverse enterprise examples, varied industry contexts #### Psychological safety - Present: Respectful acknowledgment of community contributions - Improve: Explicit discussion of failure modes and learning from mistakes ### ✅ Logical Validity #### Strong reasoning - Deductive strength: Strong logical flow from enterprise challenges to pattern solutions to implementation results - Inductive strength: Good use of specific AXA experience to suggest general enterprise applicability - Causal reasoning: Clear connections between pattern adoption and collaboration outcomes - Analogical strength: Effective "standing on shoulders" metaphor for building on community work #### Fallacies - Appeal to authority: Heavy reliance on Red Hat and InnerSource Commons credibility without independent validation - Survivorship bias: Focus on successful patterns without discussing failed experiments or abandoned approaches #### Tone of voice - Overall tone: Professional, collaborative, humble with appropriate attribution to community sources ### 🛡️ DARVO Analysis - Deny: No denial patterns detected - speakers acknowledge challenges openly - Attack: No attacks on alternative approaches or competitors - Reverse victim/offender: No victim/offender dynamics present - Emotional cues and rhetoric: Positive, collaborative language emphasizing community contribution and gratitude ## 🎯 Conclusion AXA's nine-year inner source journey demonstrates that large enterprises can successfully implement inner source by adapting proven community patterns rather than developing custom solutions. Their "secret equation" combining Red Hat expertise with Inner --- ## Full Transcript [00:06] Thank you for having us here. It's our [00:07] first time in in Inosour Commons. Thanks [00:09] SAP. I hope it's not the last one. Let's [00:12] keep up with the good mood. It's very [00:15] it's it's been, you know, very very [00:17] interesting, very great so far. So let's [00:19] see if we can have it can do it. And we [00:21] are already presented. I'm Carlos [00:23] Navaro, principal engineer at AXA. I'm [00:25] leading the boarding staff at AXA, [00:27] governance architecture. [00:29] um you know compliance and so on and and [00:32] that's me I'm Roman Martin I'm principal [00:34] architect at Imia services so basically [00:36] I'm from redhat that means an open by [00:39] default and a open source and inner [00:41] source believer [00:43] and I'm anagamito I'm currently the open [00:46] source program officer at taxa group um [00:49] I'm a tech passionate I'm always [00:52] involved in ethical things in [00:54] engineering like uh sustainability [00:57] accessibility [00:59] open and inner source um lot of things [01:03] and community building because I I [01:06] believe that uh we can arrive uh far [01:08] away if we work together and we improve [01:14] together then [01:19] let's start we want to share today our [01:21] journey at AXA our journey regarding [01:24] inner source uh and how we build our [01:27] inner source foundations um through the [01:30] inner source patterns. You share it [01:33] um supported by the Red Hat and fueled [01:36] by a completed year of uh hard work [01:40] together with the open innovation lab uh [01:44] team we build together in order to to um [01:49] challenge each others to to create the [01:52] the good setup. Okay, imagine that um [01:56] you are joining us at the very very [01:59] beginning of this uh journey and we [02:02] start with a question how we can work [02:05] together we can go work better together [02:09] across teams across uh borders across [02:12] different disciplines. [02:15] Today we will guide you through the [02:17] story of AXA uh at the inner source and [02:22] we will start with [02:25] no [02:27] back. [02:32] Thank you. [02:35] We will guide you through uh our [02:38] journey. Um [02:41] because why? because we are interested [02:43] in in right now. Uh what is our open [02:47] timeline because we start a long time [02:49] ago. Um a description of the patterns [02:54] that we are applying right now and and a [02:57] demo and also what's next what's next [03:02] now. Yes. [03:05] And next, [03:08] as you know, AXA is a worldleading [03:10] insurance and an asset management group. [03:13] We serve uh over 95 million of uh [03:17] customers and we are in mostly 50 [03:22] countries. [03:23] Our mission is simple simple yet po [03:27] powerful act for human progress by [03:30] protecting what matters. [03:33] We have a truly global footprint. We we [03:37] have over [03:40] 150 uh employees [03:42] with a real uh real committed to to our [03:46] core values. Customer first, courage, [03:50] integrity and wanaka. [03:53] These values guide us uh everything we [03:56] do every day everywhere. [03:59] This year is especially significant for [04:02] us because we are is our 40 anniversary [04:07] and is a real testament of our [04:09] commitment to innovation, progress and [04:11] protecting what matter matters most. [04:15] Our scale is significant as you know as [04:18] I said before we over 100 billion [04:23] in an annual revenues which means [04:26] collaboration and reuse of solutions are [04:30] not just beneficial [04:32] is essential for us to succeed [04:38] as we move uh towards more driven and [04:42] digital first services. [04:45] We need to break breaking down silos and [04:47] accelerate innovation [04:49] across our federated structure. [04:53] This be becomes critical for us. It mean [04:56] it mean that sharing just uh sharing is [04:59] not just code is also sharing knowledge [05:02] best practices and also challenges and [05:04] and learnings from failings. [05:08] Then for us to to to contribute, learn [05:11] and grow together is super important. [05:15] This is where inner source come commi [05:17] comes in by applying opensource [05:19] principles internally which foster [05:21] transparency [05:23] collaboration and share ownership [05:27] making it possible for teams to build on [05:29] each other work co-create and accelerate [05:33] innovation. [05:35] Innersour has turned out this as an [05:38] strategic enable enabler for innovation [05:41] at the scale. [05:46] As I mentioned, AXA is a large ecosystem [05:50] with thousand of talented people working [05:52] towards a common goal. Deliver secure [05:55] highquality digital solution for [05:58] millions of customers around the world. [06:01] In such a big big organization, how do [06:04] we keep innovation flowing and avoiding [06:07] silos? [06:10] That's where in inource come in. [06:14] We reuse code, co-create solution and [06:17] scale AI uh initiative efficiently. But [06:20] inner source is more than technology is [06:23] built on our four key uh principles. [06:27] Collaboration, transparency, recognition [06:29] and compliance. [06:31] These pillars create a safe and open [06:34] environment where teams can share ideas [06:37] and innovate efficiently. [06:40] Inner source isn't just a method, it's [06:43] an strategic enabler for us that help [06:46] AXA deliver secure and high quality [06:49] solutions. [06:54] Now time for our open timeline. [06:59] Uh as you see we started a long time ago [07:03] mostly with um Innosource common in [07:06] parallel. We start with u creating our [07:09] open culture. We celebrate in 2016 nine [07:12] years ago our first summit where uh [07:16] different engineers from the different [07:17] entities and countries start to share [07:20] their practices and and collaborate [07:22] together. [07:24] But this this is uh something that we [07:26] have a continued and keep [07:29] year by year. Last week we we've been in [07:33] Sevilla with uh 3,000 engineers [07:37] sharing again and our comm community has [07:41] grown to [07:43] 2,500 [07:46] developers [07:48] and people interested in software [07:49] engineer. That is a a big number for us. [07:54] Since then we h hit a major major [07:57] milestones [07:59] early experiments in sharing and reuse [08:01] adopting open source licenses. We are [08:04] also members of fenos and the Linux [08:06] foundation and we have launched our open [08:10] source program officer that office that [08:12] is also in charge of innersource. [08:16] Past JR we step into the Red Hat open [08:19] innovation lab with a single goal. Build [08:23] inner source foundation that breaks [08:25] silos, accelerates innovation and foster [08:28] community. And now in 2025 we are [08:32] scaling with patterns. [08:34] Why patterns? Because pattern are shared [08:38] wisdom. Your wisdom. [08:41] We didn't reinvent the wheel. [08:44] We stood on your shoulders uh of [08:47] community and proven patterns to fit our [08:50] reality at AXA. [08:55] Our secret equation combines Red Hat uh [08:59] open expertise [09:01] with H innersource common private [09:04] patterns. [09:05] With Red Hat giving us we embed escalab [09:08] scalable and open practices across AXA. [09:11] By applying inner source patterns, we [09:13] gain a shared language and a toolkit for [09:16] transparency, trust and innovation. [09:19] The result, a winning combination of our [09:22] secret equation that accelerates [09:25] collaboration break down silos and [09:27] empowers every AXA engineer to become a [09:30] catalyst for change. [09:34] At AXA, we already adopt key inner [09:38] source patterns. We set a clear legal [09:41] framework through our inner source [09:42] license. We define our guiding pre [09:46] principles at the knowledge portal. [09:49] Every project include a standard [09:51] documentation from our inner source [09:53] template [09:55] and we every every project is lead by a [09:59] core team and recognize trust trusted [10:02] contributors. We will use review [10:04] committees for important changes. [10:08] centralized project visibility at the [10:10] inner source portal. [10:12] We are also developing a really a a [10:15] really and powerful platform to collect [10:18] the data and to share the projects. [10:25] We are uh rely also in a strong [10:27] communication tools and issue tracking [10:30] at GitHub and we will measure maturity [10:33] and health in our insights portal and we [10:37] celebrate every contribution [10:40] but our journey is not over. We will [10:43] keep exploring and adopting new patterns [10:45] to fit our needs. Let's hand over to the [10:48] demo. Yeah, it takes courage to [10:50] implement new force and it takes more [10:52] courage to explain it in front of you. [10:54] So, thanks Anna. Uh, demo time, virtual [10:57] demo time. It's a video. So, you will [10:59] see how we climb the peak of a [11:01] standardization and then we were ready [11:03] to to freeall to the valley of [11:07] automation. We are not yet there. We are [11:09] not crazy guys. We don't reinvent the [11:11] wheel. So, we are using a red parachute [11:14] to do this. We are relying on a standard [11:16] patterns and our partners Red Hat to [11:18] build the automation. So it's a you know [11:20] it's a humble journey today but uh you [11:24] will see more or less what we are [11:25] building even our branding. Okay. So [11:28] well I think I don't know if we are [11:30] going to have enough time to present all [11:31] the video but I think could be part of [11:33] the outputs but well here you can see [11:36] that one of the first patterns we [11:39] introduced were related about the inner [11:41] source portal. We implemented different [11:43] kind of inner source portal. One is just [11:46] this this kind of on boarding but also [11:48] we created some learning paths just for [11:51] newbies for people that they don't know [11:53] anything about inner source but also we [11:55] have this inner source knowledge portal [11:57] that's basically uh align with the [11:59] documenting your guidance. So it's [12:02] basically another pattern where you are [12:04] describing all the main things that you [12:06] need to know about what is inner source [12:08] why it's important at AXA and also some [12:12] kind of guidelines and also the [12:14] structure of the governance model. So we [12:16] introduce another pattern the what we [12:17] call core group but is connected with [12:19] the cine pattern that is basically the [12:23] maintainers or the trusted committers [12:25] that they are supporting inner source [12:27] project. So but we are not describing [12:29] only the the the the pattern it's also [12:32] we are visualizing where are you in [12:34] terms of you are p member of the open [12:36] committee you are members of the open [12:38] group and also which kind of roles and [12:40] responsibilities you have [12:41] >> and we always build assets first as you [12:43] can see this is a dosarus based template [12:46] uh tailored for axa branding and there [12:49] are more templates so how do we start [12:50] there is also a pattern for that right [12:52] so um um what what what patterns do you [12:56] need to to start a project [12:57] >> so So in a couple of minutes in a couple [12:59] of seconds we're going to introduce the [13:00] how to start. So we have also this kind [13:02] of guidelines in how we can contribute [13:04] how can start this these projects. So in [13:06] the how to start we have I think is the [13:08] most powerful pattern for us is the [13:11] standard based documentation we extended [13:14] and expanded that pattern as much as [13:17] possible intends to introduce all the [13:20] templates all the structures all the [13:22] guidelines and also all the automations [13:24] are important in one single place. We [13:27] created uh this inner source template [13:29] repository that basically provides you [13:32] all the things that you need to start [13:34] from the beginning. So basically it's a [13:36] set of assets and templates that give [13:39] will give you all the powerful to start [13:42] from the beginning. So the rest of the [13:44] video will present those kind of things [13:46] and also how to introduce [13:47] >> and we avoid most of the pardon. We [13:49] already have the code of conduct the [13:50] contributing the license the security [13:52] guidelines all in one place. Okay. For [13:54] for us it's important in code of conduct [13:56] because represent how we are going to [13:58] collaborate all together but also the [14:00] license because AXA is a federated [14:02] organization. So we need to be sure how [14:05] to manage the code across the different [14:08] entities. [14:08] >> Same IP projects we were mentioning this [14:10] morning. Right. [14:11] >> Okay. So I think the video is a bit [14:13] longer but I think we can hand over to [14:16] Anna just to finalize. But basically the [14:18] previous slide we presented all we have [14:21] in around 8 minutes all of the patterns [14:24] included [14:25] >> how you create the pull request how you [14:27] >> so I think you can wrap up [14:29] >> four minutes [14:30] >> four minutes well at the end what you [14:32] are showing the what we are showing in [14:33] the video is how Romanian his role of of [14:35] of core contributor and after um um [14:39] trusted contributor contributor uses [14:41] pull request to create uh uh um well you [14:45] know solve an issue [14:47] from for us every everything is guided [14:49] via pull request request. [14:51] >> One of the things that maybe we can [14:53] highlight here is it is a standard based [14:55] documentation plus others about [14:56] documenting your your print simples uh [14:59] praise your uh participants and and so [15:02] on is basically we can say that is a [15:04] self service. You have everything [15:06] described. You don't need to ask anyone. [15:09] You can jump into the different [15:10] inosource portals. Then you can jump [15:12] into the documentation and then you can [15:13] start because everything is already [15:15] described and again all those assets are [15:19] open for contributions. We are not [15:21] experts or maybe we are we are not [15:23] covering everything but we are open also [15:25] because we we have our contribution [15:28] guidelines to everyone [15:30] >> and we open also our community um [15:34] channels different to us and to to to be [15:38] involved and to participate. [15:42] Could you [15:42] >> next [15:43] >> next go to the next please. Thank you. [15:46] Then our next innocious patent to adapt [15:49] and adopt in the next year maybe are [15:52] these that we have started to select [15:54] like the dedicated community leader or [15:56] set the split explicit governance [15:58] levels. Um also the project valuation we [16:02] the cross team project valuation will [16:04] will be something that uh u valuable for [16:07] us. Um also how to document the [16:10] decisions the the teams uh start to to [16:13] take uh in order to to have a [16:15] synchronous way of uh connect to the [16:18] project and to start and to to know the [16:20] direction and the address that they need [16:22] to to to follow and we have we have said [16:27] as several but uh we we want to thank [16:30] you all of you because these are your [16:33] patterns these are thing that you have [16:35] learned with your experience and we have [16:37] uh ten take advantage of this in order [16:39] to implement in our big company. [16:43] And that's it. Maybe you have some [16:46] questions or doubts or anything you want [16:49] to