This is a point that has always confused me about open source software. Normally, I write everything from scratch. What I'm trying to find out is what licenses allows me to do this?
A:
Why would you want to do more work? Of course you should. All you have to do is redistribute the OS technology source with your app (I am not a lawyer, but thats how I understand it).
The assumes
1) You are talking about an established open source solution, like hibernate, that you can reasonably assume works well.
2) The product you are developing is not using the open source technology as the 'secret sauce' that is going to make you money. Else you might have to open source that special part of your app.
hvgotcodes
2010-10-15 18:49:46
A:
Agent_9191
2010-10-15 18:50:20
+2
A:
Stay away from the GPL (LGPL is okay) and you won't have any problems. If you want to include GPLed packages in your application, things get tricky. BSD and MIT style licenses will get you the fewest obligations. In general, find the software package you want to use and read the license. They're usually pretty straightforward about what is and is not acceptable to do.
Nathon
2010-10-15 18:51:52
Ok thanks alot :D. I almost got scared away until I saw your answer the guys at the top came off like trolls.
Chester Grant
2010-10-15 19:19:54
In case it isn't clear, the GPL shouldn't prevent you from *using* software to build your products. GCC and Make, for example, are great tools. Just make sure you aren't *shipping* GPL'd code. That's when you start to have obligations.
Nathon
2010-10-15 20:32:14