Ventoy source code contains some unknown BLOBs, still no word on the issue from the dev after months

Open Source@lemmy.ml – 454 points – 1 months ago

[issue]: Remove BLOBs from the source tree · Issue #2795 · ventoy/Ventoy

I had no idea this issue had been identified. While I find this tool very useful, the project is seeming rather questionable to me now.

You are viewing a single comment

View all comments

God I hate people who use github comments for their own benefit. "Just fork it bro" is never helpful.

For me the problem is more in GPL violation: they distribute blobs under GPL3, user made a request of the source code by creating an issue, but they ignored that request. It is not only about "you have to fix it" versus "just fork it" imo.

Licence doesn't apply to the creator.

He already owns the copyright, he doesn't need a licence, he doesn't need to adhere to the gpl

The binaries in question are various GNU and FOSS tools from elsewhere, not part of the Ventoy project itself. So no, the Ventoy author does not own the copyright of the tools in question.

Even then, he's still allowed to provide binary blobs. He doesn't have to provide it as source code. If that was the case, we'd all have to build from source and package managers like apt, dnf and flatpak wouldn't exist.

All he has to do is make the source code available, i.e. just link back to the original Github Repo.

Seriously this. Any comment about a complicated system that starts with "just" can be ignored 99% of the time.

Also, there are 4k forks of Ventoy already. Obviously forking it isn't helping. Actual work needs to be done.

I agree that comments like that are unhelpful/unnecessary, but how is that "for their own benefit"? Other than the actual devs themselves using that as a way to just ignore issues, I do not follow

It makes them feel good and devalues the quality of discussion. Benefits them, harms others.