Legal and Ethical Concerns Popcorn and HW Hacks
Popcorn Hack 1:
What is a legal concern that arises when sharing/using code?
- A legal concern that arises when sharing/using code is copyright infringement. If the code is not properly licensed or if you use code without adhering to its license terms, you could violate the copyright holder’s rights. This can lead to legal consequences, such as fines or lawsuits. Always ensure that you understand and comply with the licensing terms of any code you use or share.
Popcorn Hack 2:
What is an ethical concern that arises when sharing/using code?
- An ethical concern that arises when sharing/using code is plagiarism or lack of attribution. Using someone else’s code without giving proper credit to the original author is unethical, even if the code is publicly available. It undermines the contributions of the original creator and can harm trust within the developer community. Profiting off this code also is ethically wrong.
Popcorn Hack 3:
You’re building an open-source lyric guessing app. You want it to spread fast, but also don’t want big corporations to steal your work (without giving you credit!). Which license do you pick?
- I would choose the GPL (GNU General Public License) for my lyric guessing app. I want the app to grow and spread, but I also want to make sure that big companies can’t take my code, make changes, and keep it private without giving credit. The GPL makes sure that anyone who uses or changes my code also has to share their version under the same license. This way, the project stays open-source and I still get recognition for the work I put in. Other licenses like MIT or Apache are more relaxed and would let companies use my code without sharing anything back, which I don’t want.
Homework Hack:
License Repo: https://github.com/CyberLord09/snake-game
I chose the GPL license for my Snake game because I believe in keeping software open and available for everyone. With GPL, anyone can use or modify my code, but they also have to share their changes under the same license. That means the project stays open-source, and no one can take the code, improve it, and make it closed or private. I want others to learn from my project and contribute back if they make something better. It’s a way to protect my code and make sure the project keeps growing in a fair way.
MCQ Explainations
Q1: Open-source software is NOT considered a form of intellectual property (IP)
Intellectual property includes things like copyrights, trademarks, and patents, which are legal protections. Open-source software can be under a copyright, but the term “open-source” itself just refers to how the software is shared and licensed, not a specific legal category like the others.
Q2: Open-source software allows modification, but open-access research usually doesn’t
Open-source licenses specifically allow people to view, change, and share the code. Open-access research just means you can read it for free, but not necessarily remix or alter it. It’s about access, not modification rights.
Q3: The “digital divide” is about differences in technology access between regions
The digital divide is a social issue—it refers to how people in different parts of the world (or even within the same country) have unequal access to technology, like the internet, computers, or education about tech.
Q4: Open-source software can be modified and redistributed under certain licenses
That’s what makes it open-source! Licenses like MIT, GPL, or Apache allow users to change and share the software, often with conditions (like attribution or keeping it open).
Q5: Copying code without credit is plagiarism
Even if the code is open-source, claiming it as your own in a competition or assignment without attribution is unethical. It’s considered plagiarism, just like copying words in an essay without citing.
Q6: “Speed of AI” is NOT an ethical concern
While AI is fast, speed isn’t what people worry about ethically. They worry more about bias, misinformation, and privacy violations—because these things can cause real-world harm.
Q7: GPL requires derivative works to be open-source; MIT does not
GPL is a “copyleft” license, which means if you modify GPL-licensed software, your version has to be open-source too. MIT is more relaxed—you can even use it in proprietary (closed-source) projects.
Q8: Selling modified GPL code without sharing the source breaks the license
GPL says if you distribute a modified version, you must also share your source code under the same license. If you don’t, that’s a license violation.
Q9: Proprietary software comes with EULAs that restrict usage
Proprietary software is closed-source and controlled by the company. You usually agree to a license (an EULA) that says you won’t change it, copy it, or share it.
Q10: Violating an open-source license can result in a lawsuit
Open-source licenses are legal contracts. If you break the rules (like not crediting authors or not releasing your source), the creator can take legal action.
Q11: GPL requires all derivative works to use the same license
This is called “copyleft.” If you modify GPL software and distribute it, your version must also be GPL. This ensures the software stays open forever.
Q12: MIT License lets companies use code in closed-source projects
Unlike GPL, the MIT License doesn’t force companies to release their own code. That’s why businesses like it—they can use open-source tools without having to share their internal code.