(Created page with "{{draft blog|~~~~~}} {{blog author|Chriswaterguy|Chris Watkins}} For Open Source Appropriate Technology, we strongly recommend either: * The CC-by-sa license (Creative ...") |
No edit summary |
||
| Line 4: | Line 4: | ||
For [[Open Source Appropriate Technology]], we strongly recommend either: | For [[Open Source Appropriate Technology]], we strongly recommend either: | ||
* The [[CC-by-sa]] license (Creative Commons Attribution ShareAlike) | * The [[CC-by-sa]] license (Creative Commons Attribution ShareAlike) | ||
or public domain. | or public domain. | ||
* I.e. explicitly relinquishing all copyrights. | |||
Note that saying "feel free to use this" does not have clear legal force - if you want to be part of the knowledge commons, choose one of these options.<ref>The less common [[CC-by]] license serves just as well - it lies between CC-by-sa and public domain, requiring attribution but not requiring derivative works to follow the same license.</ref> | |||
That's speaking on behalf of myself and the Appropedians I discuss this with, including [[User J.M.Pearce|Prof Joshua Pearce]] (see his paper...) | That's speaking on behalf of myself and the Appropedians I discuss this with, including [[User J.M.Pearce|Prof Joshua Pearce]] (see his paper...) | ||
[[User:Vinay Gupta|Vinay Gupta]] (creator of the [[Hexayurt Project]], which releases its work as public domain | [[User:Vinay Gupta|Vinay Gupta]] (creator of the [[Hexayurt Project]], which releases its work as public domain. | ||
Friends who share this philosophy of sharing include: | Friends who share this philosophy of sharing include: | ||
* [[Open Source Ecology]][http://opensourceecology.org/] | * [[Open Source Ecology]][http://opensourceecology.org/] | ||
* [[AIDG]][http://aidg.org/] - Appropriate Infrastructure Development Group. | * [[AIDG]][http://aidg.org/] - Appropriate Infrastructure Development Group. | ||
* [https://twitter.com/alanna_shaikh/ Alanna Shaikh]'s development blog, [http://bloodandmilk.org/ Blood and Milk], licensed as [[CC-by]].<ref> | * [https://twitter.com/alanna_shaikh/ Alanna Shaikh]'s development blog, [http://bloodandmilk.org/ ''Blood and Milk''], licensed as [[CC-by-sa]].<ref>[http://bloodandmilk.org/2001/04/10/occasionally-asked-questions/ License statement]</ref> ''Blood and Milk'' looks at what works and what doesn't in international development - i.e. the [[principles of development]]. That's important when looking at [[appropriate technology]] - which is about understanding [[context]] rather than simply applying technology. | ||
=== Why this matters === | === Why this matters === | ||
| Line 19: | Line 21: | ||
Please avoid using additional restrictions which reduce the free flow of knowledge - see | Please avoid using additional restrictions which reduce the free flow of knowledge - see | ||
Don't mix up "public domain" with "[[open access]]" - just because something can be accessed without restriction or cost doesn't make it public domain in the true sense. | |||
=== So what do I do? === | === So what do I do? === | ||
Revision as of 08:46, 20 March 2013
Template:Draft blog Template:Blog author
For Open Source Appropriate Technology, we strongly recommend either:
- The CC-by-sa license (Creative Commons Attribution ShareAlike)
or public domain.
- I.e. explicitly relinquishing all copyrights.
Note that saying "feel free to use this" does not have clear legal force - if you want to be part of the knowledge commons, choose one of these options.[1]
That's speaking on behalf of myself and the Appropedians I discuss this with, including Prof Joshua Pearce (see his paper...) Vinay Gupta (creator of the Hexayurt Project, which releases its work as public domain.
Friends who share this philosophy of sharing include:
- Open Source Ecology[1]
- AIDG[2] - Appropriate Infrastructure Development Group.
- Alanna Shaikh's development blog, Blood and Milk, licensed as CC-by-sa.[2] Blood and Milk looks at what works and what doesn't in international development - i.e. the principles of development. That's important when looking at appropriate technology - which is about understanding context rather than simply applying technology.
Why this matters
Watch out for...
Please avoid using additional restrictions which reduce the free flow of knowledge - see
Don't mix up "public domain" with "open access" - just because something can be accessed without restriction or cost doesn't make it public domain in the true sense.
So what do I do?
Declare
CCWiki howtos
Footnotes
- ↑ The less common CC-by license serves just as well - it lies between CC-by-sa and public domain, requiring attribution but not requiring derivative works to follow the same license.
- ↑ License statement