LiveCode can’t use your contribution without the CLA. Someone from LC May need to clarify the details. Since they release code as GPL and Commercial, we need to assign copyright to them for any changes we make and also assert that we are not introducing code where we are not able to assign said copyright.
As long as GitHub can’t verify the CLA, I don’t think the PR can move forward. Thanks, Brian On Jan 20, 2019, 12:17 AM -0600, Geoff Canyon via use-livecode <use-livecode@lists.runrev.com>, wrote: > On Sat, Jan 19, 2019 at 8:22 PM Brian Milby via use-livecode < > use-livecode@lists.runrev.com> wrote: > > > I agree that the dictionary isn’t the easiest to update without a GutHib > > client, but dictionary updates can be done completely in a browser. > > > Yep, I figured that out after I spent several minutes looking for the > dictionary data and poking through the dictionary stack. I already cloned > LiveCode some time ago, and GitHub was smart enough to realize that even > though my clone is substantially out of date, the merge entry hasn't > changed. So all i had to do was find it, edit (my copy of) it, save, and > issue a pull request. > > And then notice a few minutes later that LC was asking me to sign the > waiver and tie my accounts together. I've done everything but that last > bit, so we'll see what happens. > > gc > _______________________________________________ > use-livecode mailing list > use-livecode@lists.runrev.com > Please visit this url to subscribe, unsubscribe and manage your subscription > preferences: > http://lists.runrev.com/mailman/listinfo/use-livecode _______________________________________________ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
