In the business world, picking a different name for marketing and using functional elements for compatibility is a good way to get sued but win. See, for instance, Sega v. Accolade - Accolade sold software for the Sega Genesis without Sega's approval. Sega added something to the Genesis game loader which checked for the string "SEGA" and displayed the message "Produced by or under license from Sega Enterprises LTD." Accolade's games caused that message to appear, even though there was no license. The courts ruled that Accolade was entitled to do this, because the point was compatibility.
It's interesting to see the instance of HN groupthink speculation (and lack of google fu) there has been in this comment section. Folk should come idle/chat in #lad. It's available via Matrix.
Fork the project and pick another name. Spend the effort to market and build the integration with the new name. No one would have a problem.
I think it should be clear to anyone the relationship; the README mentioned JML from the get go, it's not framed as NON related, there is reference client and daemon, and it's just the same acronym because there's no reason to change.
The new projects name is New Session Manager.
Using the same acronym and the same binary file names to push out Non from the distribution is very underhanded.
This looks like a deliberate aim to confuse the users and taking over the project code and identity. It's not cool.
I don't know JML and don't know his development style. Since he has been gracious enough to open source his project, I assume he's generous enough to share his hard work with others. If people don't like his style, fork the project with a different identity and compete on the merits, rather than stealing his project's identity with confusion.
You are trying to argue a course of action that would just have confused both users and devs.
In the business world, this is a clear case of trademark infringement and they would be sued out of existence.