With many (most?) free software projects, implementing it and getting it to a stable working condition is only a fraction of the overall amount of work invested

With many (most?) free software projects, implementing it and getting it to a stable working condition is only a fraction of the overall amount of work invested over time in maintaining the thing. Compilers change, system libraries change, operating systems change, build systems change, language standards change and so on - and you, who just wanted to write, say, a DHCP server you or your organization needed at some point in life, tear yourself away from your day job, your family, your current pursuits and interests - which have likely not included fiddling with that old piece of code you wrote all those years ago - and bringing it in line what the current state of things. Sisyphic work, which is usually rewarded mostly with complaints about why the thing is not up to date. "But they only just broke it! Do you expect me to spend my time also anticipating what infernal subtle ways the rug is going to get pulled from under me?" ... but you never tell people that. You dutifully write your fix and re-publish (which can also be a bunch more work, since the platforms for publishing your FOSS project also change). I salute you, Roy Marples! (and I donated.)