Welcome to the Slashdot Beta site -- learn more here. Use the link in the footer or click here to return to the Classic version of Slashdot.

Thank you!

Before you choose to head back to the Classic look of the site, we'd appreciate it if you share your thoughts on the Beta; your feedback is what drives our ongoing development.

Beta is different and we value you taking the time to try it out. Please take a look at the changes we've made in Beta and  learn more about it. Thanks for reading, and for making the site better!

Which licensing model for a "free to use" application?

Doug Otto (2821601) writes | about a year and a half ago


Doug Otto (2821601) writes "I work for a small defense contractor. We provide long range cameras and control systems to the military. We've developed an application to aid in configuration and maintenance of these systems that we'd like to distribute with the camera systems. The idea is to provide the application with a "free to use and distribute" license that doesn't give up ownership. Any thoughts?"

Sorry! There are no comments related to the filter you selected.

Bruce Perens (1)

Dr_Barnowl (709838) | about a year and a half ago | (#43342497)

Bruce Perens has an opinion : []


You don't give up ownership of your code when you release it under any OSI license. Because you are the copyright holder, you retain all your rights, including the right to release it under another license.

Most companies seem to prefer BSD-style licenses like Apache 2, so if the participation of other corporations in your software project is key, you may want to use them. If not, GPL is fine - not only does it provide an open-source license, it will prevent your competitors tweaking your code and selling it on as a closed-source product. Ignore the crap about it being viral - for your own code, as I state above, you retain the right to re-license it however you want.

Check for New Comments
Slashdot Login

Need an Account?

Forgot your password?