3 ms·
Tinkering is fine. Even leaking and study is fine. But re-licensing someone's else code is at the very least impolite. People avoid using BSD-licensed code in
by nine_k 4y ago
Tinkering is fine. Even leaking and study is fine.
But re-licensing someone's else code is at the very least impolite. People avoid using BSD-licensed code in GPL code base, or vice versa, just to not violate an open-source license of some fellow hacker who won't sue (but would yawp on Twitter, or something).
Also, cutting proprietary stuff out of the thick scaffolding of proprietary dependencies is often hard. Removing proprietary cruft / tech debt may be even harder. A rewrite from scratch (not clean-room though) may be just easier.
This is to say nothing about any serious business unwilling to depend on code of unclear provenance, with possible legal complications attached; there goes adoption.
- viraptor 4y ago> People avoid using BSD-licensed code in GPL code base Huh? I don't believe they do that. It's completely fine to use BSD in GPL code, but not the other way around.
- ipaddr 4y agoIt is fine to do either but the result is always a GPL license.
- dotancohen 4y agoI actually laughed when I read this. It is a terrific, concise explanation of the nature of both licenses.
- andrewaylett 4y agoThe code keeps the original license, please don't go sticking "GPL" on the BSD bits when redistributing the source. Binaries, yes -- either more or less restricted depending on which side of the ideological fence you're sitting on.