week_13

• 1) - Individual：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.

I am relatively familiar with the concept of open source. In my experience with computers and the Internet, I have seen various licenses, such as DVDS with radio warnings, installing software, downloading music, and so on. However, I've never really looked into the details of open source licenses or ideas. The first thing I did this week was read about permissions.

When you License your product, you do not give up any rights. You still have the original copyright. License simply gives them a specific right to use your product. License simply releases your work into the public domain or grants permission to individual copies. It also means that you are giving up copyright income and that no one else is obligated to list you as an original author or contributor. Open source license agreements make it easier to contribute to others without having to seek special licenses. It also protects your rights as an original, or at least recognizes your contribution. It also ensures that your work is not plagiarized.
⑴ GNU General Public License
The GNU General Public License (GPL) is probably the most commonly used License for open source projects. The GPL gives and guarantees extensive rights to developers of open source projects. Basically, it allows users to legally copy, distribute and modify software. This means you can:
① Copy software
Copy software to your own server, client server, your own computer, almost anywhere you want, and there is no limit to the number.
② Release software
Distribute the software you want, for example, by providing download links on your website, carving CDS, printing them out, etc.
③ Charge fees
If you want to charge for software you provide to someone else, such as setting it up on someone else's website or for other purposes. The GPL allows you to do this, but you must give your customers a copy of the GPL and tell them they can get a free version elsewhere. Of course, it's best to tell the customer why you're charging before you do.
④ You can make any changes
If you want to add or remove features, no problem. If you want to use parts of the code in other projects, that's fine, but the only limitation is that the project must also be distributed under the GPL. Commercial software cannot use GPL code.
⑵ GNU Lesser General Public License
The GNU Lesser General Public License (LGPL). It grants fewer permissions than the Plain general, LGPL is better for libraries that connect to non-GPL or non-open source files. Because of the GPL, software that USES part of the GPL code must also use the GPL, and developers cannot use the GPL to develop paid software or proprietary software. The LGPL has no such requirement and does not require the use of the same License as part of the code. Commercial software can be used, but not modified LGPL code.
⑶ BSD License
The BSD License has fewer restrictions than other free software licenses, such as the Glenore, however, the difference between the two versions of the BSD License: The New BSD License/Modified BSD License and the Simplified BSD License/FreeBSD License. Both are gulp-compatible free software licenses.
The New BSD License (" 3-license ") can be used for any purpose as a disclaimer of copyright and warranty License and can be maintained by infinite redistribution, meaning that if the redistributed product contains the source code, the source code must be accompanied by the BSD agreement from the original code. It also has a special restriction that, without a special license, restricts the use of worker names for derived work, which means that the name of the author/organization of the open source code and the name of the original product may not be used for marketing purposes.
The main difference between the New BSD License and the Simplified BSD License is that the latter ignores the non-accreditation clause. Commercial software can be used or modified to use the BSD protocol code.
⑷ MIT License
MIT is as loose a license as BSD, and the authors only want to retain copyright and no other restrictions. That is, you must include a statement of the original license in your distribution, whether you distribute it in binary or in source code.
① You can use, copy and modify the software
② You can use the software for free or sell it
③ The only limitation is that it must be accompanied by an MIT license agreement
Commercial software can use, modify, or even sell the CODE of the MIT protocol.
⑸ Mozilla Public License 1.1 (MPL)
The MPL protocol allows free redistribution and modification, but requires that the originator of the software copyright the modified code. This license protects the interests of commercial software, which requires the free contribution of Copyrights based on modifications to the software. In this way, Copyrights for all the code around the software are concentrated in the hands of the originator. But MPL is allowed to modify, free of charge. There is no link requirement for MPL software. Commercial software can use or modify the MPL protocol code, but the copyright of the modified code belongs to the originator of the software.
⑹ Common Development and Distribution License
The CDDL (Common Development and Distribution License) is an extension of the MPL (Mozilla Public License). It allows the use of Public copyright without royalty, provides patent protection, can be integrated into commercial software, and allows self-distribution of licenses. Commercial software can be used to modify the CODE of the CDDL protocol.
⑺ Apache License
Apache License is an agreement adopted by Apache License, a well-known non-profit open source organization. Similar to BSD, the protocol also encourages code sharing and respects the copyright of the original author, and also allows code to be modified and redistributed (as open source or commercial software). Requirements to be met:
① Users of the code should be given an Apache License.
② If you change the code, you need to specify it in the modified file.
③ In the extended code (modified and sourced-derived code) the agreement, trademark, patent statement and other instructions specified by the original author in the original code shall be included.
④ If a Notice file is included in a released product, an Apache License is required in the Notice file. You can add your License in the Notice, but it may not appear as a change to the Apache License. Apache License is also a business-friendly license. Users can also modify the code as needed to meet the needs and release/sell it as an open source or commercial product. Commercial software can use or modify code that USES the Apache protocol.
⑻ Eclipse Public License
EPL is a similar license to CPL, and any code extending from the Eclipse source must also be open source.
⑼ Creative Commons
Creative Commons (CC) licenses are less open source and are typically used for design projects.CC licenses have broad definitions, each of which grants certain rights. It has four basic parts and can be used individually or in combination. Here’s a partial overview:
① signed
The author must be the originator of the work. In addition, the work can be modified, distributed, copied and used in other ways.
② Share in the same way
The work can be modified, distributed, and so on, but must be under a license.
③ noncommercial
Can be modified, distributed, etc., but not used for commercial purposes. There is some ambiguity about what is "business" (no clear definition is provided), so you may need to clarify this in your own projects.
④ No modification
This means that you can copy and distribute licensed work, but you cannot modify it in any way, or develop it on an as-is basis.
Commercial software is used in accordance with the CC Protocol, and the strictest license will be a "signed, non-commercial, non-modifiable" license. That means you can freely share the work, but you can't change it. You have to give credit to the originator.
⑽ Common Public License 1.0
The Common License has some detailed requirements to consider:
① Specify the patent authorization. General open source software is clear that the copyright owner of the source code will be their right to modify, copy rights and other copyright rights to the public license, but retain the right of authorship, and the Common license on this basis also makes clear that if the source code contains patent rights, the source code patentee will copy, use the exclusive rights to the public license.
② Provides that source code and modified source code may be distributed as a new product in combination with other types of code not subject to this license, provided that the source code obtained under this license and the modified source code are distributed as required under this license.
③ Details the circumstances of termination of this license, including patent infringement litigation.
④ Specifies the principle of independent liability that if a user of the source code under this license applies the obtained source code for commercial use, he shall be fully liable for any infringement action arising out of the use of the source code program in a commercial application. This is a special rule that most open source software licenses do not require.
Commercial software can be used or the code of the Common Protocol can be modified, but it is liable for the infringement caused by the code.

My plan is to complete the final project with weekly assignments. By linking the assignments to the final project, I will be able to finish the final project on time. My project is a smart WIFI socket, with temperature and humidity sensors, light sensors, and the sensor data displayed on the LED screen.

1. Design intelligent cartridge case and make it with laser cutting machine;
2. Design lighting sensor, temperature and humidity sensor PCB;
3. Design LED screen display PCB board;
4. Design and control PCB board;
5. Connect the components to the designed circuit;
6. Make slides and videos;
Upload them to the root directory.

My initial inspiration for this project and the function behind it is to add light sensors, temperature and humidity sensors to the existing wifi smart socket and display them on the LED screen. In addition, the various parts of the project and their functions are commonly used electronic concepts such as light sensors, AC/AD power modules, etc., which I learned from the open source community. I didn't come up with the idea, but I learned how to use it and applied it to my own work to make it cool. Therefore, I do not intend to apply for any patents or Copyrights for my project. But I still want to keep some kind of license for my work to prevent others from using it for commercial purposes/profit. So, I'm going to use the MIT license. This basically means that anyone can use, modify and change my work as long as they give me full permission

The idea behind my project is to add light sensors, temperature and humidity sensors to the existing wife smart plugboard, and display them on the LED screen. I have no financial motivation and no interest in developing a business. My interest is in the Shared development of human knowledge, and to this end, I will publish my project under a license that allows schools or anyone interested to use and modify the project without restriction. I think I have a lot of options to really allocate this project. I think YouTube and Instructables are the best websites for promoting your project.