Editing
How to choose open source solution
(section)
Jump to navigation
Jump to search
Warning:
You are not logged in. Your IP address will be publicly visible if you make any edits. If you
log in
or
create an account
, your edits will be attributed to your username, along with other benefits.
Anti-spam check. Do
not
fill this in!
== 延伸閱讀 == Wizard of license * [https://choosealicense.com/appendix/ Appendix | Choose a License] * {{Gd}} Yi-Feng Tzeng (Ant) (2014). [http://blog.gcos.me/2014-11-03_how-to-choose-open-source-software-or-third-party-software.html 如何正確選擇自由/開放源碼軟體(或第三方軟體) | Ant's ATField] {{access | date=2015-02-21}} * Randy Metcalfe (2004). [http://oss-watch.ac.uk/resources/tips Top tips for selecting open source software] {{access | date=2016-08-04}} * [https://www.facebook.com/backtrue/posts/10203889235625414?pnref=story 邱煜庭] (2015). - 「#自己架設電子商務網站很常被忽略的潛在成本 很多人都覺得市面上很多電子商務官網服務,包含 [https://www.meepshop.com/ meeshop], [http://qdm.com.tw/ qdm], [http://91app.com/act/openshop/index.html 91app], [http://www.shoplineapp.com/?locale=zh-hant shopline] 收的錢很貴,都想自己架設會不會比較便宜?帳面上的數字看起來當然是比較便宜,但是你有想過自己架官網,'''有些費用你是否忽略了?這中間包含:1. 伺服器租用成本 2. 頻寬成本 3. 資料庫成本 4. 1到3 維護IT人力成本 5. 資安維護成本 6. 官網維護更新成本 7. app版本維護更新成本 8. 6到7 人力成本''' ... ...」([https://www.facebook.com/backtrue/posts/10203889235625414?pnref=story 全文]) {{access | date=2015-08-04}} * Marty Weiner (2015). [http://engineering.pinterest.com/post/116038532184/learn-to-stop-using-shiny-new-things-and-love Making Pinterest — Learn to stop using shiny new things and love...] 選擇任何技術方案之前,先問幾個問題 '''(1) Does the technology meet your needs? (2) How well does it scale? (3) Is the cost justified? (4) How mature is the technology?''' {{access | date=2015-04-13}} * Government Digital Service (2014). [https://www.gov.uk/service-manual/making-software/choosing-technology Choosing technology — Government Service Design Manual] {{access | date=2014-11-27}} 中文翻譯: [http://gds.hpx.tw/service-manual/making-software/choosing-technology/ 選擇技術(Choosing technology)] * 黃彥棻 (2014). [http://www.ithome.com.tw/people/92654 Muzik從實體跨入線上的關鍵 選對適用老技術避專利高風險 | iThome] {{access | date=2014-12-19}} * Papasign (2014). [http://blog.papasign.com/wordpress/2014/12/17/%E5%A6%82%E4%BD%95%E9%81%B8%E6%93%87erp%E4%B8%AD%E5%B0%8F%E4%BC%81%E6%A5%AD%E7%AF%87/ 中小企業如何選擇ERP] {{access | date=2015-02-19}} * [http://www.naipo.com/Portals/1/web_tw/Knowledge_Center/Infringement_Case/publish-96.htm 北美智權報 第110期:利用開放原始碼撰寫軟體應注意什麼事? - 以美國2008年Jacobsen v. Katzer案為例] 「任何利用網路上開放原始碼軟體所撰寫的程式,都需要注意,其所利用的開放原始碼,採取的是怎樣的授權條件。如果該授權條件要求後續使用者可自由修改、再散布,且不排除商業性利用,則使用者可以放心的利用他人的開放原始碼程式。但是需注意的是,開放原始碼程式通常要求對前者的貢獻給予肯定,亦即,必須在修改後的版本標示出原著作之作者、出處,並說明其修改之處。」 {{access | date=2015-06-19}} * 網路資訊雜誌 (2010). [http://news.networkmagazine.com.tw/classification/software-application/2010/08/08/20468/ IT程式開發平臺的選擇 開放原始碼vs.商業平臺] 「商業和開放原始碼平臺在IT程式開發上,各有其優缺點,商業平臺較方便,入門門檻低;而開放原始碼的花費較低且安全性較高,但發展比較不可預期,可說是各有優缺點,選擇時端看IT系統的用處和條件,以及一直以來開發的慣例來延續一致性。 ... ...」{{access | date=2015-08-09}} * 資安人科技網 (2015). [http://www.informationsecurity.com.tw/article/article_detail.aspx?aid=8212 (專訪)預防Open Source安全風險與侵權爭議] 「開放原始碼三大風險: 版權問題、資安漏洞、OpenSource使用廣泛,不易追蹤辨識... ...」{{access | date=2016-01-13}} * 林信良 (2017). [http://www.ithome.com.tw/voice/112994 多看一眼授權] {{access | date=2017-04-16}} * 林誠夏 (2017). [https://twoss.io/2017Tech.html 開源軟體法制授權與供應鏈協作] {{access | date=2017-08-05}} * data gravity https://twitter.com/kakashiliu/status/968843915997491200?s=19 * [https://blog.pulipuli.info/2023/01/how-to-evaluate-an-open-source-project.html 如何評估開放原始碼專案? / How to evaluate an Open Source Project? - 布丁布丁吃什麼?] * Louis Lin (2021). [https://lupopi.com/blog/wordpress 為什麼用 WordPress?] {{access | date=2023-07-06}} * [https://www.youtube.com/watch?v=f6Mo7W6YgWI 網頁開發人員如何意外使用到商用授權的開放原始碼套件 - YouTube] 選擇技術 * [https://boringtechnology.club/index_zh_TW.html 選擇無聊的技術] 評估開放原始碼 AI 專案 * [https://github.com/el09xccxy-stack/oss-investment-scorecard el09xccxy-stack/oss-investment-scorecard: A structured 5-dimension scoring framework for evaluating open-source AI projects from a VC investment perspective. Maintained by Lucy Chen, EIR at Zoo Capital (Singapore, $2B+ AUM).] ([https://www.facebook.com/lucy.chen.908347/posts/pfbid0knY8DTg8r8MHDpX4vntCZcPuKymThrJ4P48wkRMj7DFv1CCnMrbyCd9Q1JMaZ7eml 作者臉書]) Copyright compliance * [https://blog.gcos.me/tags/license/ License · Ant's ATField] * [https://www.facebook.com/photo.php?fbid=10213151937712465&set=a.2104140142503&type=3 #DevOps #Compliance #OpenSourceLicense 執行確實的... - Ant Yi-Feng Tzeng] "執行確實的 DevSecOps,除了 (Information) Security 外,還會有 Compliance 流程。這些涉及法遵相關的議題,包括法令及契約 (上下游或第三方) 等。 圖片引用 #招商銀行 在 DevSecOps 流程中納入 Black Duck Software 產品的流程,以遵守或避免開放/自由軟體授權契約的風險。" BSD, Apache, MIT > MPL > LGPL > GPL
Summary:
Please note that all contributions to LemonWiki共筆 are considered to be released under the Creative Commons Attribution-NonCommercial-ShareAlike (see
LemonWiki:Copyrights
for details). If you do not want your writing to be edited mercilessly and redistributed at will, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource.
Do not submit copyrighted work without permission!
Cancel
Editing help
(opens in new window)
Navigation menu
Personal tools
Not logged in
Talk
Contributions
Log in
Namespaces
Page
Discussion
English
Views
Read
Edit
View history
More
Search
Navigation
Main page
Current events
Recent changes
Random page
Help
Categories
Tools
What links here
Related changes
Special pages
Page information