Assignment:develop a plan for dissemination of your final project, 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 (Video is optional).
Learning outcomes: Recognise the range of licenses available, formulate future opportunities.
Assessment: Have you: Summarised two kinds of licences and explained why you chose one. b) Imagined and outlined possibilities and described how to make them probabilities
I built the composite base for the robot on Wildcard week, tested that the sonar works on Input week, and gotten the motors to work on Output week. Now I "just" need to get them to work together.
Still on my todo-list is also finding a way to attach the sonar and the motors to the base neatly, as well as lasercutting a shell for the turtle (I am thinking fusion360+slicer). I am also wondering if I can use the 9V battery I have there to power my Attiny board (in addition to the motors it is connected to now). It would be handy if I did not have to walk beside the robot with my laptop attached with an ftdi cable to make it work.
As for the video part, I decided to skip it this week, but for the final presentation I will keep it simple:
- Starting with the final presentation slide: Me narrating the purpose of the project, how it was done
- Ending with a short clip of the robot in action
Personally I am hoping I can use my work in the future as a scaled down version with children who are participating in the digital fabrication related projects carried out with our research group. With the scaling down I mean a bit less expensive. I calculated the rough cost of my robot on week 18 and it wasn't cheap. The total cost was around 70-80 dollars. I think I could bring this number down for example by replacing the quite expensive composite base with a lasercut chassis that is cheaper and faster to build. With children it would also be more feasible. I wanted to explore the process during my time in the FabAcademy, but I do not think that many teachers or parents would be willing to try that process out with the kids, as there are so many safety consideration with the chemicals used.
In addition to hopefully using my final project as a basis for my own future research projects with children, I also want to share my work to a wider audience. I want anyone who is interested in any of the processes I learned about during my time in FabAcademy to be able to use my documentation as a basis for learning.
I have no intention of turning any part of my FabAcademy final project or weekly assignments into business ventures that would give me income, instead I want them to be freely available to anyone for educational purposes. Because of this, it was a natural choice for me to go with either the Fab license or one of the Creative Commons licenses for the contents of my website.
Fab license: (c) holder date. 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.
Creative commons licenses:
- "Attribution (By): All CC licenses require that others using the work must give you credit the way you request, but not in a way that suggests you endorse them or their use. If they want to use your work without giving you credit or for endorsement purposes, they must get your permission first.
- ShareAlike (SA): You let others copy, distribute, display, perform, and modify your work, as long as they distribute any modified work on the same terms. If they want to distribute modified works under other terms, they must get your permission first.
- NonCommercial (NC): You let others copy, distribute, display, perform, and (unless you have chosen NoDerivatives) modify and use your work for any purpose other than commercially unless they get your permission first.
- NoDerivatives (ND): You let others copy, distribute, display and perform only original copies of your work. If they want to modify your work, they must get your permission first." (Creative commons, 2018)
--> Out of these licenses, the "Attribution, ShareAlike, NonCommercial" -license sounds most suitable for my purpose: "This license lets others remix, tweak, and build upon your work non-commercially, as long as they credit you and license their new creations under the identical terms" (Creative commons, 2018), so I have chosen to use that for my documentation. The Fab one is fine for all of it's simplicity - but as I want my work to be available freely for only educational purposes, I go with the Creative Commons
--> In addition, I was explained that the creative commons is meant for exactly those, creative works, and software works are covered by other licenses. Even though I personally believe coding is also a creative process, I have selected to use the MIT license for all of the code produced
Copyright © Heidi Hartikainen 2018
Template copyright ©Blackrock Digital LLC 2013-2018
This work is licensed under a Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International License.