Hi Everyone,
I'm potentially contemplating a switch from my current Standard Plan to a Create Standard Plan but wanted to know what the state of licensing is for open source developers, the intention is to develop my apps, open source them under the MPLv2 and last I remember, Create wants to put an ad banner in at start up. Is that still the case or is it fine for an About dialog to have a mention of LiveCode Create being used, I'm already using that as an option to state I'm using Icons8 for graphics.
Mike
LiveCode Create Licensing for Open Source Developers
Moderators: FourthWorld, heatherlaine, Klaus, kevinmiller, robinmiller
-
- VIP Livecode Opensource Backer
- Posts: 246
- Joined: Tue Jun 30, 2009 11:15 pm
Re: LiveCode Create Licensing for Open Source Developers
To be sure, ask Heather: support@livecode.com
-
- VIP Livecode Opensource Backer
- Posts: 10043
- Joined: Sat Apr 08, 2006 7:05 am
- Contact:
Re: LiveCode Create Licensing for Open Source Developers
The Create EULA is very different from previous licenses, well worth reviewing in detail. LC Ltd makes it available for review here:
https://future.livecode.com/eula/
I've not used MPL professionally so I have no opinion about its compatibility with any of the LC licenses currently or previously used.
One question that had come up before the period in which LC delivered an open source version under GPL v3 (their maintenance on that edition was discontinued Aug 31, 2021) was the compatibility, in principle and in practice, of delivering stack files which may be under open source license but which can only be run within an engine environment governed by proprietary license.
And that was for tools and other software aimed at delivery as stack files, separate from the engine.
If the work delivered in your case is a standalone executable, the terms of the two licenses become more deeply commingled. Even if MPL may impose no limitations on such mixed use as a matter of principle, in practice there may be details in the terms which inhibit distribution and/or contribution.
Given the scope of changes in the new Create EULA, careful review will give you a sense of usage rights and responsibilities, and hopefully your own experience with MPL and your goals for the project can help you determine fitness for your project.
If you have specific questions after reviewing the Create EULA I'd be happy to help find answers which may affect usage and contribution, with the understanding that I'm not a lawyer and nothing I write can be construed as legal advice. But as an Ubuntu contributor for more than a decade, and having served as the LC Community Liaison during the LC open source years, I have a personal interest in furthering open source projects and would be happy to help where I can.
And as Klaus noted, the best source for questions specific to terms in LC licenses is from the copyright holder, reachable at the support address he provided.
https://future.livecode.com/eula/
I've not used MPL professionally so I have no opinion about its compatibility with any of the LC licenses currently or previously used.
One question that had come up before the period in which LC delivered an open source version under GPL v3 (their maintenance on that edition was discontinued Aug 31, 2021) was the compatibility, in principle and in practice, of delivering stack files which may be under open source license but which can only be run within an engine environment governed by proprietary license.
And that was for tools and other software aimed at delivery as stack files, separate from the engine.
If the work delivered in your case is a standalone executable, the terms of the two licenses become more deeply commingled. Even if MPL may impose no limitations on such mixed use as a matter of principle, in practice there may be details in the terms which inhibit distribution and/or contribution.
Given the scope of changes in the new Create EULA, careful review will give you a sense of usage rights and responsibilities, and hopefully your own experience with MPL and your goals for the project can help you determine fitness for your project.
If you have specific questions after reviewing the Create EULA I'd be happy to help find answers which may affect usage and contribution, with the understanding that I'm not a lawyer and nothing I write can be construed as legal advice. But as an Ubuntu contributor for more than a decade, and having served as the LC Community Liaison during the LC open source years, I have a personal interest in furthering open source projects and would be happy to help where I can.
And as Klaus noted, the best source for questions specific to terms in LC licenses is from the copyright holder, reachable at the support address he provided.
Richard Gaskin
LiveCode development, training, and consulting services: Fourth World Systems
LiveCode Group on Facebook
LiveCode Group on LinkedIn
LiveCode development, training, and consulting services: Fourth World Systems
LiveCode Group on Facebook
LiveCode Group on LinkedIn