in reply to Debugging Question
If you are filing source code for US copyright protection, you are allowed to black out trade secrets. This could get rather tedious without some automated way to do it. Filing (in the USA) isn't strictly necessary but it gives legal umph to any claims you make, negotiating power, the ability to collect legal fees and statuatory damages, among other advantages- see Copyright registration for computer programs, US copyright office and PubLaw: Advantages of Copyright Registration.
If you want to protect intellectual property as a trade secret you have to make some explicit efforts to protect that knowledge from outsiders. A sampling of these include NDA's, no-reverse-engineering clauses in software licenses, company policies, headers in your source code files, and so forth. But I can see that distributing code that is easily readable might breach a trade secret, especially if you don't have NDA's in place.
Also, you should clear any encryption/obfustication/blackout technique you use with your lawyer. What counts as sufficient efforts to protect a trade secret depends on case law, varies from country to country, and requires an experienced person to evaluate.
Note: Though I have been involved in the IP process, To be very clear, I am not a lawyer and this is not legal advice - if you are concerned about trade secrets, consult with a lawyer if you haven't already. They can be very tricky to protect and encryption of your source code may not be enough - especially if someone can point to list of nodes and links like Anonymous Monk posted and say: "But he/she should have known that it doesn't *really* protect the source."
Best, beth
|
---|