I have nothing against the GPL--but to me it represents an unknown that I would like to get out of the way as early as possible so that I no longer have to think about it. Although the software will never be commercial, I may have a future purpose for the software that involves connecting with closed-source code, and I simply don't know enough about the legal aspects there. I'd rather err on the side of safety when it comes to licensing. Part of the reason for developing my own software was to avoid just these kinds of difficulties.
On Wed, Sep 26, 2012 at 12:30 AM, Scott Cutler <scott@scottcutler.net> wrote:
> Do you have suggestions, then, as to the approach I should take? I plan onSuggestion - don't spend time circumventing the GPL compatibility and
> using a GPL-compatible license eventually, but the code isn't ready for that
> yet
release your code in open-source from the day one. Saved time could
spend to get the software working better.
--
Regards,
Alexander Chemeris.
CEO, Fairwaves LLC / ООО УмРадио
http://fairwaves.ru