I believe that the right way (TM) is to just publish the source code, no strings attached, no guarantees given. If anything, register the name as a trademark. If that is too radical for you, LGPL might just be what you want.
You already outlined your business model: "make money by helping other companies making money with our software; comprising training, enhancing our software, writing custom data apps, etc."
Nothing of that requires any licensing. You demonstrate that you can write good code, keep it up to date, invent some new things. You will have written a very useful toolkit, and no one knows it better than you. Do you really fear that someone trusts other people more to build on it? Do you really fear that you will be out of work, when you have demonstrated these skills for all the world to see?
Comments
I believe that the right way (TM) is to just publish the source code, no strings attached, no guarantees given. If anything, register the name as a trademark. If that is too radical for you, LGPL might just be what you want.
You already outlined your business model: "make money by helping other companies making money with our software; comprising training, enhancing our software, writing custom data apps, etc."
Nothing of that requires any licensing. You demonstrate that you can write good code, keep it up to date, invent some new things. You will have written a very useful toolkit, and no one knows it better than you. Do you really fear that someone trusts other people more to build on it? Do you really fear that you will be out of work, when you have demonstrated these skills for all the world to see?