Well, the
answer depends on usage - academic/non-commercial usage is
free. If a company wants to run VW on a server for internal use, then
they would need a license. However, a commercial VW license isn't that
expensive for such usage
How much?
Which means that we may stop to develop smallwiki on VW then. I think that
this is the next logical consequence.
I do not understand then what is the situation for bottom feeder, it is
because you pay a license that you can offer it for free? Because
Smallwiki is exactly in the same situation as bottomFeeder.
Should I pay a license to use bottomFeeder if I'm working in a company and
using your tool during my working time?
Does it mean that if I want that my users can use a tool that I'm
developing for free that I have to pay a license? I think that you are
simply killing the use of VW for us then.
It really depends. I explicitly open sourced BottomFeeder, and I'm not
making money off it. So, if you put SmallWiki under an Open Source
license, you would also be ok on usage. It would be unsupported by Cincom,
but I suspect that's not really an issue here.
There is also a really vicious side-effect for all the
tools that we are
developing in open-source. A programmer in a company using Moose (which is
open-source) would have to pay. So it seems that developing open-source
and VW are incompatible. To bad we will have to learn from that sad news.
I think that you are doing a mistake but I cannot change it so we will
have to adapt ourselves.
>>>and instead of spending some of the time I don't have ;-) on porting, I
>>>would love to be able to invest that time into development efforts directly.
>>>Is there any chance you guys could be persuaded to switch to Squeak?
>>
>>Stef
<Talk Small and Carry a Big Class Library>
James Robertson, Product Manager, Cincom Smalltalk
http://www.cincomsmalltalk.com/blog/blogView
jarober(a)gosmalltalk.com