3 ms·
You seem to be confused. Even if the project is big and they change the license, so what? The old code is there with the existing license still. Fork it and mo
by endisneigh 3y ago
You seem to be confused. Even if the project is big and they change the license, so what?
The old code is there with the existing license still. Fork it and move on.
People, man.
- rmbyrro 3y agoDo you have any idea of what constitutes an OSS project besides characters written on an versioned repository?
- Barrin92 3y agoyou can't fork and maintain everything yourself, and that de-facto lock in is exactly what companies bank on when they pull this kind of bait and switch. The idea is precisely to gain popularity with open source, "the first dose is free" style, and then capitalize on the dependency and popularity. Literally just the developer analog to the misleading "everything is free and always will be" advertisements of consumer facing software.
- endisneigh 3y agoOk find other people to help, that’s how open source works no? There’s no issue here. Just whining. There is no lock in at all. Even if it were OSI open source the maintainers like the very thread we are in could die. Then what? Oh you fork and maintain yourself, or the project rots. License changes are irrelevant.