Week 19:

Invention, Intellectual Property & Income

Table of Content

  1. Context & the necessity for dissemination
  2. Instructables
  3. Patents & Licencing
  4. Choosing a Licence
  5. The License I ended up choosing & My Plan for Dissemination
  6. Draft Presentation & Video Links.

Assignment

  1. Develop a plan for dissemination of your final project
  2. Prepare drafts of your summary slide (presentation.png, 1920x1080) and video clip (presentation.mp4, 1080p HTML5, < ~minute, < ~10 MB) and put them in your root directory

Context & the necessity for dissemination:

Due to various circumstances, I had to drop out of college back in 2013. Ever since then, I have been a self taught man. Almost everything I learnt, I learnt through the internet. It is for amazing people around the world, who love to share and spread what they do, I have been able to come so far. I plan to do the same for all my work here and eventually plan to write instructables on all the topics I have learnt at Fab Academy.

Instructables:

Instructables is probably one of the best things about the internet. Plenty of similar websites have come and gone but I have been a keen learner from instructables since its earliest days. The best part about it is the simplicity and the responsive community. When I started out, I didn't know what capacitors or resistors were or how to read and decipher a circuit schematic. But instructables and the lively community there was helpful enough to explain these to a simpleton like me.

The vision of instructables is kinda like this, everything can be made if you follow a recipe. Well techically, everything should be doable if there is a good enough recipe to do it. If documentation can be made simple enough, anyone can follow through inspite of their level of skill and learn along the way. I believe fab academy runs on a similar principle. But an advantage an instructable article has over a fab academy weekly documentation is that it is a recipe for a particular thing, where a fab academy weekly documentation becomes far too obscure with all the details put into it.

Another good feature about instructables is their contests. There are always multiple contests running on various topics in instructables, ranging from cooking, sewing to making lunar rovers. I hope to publish my final project, PixelFace in such a contest. I was always awestruck at the contest entries and the winners from instructables, I hope publish my own entry once I have all the documentation done in a simpler toned down way.

I plan to publish my Final Project on instructables as a contest entry whenever a fitting contest comes up.

Patents & Licencing

As the title says another one of this week’s aim is to learn about protecting your idea and how to avoid people misusing your idea/product for their personal gain. There are many types of patents for the same. The aim was to learn about them and chooses which one is right for us. As I am planning to publsh my work online, I had to go through documentations from last year to find a fitting license for my work. Although I can't enforce a license on an instructables content, I hope to host the content on a github repository, where I will mention the license I end up choosing.

What is a patent?

A patent is a form of intellectual property that gives its owner the legal right to exclude others from making, using, selling, and importing an invention for a limited period of years, in exchange for publishing an enabling public disclosure of the invention.

Advantages of Licencing

Not all inventors want to make or sell products or designs. Patent licensing lets you profit from the rights to your invention. You can collect royalties from sales.

    '
  • Limited Risk
  • Global Distribution
  • Limited Time Period
  • Eliminating Patent Infringement

Disadvantages of Patent Licensing

  • Soliciting Manufacturers
  • Low Success Rate

Types of Licensing

These are some of the types of open source licenses.
  • Creative Commons license :

    A Creative Commons (CC) license is one of several public copyright licenses that enable the free distribution of an otherwise copyrighted work. A CC license is used when an author wants to give people the right to share, use, and build upon a work that they have created. CC provides an author flexibility (for example, they might choose to allow only non-commercial uses of their own work) and protects the people who use or redistribute an author’s work from concerns of copyright infringement as long as they abide by the conditions that are specified in the license by which the author distributes the work.
  • MIT License :

    The MIT License is a permissive free software license originating at the Massachusetts Institute of Technology (MIT). As a permissive license, it puts only very limited restriction on reuse and has, therefore, an excellent license compatibility. The MIT license permits reuse within proprietary software provided that all copies of the licensed software include a copy of the MIT License terms and the copyright notice. The MIT license is also compatible with many copyleft licenses, such as the GNU General Public License (GPL); MIT licensed software can be integrated into GPL software, but not the other way around
  • GNU General Public License :

    The GNU General Public License (GNU GPL or GPL) is a widely used free software license, which guarantees end users the freedom to run, study, share and modify the software. The license was originally written by Richard Stallman of the Free Software Foundation (FSF) for the GNU Project, and grants the recipients of a computer program the rights of the Free Software Definition. The GPL is a copyleft license, which means that derivative work can only be distributed under the same license terms. This is in distinction to permissive free software licenses, of which the BSD licenses and the MIT License are widely used examples. GPL was the first copyleft license for general use.
  • GNU Lesser General Public License :

    The GNU Lesser General Public License (LGPL) is a free software license published by the Free Software Foundation (FSF). The license allows developers and companies to use and integrate software released under the LGPL into their own (even proprietary) software without being required by the terms of a strong copyleft license to release the source code of their own components. The license only requires software under the LGPL be modifiable by end users via source code availability. For proprietary software, code under the LGPL is usually used in the form of a shared library, so that there is a clear separation between the proprietary and LGPL components. The LGPL is primarily used for software libraries, although it is also used by some stand-alone applications.
  • BSD licenses :

    BSD licenses are a family of permissive free software licenses, imposing minimal restrictions on the use and redistribution of covered software. This is in contrast to copyleft licenses, which have reciprocity share-alike requirements. The original BSD license was used for its namesake, the Berkeley Software Distribution (BSD), a Unix-like operating system. The original version has since been revised and its descendants are more properly termed modified BSD licenses. The BSD license is a simple license that merely requires that all code be licensed under the BSD license if redistributed in source code format.
  • Apache licenses :

    The Apache License is a permissive free software license written by the Apache Software Foundation (ASF).The Apache License, Version 2.0 requires preservation of the copyright notice and disclaimer. Like other free software licenses, the license allows the user of the software the freedom to use the software for any purpose, to distribute it, to modify it, and to distribute modified versions of the software, under the terms of the license, without concern for royalties. This makes ALv2 a FRAND-RF license. The ASF and its projects release the software they produce under the Apache License and many non-ASF projects are also using the ALv2.

Choosing a Licence

After exmining everything, I decided to go with the creative commons licensing. I would like to share my work with people while I atleast get credit for it. My dissemination plan for my project is to publish an instructable on it while I plan to improve the design a bit more.

Types of CC Licenses

There are 6 main CC licenses to choose from:
  • Attribution license :

    OER licensed CC-BY can be modified, used commercially, and may or may not be shared in the same manner, provided credit is given to the author.
  • Attribution-Non-Commercial license :

    OER licensed CC-BY-NC can be modified and may or may not be shared in the same manner, but credit must be given to the author and it cannot be used commercially.
  • Attribution-Non-Commercial-Share Alike license :

    OER licensed CC-BY-NC-SA can be modified, but credit must be given to the author. Additionally, it may not be used commercially and must be shared in the same manner.
  • Attribution-Non-Commerical-No Derivatives :

    Materials licensed CC-BY-NC-ND cannot be modified or used commercially. It may or may not be shared in the same manner and credit must be given to the author. Materials that possess a No Derivatives license are not considered to be OER.
  • Attribution-No Derivatives license :

    Materials licensed CC-BY-ND may or may not be shared in the same manner, can be used commercially, but credit must be given to the author and it cannot be modified. Materials that possess a No Derivatives license are not considered to be OER.
  • Attribution-Share Alike license :

    OER licensed CC-BY-SA may be modified and used commercially, provided credit is given to the author and it is shared in the same manner. This license is somewhat similar to the GNU Free Documentation License.
Creative Commons license spectrum- illustration by Commonwealth Learning
Source :

Generating my CC license:

Once I was done Deciding, I just went to Creative Common's Website to create my license. They have a really nice and easy website where you can get your license just by filling up some tick boxes.

My Dissemination Plan:

Dissemination Platform: Instructables

Hosting Repository: Gitlab

License: Attribution-SharAlike 4.0 International

And here is the sticker generated by creative commons for my license with all the relevant information in it.

Creative Commons License
PixelFace by Samiul Hoque is licensed under a Creative Commons Attribution-ShareAlike 4.0 International License.
Based on a work at http://archive.fabacademy.org/2019/labs/cept/students/samiul-hoque/projects/finalproject.html.

Draft Presentation & Video Links