On 5/16/11 3:49 PM, Richmond Mathewson wrote:
$12k and a license seems to contradict Open Source. Oh, well, Richmond
is probably missing
something again . . . :(
The $12k pricetag is if you want to write a commercial program and
include TightVNC functionality (which was my original plan).
I
Hi Richmond,
That's called a dual license, I think.
--
Best regards,
Mark Schonewille
Economy-x-Talk Consulting and Software Engineering
Homepage: http://economy-x-talk.com
Twitter: http://twitter.com/xtalkprogrammer
KvK: 50277553
New: Download the Installer Maker Plugin 1.6 for LiveCode here
On 05/16/2011 11:30 PM, Derek Bump - Dreamscape Software wrote:
Thank you to everyone for your help on this.
I hate to say it, but I'm spending too much time on this. Add to
that, the GPL, FOSS and Open Source concept is a bit confusing (to me
anyways).
I'm going to remove TightVNC from the
Thank you to everyone for your help on this.
I hate to say it, but I'm spending too much time on this. Add to that,
the GPL, FOSS and Open Source concept is a bit confusing (to me anyways).
I'm going to remove TightVNC from the code and not include that
functionality. Then I don't have to f
Hi Andre,
You're right (AFAIK) but the problem is that LiveCode may be considered a
non-system library that is linked to.
--
Best regards,
Mark Schonewille
Economy-x-Talk Consulting and Software Engineering
Homepage: http://economy-x-talk.com
Twitter: http://twitter.com/xtalkprogrammer
KvK: 50
Mark,
Please correct me if I am wrong but if he isn't linking against tightvnc
libs then he can simply offer the tightvnc source and license his souurce as
MIT or BSD. Bundling gpl software along with your own is ok as long as you
distribute the source for the gpl part. If he is not bundling but h
Richmond, Andre, Derek,
It is not true that you can't release your LiveCode stacks as open source,
because the LiveCode development tool is not open source. Unless the license
explicitly states that the development tool has to be open source, you can
safely release your LiveCode stack as open s
Folks,
First, the expert here on the list is David, he'll probably chime in soon.
In the meanwhile let me give a couple information here.
LiveCode stacks can be released as FOSS. We're over the linking with
proprietary engine trouble, that has been discussed a lot and in the end,
the stack is you
On 05/16/2011 09:13 PM, Mark Schonewille wrote:
Richmond,
That's not true. You could at least release your source code as open-source.
There are open-source licenses that allow this. If you think no license fits,
then simply invent your own.
--
Best regards,
Mark Schonewille
What's not true
Richmond,
That's not true. You could at least release your source code as open-source.
There are open-source licenses that allow this. If you think no license fits,
then simply invent your own.
--
Best regards,
Mark Schonewille
Economy-x-Talk Consulting and Software Engineering
Homepage: http
On 5/16/11 12:33 PM, Richmond Mathewson wrote:
If your project involves Livecode/Runtime Revolution it CANNOT be
released as Open Source as the
Livecode engine is Closed Source.
I fell foul of this about 5 years ago when I offered a slew of my EFL
programs as freebies to
the Edubuntu arm of Ubun
On 05/16/2011 08:11 PM, Derek Bump - Dreamscape Software wrote:
Does anyone have any suggestions for an easy way that I can release a
project as Open Source?
Do I just put the code up on sourceforge or freshmeat?
The project already includes TightVNC functionality, and as such,
forces me to r
Does anyone have any suggestions for an easy way that I can release a
project as Open Source?
Do I just put the code up on sourceforge or freshmeat?
The project already includes TightVNC functionality, and as such, forces
me to release the project as Open Source. Also, I'm not looking to
act
13 matches
Mail list logo
