Absolutely and I think the author should have concentrated on that future-deliverables aspect rather than the 'what you owe to Caddy' argument.
The latter is emotionally strong but logically frail; as the author himself points-out he depends on Go and Let's Encrypt ( amongst many other 'free' projects I'm sure ) so will he be making a 'what I owe to you' contribution upstream to all those projects? He won't have much money left after that let alone paying the voluntary cost of a Github Enterprise account, of course, because otherwise someone else is paying for his use of that service...
Spinning the request as a support-contract for ongoing bug and security fixes would not only have been more business-friendly but also more robust as a general appeal.
> There's no such thing as free software.
That's a hyperbole.
He also says
> The question is, "Who pays the price?"
Not everything is done for gain. When someone gives you an apple you're probably not that concerned about how it came to be, to you that apple is free. But there's also that added advantage of software - you can copy and share it just like that with the whole world.
I do agree with patio11 that it's easier to just have a real support contract. IMO, one of the model open source projects is Sidekiq. It's become a very sustainable business for its author.