WEB Stream Aligned WEB WEB WEB ISP ISP ISP ISP Enabling SRE Cloud Strategy Security Complex Subsystem ISP Network Platform Member Management Billing and Invoicing Data Foundation Internal Information ISP Approximately 160 Engineers
InnerSource 8 Back in 2022. As an engineering manager, I was troubled by the issue of resource efficiency. Is there a way to use more internal resources without relying on external ones? Is there a method to reduce lead time even if we focus development on a specific team? It was a shocking encounter!! There is such a thing as ' InnerSource' in this world!! I want to do it! I want to introduce it to the organization! https://codezine.jp/article/detail/14809
9 InnerSource is the use of open source software development best practices and the establishment of an open source-like culture within organizations for the development of its non-open-source and/or proprietary software. Write CONTRIBUTING.md!
on a 1- person advocate Let's create some in-house achievements with something simple Call other EMs and include it in the business plan to involve them Let's get the word out first among all the LT engineers Let's clarify the evaluation criteria for contributors Let's clarify the labor accounting for contributors Let's give shy engineers the experience of external speaking engagements Let's inform the company internally and foster a sense of commitment I want to let the members experience the joy of connecting with people Good job, it has spread throughout the company. Let's commit to engaging in external activities within our work Create a cross- departmental promoter group Continue to include in the business plan and be aware of the promotional activities themselves Integrate into the promoter's plan Evaluate the promoter The journey of NIFTY’s InnerSource
the convenient tool together! 14 There is an environment where engineers can easily create tools and also easily spread the tools they create within the company. Such tools are very effective for InnerSource. Just like OSS, it's easy to generate contributions!
for API user-defined files 15 Branching, fixing, and integrating into the development environment. It may take a few days to a week, and I apologize for the delay... People who want to use the API (other teams) API Administrator Applied for use via Slack workflow. Checked. Please deploy. Create PR internally Deployed. Review & Merge Added and confirmed the functionality in the development environment, please. BEFORE
for API user-defined files 16 API Administrator We have confirmed it. Please deploy. Deployed. Review & Merge AFTER - Much faster No lead time Communication costs are half as much. Running a workflow with branch selection for deployment in GitHub Actions Creating a Pull Request Create a branch and check the development environment People who want to use the API (other teams)
even if not an engineer!? 17 •Revise the email text, have the business department directly create PRs on the browser •Feel the acceleration of corrections PR to merge is completed on the GitHub GUI. The InnerSource is no longer just for engineers!
stream-aligned teams with different domain knowledge Realized after trying again. The left figure works well, but it doesn't work if the direction is different... In a situation where "there is no motivation to contribute in the first place" and "the teams are not collaborative with each other," contribution is unlikely to occur. InnerSource is not a solution to everything. Perform effectively in the right place!
document 20 ? I want to, but how do I do it!? How do I design the xls document!? And even more, I want to target the entire company's documents! I feel the possibility, but I am struggling with the actual approach!
said like a silver bullet 21 “I want to develop a new product, but there aren’t enough people, can’t we gather from each team and do it internally? “ No, I don't think that's a good idea. InnerSource are about established contribution methods, and we also do not recommend being bound by schedules. (Is there one?) “Even if there are tools that my team doesn't understand and wants to get rid of, can't we figure something out?” No, it's impossible. InnerSource require repository managers (trusted committers). First, let's clarify the responsibility. Manage responsibly while making the black box clear. Or, consider throwing it away. There are times when understanding has not permeated enough
Commons Community Introduce best practices for OSS contribution into in-house sources! Slack is available. Feel free to join! There is also a Japanese channel!!: #jp-general
the GitHub platform, introduce the mechanism of 'InnerSource', and if there are people heading in the same direction, cultivate a collaboration culture within the organization with the backing of the organization! This is how the collaboration culture grew on GitHub!! Mutually beneficial! Same domain area! Minimize lead times for each other!
niftycorp
philipschwarz
daisukeshinoku
blueswen
oekazuma
xuwei_k
sgash708
xosofox
karugamo
kotamanegi
ssssota
orgachem
ivargrimstad
addyosmani
aki_iinuma
colly
sugarenia
phodgson
stephaniewalter
keavy
jmmastey
lauravandoore
mza
productmarketing
kevinliebholz
![Copyright © NIFTY Corporation All Rights Reserved. 22 [PR] InnerSource](https://files.speakerdeck.com/presentations/982373e1e33c4469bb61cc596577e2aa/slide_21.jpg){kind=link}
