On 9/9/21 7:18 AM, Mark Waddingham via use-livecode wrote:
> We (LiveCode Ltd.) cannot take any code changes you make to your
project's version of the LiveCode source-code and use them in our
commercial code as (by default) it will be GPLv3 licensed, and the
copyright of that will be held
Thank you very much for the info and advice Mark, very much appreciated.
This is all entirely new ground for me and so I may make mistakes going
forward, just let me know and I’ll do my best to correct them ASAP!
I hope certainly hope anyone else trying to do anything with the legacy code
base
On 2021-09-08 22:54, Paul McClernan via use-livecode wrote:
I've already fixed a bug that I reported back in April in my fork(s)
and
added a link to my fix to that bugzilla report.
https://github.com/PaulMcClernan/LiveCodeCommunity-IDE-DontPanicEdition
At this point in any changed
Just as a way of showing off my goofiness: how do I compile LiveCode
from your github downloadables?
On Thu, Sep 9, 2021 at 12:55 AM Paul McClernan via use-livecode <
use-livecode@lists.runrev.com> wrote:
> Well I've wanted to contribute more, and have as time allowed. I first had
> to learn how
Well I've wanted to contribute more, and have as time allowed. I first had
to learn how to use GitHub before I could even start to contribute, and did
appreciate the hand holding I got from the team along the way. But
understand that LC needs to be very careful and methodical about what they
Yes - I agree with the reasons mentioned for difficulty getting contributions.
I have some faith in new opportunities, and I personally would invest in
growing and maintaining some aspect of an open source strategy - particularly
around the server.
I would have thought that having an open
That’s true Mike and I’ve looked into it for my own benefit from time to time
over the years. What I was suggesting was some formal support from the company
to facilitate contributions to the IDE going forward. I never attempted much
in the IDE because I’m not comfortable with my
You could always get at the IDE. You still can. Hopefully that won't
change, because there are plenty of times where something is broken and it
takes forever to get it fixed.
On Wed, Sep 1, 2021 at 9:37 AM Timothy Bleiler via use-livecode <
use-livecode@lists.runrev.com> wrote:
> I’m afraid I
I’m afraid I have to agree with Andre that if people didn’t contribute before,
with Livecode Ltd. overseeing the process, they’re not going to now. A large
part of the problem is that there just aren’t very many of us with the time and
skills to make contributions to the engine.
Like Sean,
I'll refer again to the Firebird project. One of the ways they were able to
build on this opensource project was that as a community they employed and
funded programmers (mostly in Russia, if memory serves) to add the features
the community wanted. So one way or another FOSS projects end up
The main reasons I stopped contributing were:
No easy support for LiveCode script as it was all in binary so versioning
was non-existent.
Life cycle between a pull request, merge and deployment
The dictionary was the only place I was able to properly contribute. But it
still sucked a lot. And was
People had eight years to contribute to the community edition, and they
didn't. I don't think people would now start caring for and devoting the
necessary energy to maintain the community edition. It is because people
didn't organise and contribute that this recent change happened.
On Wed, 1 Sept
Here are my thoughts on this - and a request.
Yes - it’s not a surprising move by Livecode Ltd - they were clearly struggling
supporting the community aspect and taking the language to the next level and
they need more revenue to do that.
The question is (for my part at least) - what to do
13 matches
Mail list logo
