InnerSource の事例

“We’re moving towards more openness, which ultimately creates a communication culture and a generative culture, rather than one that’s bureaucratic and process-based.”

“InnerSource paves the way for ADEO to introduce new open source projects and give developers more freedom.”

“If we give people the right tools and the right platform, it’s a start. We can share more within our company and with each other, growing as an InnerSource organization.”

“InnerSource has allowed us to deliver dozens of cross-cutting features more efficiently, spanning multiple teams and services.”

“Our tools have been built been built from the ground up with an expectation of InnerSource … The way that we encourage that in a very disparate organization is mostly word of mouth and clear documentation.”

“Thanks to an InnerSource strategy we are scaling the reusability of Data Science code in a wide range of countries and business areas at BBVA. To achieve this, we developed a Python library, named Mercury.”

“InnerSource is not new to Bloomberg … our competitive advantage is really in being able to innovate, come up with new ideas and get them out to our specialized consumers on a regular basis at the speed that they require it to be competitive in the market.”

“InnerSource has proven invaluable for us. It has become the gold standard for internal collaboration on software at Bosch.”

“Our InnerSource journey started small and then started to grow to an enterprise scale.”

“InnerSource has absolutely made our developers stronger.”

“InnerSource helped us create a community inside the company... InnerSource is truly a cultural transformation.”

“With InnerSource, we want to enable all developers with the freedom to be creative, to drive innovation without barriers, and to be appreciated for their contributions across the company.”

“static/images/logos/deloitte.png”

“What we're seeing now is the technology has caught up with all these ideas of innovation and collaboration, and that's really critical for us.”

“Everyone should be able to read the code that powers etsy.com and contribute to the broader success of the company.”

“Our environment allows developers to find solutions that have already been developed. They can collaborate on those, and then reuse them.”

“The reason why InnerSource works is because like open source you're working with people who are collaborating with different priorities because they're working on different things”

“We need to build a community around the InnerSource projects of people who share the same ideals.”

“We see InnerSource as a way to improve efficiency through code reuse. But even beyond that, it's an amazing conduit for learning and exchanging ideas and facilitating innovation within IBM.”

“We have seen greater engineering satisfaction among teams that practice InnerSource... we have [also] seen better product quality and responses because of InnerSource.”

“We knew (with InnerSource) were going to save money, but that savings immediately turned into more capacity for teams to do the most valuable work for our business.”

“We found it very useful to work within the InnerSource Commons.. Where you can bounce ideas off of other InnerSource practitioners”

“We try to standardize our code style, our languages so that everybody can contribute to repositories. It’s really good for me making a change on a project, a service skeleton, or a common library to know that everybody’s going to use that to deploy their service.”

“The Process of InnerSource is actually the mindset of Collaboration.”

“We work together as a team to provide InnerSource methodology to encourage new people to initiate new projects... 70% of SAP employees would like to contribute if suitable projects are available.”

“Pull requests are welcome. Someone out there might find a better solution than I can.”

“This internal community removes friction as we build software while making all of our projects more open and social.”

“[Tencent] adopted InnerSource to promote engineer culture inside the company... 80% of projects get InnerSourced.”

“Our development teams have benefited from the collaborative features of GitHub. It allows them to take co-development to a whole new level by working as a community and maturing our InnerSourcing practices.”

“Anyone can learn something from another team and quickly see what’s in the code..Having a fairly open structure allows people to get involved quite easily and quickly.”

“We have an InnerSource policy: Everybody has access to create pull requests on all repositories. You can see all our code. We don’t lock down anything.”

“Twilio engineers are encouraged to submit pull requests to projects that are not immediately owned by their team. They can then work with the owning team on integrating their change into the code base.”

“A project isn’t just about the code, there’s a team behind it, including writers, designers and project managers. [InnerSource] gives you the opportunity to collaborate across multiple time zones and business units.”

“Once you embrace it [InnerSource] and see new teams come on, you show examples of places where not only can people contribute, you unlock bottlenecks”

“Suddenly developers are buttoning up the structure of their code—open source and InnerSource act as a forcing function to get the details right and ready for more eyes.”

“We have thousands of developers working on these projects today and at any given time we’re doing dozens of different projects... 75% of our clients with large global enterprises are trying InnerSource in some way, shape or form.”

“Our engineering culture is open and centred around teams owning services and being responsible for running them in production.”