Re:How to correctly use code you didnt write
by raphman on Sunday March 11, 2012 @05:14PM
(#3691308)
I under-appreciated licenses for a very long time and only recently realized the very real risk of writing some code, posting it to github without any licensing, it being picked up by some commercial organization, and then them licensing it and (possibly, later) taking action against you for using their code without a license (ha!).
I am not completely sure about US copyright law. However, at least in the European Union, you are the sole owner of your code as soon as you write it. Therefore, anyone putting their license on your code would be violating your author rights.
Re:How to correctly use code you didnt write
by Cushman on Sunday March 11, 2012 @05:49PM
(#3691393)
You do, under the law, implicitly own the copyright to everything you create. This will not inherently protect you from costly lawsuits requiring you to prove that you do, however.
Re:How to correctly use code you didnt write
by true_religion on Sunday March 11, 2012 @05:55PM
(#3691407)
Nothing protects you from lawsuits. I could right now sue you for slander for some comment you never made, and I fabricated evidence for.
That would just make me unethical, and you can't protect against that.
Re:How to correctly use code you didnt write
by Cushman on Monday March 12, 2012 @02:18PM
(#3694668)
That may be true in the abstract, but having a registered copyright does give you additional protections that could make it easier to dismiss a suit.
Re:How to correctly use code you didnt write
by true_religion on Sunday March 11, 2012 @05:53PM
(#3691404)
How is that a real risk?
If they're so unethical to try and sue you for using code they just found on the internets without a licence, they're just as likely to steal your code even if it had an MIT licence and claim you were the original thief.
Re:How to correctly use code you didnt write
by Someone on Sunday March 11, 2012 @08:20PM
(#3691785)
It does not require outright malice to have a company think code they have in their repository is theirs, and you having the same code must be stolen; it can just be a matter of sloppy attribution plus some 'to protect our interests, we have to do what everyone else does'. Adding licensing info to every file makes it less likely that that sloppy attribution will take place.
I under-appreciated licenses for a very long time and only recently realized the very real risk of writing some code, posting it to github without any licensing, it being picked up by some commercial organization, and then them licensing it and (possibly, later) taking action against you for using their code without a license (ha!).
Anyway, I appreciate the spirit of the post, but it didn't make much of an argument...
Edit: I guess he also argues that it might upset the code's author to copy their code without attribution (totally possible), which would lead to their writing less open source code (seemingly less likely). I think the risk of commercialization of your code is more salient, though.