And the public opinion was really only against the dev because he was being intentionally difficult while the NixOS people were bending over backwards to look for a mutually-satisfying solution. It would have been a non-story if the dev hadn't been a bit of an ass in public forums.
As you described above, they damanded a conversation about why he was making the request he did. They couldn't just acknowledge that he had a request and choose to respect it or not when it was clear he didn't want to talk about it. Instead they dragged him into a huge spectacle. Even after they closed the issue on their side, (other?) NixOS people went to endlessly harass him on the home assistant forums.
[1]: https://community.home-assistant.io/t/consider-to-avoid-addi...
Personally, I probably would have sided with jtojnar that cited Debian’s policy to drop packages when the relationship to the upstream is beyond repairing [2].
[2]: https://github.com/NixOS/nixpkgs/pull/126326#issuecomment-86...
That is just a lie and not what happened.
They didn't demand a conversation. They continued a conversation. If he doesn't want to engage in discussion with them he shouldn't have.
> They couldn't just acknowledge that he had a request and choose to respect it or not when it was clear he didn't want to talk about it.
They were trying to arrive at a compromise. This is usually regarded as part of good faith negotiations. Trying to describe this as "dragging him into a huge spectacle" is quite shocking to me. Do you genuinely believe that if a person says "please do not distribute my package" the only reply to that thread should be one that says "we will remove it" or "we will not remove it" and then the thread should be closed?
> Even after they closed the issue on their side, (other?) NixOS people went to endlessly harass him on the home assistant forums.
I don't think this is an accurate description of that thread, but indeed, I think opening that thread was an example of poor judgement. A threat to make a certain library proprietary during a heated discussion is something that might be reconsidered or it might be a bluff. It should be confined to the negotiation unless it comes to fruition.
He may or may not have had reasons for making it MIT. There aren't really standard licenses for situations like this. Using a non-standard license has its own problems. He may not have anticipated getting the attention it did. Or whatever other reasons. I don't think it's necessarily easy to anticipate all future situations and codify them into a license ahead of time. He may change the license going forward as a result of this and that is fine too.
So, I think it's reasonable to suggest that "hey I can't maintain this software if you include it in your distribution because of the added workload".
Plausibly, but AFAIK this author (and certainly this package) has never received a bug report from a NixOS user.