About Open Collaboration: Difference between revisions
No edit summary |
No edit summary |
||
Line 1: | Line 1: | ||
OSE is interested in partnering and working with various startups, entrepreneurs, institutes, nonprofits, and other organizations - as long as the development is placed under an open license congruent with the [[Open Source Hardware Definition]]. OSE uses [[CC-BY-SA 4.0]] for its designs, [[Public Domain]] (CC0) for its writings, and [[GPL 3.0]] as its software license. | OSE is interested in partnering and working with various startups, entrepreneurs, institutes, nonprofits, and other organizations - as long as the development is placed under an open license congruent with the [[Open Source Hardware Definition]]. Further, it is also useful if [[Best Practices for Open Source Hardware]] are followed | ||
OSE uses [[CC-BY-SA 4.0]] for its designs, [[Public Domain]] (CC0) for its writings, and [[GPL 3.0]] as its software license. | |||
If you are interested in working together and if you are inquiring about a joint project or collaboration, the license for your work must be open source and must be clear and expressed publicly on your website or information packet. | If you are interested in working together and if you are inquiring about a joint project or collaboration, the license for your work must be open source and must be clear and expressed publicly on your website or information packet. |
Revision as of 21:44, 25 September 2015
OSE is interested in partnering and working with various startups, entrepreneurs, institutes, nonprofits, and other organizations - as long as the development is placed under an open license congruent with the Open Source Hardware Definition. Further, it is also useful if Best Practices for Open Source Hardware are followed
OSE uses CC-BY-SA 4.0 for its designs, Public Domain (CC0) for its writings, and GPL 3.0 as its software license.
If you are interested in working together and if you are inquiring about a joint project or collaboration, the license for your work must be open source and must be clear and expressed publicly on your website or information packet.
OSE receives frequent requests for collaboration, so we are clear about the open source nature of our work up front. This is because we have seen a number of dead ends occur with potential collaborators as a result of license incompatibility. Unless assurance of license compatibility is present and clear up front, license incompatibility is a risk that OSE is not willing to take