Licensing

[Peter Haworth]

OK, thanks Mark, this is so confusing.  Maybe the best approach is to just
do it and adopt the "better to ask for forgiveness than permission" axiom"

Pete
lcSQL Software <http://www.lcsql.com>
Home of lcStackBrowser <http://www.lcsql.com/lcstackbrowser.html> and
SQLiteAdmin <http://www.lcsql.com/sqliteadmin.html>

On Tue, Jan 6, 2015 at 7:29 PM, Mark Wieder <mwieder at ahsoftware.net> wrote:

> Pete-
>
> Tuesday, January 6, 2015, 7:02:22 PM, you wrote:
>
> > On Tue, Jan 6, 2015 at 5:58 PM, Richard Gaskin <
> ambassador at fourthworld.com>
> > wrote:
>
> >> If a plugin is created with the Community Edition, it must use the same
> >> license the Community Edition uses, GPL v3.
>
>
> > OK, well if that's true, it puts a stop to my plan.
>
> I wouldn't worry about that. What Richard's saying would apply if your
> end-users were bundling your plugin with the stacks they distribute.
> Since your plugin operates wholly within the IDE in the developer's
> ecosystem there's no conflict.
>
> --
> -Mark Wieder
>  ahsoftware at gmail.com
>
> This communication may be unlawfully collected and stored by the National
> Security Agency (NSA) in secret. The parties to this email do not
> consent to the retrieving or storing of this communication and any
> related metadata, as well as printing, copying, re-transmitting,
> disseminating, or otherwise using it. If you believe you have received
> this communication in error, please delete it immediately.
>
>
> _______________________________________________
> use-livecode mailing list
> use-livecode at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your
> subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode
>