对Copyleft开源许可证的普遍误解Common-AmazonAWS.PDFVIP

对 Copyleft 开源许可证的普遍误解 Common Misunderstanding of Copyleft 林誠夏 / Lucien Cheng-hsia Lin 開放文化基金會 法制顧問 / Legal Adviser, Open Culture Foundation /wiki/D-Link#GPL_violation /resources/2009/busybox-complaint-2009-12-14.pdf 2009年间发生在美国的BusyBox系列诉讼 BusyBox Lawsuits 2009 in the U.S. 协助开源许可证争议处理时的常见问题 Frequently proposed Questions in FOSS licenses disputes ● 我们真的有用到GPL的源代码吗 ？-Do we really have used the GPL licensed codes? ● 警告我们失权后续会怎么样 ？产品要下架吗 ？-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? 开源社区与产品制造商之间的思维差异 Different Thinking ways between FOSS community OEM / ODM ● 编程是艺术-Beautiful coding shall be art ● 及时上货-Time to market ● 知识产权可以共同拥有-IPR can be ● 以商业公司名义做知识产权处分-Do owned respectively the IPR management on its own ● 每一笔代码贡献应被尽量表彰-Every ● 额外的义务负担愈少愈好-No extra contribution of codes shall be attributed properly to obligations imposed will be appreciated an extend ● 提供源代碼不能与公司利益冲突-The ● 源代码应与其他参与者共享-Source source code provision shall not in conflict codes shall be provided “op