How can we make Meld for macOS better?

[artmg]

First of all a very big thank you to @yousseb who has poured so much effort into this repo to give us all a chance of running Kai Willadsen's excellent Meld tool on a totally different OS. I pray for the soul of your brother Osama, Youssef, and for the family he has left in your care.

Like many here, I am grateful for the effort that has gone into developing this software, even though I sometimes get frustrated that it can be hard to keep up with the march of updates to the macOS system we run it on, due to the various ways that Apple attempts to protect its customers. I have started this thread to try and get a shared understanding of where development is at with this repo, and its upstream Also to see how willing community members could contribute to making the best, most stable and most easy-to-maintain way to run Meld on all Macs.

First of all, bearing in mind this repo's README has come straight from the upstream, please make sure you have read yousseb's own project home page at https://yousseb.github.io/meld/ – there you will get an understanding not only of how to best use the software in its current state, but also of how the maintainer sees this project in relation to the upstream. Also see the releases, showing not only that this project is definitely not dead, and that yousseb has done well to keep within just one feature version of the upstream. It also indicates ares where the community might be able to help out to improve packages and/or functionality.

So, where are we now? #143 asks if there is a plan for new version, yet release osx-20 shows that there now clearly is. Brew's reports of discontinuation now seem a little unfair.

Ok, where could things go next? In #149 @stlin proposed, and numerous others +1ed, to convert this project into an organisation and possibly add sponsorship. This could help to keep the current functional level working on macOS for a lot longer. However the upstream project continues to develop, currently 55 commits ahead. And they are well along the way towards an upgrade to GTK4, so the delta will only continue to increase.

The alternative suggestion was to Integrate the macOS port upstream. That would mean taking the smarts from this repo and applying them as a PR to the upstream repo. It would probably mean becoming part of the maintenance team up there, too, as the current devs don't seem to have Mac skills or equipment to develop or test. However, they seemed very open to Mac folk joining them. In the long run, that might make it a better outcome for the users who gave this repo 2k2 stars, as the new features just arrive in the mac build. I'm just not sure how that balances the development effort needed – supporting the mac build up there, compared with keeping up with features down here.

I'd love to hear @yousseb on which direction he would rather move in the longer term. Then perhaps if those who might be interested in participating are in agreement, I'd be happy to begin some minor PRs around the documentation, to make things clearer for users and to try and get through some of the issue backlog. I can also get involved in testing when pre-releases are available. To anyone else, what's your view and how could you help?