Grow on GitHub Collaboration Culture: Case Study of InnerSource Challenge - GitHub Universe 2024 Recap in ZOZO

Slide 1

Slide 1 text

Grow on GitHub Collaboration Culture: Case Study of InnerSource Challenge 2024-12-16 GitHub Universe 2024 Recap in ZOZO NIFTY Corporation Ryo Ashikawa

Slide 2

Slide 2 text

Copyright © NIFTY Corporation All Rights Reserved. 2 Self-introduction NIFTY Corporation Engineering Manager Ryo Ashikawa InnerSource Commons Japan InnerSource Advocate 2010 2015 2020 2025 Scrum Master Engineering Manager Backend Engineer

Slide 3

Slide 3 text

Slide 4

Slide 4 text

Slide 5

Slide 5 text

Copyright © NIFTY Corporation All Rights Reserved. engineering organization 5 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

Slide 6

Slide 6 text

Copyright © NIFTY Corporation All Rights Reserved. GitHub Usage Status 6 ● organization is one. Anyone within the organization can view. ● copilot about 50, increasing in use every day Copilot Metrics Viewer

Slide 7

Slide 7 text

Slide 8

Slide 8 text

Copyright © NIFTY Corporation All Rights Reserved. Start of the 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

Slide 9

Slide 9 text

Copyright © NIFTY Corporation All Rights Reserved. Definition of InnerSource 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!

Slide 10

Slide 10 text

Slide 11

Slide 11 text

Copyright © NIFTY Corporation All Rights Reserved. 11 Let's decide 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

Slide 12

Slide 12 text

Slide 13

Slide 13 text

Slide 14

Slide 14 text

Copyright © NIFTY Corporation All Rights Reserved. Let's contribute to 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!

Slide 15

Slide 15 text

Copyright © NIFTY Corporation All Rights Reserved. Shortening lead time 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

Slide 16

Slide 16 text

Copyright © NIFTY Corporation All Rights Reserved. Shortening lead time 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)

Slide 17

Slide 17 text

Copyright © NIFTY Corporation All Rights Reserved. Can anyone contribute, 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!

Slide 18

Slide 18 text

Slide 19

Slide 19 text

Copyright © NIFTY Corporation All Rights Reserved. 19 Collaboration between 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!

Slide 20

Slide 20 text

Copyright © NIFTY Corporation All Rights Reserved. Contribution to the 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!

Slide 21

Slide 21 text

Copyright © NIFTY Corporation All Rights Reserved. It is sometimes 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

Slide 22

Slide 22 text

Copyright © NIFTY Corporation All Rights Reserved. 22 [PR] InnerSource 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

Slide 23

Slide 23 text

Copyright © NIFTY Corporation All Rights Reserved. Summary 23 Through 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!