Sure, but saying "I won't merge this because I don't want my software to be compatible" seems to be strange. Would you not accept say changes to your Makefile to support BSD or Windows or Linux?
It depends. Trying to avoid being compatible with Systemd would be strange. Simply not valuing at all -- if it works, that's okay, but you won't add any Systemd-specific code -- is a different thing.
Simply not valuing at all -- if it works, that's okay, but you won't add any Systemd-specific code -- is a different thing.
That's a fair stance to take if you're just a group hackers hacking away on this cool open source project in you free time. It's a very bad look when you're trying to present yourself as a serious company that other serious companies can depend upon for some of their most critical infrastructure components.
If it is some obscure compatibility we are talking about, I can understand it. If it is a defacto or official standard, then no. Regardless of whether I use Systemd or not (my primary OS uses launchd...), its usage in Linux distributions is currently widespread.
Not wanting to develop compatibility yourself, I can understand. No discussion about it.
Not wanting to include compatibility PRs is a recipe for hostility, and ultimately, a fork. There's a nuance here that it could lead to a lead dev importing PRs for software they don't use or understand but other than that, it seems the way to go if you want an inclusive and gentle environment.
