NotProton maintainer confronts influencer-backed fork Bridgeplay over macOS Wine sustainability; owner refuses to take down repo despite upstream's demands
retained text
On GitHub, the creator of NotProton asked the maintainer of Bridgeplay, a fork of NotProton, to stop distributing it because they believed it weakens the funding behind Wine on macOS. The owner refused to take the repository down. He kept it public, added a "Support Wine / Buy CrossOver" line to the README and website, and closed the issue as completed. The discussion is in [Bridgeplay Issue #79: "This should not exist."](https://github.com/raymondchins/Bridgeplay/issues/79) Running Windows games on macOS, especially on Apple Silicon, depends almost entirely on Wine. The main company funding full-time Wine work for macOS is CodeWeavers, which pays for it through sales of CrossOver and contract work such as Valve's Proton. When the Whisky project was discontinued, its maintainer said they did not want to take more than they gave or weaken CodeWeavers' ability to keep Wine going. NotProton, which connects native Steam to Windows runtimes, was built to require CrossOver for the same reason. Raymond Chin, an Indonesian tech influencer and entrepreneur, forked NotProton as Bridgeplay and replaced the CrossOver requirement with a free Wine engine built from source. He promoted it on social media: > Windows games on Mac? Done ✅ I open-sourced the most seamless free way to play Windows games on your Mac Steam. bridgeplay.dev, go star/contribute NotProton's creator opened Issue #79 with three objections: - A free alternative that skips CrossOver could cut the license sales that fund Wine on macOS. - The fork merged unreviewed work-in-progress PRs from NotProton that its maintainers did not fully understand. - The fork was an opportunistic "slop fork" built for personal branding rather than technical contribution. The maintainer wrote: > Stop. These slop forks are not helpful. They harm the Wine Project. The owner admitted he had pulled unmerged WIP PRs and acknowledged that the project depends on NotProton and CodeWeavers. He did not agree to stop: > Where I see it differently: Bridgeplay will stay free and non-commercial... I understand if you still disagree with that. He said the slop-fork argument would never be settled and that he would keep working on the project as an open-source side project. Commenters said the CrossOver line looked like a gesture while the request to stop was ignored, and that closing the issue ended the criticism. daudonhere wrote: > Stick to what you understand before lecturing others about open source. Your handling of this situation has exposed a serious misunderstanding of the ecosystem you're operating in. The main objections were that the fork kept being distributed after its upstream author said it harms the software it runs on, that sustainability was handled as a marketing item while the free engine stayed available, and that closing the issue ended the criticism while the fork kept benefiting from upstream work and the owner's personal brand. The case leaves some questions open. Does an upstream maintainer's request to stop distributing a fork carry weight, and if so, when should a fork comply even though the license permits it? Does a "Buy CrossOver" line actually address the sustainability concern, or is it only a partial step? And what do forks of niche developer tools owe the projects they build on, especially when they are promoted mainly as personal brands rather than as technical work? Issue: https://github.com/raymondchins/Bridgeplay/issues/79
document fetched 2026-10-24 10:39 · canonical https://reddit.com/r/opensource/comments/1xdrzt2/notproton_maintainer_confronts_influencerbacked