To new people coming in - How to help or contribute

The purpose of this topic is to create a little guide for new people joining this platform. I may be wrong in some of what I write, so to those who have a better understanding: Please correct this or just rewrite, I do not own anything.

HyperXTalk is actively being worked on on GitHub here:

It is not technically a fork of the LCC codebase, LiveCode Community 9.7.0-DP-1, discontinued and archived on August 31, 2021:

The HyperXTalk project starts with a copy of the old code, but has seen quite some changes already - just go to GitHub and have a look at them anytime. Note that the IDE code has been moved into a new folder inside the now single repository. The old code passes on its GPL license of course, it will be valid for our codebase as well.

The clean cut makes this effort different from the situation in the past few years. The cut is a necessity as otherwise people who are already connected to the old repository would not be able to contribute to HyperXTalk, which is a new take at a community-led and code-managed continuation of xTalk and LCC legacy, one that also offers downloadable binaries directly derived from the code seen in its repository. As proof has been made recently that the old code can be revived and compiled for all current desktop platforms we should take the next step and see that a) this can be done from a shared repository and b) it can be continued to be done, as structured and documented as it can get. HyperXTalk should become the community reference location and the place to go for the future of this code. Please join!

These forums will focus on discussion of this effort. There is a website in the works (see related topics here). Both sites will serve to reflect the status of the project but are still in their infancy. Please be patient or even better - help.

To all people who have contributed to LCC code over the years or have worked with the codebase and implemented valuable changes in other ways, please note:
Stale pull requests against the old archived codebase if still relevant could become alive again and are very welcome here, but would have to be manually recreated.
This is true as well for all changes created and maintained outside of GitHub - we need such contributions to be entered in GitHub somehow.
The community present here wants to help the integration of everything that pushes the codebase forward, so if you want support in getting such things across, please let us know.

The first objective of HyperXTalk is to get rid of all the original branding (as the original authors strictly wish to have it this way), to squish bugs or out-dated code in all of its components, starting with the compilation scripts and instructions. Once this is done for all the platforms it runs on, there can be better discussion of where to go in the future.

To all people not having forked any old LCC code on GitHub before: Your situation is easy. In case you can contribute please fork the HyperXTalk repository referenced above now, write pull requests, join the effort! Any kind of help is greatly appreciated.

1 Like

Yes please. Any help in removing the old branding (I think I got it all) as well as the old licensing system (still lots of work to do in that department). Documentation clean-up as well. If you want to help, but don’t know where to start, feel free to ask.

GPL enthusiasts may prefer “inherited” over “infective”.

It’s a feature, not a pathogen. :blush:

Some would argue with you :wink:

1 Like

:rofl: Thanks guys. @FourthWorld Good catch, I rephrased. :face_blowing_a_kiss:

Ah - do we have a non-fork fork of the IDE repo as well? I could add that link.

1 Like

The IDE is in the repo in a folder called “ide” :wink:

If there ever was a real “hidden gem”, then this is it. :grinning_face_with_smiling_eyes: I added the information in the text, thanks!