Part of the agreement that you make when you submit a PR is that you assign rights for the fixes to LC so the code can be integrated into the commercial versions. You can’t mix the code on GitHub with the commercial versions yourself though.
I have submitted stuff that is now in released versions, so they do accept contributions (and not everything was strictly bug fixes). Thanks, Brian On Oct 3, 2019, 1:48 PM -0400, Erik Beugelaar via use-livecode <[email protected]>, wrote: > Does anyone know if you fork the Community Edition of LiveCode, solve bugs > (e.g. IDE-related, plugins etc.), compile the LC version again and integrate > it to the Indy version? > Or is this just not possible because of the closed source of the engine? > > On 03/10/2019, 18:16, "use-livecode on behalf of Mark Wieder via > use-livecode" <[email protected] on behalf of > [email protected]> wrote: > > On 10/3/19 8:47 AM, Trevor DeVore via use-livecode wrote: > > > > All true. But will the idle state of LC ever change again? > > > > > > > I believe that it will if LiveCode FM gets traction. I may be wrong. > > Additionally, the patch that Mark Waddingham just implemented related to > the frozen pool (I am the walrus?) affecting debugging is encouraging. > > -- > Mark Wieder > [email protected] > > _______________________________________________ > use-livecode mailing list > [email protected] > Please visit this url to subscribe, unsubscribe and manage your subscription > preferences: > http://lists.runrev.com/mailman/listinfo/use-livecode > > > > > _______________________________________________ > use-livecode mailing list > [email protected] > Please visit this url to subscribe, unsubscribe and manage your subscription > preferences: > http://lists.runrev.com/mailman/listinfo/use-livecode _______________________________________________ use-livecode mailing list [email protected] Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
