2026-11-09 23:51 UTC
Replies (3)
-
@xthexder@l.sw0.com 2026-11-10 00:16
Yeah, that’s pretty much the basics of these: The code must be attributed to the original author The original author is not responsible for what you do with it (no warranty/liability)
-
@treadful@lemmy.zip 2026-11-10 01:39
It’s not that I would be obligated to maintain it, necessarily. I guess I could just ignore contributions/publications on a GPL project. It’s just that with MIT code everyone knows I don’t expect anything from them, and I don’t care what they do with the code (except attribution).
-
@JackbyDev@programming.dev 2026-11-11 04:27
It seems like you think you think GPL makes it harder to maintain because the changes are “contributed back.” That’s not the case. The changes just have to be made available and licensed under GPL. In that sense they are “contributed back”, yes, but it’s not that they must be submitted as patches/pull requests.