开源之道(2016 12 03)
Sat Dec 3, 2016 | 800 Words | 大约需要阅读 2 分钟 | |
声明:本博客言论,仅代表我自己,不管任何其它!
文章点评
所有的公司都是技术公司:看开源和 Inner Source 是如何改变IT领域的
原文链接:All companies Are Tech Companies:How Open Source and Inner Source are changing the IT Landscape
适兕点评:
毋需赘言,开源已经用实际行动证明其是如何成功的了。那么保守的企业该如何处理?该如何处理自身日渐臃肿的机构和无法满足的业务需求?成本巨高不下?
InnerSource 是个不错的解决之道,既然知识产权左顾右盼,不如暂时放下争执,先在内部实施开源的方法论和流程。用事实来证明现有的员工可以胜任日渐增长的需求变革。
本文最牛的一句话是:Capital One 认为自己是一家技术公司,不过恰好是在一家银行罢了!
亚马逊招募了一位开源的大拿
原文链接:Amazon Brings On a New Open Source Guru
适兕点评:
Zaheda Bhorat 一度在 Salesforce,Google工作过的开源战略官。AWS不久前还招募了Adrian cockroft。
正如文中所言,AWS也要在开源方面发力了,虽然AWS一直以来都是开源的最大受益者,比如其EC2服务使用的就是Xen虚拟化开源技术,其对社区的态度一直保持冷淡。直到AI服务落后。现在才开始发力了。
AWS 这个时候开始玩开源战略,一点也不晚!其实也就是争取更多的开发者,占领更高的高地,打时间差,赚取更多的利润。
如何处理好代码之外的社区
原文链接:How to care for the community over the code
适兕点评:
Joe Brockmeier 在 all things open 2016 的会上回答了一个问题:企业如何高效的社区一起工作。
我想我没有必要翻译,我列出来好的社区应该有那几条:
- Always remember that core community principles of transparency and openness are necessary.
- Mentors are key to showing people the ropes and helping new community members succeed. Nobody in a community is irreplaceable.
- Remember that all contributors matter. It’s a bummer when a community only acknowledges coding contributions. You need UX, design, documentation, marketing, and more to have a successful community.
- One size can’t fit all
- Have clear guidelines
- Have Contributor License Agreements (CLA) that avoid terms that make one entity “more equal than others”
- State how a user becomes a contributor
- State how a contributor becomes a core contributor or earns rights
- Follow the golden rule: Think of what behavior you’d want to see in a community and be that
- Emphasize diversity and inclusivity in both skills and people
基础设施那块,我就不再啰嗦了。