On Wed, Feb 19, 2014 at 1:17 PM, Matthias Trute <mtr...@web.de> wrote:
> Sam, > > > Matthias has the only opinion which matters, and is on record as strongly > > opposed to this sort of license. > > You seem to ask why? These licenses are like one-way roads. From the > vendor (me and a few other people) to all. The vendor gives away all > he has and gets nothing in return. I mentioned the energy bill problem > for some BSD flavour. This kind of freedom is not desirable. > > I feel this invites a brief reply. the issue of project success (keeping the lights on) is one of developer interest, not nature of license. The world is littered with abandoned projects of every flavour. A GPL is assuredly no talisman here. Let's focus on AmForth. Enoch is contributing to the codebase, and paying his bills. It is a net gain for AmForth, which AmForth stands to lose if he cannot pay his bills in this way. BSD is predicated on the idea that projects can benefit from contributors such as Enoch, and that developer interest is the only thing that 'keeps the lights on'. Right at the beginning I mentioned the presumption of goodwill. This is that presumption in action. Many languages, Lua to cite one, thrive on this kind of license, and many coders get paid to integrate Lua into projects. That's all that is useful to say, as change in the license has never been contemplated. If I do write for AmForth, which is unlikely at this point, my code will be public domain or BSD. If you wish to repurpose it to the GPL, you certainly can. You won't even hurt my feelings. ^_^ cheers, -Sam. > This is all especially sad because Forth is small and getting smaller. > > Meanwhile, I'm excited about the potential and future of the language, > > especially in microcontrol. > > That makes serious and successful projects even more important. > e.g. Jens' TCP/IP stack is something I admire. I can study > it, I can modify it (or the underlying core system) > and I can publish my changes. My internal system got a few > code snippets that improve the performance of his code by > 20%, and I'm not yet finished. The same code should improve > SD-Card performance as well. I'm not interested in dish washers > per se, but I may re-use code parts for a robot. And I do not > want to discuss legal terms. All code is under the same > license and everyone can and has to use it. The GPL is made > for exactly this. > > Matthias > > > ------------------------------------------------------------------------------ > Managing the Performance of Cloud-Based Applications > Take advantage of what the Cloud has to offer - Avoid Common Pitfalls. > Read the Whitepaper. > > http://pubads.g.doubleclick.net/gampad/clk?id=121054471&iu=/4140/ostg.clktrk > _______________________________________________ > Amforth-devel mailing list for http://amforth.sf.net/ > Amforth-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/amforth-devel > ------------------------------------------------------------------------------ Managing the Performance of Cloud-Based Applications Take advantage of what the Cloud has to offer - Avoid Common Pitfalls. Read the Whitepaper. http://pubads.g.doubleclick.net/gampad/clk?id=121054471&iu=/4140/ostg.clktrk _______________________________________________ Amforth-devel mailing list for http://amforth.sf.net/ Amforth-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/amforth-devel
