#1 Members - Reputation: 139
Posted 27 March 2012 - 08:40 AM
#2 GDNet+ - Reputation: 1650
Posted 27 March 2012 - 08:50 AM
I should point out the reason I ask for this is that some software companies do allow products made under their license to be sold as a commodity separate from the license holder and some companies do not but the details would be held in the license you hold.
#4 GDNet+ - Reputation: 1650
Posted 27 March 2012 - 09:13 AM
Our General Public Licenses are designed to make sure that you have the freedom to distribute copies of free software (and charge for this service if you wish), that you receive source code or can get it if you want it, that you can change the software or use pieces of it in new free programs; and that you know you can do these things.
if you distribute copies of such a program, whether gratis or for a fee, you must give the recipients all the rights that you have. You must make sure that they, too, receive or can get the source code. And you must show them these terms so they know their rights.
Short answer = Yes - On the basis of your post, you can sell your code no problems, the buyer will inherit a license automatically, whether they choose to accept it or not is up to them and irrelevant to you.
The terms and conditions are fairly reasonable here -- just make sure you document where appropriate in line with the license conditions etc.
I hope this helps and congratulations on a future profit
#6 GDNet+ - Reputation: 1650
Posted 27 March 2012 - 09:51 AM
Edit: Ah I should point out if you are selling your product then yes a contract is advisable or at least some form of recognisable sale. but that's only with regard to the company you are selling to. You don't need a contract with GNU at all as you already have one, and when the company you sell to takes your product they will also effectively have a licensing contract with GNU...but that is completely separate to you. All you need to do is simply paragraph 1 and you are covered.
#7 Members - Reputation: 139
Posted 27 March 2012 - 10:08 AM
#8 GDNet+ - Reputation: 1650
Posted 27 March 2012 - 10:16 AM
As long as you acknowledge the gnu portions inline with their conditions. What this means is simply your license for your work as well the GNU license for their work will both apply. For all intensive purposes they are two separate licenses that the company will be accepting but yours will be the one relevant to you and GNU one is simply passed by your documentation.
#10 GDNet+ - Reputation: 1650
Posted 27 March 2012 - 10:30 AM
Gah going to shoot myself in the head ><
Edit: Just occured to me I am only interested if you patented it as a license, if you simply copyrighted it as a license my question is irrelevant and previous advice stands
#11 GDNet+ - Reputation: 1650
Posted 27 March 2012 - 10:36 AM
Note that you only have the right to sell your code. If you have contributions of others in there, you need to get their consent.
You are correct sir. However if applying that to the GNU part then permissions are automatically granted under the licence so long as the documentation is crediting it. As to other parties definitely, unless it is under one organisation umbrella in which case the company owns the license and not the employees.
Edit: This advice fails to take into account 3rd party contributions under the GPL utilised - spoken of later in the thread
#12 Members - Reputation: 139
Posted 27 March 2012 - 10:48 AM
#13 Members - Reputation: 3708
Posted 27 March 2012 - 10:55 AM
It is my personal project and the codes were written just by me. Although there were some volunteers testers and documentation writers that helped me on the project. So does it make anything different?
No, only other copyright holders have a say in the licensing (Testers do not hold any copyrights to your work, the documentation writers would hold the copyright to the documentation they've written though unless they've signed it over to you and you might need their permission to distribute the documentation) so the GPL only matters if you are using other peoples GPL licensed work (as the GPL then dictates the terms under which you are allowed to use their work)
The voices in my head may not be real, but they have some good ideas!
#14 GDNet+ - Reputation: 1650
Posted 27 March 2012 - 11:02 AM
It is my personal project and the codes were written just by me. Although there were some volunteers testers and documentation writers that helped me on the project. So does it make anything different?
I am going to assume you did not take out a patent then...if you did let me know as it would be relevant to the GNU issue.
Volunteer testers would hold no rights persay over your code unless you gave them rights.
Document writers - if you paid them they have no claim - if they volunteered then possibly they might have a claim but not with respect to your coding - only with regard a copyright of their documentation work which I am assuming was consigned to you, unless of course you accorded them rights.
I would suggest that for future "volunteer" situations you have a simple contract that acknowledges them as donating their work and holding no right to claim on the basis of this donation.
Meh: Simon types faster than I do
#15 Members - Reputation: 139
Posted 27 March 2012 - 11:58 AM
#18 Moderators - Reputation: 7624
Posted 28 March 2012 - 10:22 AM
Thanks both of you for the explanations. So, I guess I will just negotiate with the company about selling them the source codes with GPL exceptions. Thanks again!
Both of these are excellent questions for a business lawyer.Any suggestion how to price it?
You absolutely should have a lawyer help you with the negotiations. That is what they do. They work with contracts in exactly the same way a programmer works with code.
Business lawyers are also very experienced at coming up with valuations for products. They know what source code is selling for, how much to ask, and how much to accept.
If you don't have a lawyer you may discover that you signed a contract written entirely in their favor that ends up leaving you exposed to all kinds of problems. Topics like IP rights, indemnity, severability, and venues are all very important and you are likely to get some of them wrong unless you have help from a lawyer who understands it.
Just like a non-programmer trying to write complex source code, a non-lawyer trying to write a contract is likely to end up with serious problems.
The cost of a lawyer is pretty cheap; in my area it is about $150/hr. Compare that with the potential cost of a bad contract, which through indemnity clauses and other problems could potentially hold you liable for a fortune in a worst-case scenario.
#19 Members - Reputation: 139
Posted 28 March 2012 - 10:28 AM






