Part 1

GPL General Public Licensing

Companies like Qualcomm makes its money on patents. If you use GPL software you could be voiding your rights to charge for software and patents.
Open source means it is meant to be shared
Qualcomm wants all derivative work to require a royalty payment payment, also anyone who uses the idea/patent pays royalty.
Examples: Blackduck manages security, quality, etc.
analyzing impact of such licenses to its ability to charge royalties for the use of their Patents.

What's the Problem with Open Source?

often they are given an assignment and instead of developing their own algorithm they opt to copy something off the internet.
In summary, it is important to know the type of software license you are copying, it could impact billions of dollars in business.

License Types

Generally, there are three things that people need to follow if they want a license or patent on github or anywhere else

Do I want to waive default copyright in reuse?
Do I want to allow derivative works or not?
Do I want to require all derivative code to be shared?

Open source MIT License: This license in friendly to someone like Qualcomm! This allows using code freely and making and distributing closed source versions.
Open Source GPL: The GNU GPLv3 also lets people do almost anything they want with your project, except distributing closed source versions. Open source means the GitHub project must be public.

Legality and Ethics

Must comply with terms and services of each individual license that is distributed to the individual or company.
As consumers, we have become aware that Music and Movie companies own content. These companies build DRM (Digital Rights Management) software to protect, play, and/or distribute content.
Mostly, if we use things in class, there is “no problem” with Open Source as our usage is considered educational use. Creative Commons software has enabled innovation because it's free!
Examples of GPL: A very premium (or version) of Linux called Red Hat was required by GPL's licensing that they were distributing the
However, businesses will not last without income. And today, businesses won’t last without engineers pulling Open Source software.

Part 2

In your blog, summarize the discussions and personal analysis on Software Licenses/Options, Digital Rights, and other Legal and Ethical thoughts from this College Board topic.

There are many different Software Licenses that anyone can use depending on what they want to do, some of which include the following:

The Creative Commons CC0 Public Domain Dedication (waives copyright interest in a work you’ve created and dedicates it to the world-wide public domain.)
MIT License (allows using code freely and making and distributing closed source versions.)
GNU GGLv3 License (lets people do almost anything they want with your project, except distributing closed source versions.) Now, obviously, many licenses means that there is a lot of specificallity and diversity for each project, so the question is: Does one license truly benefit over another? As in, If you were to creative a particular project, how important will these licenses be said project is not mainstream (popular)?

Part 3

My blog is currently utilized the apache 2.0 license and my team flask is also using the same licensing. It gives the same benefits as many other licenses, but I feel like staying on it may be of best interest because it makes it so that I do not interefere with stuff that is already working (most of the code is not mine and I am afraid if I interact with it I will dispruot something, and when searching up the benefits, I already saw that it had good creative commons pros and such). Our team made the unanimous agreement that what I noted above it the best decision: don't touch whats not broken

similar benefits to GPL
Already made for us