We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
撰寫 g0v 建議的授權方式,以及若採用其他授權需注意的事項
問題:
選擇其他授權方式需注意事項:
The text was updated successfully, but these errors were encountered:
如果要 decentralize,「跟誰聯絡」指的只是窗口、負責轉接給個專案對嗎? 不然各專案各自有人、也應各負責任處理,似乎無法代理決議是否接受。 (除非已經先說好大家就是把權利交由某人代理那類)
Po-chiang Chao Mozillian, Creative Commoner, UX Ninja
On 2013年8月9日Friday at 下午3:00, Chia-liang Kao wrote:
撰寫 g0v 建議的授權方式,以及若採用其他授權需注意的事項 mockup/wireframe: CC0 code: mit http://g0v.mit-license.org/ 文件、網頁成果: CC-BY 問題: 若 CC-BY 成果被引用而未註明,採取的行動是? 選擇其他授權方式需注意事項: 若採 CC-BY-NC, 那需要 commercial usage 的人要和誰聯絡?接受的原則是? — Reply to this email directly or view it on GitHub (#18).
撰寫 g0v 建議的授權方式,以及若採用其他授權需注意的事項 mockup/wireframe: CC0 code: mit http://g0v.mit-license.org/ 文件、網頁成果: CC-BY
問題: 若 CC-BY 成果被引用而未註明,採取的行動是?
選擇其他授權方式需注意事項: 若採 CC-BY-NC, 那需要 commercial usage 的人要和誰聯絡?接受的原則是?
— Reply to this email directly or view it on GitHub (#18).
Sorry, something went wrong.
是的,那就需要另外的一些 boilerplate 說明要和誰聯絡,然後可能就不能用 g0v contributors 當做 owner
richardllin
No branches or pull requests
撰寫 g0v 建議的授權方式,以及若採用其他授權需注意的事項
問題:
選擇其他授權方式需注意事項:
The text was updated successfully, but these errors were encountered: