About any software stack for about any computer task involves at least some open source code running for you, written by someone on their free time, mostly out of pure altruism. I wonder how many dollars has this person contributed to, say OpenSSL, or to GnuPG, or to the GNU project, or to Linux, or to the Apache Foundation, &c.
If you dont want to respond to pull requests or to emails, just ignore them or dont put your code up on a platform that allows these. Publish release tarballs. Nobody's obliged to accept patches. But what this article tells is a merely a shortcut to making someone hard-fork your project. If I have to pay to get my patch upstream, well, I'll just maintain my patchset against upstream instead, if there are no alternative projects.
If you dont want to respond to pull requests or to emails, just ignore them or dont put your code up on a platform that allows these. Publish release tarballs. Nobody's obliged to accept patches. But what this article tells is a merely a shortcut to making someone hard-fork your project. If I have to pay to get my patch upstream, well, I'll just maintain my patchset against upstream instead, if there are no alternative projects.