That was lucky. I would not bank on being equally lucky with each new issue discovered going forward.
To "steal a march" from anyone isn't an interesting goal to me, and likely not relevant to them or their subscribers.So an OXT build that runs on MacOS 14 now would steal a march on our friends in Scotland.
Most of their current subscribers make proprietary apps, something any GPL governed work cannot do.
The enterprise uses with internal apps can benefit from a FOSS edition, but in my conversations with some of them I see a clear pattern: LC was introduced into their workflow many years ago, and even where it's still adding (sometimes significant) value it's scheduled for replacement with something more "industry standard", something with more dev resources available than the handful of remaining LC consultants, and/or simply a better fit for evolving business needs. Many of these re-implementations are underway right now.
A FOSS xTalk matters to an audience larger than the members of this list to the degree that such an audience can be reached, and that the project can demonstrate long-term viability with fresh engine builds to keep current with the ongoing changes from OS vendors.
This means both marketing and dev budgets.
And donations are hard to come by without grants and tax deductions, both available to a 501c3 nonprofit. But setting up and maintaining a corporate shell for this as a sort of OpenXTalk Foundation is a lot of work.
Running though a some back-of-a-napkin numbers several weeks ago, I'd estimate that establishing such a foundation would take a crowdfunding effort of at least $180k for the first year. Subsequent years would need to become self-sustaining through ongoing grant and fundraising efforts.
Long-term sustainability of a million-line code base is not a simple problem to solve.