Suggestions/comments on releasing paid version of plugin

Hello everyone,

I am (tentatively) considering releasing a paid version of my plugin and want to know if anyone has suggestions on how best to do that.  Specifically, how to protect it, etc. from a technical standpoint (license keys, etc.)  Are any of you doing this right now and/or have suggestions on how best to proceed?

My plugin is now available as open-source but there is still a demand for pre-built versions of it and I am still getting bug reports and feature requests.  I don't have a lot of time to address these, which is one of the reasons I opened the source in the first place.  I really don't plan to continue to update it due to time constraints with my translation work and paid software development work.  But it seems that most users of my plugin lack the technical skills to take it and modify it for their own needs, at least up to now.

If I could get some sort of revenue stream out of it, however, then it might allow me to devote some time to updating/bug-fixing.  My plan would be to keep the source open but use a kind of dual-licensing model, possibly with advanced features in a pro version, etc, but most importantly with the only way to get an official build signed by SDL being through payment. 

Any help/suggestions would be greatly appreciated.

Thanks,

Patrick Porter

Parents Reply Children
No Data