|
|
|
|
|
by segfaultbuserr
2095 days ago
|
|
To FOSS projects, leaked source code is highly toxic and infectious. The FOSS community's attitude on leaked source is similar to the corporate world's attitude towards GPL in the early 2000s, but unlike GPL, this is not just exaggerated FUD - the dangers of leaked, unauthorized or proprietary source code is real. Once leaked sources found its way to FOSS projects, the entire project may become illegal and face potential lawsuits (see the history of how BSD was almost killed by AT&T's lawyers). And once leaked sources found its way to your brain, it's not 100% safe [0] to work on FOSS anymore and the best option is banning yourself from participating similar projects, it's almost a memetic virus. Projects on reverse-engineering and reimplementing proprietary technologies are the most vulnerable. A decade ago, ReactOS's development was suspended for years until the codebase has been reviewed. [0] It's not illegal. If you can absolutely guarantee your work is not a derivative work based on the leaked source, but just a reimplementation, it's fine to proceed (the clean-room approach is not always needed, it simply offers the strongest legal guarantee). But for a big project with numerous contributors, the risk is high. |
|