Project Browser vs App Browser (was "script scope variables inexplicably becoming unset")

Dr. Hawkins dochawk at gmail.com
Sun Jan 4 20:21:36 EST 2015


On Sun, Jan 4, 2015 at 8:58 AM, Peter Haworth <pete at lcsql.com> wrote:

>
> But I still need some sort of protection against someone simply copying
> code out of it and inserting it into their own products, that's where it
> gets hazy for me.  If my license is "open source", does that mean they
> would have to release their product as "open source" since it includes my
> open source code?
>

If you used a viral license, yes.  (well, once the code is exposed, they
can also just violate copyright law and steal it . . .)

That still begs the question of what the benefit to *you* of open sourcing
it is.

It's this type of thing that has prevented me form going open source up to
> now.  It's a couple of minutes work for me to remove the password
> protection from the code but much more time required to figure out a good
> license and how to deal with not having a free demo any more.
>

Nothing would stop you from having the free closed source version, full or
stripped.  You are the copyright owner.   The license doesn't bind you; it
binds those you license it to.


> But I am getting more and more requests from Community Edition users to
> make it available to them so I think I need to bite the bullet.
>

But again, to what end?  Unless LiveCode creates an exception allowing
development tools to be opened with password protected stacks (which they
could, but it wouldn't make sense for *them* to create ways for folks like
you to get paid for add-ons to software that they don't get paid to sell .
. .)



> OK Google - "How do I sell an open source product"
>

Once.

Seriously.

Once you've sold it, any open source license lets that person redistribute
freely.


-- 
Dr. Richard E. Hawkins, Esq.
(702) 508-8462



More information about the Use-livecode mailing list