inner source introduction
TRANSCRIPT
![Page 1: Inner source introduction](https://reader031.vdocuments.site/reader031/viewer/2022021918/58a5d21e1a28ab6c2a8b65bd/html5/thumbnails/1.jpg)
![Page 2: Inner source introduction](https://reader031.vdocuments.site/reader031/viewer/2022021918/58a5d21e1a28ab6c2a8b65bd/html5/thumbnails/2.jpg)
InnerSource如何在企业内部采用开源软件模式
![Page 3: Inner source introduction](https://reader031.vdocuments.site/reader031/viewer/2022021918/58a5d21e1a28ab6c2a8b65bd/html5/thumbnails/3.jpg)
About Me
n 现就职于UMCloud,任OpenStack技术顾问
n 开放云精选(社区)创始人
n 博客作者
n 技术作家,代表作《云落谁家?OpenStack架构指南》《开源虚拟化开
发指南》
n Linuxer、Pythonic、不入流的程序员
n 开源文化布道师,混迹于北京线下开源社区交流
n InfoQ中国开源专栏主编
![Page 4: Inner source introduction](https://reader031.vdocuments.site/reader031/viewer/2022021918/58a5d21e1a28ab6c2a8b65bd/html5/thumbnails/4.jpg)
议程
• 起因• 什么是Inner Source?• 谁在使用?效果如何?• 为什么要采用Inner Source?• 谁比较适合采用Inner Source?• 如何采用Inner Source?
![Page 5: Inner source introduction](https://reader031.vdocuments.site/reader031/viewer/2022021918/58a5d21e1a28ab6c2a8b65bd/html5/thumbnails/5.jpg)
默认开源的年代
![Page 6: Inner source introduction](https://reader031.vdocuments.site/reader031/viewer/2022021918/58a5d21e1a28ab6c2a8b65bd/html5/thumbnails/6.jpg)
Open-source is vibrant
![Page 7: Inner source introduction](https://reader031.vdocuments.site/reader031/viewer/2022021918/58a5d21e1a28ab6c2a8b65bd/html5/thumbnails/7.jpg)
开源用事实证明是成功的
沃尔玛、耐克、GE都在拥抱开源!
微软拥抱Linux,包括我们这次的会议。
![Page 8: Inner source introduction](https://reader031.vdocuments.site/reader031/viewer/2022021918/58a5d21e1a28ab6c2a8b65bd/html5/thumbnails/8.jpg)
没有理由不去学习和采纳
![Page 9: Inner source introduction](https://reader031.vdocuments.site/reader031/viewer/2022021918/58a5d21e1a28ab6c2a8b65bd/html5/thumbnails/9.jpg)
什么是Inner Source?
![Page 10: Inner source introduction](https://reader031.vdocuments.site/reader031/viewer/2022021918/58a5d21e1a28ab6c2a8b65bd/html5/thumbnails/10.jpg)
定义
• 可以理解为在公司这个大教堂内部使用集市的方式的开发模式
• 企业内部采用开源的实践来开发他们自己的软件
• 区别于:使用开源社区的软件做定制或二次开发,或者参与到开源社区的开发。(这是另外一个尚待挖掘的课题)
![Page 11: Inner source introduction](https://reader031.vdocuments.site/reader031/viewer/2022021918/58a5d21e1a28ab6c2a8b65bd/html5/thumbnails/11.jpg)
借用概念
![Page 12: Inner source introduction](https://reader031.vdocuments.site/reader031/viewer/2022021918/58a5d21e1a28ab6c2a8b65bd/html5/thumbnails/12.jpg)
打个比方(开源与Inner Source)
![Page 13: Inner source introduction](https://reader031.vdocuments.site/reader031/viewer/2022021918/58a5d21e1a28ab6c2a8b65bd/html5/thumbnails/13.jpg)
谁在使用?效果如何?
![Page 14: Inner source introduction](https://reader031.vdocuments.site/reader031/viewer/2022021918/58a5d21e1a28ab6c2a8b65bd/html5/thumbnails/14.jpg)
PayPal
•原因:清算团队得花2/3的时间去修改各个区域团队提交上来的代码
• Apache软件基金会的实践获得了灵感!
•效果:清算团队再也没有花时间去重写别人的代码了,而仅仅花了10%的时间去做审核代码的工作,工作效率提高了4倍。
![Page 15: Inner source introduction](https://reader031.vdocuments.site/reader031/viewer/2022021918/58a5d21e1a28ab6c2a8b65bd/html5/thumbnails/15.jpg)
沃尔玛
• JeremyKing 2011年从eBay跳槽到沃尔玛,开始推行InnerSource•研发团队一千多人,每个月作三万多次代码部署,分为100多个小组,每个小组有10-20人,开发、构建、测试和部署等全部由小组自行负责,以DevOps模式工作。
• Inner Source在小组之间可以共享、开发和贡献代码就非常重要!•企业版GitHub
•吸引了很多优秀的人才!
![Page 16: Inner source introduction](https://reader031.vdocuments.site/reader031/viewer/2022021918/58a5d21e1a28ab6c2a8b65bd/html5/thumbnails/16.jpg)
其它
• Google• IBM
• PhilipsHealthcare• Alcatel-Lucent• PhilipsResearch
![Page 17: Inner source introduction](https://reader031.vdocuments.site/reader031/viewer/2022021918/58a5d21e1a28ab6c2a8b65bd/html5/thumbnails/17.jpg)
为什么要采用Inner Source?
![Page 18: Inner source introduction](https://reader031.vdocuments.site/reader031/viewer/2022021918/58a5d21e1a28ab6c2a8b65bd/html5/thumbnails/18.jpg)
软件产品和组件的代码重用
![Page 19: Inner source introduction](https://reader031.vdocuments.site/reader031/viewer/2022021918/58a5d21e1a28ab6c2a8b65bd/html5/thumbnails/19.jpg)
改进代码质量Givenenougheyeballs, allbugsareshallow.-- Linus法则
![Page 20: Inner source introduction](https://reader031.vdocuments.site/reader031/viewer/2022021918/58a5d21e1a28ab6c2a8b65bd/html5/thumbnails/20.jpg)
开放式的创新
![Page 21: Inner source introduction](https://reader031.vdocuments.site/reader031/viewer/2022021918/58a5d21e1a28ab6c2a8b65bd/html5/thumbnails/21.jpg)
加速开发速度,减少上市时间
![Page 22: Inner source introduction](https://reader031.vdocuments.site/reader031/viewer/2022021918/58a5d21e1a28ab6c2a8b65bd/html5/thumbnails/22.jpg)
避免人才的单一化
![Page 23: Inner source introduction](https://reader031.vdocuments.site/reader031/viewer/2022021918/58a5d21e1a28ab6c2a8b65bd/html5/thumbnails/23.jpg)
谁比较适合采用Inner Source?
![Page 24: Inner source introduction](https://reader031.vdocuments.site/reader031/viewer/2022021918/58a5d21e1a28ab6c2a8b65bd/html5/thumbnails/24.jpg)
哪些企业
•跨地域的团队(这点在国内现在蛮高的,如逃离北上广)•部门多,涉及到的重用的组件、模块•大型团队,
•自顶向下瓶颈过于明显•重复、浪费严重•沟通困难
![Page 25: Inner source introduction](https://reader031.vdocuments.site/reader031/viewer/2022021918/58a5d21e1a28ab6c2a8b65bd/html5/thumbnails/25.jpg)
如何采用Inner Source?
![Page 26: Inner source introduction](https://reader031.vdocuments.site/reader031/viewer/2022021918/58a5d21e1a28ab6c2a8b65bd/html5/thumbnails/26.jpg)
•种子产品(基础设施)•模块化设计
• GitHub• Apache(邮件列表、IRC、分层的职责/晋升设计)
•文化转变:扁平、透明
![Page 27: Inner source introduction](https://reader031.vdocuments.site/reader031/viewer/2022021918/58a5d21e1a28ab6c2a8b65bd/html5/thumbnails/27.jpg)
方法论(Apache)
文化沟通透明协作社区精英
![Page 28: Inner source introduction](https://reader031.vdocuments.site/reader031/viewer/2022021918/58a5d21e1a28ab6c2a8b65bd/html5/thumbnails/28.jpg)
Thanks for yourListening!