3 ms·
If you translate an existing project into Rust, it is a derivative work and should retain the original license. If the rewritten project gets more successful t
by cnfhsg 6y ago
If you translate an existing project into Rust, it is a derivative work and should retain the original license.
If the rewritten project gets more successful than the original (perhaps due to corporate promotion), you have morally stolen the work of the original authors.
If you write a project from scratch without looking, this of course does not apply. But I doubt that is how Rust rewrites actually happen, the temptation is too great.
- TheReverend403 6y ago> If you translate an existing project into Rust, it is a derivative work and should retain the original license. By this logic, WINE is a derivative of Windows and should retain their license.
- rcxdude 6y agoWINE goes to some length to avoid any reverse engineering of windows components and certainly any glimpse of the source code (such as the leaks which have happened over the years: if you have seen any of them then WINE does not want your code). They do this to avoid any accusations of their code being a derivative work. If you re-implement an open-source project on the same terms then it does not qualify as a derivative work. However if you look at the source code and use that to develop your new implementation, then that qualifies.
- aaomidi 6y ago> If the rewritten project gets more successful than the original (perhaps due to corporate promotion), you have morally stolen the work of the original authors. Ownership is by "moral" definition something completely arbitrary and made up. If you work in open-source you most likely have different views on ownership than others.
- adrianN 6y agoNow you only need a lawyer army bigger than Google's to win your case.