Hi Enoch, > According to <http://en.wikipedia.org/wiki/MIT_License>: "The license is > also GPL-compatible, meaning that the GPL permits combination and > redistribution with software that uses the MIT License".
Live (esp my) will be much easier when no legal battles are fought. Keep things small and simple. Maintaining two different licenses in one package is everything but simple or small. > By the way, I recommend that thought is given to encourage Amforth use > in commercial (proprietary) designs. This is important if you wish to > draw in professional developers (for their skills and opening up > financial support opportunities). Here comes another simpleness: How transfer the money (to whom? A company I have to run, me myself,...), I'd have to manage that in an international context (taxes, customs, export regulations, you get the picture). No, thanks. My currency is much simpler (and probably more costly for the donor, I know): Lines Of Code and/or (public!) publications on what you did with amforth and how. The GPL helps here a lot. If someone wants to use forth in an closed environment, go ahead. Forth Inc and MPE will happily sell the tools and the support. And they will not tell everyone who uses them and for what. AmForth is pretty close to standard forth, so I'd say the porting should be easy. (I'm honored that you declined them in favor for amforth. Really.) > As you recall my first attempt to patch the shell was quick yet too > "dirty" (direct incorporation of Python dictionary, yuk :-). This local > appl_defs.frt is cleaner. It's not just code saving that I am after. I > want to keep WORDS shorter. I've committed your patch to the code base. I'm not that happy with it, but have not yet a better solution. Think of it as the starting point to make the shell more adaptable to local project settings (which is a good goal). > I want to encourage future library > submissions to be configurable (*). The GPL makes things clearer here as well. You'll _have to_ publish your code. And if your dish washer competitor uses it to make a better product, well fine. You can use his code as well. A huge example how this can work is the linux world. > (*) and here I need to highlight again the need for bracketed > conditionals. ;) Matthias PS: I've seen the other mails, so see this mail as an combined answer. ------------------------------------------------------------------------------ Symantec Endpoint Protection 12 positioned as A LEADER in The Forrester Wave(TM): Endpoint Security, Q1 2013 and "remains a good choice" in the endpoint security space. For insight on selecting the right partner to tackle endpoint security challenges, access the full report. http://p.sf.net/sfu/symantec-dev2dev _______________________________________________ Amforth-devel mailing list for http://amforth.sf.net/ Amforth-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/amforth-devel
