@Aussie_Troll
I agree. The question is not specific enough, so garbage in garbage out. I voted NO because I'm not inclined to give away the right to use my own code, unless of course, it is code that I'm being paid to write for a specific project.
Even with paid work for a specific project there's gotchas. Suppose you contribute code from libraries you have written outside the project. This needs to be specifically excluded and then the inclusion must be officially documented as being covered by the exclusion. Failure to do this could end up making every other app that uses your prior written library a violation.
At the end of the day, corporations just aren't interested in this and will force their terms on you. The only choice would be to document the disagreement and hope that your prior code never becomes big business, otherwise they will come after you....
Oracle vs Google comes to mind, although that dispute has a slightly different flavour, being patent based, not copyright based. The principle still applies. If Android hadn't made such a big market impact, Oracle wouldn't have bothered.
The best of ZDNet, delivered
ZDNet Newsletters
Get the best of ZDNet delivered straight to your inbox
