「使用開源軟體製作產品、來自社群的常見訴求，以及OpenChain管理流程導入如何協助處理相關需求」。發表於「OpenChain 台灣社群聚會：首發工作坊」，採 CC0-1.0 公眾領域貢獻宣告釋出，相關著作權利已拋棄，後續使用者可以複製、修改、發布或展示此作品，亦可進行商業利用，完全不需要經過許可。 Slideshare上最寬鬆的授權僅能預選CC BY，故形式上選取CC BY，簡報內容註解其採 CC0 發布。

2. Common requirements on OSS compliance
from communities to Taiwan companies and
how OpenChain can help to that
Lucien Cheng-hsia Lin / 林誠夏
Open Culture Foundation, Legal Adviser / 開放文化基金會 法制顧問
Open Source Legal Network Taiwan, Co-founder / 台灣開源法律網絡，共同創辦人
Email: lucien.cc@gmail.com / lucien@ocf.tw
LinkedIn: https://tw.linkedin.com/in/lucienchlin
OpenChain Taiwan Work Group 1st Meeting / OpenChain 台灣社群聚會：首發工作坊
2020.09.18
本文件使用 SIL Open Font License v1.1 釋出之 Public Sans 及 思源黑體 字型，
前者由 USWDS 發布，後者由 Adobe 、 Google 及其他合作夥伴協同發布。
簡報內容未經特別標註者，皆採 CC0-1.0 公眾領域貢獻宣告 釋出，後續得不受著作權利限制被使用。

3. Common requirements (1)
I need the Source Codes of the Product that
shall be provided under GPL.
- 我需要您產品裡應該採 GPL 提供的程式源碼。

4. Common requirements (2)
Due to the non-compliance, the FOSS license
for your distribution has been voided, you have
to cease the delivery of the product.
- 因為沒有做到自由開源合規，原自由開源授權已
經終止，你不能再交付這個產品給客戶。

5. Common requirements (3)
Even if the related components are developed partially
on your own, still, you have to provide the Source Code
of that under the GPL as a derivative work of the
original ones.
- 即使相關元件部份是由您自行開發，然而它是 GPL 原元
件的改作，您還是要提供該元件的程式源碼！

6. Common requirements (4)
You seem keep all the FOSS info from the users to hide and
obfuscate the application, however the error signal and
help page shows opposite result, please clarify this issue.
- 您似乎將自由開源軟體相關資訊給隱藏或混淆了，但是程式
的錯誤訊息及內嵌的說明頁顯示它原來就是自由開源軟體，請
釐清！

7. Common requirements (5)
The Source Code you provided corresponded to
the FOSS components is less than enough,
please rectify this situation.
- 您依照自由開源元件提供的相應程式源碼並不充
足，請改正這個狀況。

8. Common requirements (6)
The FOSS component you used in the product is originally
developed by me, all the copyright notice and attribution to me
has been wrongly neglected, please rectify this situation.
- 您產品裡使用的自由開源元件是我初始開發的，但所有關於我的著
作權聲明及顯名聲明都被錯誤忽略了，請改正這個狀況。

9. Common requirements (7)
The product comes with GPL-licensed components, I
would like to do some modification based on the FOSS
part, please provide me the certification keys to bypass
the DRM.
產品裡有 GPL 授權元件，我想基於此做一些修改，請提供
我可以避過數位權利管理的認證金鑰。

10. Common requirements
1. FOSS List
2. Corresponding Source
3. Certification Key
4. Attribution

11. https://www.change.org/p/htc-htc-needs-timely-kernel-source-releases

12. Why you should pay
attention to OpenChain?

13. https://www.iso.org/standard/81039.html

14. Why you really need to pay
attention to OpenChain?

15. I have a phone, I have a bubble tea.
"File: Nokia 3310.png" by bijutoha is licensed under CC-CC0 1.0. To view a copy of this license, visitНовый
https://creativecommons.org/licenses/cc0/1.0/.
"BiCCA 19" by spongebabyalwaysfull is marked under CC0 1.0. To view the terms, visit
https://creativecommons.org/licenses/cc0/1.0/

16. I have a phone, I have a bubble tea, uh!
Broken Phone!!!

17. Face the Music
1. FOSS List
2. Corresponding Source
3. Certification Key
4. Attribution

18. https://github.com/OpenChain-Project/Specification-Translations/tree/master/zh-Hant/2.0

19. https://github.com/OpenChain-Project/Specification-Translations/tree/master/zh-Hant/2.0

20. The crucial 6 points of OpenChain management
進行 OpenChain 開源合規的 6 大要點
1. Policy 政策書
2. Contacting Window / Liaison 協調窗口
3. Work Flow to Produce the FOSS List 產出自由開源清單的流程
4. Work Flow to Verify the FOSS List 驗證自由開源清單的流程
5. Code of Community Participation 社群參與規範
6. Updating All the Crucial Points 定期更新各項要點

21. What OpenChain can help
1. FOSS List
2. Corresponding Source
3. Certification Key
4. Attribution

22. What OpenChain can help
1. FOSS List √
2. Corresponding Source
3. Certification Key
4. Attribution

23. What OpenChain can help
1. FOSS List
2. Corresponding Source √
3. Certification Key
4. Attribution

24. What OpenChain can help
1. FOSS List
2. Corresponding Source
3. Certification Key √ (contacting window)
4. Attribution

25. What OpenChain can help
1. FOSS List
2. Corresponding Source
3. Certification Key
4. Attribution √

26. What OpenChain can help to TW ICT
1. Fairly sharing the responsibilities 權責相配
2. Fundamental Work Flow for FOSS Compliance 流程可循
3. Dances with Wolves 社群互動
4. Switching from Follower to Lead 化守為攻

27. OSLN.TW 專案頁面： https://ocf.tw/p/osln/

28. OpenChain 過往教學簡報及錄影之鏈結頁面：
https://ocf.tw/p/osln/

29. 本簡報發布及引用狀態聲明
除另有聲明，簡報採 CC0-1.0 公眾領域貢獻宣告 拋棄所有著作權利。
原作者將其著作結合 CC0-1.0 公眾領域貢獻宣告 進行發布時，代表在法律許可的範圍內，
拋棄該著作依著作權法所享有之權利，包括所有相關與鄰接的法律權利，並宣告將該著作
貢獻至公眾領域。後續使用者可以複製、修改、發布或展示此作品，亦可進行商業利用，
完全不需要經過許可。
簡報中所取用的部份截圖乃截頁自原作，僅具介紹導引性質，並不生經濟價值之任何取代
效應，原作者於演講時主張合理使用，後續使用者若要續行發布或加值利用，亦必須自忖
本身亦符合合理使用之各類情狀，並自負相關法律責任。

30. THANK YOU
Lucien Cheng-Hsia Lin 林誠夏
E-mail: lucien.cc@gmail.com / lucien@ocf.tw
LinkedIn: https://tw.linkedin.com/in/lucienchlin