Week 19. Invention, Intellectual Property, and Income
Go to:
1. Plan for dissemination
I don’t feel like my project idea belongs to me. I took the concept from a photographer on my friend’s wedding, developed it and made it work. I think that I did a good job on that, but there are things I would like to improve and I have no intention of making a commercial device from it. I like to think, that my documentation will be a good starting point for the future DIY projects. I’m trying to put on my website all information I’ve used so far, all my design files and process descriptions.
After finishing FabAcademy I'm planning to get all materials together and post it somewhere. Maybe, it is time to make a first post on www.instructables.com or Pikabu.ru (Russian analog of Reddit) or shoot a YouTube tutorial video. I haven't decided yet, but I would like to receive a feedback and any ideas how I can improve the design and code from the internet community.
2. Licences
I don’t want to people to bother mentioning my name if they are using my design, but I really would like people to share with me their results. I’m thinking about gathering all my experience together and making a full cycle Youtube tutorial.
Therefore now it is time to choose a license that meets my requirements. So to acheive this, I went through the licenses in Neil's page, I got myself familiar with the terms of different licenses listed there, I explain some of them here:
- Creative Commons (CC): is free and easy to use license for sharing creative (design) works, which is comprised of 6 main licenses with specific conditions listed bellow:
- Attribution (by), ShareAlike (sa), NonCommercial (nc), NoDerivatives (nd)
- More information regarding each condition could be found in this page.
Therefore considering Attribution (by) condition, it requires that others who use my work in any way must give me credit the way I request. - MIT: applies for software and is free of charge and without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software.
- Apache is a license for software, which is somehow similar to MIT license. It provides one to freely use, modify, distribute and sell a software licensed under the Apache License without worrying about the use of software: personal, internal or commercial. But the explicit reason that differs Apache from MIT license is that in Apache any change to the code should be clearly identified. If one redistribute software with any Apache licensed components, the person must include a copy of the license, provide a clear Apache License attribution, and add modification notices to all the files that he/she modify. Therefore, I find working with MIT license easier compared to Apache.
- Fab: This work may be reproduced, modified, distributed, performed, and displayed for any purpose, but must acknowledge "project name". Copyright is retained and must be preserved. The work is provided as is; no warranty is provided, and users accept all liability.
Considering different options and comparing different licenses, I made my mind to choose the CC license, which I believe meets my requirements. And I would choose MIT license for the software part of my project.
I am pleased that I am able to share my work with other people.
4. The Results of the week
- I've defined licences for my project
- Last mechanical parts were printed in RED(!) filament. (Other parts are white and I'm still not shure what I'm going to do with that...)
- I'm going to put everything together over the weekend, so the slide and the video are not so good now...
