"Session ID: HKG18-400K2 Session Name: HKG18-400K2 - Keynote: Shane Coughlan with guest speaker Lucien Cheng-hsia Lin- Complex Made Simple: The State of Governance in Open Source Speaker: Shane Coughlan Track: Keynote ★ Session Summary ★ Clear governance, a shared understanding of process and rules, is key to the success of open source adoption at scale. Our global community represents many perspectives, many cultures and many jurisdictions. To address these we have seen the emergence of overarching principles, practical guides and effective tools that support the necessary balance of flexibility and shared trust. This talk will focus in the key open source solutions that address real world challenges. It will highlight a stack of solutions that includes OpenChain, SPDX, Reuse.Software, FOSSology, ScanCode, sw360 and QuarterMaster and explain how they work together from meta level (e.g OpenChain standard) to practical process implementation (e.g QuarterMaster CI/CD). For the last 10 minutes of Shane's keynote, Lucien Cheng-hsia Lin will discuss License Compliance in Asia. --------------------------------------------------- ★ Resources ★ Event Page: http://connect.linaro.org/resource/hkg18/hkg18-400k2/ Presentation: http://connect.linaro.org.s3.amazonaws.com/hkg18/presentations/hkg18-400k2.pdf Video: http://connect.linaro.org.s3.amazonaws.com/hkg18/videos/hkg18-400k2.mp4 --------------------------------------------------- ★ Event Details ★ Linaro Connect Hong Kong 2018 (HKG18) 19-23 March 2018 Regal Airport Hotel Hong Kong --------------------------------------------------- Keyword: Keynote 'http://www.linaro.org' 'http://connect.linaro.org' --------------------------------------------------- Follow us on Social Media https://www.facebook.com/LinaroOrg https://www.youtube.com/user/linaroorg?sub_confirmation=1 https://www.linkedin.com/company/1026961"

1. Complex Made Simple: The State of
Governance in Open Source
Shane Coughlan
OpenChain Project Director

2. The fabric of computing

3. Shared rules, shared results

4. The challenges today

5. The solutions today

6. www.openchainproject.org

7. “How do I trust my open source supply chain?”

8. Training
Policy
Process
Inbound Outbound

9. The future

10. Update on license compliance in Asia
Lucien Cheng-hsia Lin / 林誠夏
Legal Adviser, Open Culture Foundation / 開放文化基金會 法制顧問

11. https://en.wikipedia.org/wiki/D-Link#GPL_violation

12. Frequently proposed Questions in FOSS licenses disputes
协助开源许可证争议处理时的常见问题
● Do we really have used the GPL licensed codes?-我们真的有用到GPL的源代码吗？
● What does reinstatement mean? If we’re not allowed to be reinstated, shall all the
products be ceased to deliver?-警告我们失权后续会怎么样？产品要下架吗？
● Why we have to provide the source code being written on our own?-为什么自己写的部份也要开
放源代碼？
● How can the products be obfuscated so that no one will know there is GPL licensed
materials?-如果让对方查验不到我们有用开源软件？
● Our own source code has been lost because of the engineer in charge has already left,
what can we do with this situation for the warning letter?-源代码已经遗失或原程序员已经离职拿不
出来怎么办？
● What exactly is the scope of source code we shall provide?-源代码要给到什么范围？
● How can we properly attribute all the copyright notice and disclaimer with so many
FOSS components in one product?-用到的开源组件甚多，著作权标示和免责声明要怎么标？

13. http://www.softwarefreedom.org/resources/2009/busybox-complaint-2009-12-14.pdf

14. BusyBox Lawsuits 2009 in the U.S.
2009年间发生在美国的BusyBox系列诉讼

15. Frequently proposed Questions in FOSS licenses disputes
协助开源许可证争议处理时的常见问题
● Do we really have used the GPL licensed codes?-我们真的有用到GPL的源代码吗？
● What does reinstatement mean? If we’re not allowed to be reinstated, shall all the
products be ceased to deliver?-警告我们失权后续会怎么样？产品要下架吗？
● Why we have to provide the source code being written on our own?-为什么自己写的部份也要开
放源代碼？
● How can the products be obfuscated so that no one will know there is GPL licensed
materials?-如果让对方查验不到我们有用开源软件？
● Our own source code has been lost because of the engineer in charge has already left,
what can we do with this situation for the warning letter?-源代码已经遗失或原程序员已经离职拿不
出来怎么办？
● What exactly is the scope of source code we shall provide?-源代码要给到什么范围？
● How can we properly attribute all the copyright notice and disclaimer with so many
FOSS components in one product?-用到的开源组件甚多，著作权标示和免责声明要怎么标？

16. Different Thinking ways between FOSS community & OEM / ODM
开源社区与产品制造商之间的思维差异
● Beautiful coding shall be art-编程是艺
术
● IPR can be owned respectively-知识
产权可以共同拥有
● Every contribution of codes shall
be attributed properly to an extend-
每一笔代码贡献应被尽量表彰
● Source codes shall be provided
“openly” among participants-源代码应
与其他参与者共享
● Share the knowledge-分享知识
● Time to market-及时上货
● Do the IPR management on its
own-以商业公司名义做知识产权处分
● No extra obligations imposed will
be appreciated-额外的义务负担愈少愈好
● The source code provision shall
not in conflict with the company’s
benefits-提供源代碼不能与公司利益冲突
● Keep the know-how-保有专门技术

17. "Peace", shared by "SUBJECTIF ART" at https://flic.kr/p/QdaWkR under CC0-1.0.

18. Learn Copyleft spirit in training courses for the better judgement
透过训练课程理解Copyleft精神以利未来做较佳判断
● Copyleft = Share-alike = 相同方式分享
1. Try to deal with the issue before it starts based on the FOSS licenses-回归许可证本
身来预先解决问题
2. What kind of source code will be appreciated among communities?-提供哪种程度的
源代码是被社区欣赏的？
3. Why we should cause the modified file to carry prominent notice stating that it
has been changed?-为什么更动了源代码文档必须要做纪录？
4. Why we have to provide FOSS LICENSE TEXT in full both in binary form and
source form distribution-为何散布项目必须要夹附开源许可证全文？
5. Which method of attribution of legal statement shall be accepted among
communities?-哪一种型态的法律声明是受社区接受的？
6. Why we can not find the sublicense mechanism in source form among most of
the Copyleft licenses-为什么Copyleft型态不容许转发许可证？

19. Thank You
#HKG18
HKG18 keynotes and videos on: connect.linaro.org
For further information: www.linaro.org