Programming

21586 readers

199 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Follow the programming.dev instance rules
Keep content related to programming in some way
If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities [email protected]

founded 2 years ago

MODERATORS

[email protected]

Question about GPL-3 and deleting files from a Github project (beehaw.org)

submitted 1 year ago by [email protected] to c/[email protected]

12 comments fedilink hide all child comments

This might be an odd question to ask, but I want to be sure to understand it correctly. When I clone a project in Github that is licensed under GPL-3.0 license, am I allowed to delete bunch of files that I no longer need?

Someone took an old BCX-BASIC program and converted it into C with some additional work to make it compile in Linux, and a Python GUI. The original Basic program is still included in the project. I want to delete everything besides the .c program, license and an include file. I want to add my own Makefile and just create the commandline executable with gcc. And I might change the name of the application too and either create my own GUI or maybe (if its possible) to integrate the C program in Rust or Zig in example, but have to explore this more.

But the files that were included there, the legacy BASIC program and some other files, are licensed under GPL-3 too. Am I allowed to just delete those files from the project?

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 7 points 1 year ago (2 children)

Everyone can write a new version of the GPL.

The standard GPL permission statement explicitly clarifies that the license is "as published by the Free Software Foundation" so any later version of the license has to come from the FSF.

This program is free software: you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation, either version 3 of the License, or (at your option) any later version.

The reason for the "or later" clause is to allow the FSF to update the GPL in response to flaws that are discovered. The "or later" clause is controversial because it effectively allows the FSF to change the licensing terms of any software licensed under such a clause, and so some developers who don't trust the FSF with this authority omit this clause. Famously, Linux is licensed only under GPLv2 with no or-later option (Linus has been a vocal opponent of GPLv3)

[–] [email protected] 3 points 1 year ago

Oh that's good to know! Yeah, I never liked the "or later" too. To be fair, the software you licensed won't change the license if a new updated version comes out. It's just a third party can opt-in. So this is not a situation like a software agreement where the publisher can change the agreements at any time with full effect, despite you agreed to a prior agreement. I don't think "or later" is evil, but I personally don't like anything that is not explicit.