This case shows how Open Source will die. With anyone just being able to pipe existing code and tests through an LLM and claiming that to be "clean room" (which is hogwash) no licensing can protect your work from being accumulated and monetized by anyone. The commons are actively being shredded in front of our eyes.
Timeline
Post
Remote status
Replies
3
@mawhrin @tante but he didn't re-license code. The old code no longer exists in the repo. Not a single line of it.
He replaced the project with new code that has a new license. Anyone can do this in any project and it happens all the time. Rewriting code to change its license or its copyright holder is not unusual. Companies that force you to sign a CLA to contribute do this to launder all the code that they never got CLAs signed off for, then they can change the license of the entire project.
He should be forced to rename the project, though. I think that's his one mistake.
He replaced the project with new code that has a new license. Anyone can do this in any project and it happens all the time. Rewriting code to change its license or its copyright holder is not unusual. Companies that force you to sign a CLA to contribute do this to launder all the code that they never got CLAs signed off for, then they can change the license of the entire project.
He should be forced to rename the project, though. I think that's his one mistake.