The fear of “GPL contamination” is what the business of dual licensing GPL code is based on; you use the GPL version as a ‘try before you buy’ marketing tactic and put the software freedom community to use as a marketing team. The stronger the copyleft (ie, Affero GPLv3 is the strongest) then the higher the conversion rate on the non-GPL license will be.

Given this post is now many months old, perhaps you could make a new post reporting how things have gone?

I think you should talk to the major functional software houses/groups (Galois, various banks, and Jane Street come to mind) and see if any of them want to publicly “sponsor” your development of Reactive, under the original BSD license.

Many of these shops are a) Trying to attract functional programmers and want the name recognition of sponsoring one of the coolest ideas out there b) Wanting your expertise if they use the product (I can imagine Reactive would be quite useful to a bank) c) Open to the bleeding-edge

Slapping their logo on the website, and getting consulting hours and gratitude from you accomplishes all of these things.

The above might sound facetious, but it is only half so. This is a growth sector at the moment. Think outside the thunk.

The objection raised by Anon (“Please not the GPL”) were already addressed in Ryan’s comment: if you don’t like the GPL you need to cut a separate deal, probably involving money flowing to Conal. That is the point!

But then, if you interpret consulting as mostly training and advice, you might be able to earn bucks by explaining people how to design — in general or for a specific application — programs without falling back into pre-FRP patterns. Add a little viral marketing via a google techtalk and…

That almost sounds like a defintion of the word enterprise in the term “enterprise software” – free or non-free.

I’m not recommending you go the route at all though. Personal integrity matters and ultimately will probably prove to be good business.

I think you need to consider a broader strategy than just licensing. The majority of open source developers I’ve know who’ve been at it seriously for more than 5 years now earn a professional living from activities related to it. […]

Joseph added:

Keep things free and unencumbered for the community, and offer consulting services and a commercial license for enterprises which need support.

Thanks for bringing in this angle. I’m puzzling over how it might apply to my work.

What I’m most dedicated to in my work at is creating software that is simple to reason about (understand precisely) and to use. It’s a tremendous effort, and it’s my mission.

In order for free software to generate consulting & support business, I imagine the software has to be tricky/complicated to use. Is that so?

I also strongly agree with Robert Burrell Donkin. I think that you can maximize your personal value by keeping the license open and fostering a growing community. JBoss and MySQL are great examples of very successful outcomes from this approach. Keep things free and unencumbered for the community, and offer consulting services and a commercial license for enterprises which need support.