Difference between revisions of "Team:Cambridge-JIC/Practices"

Line 173: Line 173:
 
                 });
 
                 });
 
                 step3c = new q.step("Your product could be released with no license. This gives you no control over its use, modification and commercialisation.", {
 
                 step3c = new q.step("Your product could be released with no license. This gives you no control over its use, modification and commercialisation.", {
 +
                    1: "OK"
 +
                });
 +
                step4a = new q.step("Your product is not open source, and should not be labeled as such. This route gives you the option to sell access to your code, designs and hardware.", {
 +
                    1: "OK"
 +
                });
 +
                step4b = new q.step("A Copyleft license is most appropriate for your product. All derivative products must be under the same license.", {
 +
                    1: "OK"
 +
                });
 +
                step4c = new q.step("A Permissive license is most appropriate for your product. Derivative products can be under different licenses.", {
 +
                    1: "OK"
 +
                });
 +
                step5a = new q.step("Options for Permissive licenses include the BSD, MIT and CC Attribution licenses.", {
 +
                    1: "Learn More"
 +
                });
 +
                step5b = new q.step("Do you want to license your hardware separately from the design files and code?", {
 +
                    0: "no",
 +
                    1: "yes"
 +
                });
 +
                step6a = new q.step("A TAPR OHL is most appropriate for your product. The software can be licensed under a FOSS license e.g. GPL.", {
 +
                    1: "Learn More"
 +
                });
 +
                step6b = new q.step("A CERN OHL is most appropriate for your product.", {
 +
                    1: "Learn More"
 
                 });
 
                 });
  
Line 179: Line 202:
 
                 step2a.bind(step3a, [1]);
 
                 step2a.bind(step3a, [1]);
 
                 step2b.bind(step3c, [0]);
 
                 step2b.bind(step3c, [0]);
−
                  
+
                 step2b.bind(step3b, [1]);
−
 
+
                step3a.bind(step4a, [1]);
 +
                step3b.bind(step4b, [1]);
 +
                step3b.bind(step4c, [0]);
 +
                step4b.bind(step5b, [1]);               
 +
                step4c.bind(step5a, [1]);
 +
                step5b.bind(step6a, [1]);
 +
                step5b.bind(step6b, [0]);
 +
 
                 q.start(step1);
 
                 q.start(step1);
 
             });
 
             });

Revision as of 10:31, 8 September 2015

CAMBRIDGE-JIC

Human Practices: The Open Hardware Revolution

In choosing the novel Hardware Track, this years’ Cambridge-JIC iGEM team has come across unexpected challenges. Unsurprisingly perhaps, these have often required us to look into fields of work that we have had little or no previous experience in. This has been particularly true when navigating the world of intellectual property law, including hardware licensing and design copyright. In developing Open Source Hardware (OSH) as part of the competition, we recognised the need for an easily-digestible, comprehensive and hardware-specific guide to ensuring the OSH is accessible to the community.

Open source hardware is hardware whose design is made publicly available so that anyone can study, modify, distribute, make, and sell the design or hardware based on that design.

OSH is “free as in free speech, not free beer” or more formally Libre rather than Gratis.

Hardware Licensing

Design Copyright