Yuki Hattori โ Welcome to InnerSource Summit 2025
๐ **Source:** [Yuki Hattori โ Welcome to InnerSource Summit 2025](https://www.youtube.com/watch?v=XdiXkcwLyiM)
> [!note]+ Document Notes
> tags: [innersource, open-source, community]
> author: Yuki Hattori
> source: InnerSource Commons Foundation
> reference: https://www.youtube.com/watch?v=XdiXkcwLyiM
> date created: 2025-01-13 14:30
>
> # ๐ท๏ธ Title: Welcome to InnerSource Summit 2025
>
<!-- deep-read:sections start -->
## ๐งฐ Action Inbox
- [H1] Join local InnerSource gathering community โ 00:00-02:30 #community
- [H2] Visit innersource.org/stories for case studies โ 02:30-05:00 #resources
- [H3] Explore InnerSource patterns website for adoption methodology โ 08:00-10:00 #implementation
## ๐งญ 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](https://innersource.org)
- [InnerSource Stories](https://innersource.org/stories)
- [InnerSource Patterns](https://patterns.innersourcecommons.org)
## ๐ Summary
- InnerSource Commons Foundation celebrates its 10th anniversary and the 25th anniversary of the InnerSource term at their global 24-hour summit
- Growing global community with case studies from financial, manufacturing, and technology sectors across multiple continents
- Four core principles: openness, transparency, prioritized mentorship, and voluntary code contribution
- InnerSource helps organizations break down silos and drive AI adoption through open collaboration principles
- Community expanding globally with local gatherings and increasing participation, especially in China and Japan
## ๐ Main Content
InnerSource represents the application of open source development techniques within corporate environments. Originally coined by Tim O'Reilly in 2000, the concept was reintroduced by Dennis Cooper in 2015 as organizations faced increasing digital transformation challenges. The rise of cloud computing and digital transformation led to more IT resources, engineers, and products within companies, creating organizational silos that InnerSource methodologies help break down.
The InnerSource Commons Foundation serves as a neutral hub for organizations adopting these practices, providing patterns, case studies, and community support. The approach emphasizes four key principles: openness (accessible resources), transparency (open decision-making), prioritized mentorship, and voluntary code contribution.
## ๐๏ธ Notes
#### โฑ๏ธ [00:00](https://youtu.be/XdiXkcwLyiM?t=0) โ [H1] 10th Anniversary Celebration
- Key idea: InnerSource Commons Foundation celebrates 10 years alongside 25 years since the term was coined
- Evidence: "It's actually 25 years since the term inner source was coined by Tim O'Reilly"
#### โฑ๏ธ [00:30](https://youtu.be/XdiXkcwLyiM?t=30) โ [H2] Global Partnership Recognition
- Key idea: Multiple major tech companies sponsor and support the InnerSource movement
- Evidence: "Analog devices, Vurgia, GitHub, IBM and Microsoft and Bosch, Comcast"
#### โฑ๏ธ [01:15](https://youtu.be/XdiXkcwLyiM?t=75) โ [H1] 24-Hour Global Summit Format
- Key idea: First-ever 24-hour summit spanning Japan, Berlin, and New York
- Evidence: "This event is 24 hours event. So we are hand over to Berlin... and then we will land in New York"
#### โฑ๏ธ [02:30](https://youtu.be/XdiXkcwLyiM?t=150) โ [H2] Global Case Studies Available
- Key idea: InnerSource implementations span all major industries and continents
- Evidence: "InnerSource stories are everywhere... from the financial sector, manufacturing sector to cutting edge technology"
#### โฑ๏ธ [03:15](https://youtu.be/XdiXkcwLyiM?t=195) โ [H3] Growing Asian Participation
- Key idea: Strong representation from APAC region including Thailand, China, and Japan
- Evidence: "We have several guests from APAC region from Thailand and then China"
#### โฑ๏ธ [03:45](https://youtu.be/XdiXkcwLyiM?t=225) โ [H2] Gartner Recognition
- Key idea: InnerSource gained mainstream recognition in Gartner's Hype Cycle
- Evidence: "InnerSource the term is captured in Gartner's hype cycle two years ago"
#### โฑ๏ธ [04:30](https://youtu.be/XdiXkcwLyiM?t=270) โ [H1] Community Growth Milestones
- Key idea: Local communities expanding globally with significant events
- Evidence: "We had an event at Tokyo, Berlin, Vienna, Dublin, Shenzhen, Paris, Sรฃo Paulo"
#### โฑ๏ธ [05:45](https://youtu.be/XdiXkcwLyiM?t=345) โ [H2] Mission Statement
- Key idea: Foundation empowers organizations to apply open collaboration principles beyond open source
- Evidence: "We empower developers and organization to apply open collaboration principle in their daily work"
#### โฑ๏ธ [06:30](https://youtu.be/XdiXkcwLyiM?t=390) โ [H1] Historical Context: 2000 vs 2015
- Key idea: InnerSource became crucial when digital transformation created organizational silos
- Evidence: "In 2015... every single company are trying to be a digital company by transforming themselves"
#### โฑ๏ธ [07:45](https://youtu.be/XdiXkcwLyiM?t=465) โ [H1] Four Core Principles
- Key idea: InnerSource built on openness, transparency, prioritized mentorship, and voluntary contribution
- Evidence: "Four principles of inner source: openness, transparency and prioritized mentorship and finally voluntary code contribution"
#### โฑ๏ธ [08:15](https://youtu.be/XdiXkcwLyiM?t=495) โ [H3] Transparency vs Openness Distinction
- Key idea: Transparency focuses on decision-making processes, not just accessibility
- Evidence: "Openness is just open and accessible but transparency itself is for decision making"
#### โฑ๏ธ [09:00](https://youtu.be/XdiXkcwLyiM?t=540) โ [H2] InnerSource Patterns Initiative
- Key idea: Documented patterns provide concrete guidance for InnerSource adoption
- Evidence: "We were starting to compile those practices as inner source patterns from 2020"
## ๐ References
- [InnerSource Commons](https://innersource.org)
- [InnerSource Stories](https://innersource.org/stories)
- [InnerSource Patterns](https://patterns.innersourcecommons.org)
- [Gartner Hype Cycle](https://www.gartner.com)
## ๐ฃ๏ธ Paraphrase
- InnerSource Commons Foundation marks a decade of helping organizations adopt open source practices internally, coinciding with 25 years since Tim O'Reilly first named the concept
- The movement has grown from addressing digital transformation challenges in 2015 to becoming a globally recognized methodology with industry backing and Gartner recognition
- Core principles emphasize not just making resources accessible, but ensuring transparent decision-making, mentorship culture, and voluntary participation across organizational boundaries
## ๐ฐ Newsletter
**InnerSource Goes Global: 10 Years of Breaking Down Corporate Silos**
The InnerSource Commons Foundation just celebrated a major milestone - 10 years of helping organizations apply open source principles internally! What started as a way to address digital transformation silos has grown into a global movement spanning 24 time zones.
**Key Takeaway**: InnerSource isn't just about opening code repositories - it's about transparent decision-making and voluntary collaboration that breaks down organizational barriers.
**WordPress Connection**: These principles directly apply to how WordPress teams can collaborate across core, community, and commercial boundaries while maintaining project independence.
**Get Started**: Visit the InnerSource Patterns site for documented approaches, or join local gathering communities to connect with practitioners.
Resources: [InnerSource Commons](https://innersource.org), [Community Handbook](https://make.wordpress.org/community/handbook/), [Core Contributor Handbook](https://make.wordpress.org/core/handbook/)
## โ
Action Items
#### OSPO
- Community Engagement: Study InnerSource patterns for cross-organizational collaboration models
- Policy & Governance: Develop transparent decision-making processes based on InnerSource principles
- Developer Support: Create mentorship programs following InnerSource voluntary contribution model
#### Community
- Contributors: Implement InnerSource onboarding patterns for new contributor experiences
- Maintainers: Apply transparency principles to project roadmap and decision documentation
- Ecosystem: Foster voluntary code contribution culture across WordPress project boundaries
#### WordPress
- Core Program Team: Adapt 24-hour summit model for global WordPress contributor coordination
- Community: Organize regional WordPress InnerSource gatherings following Commons model
- Meta: Apply InnerSource transparency principles to .org project decision-making processes
## ๐งช Hypotheses
- Organizations applying InnerSource principles see reduced development silos and increased cross-team collaboration
- Transparent decision-making processes lead to higher voluntary contribution rates than traditional corporate structures
- Global 24-hour summit formats increase participation from underrepresented geographic regions
- InnerSource methodologies accelerate AI adoption by enabling better internal knowledge sharing
### ๐ Methodology
- Survey InnerSource Commons case studies for quantitative collaboration metrics
- Compare voluntary contribution rates between transparent vs. traditional corporate decision-making
- Analyze geographic participation data from 24-hour vs. traditional summit formats
- Interview organizations using InnerSource for AI initiatives
### โ Questions
- How do InnerSource transparency principles apply to open source projects with commercial stakeholders?
- What specific patterns from InnerSource could improve WordPress's multi-stakeholder governance model?
- How might 24-hour global coordination formats work for WordPress release cycles?
### ๐ฎ Future Research
- Effectiveness of InnerSource patterns in hybrid open source/commercial ecosystems
- Role of InnerSource methodologies in responsible AI development and deployment
- Cross-cultural adaptation of voluntary contribution models in different business contexts
### ๐ก Implications
- Practice: WordPress teams could adopt InnerSource transparency patterns for better cross-team collaboration
- Policy: InnerSource principles could inform governance models for mixed commercial/community projects
- Education: Global 24-hour format could expand WordPress contributor training across time zones
- Community: Voluntary contribution models could reduce barriers to WordPress ecosystem participation
### ๐ง Learning Styles Assessment
Reading level estimate: 12th grade
#### ๐ Visual learners
- Present: Geographic community map, partnership logos, timeline graphics
- Improve: InnerSource principles diagram, organizational silo breakdown visualization
#### ๐ Aural learners
- Present: Video presentation format with clear narration
- Improve: Audio-only version for podcast consumption, key quotes highlighted
#### ๐ฃ๏ธ Verbal learners
- Present: Clear definitions, historical context, principle explanations
- Improve: Analogies comparing InnerSource to traditional open source development
#### ๐งฉ Kinesthetic learners
- Present: Links to patterns website, gathering participation opportunities
- Improve: Step-by-step InnerSource adoption checklist, hands-on workshop materials
#### ๐ง Logical learners
- Present: Historical timeline, four-principle framework, cause-effect relationships
- Improve: Decision trees for InnerSource adoption, ROI metrics from case studies
#### ๐งโ๐คโ๐ง Social learners
- Present: Community emphasis, global gathering network, collaborative language
- Improve: Discussion prompts for team implementation planning
#### ๐งโโ๏ธ Solitary learners
- Present: Self-directed exploration of patterns and resources
- Improve: Individual reflection questions on organizational culture change
#### ๐ฟ Naturalistic learners
- Present: Ecosystem growth metaphors, organic community development
- Improve: Natural collaboration patterns, sustainable community building principles
### ๐ Accessibility Assessment
#### Screen reader semantics
- Present: Clear heading structure, descriptive link text for resources
- Improve: Alt text for any community/partnership graphics, ARIA labels for video controls
#### Keyboard navigation
- Present: Standard video controls accessible via keyboard
- Improve: Skip links for long speaker introductions, tab order optimization
#### Contrast and readability
- Present: Standard video player contrast ratios
- Improve: High-contrast transcript option, customizable text sizing
#### Text resizing and reflow
- Present: Responsive transcript display at 200% zoom
- Improve: Prevent horizontal scrolling, maintain readability at high zoom levels
#### Media and captions
- Present: Video content with transcript provided
- Improve: Professional captions with speaker identification, downloadable transcript
#### Forms and interactions
- Present: Basic video interaction controls
- Improve: Accessible sharing options, feedback form for summit content
### ๐ DEIB Assessment
#### Cultural breadth
- Present: Global community representation, APAC region emphasis, multilingual participants
- Improve: African community development plans, indigenous collaboration models
#### Inclusive language
- Present: Gender-neutral community terms, accessible technical explanations
- Improve: Plain-language summaries, cultural context for business practices
#### Neurodiversity support
- Present: Clear structure with timestamps, consistent presentation format
- Improve: Content warnings for rapid topic changes, visual cues for section transitions
#### Representation
- Present: Asian leadership visibility, global geographic diversity
- Improve: Gender diversity in speaking roles, varied organizational sizes represented
#### Psychological safety
- Present: Welcoming community tone, voluntary participation emphasis
- Improve: Code of conduct references, clear escalation paths for issues
### โ
Logical Validity
#### Strong reasoning
- Historical reasoning: Clear progression from 2000 term coining to 2015 reintroduction to current state
- Causal reasoning: Digital transformation โ organizational silos โ need for InnerSource solutions
- Analogical strength: Open source principles applied to internal corporate contexts
#### Fallacies
- Appeal to popularity: Mentions many sponsors/partners without explaining why this validates the approach
- Hasty generalization: "InnerSource stories are everywhere" without quantifying actual adoption rates
#### Tone of voice
- Overall tone: Celebratory and inclusive with educational elements, appropriate for community welcome address
### ๐ก๏ธ DARVO Analysis
- Deny: No denials present - straightforward community presentation
- Attack: No attacks on critics or alternative approaches
- Reverse victim/offender: Not applicable to this community-building content
- Emotional cues and rhetoric: Positive community building language, celebration of milestones
## ๐ฏ Conclusion
InnerSource Commons Foundation demonstrates how open source principles can transform internal organizational collaboration. After 10 years of community building, the movement has evolved from addressing digital transformation silos to enabling global coordination across industries. The four core principles of openness, transparency, prioritized mentorship, and voluntary code contribution provide a framework that WordPress and other open source projects can adapt for their own multi-stakeholder governance challenges.
The 24-hour global summit format and growing international community show how distributed collaboration can scale beyond traditional geographic and organizational boundaries. For WordPress contributors and community organizers, InnerSource patterns offer proven methodologies for building inclusive, transparent, and effective collaboration across commercial and community interests.
## ๐งฑ Refactor Appendix
### ๐ Literature Split Pad
Purpose: Stage CEE units that become Literature notes.
Split level: H3
### [H1] InnerSource Commons celebrates 10-year milestone with global community growth
> [!quote] [Welcome to InnerSource Summit 2025](https://www.youtube.com/watch?v=XdiXkcwLyiM) by [[Yuki Hattori]] via [[InnerSource Commons Foundation]]. Published 2025-01-13. Accessed 2025-01-13.
> "We are celebrating our 10 years anniversary at the foundation at the same time."
Foundation milestone coincides with 25 years since Tim O'Reilly coined the term, showing sustained growth.
[view highlight](https://youtu
---
## Full Transcript
[00:04] So welcome to Inosour Summit 2025.<br>[00:08] So actually it's a very special summit<br>[00:11] for us because um we are celebrating our<br>[00:16] 10 years anniversary at the foundation<br>[00:18] at the same time. It's yeah actually 25<br>[00:22] years since the term inner source was<br>[00:24] coined by Tim Oridi. So yeah, we have<br>[00:27] made it this uh far together and we<br>[00:30] could not have done it without the<br>[00:32] amazing community. Thank you very much.<br>[00:35] Yep.<br>[00:39] And uh thank you for your support. So um<br>[00:42] actually um there are so many partners<br>[00:44] and spons supporters who are<br>[00:47] contributing to us. So analog devices,<br>[00:50] Vurgia, GitHub, IBM and Microsoft and<br>[00:53] Bosch, Comcast, Fanimi, uh Lensra,<br>[00:56] Melisbens and Red Hat and SAP. Actually<br>[00:59] there are so many um inner source<br>[01:01] community out there and if you find the<br>[01:05] cases of inner source actually you can<br>[01:08] find literally everywhere around the<br>[01:10] world and thank you for our hosts summit<br>[01:13] host IBM, Mitsubishi Electric, SAP. So<br>[01:17] actually this event is 24 hours event.<br>[01:20] So we are hand over to uh Berlin. So SAP<br>[01:25] in Berlin and then we will land in uh<br>[01:29] New York. So New York will be New York<br>[01:32] summit will be operated by um IBM. So<br>[01:35] and also there is uh another uh summit<br>[01:38] dedicated sponsor GitLab, Red Hat and<br>[01:41] Bird Solutions. Uh thank you very much<br>[01:43] and for supporter is Nifty. So please be<br>[01:47] ready to be taken uh by so actually we<br>[01:50] are sharing uh this kind of excitement<br>[01:52] uh afterwards.<br>[01:54] So um I'd like to hear uh introduce<br>[01:59] about the foundation itself and why<br>[02:03] inner source matters right now and then<br>[02:06] actually I will briefly touch on AI<br>[02:09] relation of inner source.<br>[02:12] Yep. So as I said that actually Inosour<br>[02:16] stories are everywhere. So we they are<br>[02:19] building their innoc<br>[02:21] culture, Inosour program offices inside<br>[02:24] the company. So from the financial<br>[02:26] sector, manufacturing sector to cutting<br>[02:29] edge technology or maybe big tech. So<br>[02:32] actually and then there are several<br>[02:34] Japanese companies uh cases available<br>[02:37] here. So please visit<br>[02:39] innerossource.orgstories. argstories<br>[02:44] and inner source community across the<br>[02:47] world is very very exciting thing. So<br>[02:50] from uh Europe, America and Japan and<br>[02:54] China actually we have several guests<br>[02:56] from uh Apac region from Thailand and<br>[02:59] then China. So actually uh please enjoy<br>[03:03] those kind of global session as well<br>[03:04] today.<br>[03:07] So and actually Inosource itself is also<br>[03:12] uh growing and exciting. So Inosource<br>[03:15] the term is captured in Gardner's hype<br>[03:18] cycle uh two years ago and then actually<br>[03:21] Gartner's uh Nitish Thiagi M principal<br>[03:23] analyst will present the current status<br>[03:25] of inner source uh today. So actually we<br>[03:29] are gaining momentum and then also inner<br>[03:31] source itself is very important uh topic<br>[03:34] for driving AI adoption as well.<br>[03:39] So I will explain it later. So actually<br>[03:42] um our first summit was um conducted in<br>[03:46] 2015. Um actually it was a closed uh<br>[03:48] very private one. However, actually um<br>[03:52] we have a very first summit in uh 2016<br>[03:55] and<br>[03:57] um actually this year's summit is very<br>[04:00] special because um this is 24 hours<br>[04:02] format. So actually Japan is the first<br>[04:06] um uh place for uh this summit. So<br>[04:10] please enjoy. Actually uh you can also<br>[04:12] join the new Berlin and New York summit<br>[04:14] online as well. So please enjoy those uh<br>[04:17] content as well.<br>[04:21] Yep. And then actually u there is some<br>[04:24] black boxes in the right bottom corner.<br>[04:26] However uh there's a inner source man<br>[04:28] here as well. So actually afternoon you<br>[04:31] will see inosource hero in uh this uh<br>[04:36] summit Yokohama venue but actually our<br>[04:39] uh community itself local community is<br>[04:42] also expanding. So starting from the<br>[04:45] Dublin community actually we had a<br>[04:48] formed inos gathering brand h in 2024.<br>[04:52] So we had an event at Tokyo, Berlin,<br>[04:54] Vienna, Dublin, Shenzhen, Paris um Sa<br>[04:58] Paulo and then we are looking forward to<br>[05:00] the African community as well. So<br>[05:02] actually um you can join uh your<br>[05:04] community in Japan of course if you are<br>[05:06] in a different location you can join<br>[05:08] those community as well as you can<br>[05:11] actually found your community yourself.<br>[05:14] So we are very looking forward to your<br>[05:16] contribution<br>[05:19] and actually recent highlight is China<br>[05:22] and Japanese community growth. So in<br>[05:25] China it's actually last year we had a<br>[05:28] 10,000 um participants level online<br>[05:31] event uh in it's actually hybrid event<br>[05:34] and also last year and this year we had<br>[05:37] an amazing Japanese uh community in the<br>[05:39] gathering event. We will uh join<br>[05:42] gathering event the uh next year as<br>[05:44] well. So please stay tuned<br>[05:50] and actually our mission is we empower<br>[05:54] developers and organization to apply<br>[05:55] open collaboration principle in their<br>[05:57] daily work. It's not about only about<br>[06:00] open source but for also for propri<br>[06:03] proprietary area. So we build a strong<br>[06:07] uh inclusive community and also we<br>[06:09] should be a neutral hub as inner source<br>[06:12] commons. So if you are willing to take<br>[06:15] kind of inner source approach inside<br>[06:17] your company. So please uh join our<br>[06:21] community and then also uh probably you<br>[06:24] can post something on uh slack or maybe<br>[06:27] you can join the GitHub conversation as<br>[06:29] well. Yep. So<br>[06:32] now<br>[06:34] probably some of you have may have known<br>[06:38] about inner source and then some may not<br>[06:41] know very well about inner source. I'd<br>[06:43] like to explain a little bit more on<br>[06:45] inner source what the inner source is<br>[06:47] and why innosource matters. So actually<br>[06:51] 2000 as I said Tim Oridi coined the term<br>[06:54] Inosource<br>[06:57] but since<br>[06:59] the Inosource definition is like a<br>[07:02] helping team and a companies to use open<br>[07:04] source development technique within the<br>[07:06] corporation with a cluster of key<br>[07:08] customers. So there were some community<br>[07:11] and there were some practitioner but<br>[07:13] it's not unnamed or maybe it was just<br>[07:17] taken as a part of open source and then<br>[07:19] it was okay because there were not that<br>[07:22] many silos inside the organization at<br>[07:24] the time because actually um there are<br>[07:27] IT resources just existing for<br>[07:30] supporting their corporate business<br>[07:32] objectives or maybe their mean core<br>[07:34] businesses. However, in 2015, Dennis<br>[07:39] Cooper, our Inos comm Foundation's uh<br>[07:42] founder reintroduced inosource. There's<br>[07:45] a why the reason because um actually in<br>[07:49] 2015 what happened it was a cloud era<br>[07:52] cloud I mean adoptions and every single<br>[07:56] company are trying to be a digital<br>[07:58] company by transforming theirself. So it<br>[08:01] was called it was called digital<br>[08:03] transformation and it resulted<br>[08:07] every company's IT resources were<br>[08:10] increased and also they are hiring they<br>[08:12] hired so many engineer inside the<br>[08:15] company and they created so many<br>[08:17] products inside the company. So that<br>[08:20] made silos and corporate silos in the<br>[08:24] organization. So there were the reason<br>[08:28] to drive the inner source cultural I<br>[08:31] mean changes and also driving the<br>[08:33] transparent culture inside the company<br>[08:36] or maybe their uh reason to there were<br>[08:39] reason to break down the silo across the<br>[08:41] organization because they shouldn't<br>[08:43] reinvent the wheel inside the company or<br>[08:46] actually they need to share their um<br>[08:50] corporate resources or maybe co uh<br>[08:52] competitive resources across the company<br>[08:55] because they are trying to they were<br>[08:57] trying to create a synergy uh inside the<br>[09:00] organization by co-creation. So that's<br>[09:04] the reason why innosource matters<br>[09:07] mattered at 2015 and then actually we<br>[09:11] are uh thinking that innerource itself<br>[09:13] is very important uh topics for AI as<br>[09:16] well. So, so there are four principles<br>[09:20] of um inner source openness uh<br>[09:24] transparency and prioritized mentorship<br>[09:26] and finally uh voluntary code<br>[09:28] contribution. So openness and uh<br>[09:31] transparency is a little bit different<br>[09:33] because um openness is just open and<br>[09:36] accessible but transparency itself is<br>[09:39] for decision making. So if your decision<br>[09:43] making is open and transparent and<br>[09:46] conducted in a transparent way, it will<br>[09:49] bring uh something new to your<br>[09:51] organization. Probably your team or<br>[09:53] neighbor team can start contributing to<br>[09:56] your team or maybe you can easily access<br>[09:59] to your corporate resources<br>[10:01] um without any boundary. So open<br>[10:05] transparency and also opensource culture<br>[10:07] based prioritized mentorship and a<br>[10:09] voluntary code contribution is very<br>[10:11] important thing. Yep.<br>[10:14] And actually the open-source<br>[10:19] practices so it's kind of broad idea<br>[10:22] right? So it could be anything. So it<br>[10:24] could be for instance um just<br>[10:26] contributing to other team or just<br>[10:28] removing uh your configuration for<br>[10:31] closed configuration or maybe you you're<br>[10:33] opening up your repository. However<br>[10:35] actually we were starting to um compile<br>[10:39] those practices as inner source patterns<br>[10:41] from 2020. So you can visit innerosource<br>[10:45] patterns and you will find the idea what<br>[10:48] the inner source is and how to adopt the<br>[10:51] inner source methodology inside the<br>[10:54] organization. So it's uh it's all about<br>[10:58] the I mean organizational theory thing<br>[11:00] and also culture change and then also<br>[11:03] decision making processes. So it's very<br>[11:06] uh I I I'd really recommend visiting<br>[11:09] this site as well and there are so many<br>[11:12] uh inner source books available. So it's<br>[11:15] very uh great starting point to learn<br>[11:19] inner source.<br>[11:21] Yep. So this is innerource summit which<br>[11:25] is a global flagship conference and then<br>[11:29] actually we have a gathering event in a<br>[11:32] different location as I explained. So uh<br>[11:35] actually we have done three gatherings<br>[11:38] in Tokyo but actually uh in Europe<br>[11:41] regions and then American region there<br>[11:43] are different one. So if you are<br>[11:46] traveling to Europe or maybe America or<br>[11:48] maybe other regions and then if you are<br>[11:50] connected to Inosour um community yeah u<br>[11:54] I I'd recommend that um you will join<br>[11:57] the Inosour gathering or maybe<br>[11:59] conference as well.
<!-- deep-read:sections end -->