Open Source and Legal Protection 250
A nameless submittor sent in this issue on seeking legal protection for an eventual open source project of a reverse-engineered from published works. Here's the problem: the project implements what many have made clear to be proprietary information and trade secrets. What can one do to protect themselves from the eventual legal backlash when this project is finally made available to the public? Need an example of things that could go wrong with such a situation? Then one need not look farther than the DeCSS fiasco. Click the link below for the full submission.