How to risk your project and your livelihood with sloppy licensing

  2008-07-10 07:30:03
Recently the makers of the free-as-in-cost iPhone jailbreaking utility PwnageTool discovered that someone was reselling their creation -- without permission, under a new name, and for profit. That's a situation no software developer wants to be in, but the PwnageTool team was in an even tougher position because of the license under which it released its code. It didn't have one. What the reseller did is flat-out illegal, of course; PwnageTool is protected by its creators' copyright, period. No one who downloads it has any right to modify or redistribute it without permission. 
  PNG Image  PNG Image  PNG Image
  Related tags  


This particular article has been collected via RSS syndication. We apologize if it's too brief.
If You wish to publish articles on LinuxStreet.net please contact us.


  Similar articles found on LinuxStreet  
ImageFive Things Linus Torvalds Has Learned About Managing Software Projects
ImageSharing medical software: FOSS licensing in medicine
ImageIE users at risk for 284 days in 2006
ImageOpen source, open mind
ImageSun CEO Mum on GPLv3, Reveals Licensing Hopes
ImageAvoiding BSD v. GPL licensing issues
ImageRobert Slade Review:"Information Security and Employee Behaviour"
ImageMS climbs-down over Vista licensing
ImageMH: Oregon RHIO Planning Effort Comes to a Halt
ImageA Quick Look at Mono Licensing and Microsoft Licensing

Leave a comment on this article


Captcha

  
Check this if the code you see is not readable and resubmit the form.
(Data you entered will be preserved)



  

Comments (0)