Plan for dissemination
My project is not a new idea, but rather simple implementation of the existing product.I want to make the customized, simplified and cheap alternative of the micro resolution stage to be used in microscopic observations/measurements.
In case of success, the project have a commercial potential: it can be commercialized as a readily functioning product, or as a kit of materials and instructions to fabricate it. However, there are numerous reasons why at the current stage I would prefer to make the instructions, designs, and codes on a website available for everyone:
- During project development, I'm using the help of Fablab instructors, and the ideas and instructions from the people who have done the similar projects beforehand.
- This final project is a first prototype of the product.
- I'm using different free sources myself to make the project. I will probably share the project's design files on Thingiverse , while the instructions will be published on my Final project page. I believe it can be useful for many labs to have an affordable analogue of the microscope stage.
Licences
-
CreativeCommons
free and easy to use license for sharing creative (design) works, which is comprised of licenses with specific conditions:
Attribution (by), ShareAlike (sa), NonCommercial (nc), NoDerivatives (nd).
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
applied for software and free of charge without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software.
-
Apache
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.
My choice for the final project is to apply the CreativeCommons, specifically Attribution-NonCommercial-ShareAlike, where the "Attribution requires" to give appropriate credit to the author of the work, the "NonCommercial" - the materials cannot be used for commercial purposes, and "ShareAlike" - transformed work should be distributed under the same license as the original. I will be happy, if someone will find my work useful.
For the software part of the project, if there is going to be any, I will apply MIT License.
Summary slide draft (CAD design presented with Power point)
I plan to make a video with Openshot video editor, which provides a broad functionality to make a video by simply placing the images, videos, and audio in a timeline. I have also checked for the free audio samples, which are shared under the Creative Commons licences, for example Free music archive, or Free Stock music. But I don't have a video to show so far because I haven't started the project implementation yet due to the quarantine.
Reflection
This week I defined the dessimination plan for the project and learned about the licences.
