So very (and unfortunately) true. However they also have no power to make you do the thing they need straight away, or ever.
> Even if you put hard work in it, you sacrifice a bit of your life.
And this is bad. We need to move the needle away from this. It is incredibly exclusionary
I am a younger person, no kids, in a job where I was able to negotiate for open source maintenance time. By making "sacrifice" a requirement it makes it off putting for someone with kids, or working in a job that has them working long hours, or working multiple jobs.
> But the user, well, they just are what they are, software can't fix that.
No, software can't fix it. but highlighting the problem, and letting people possibly see what they are doing is not useful may change the user.
I have been a maintainer of a project for a long time, and I get everything from people pinging me in our IRC channel, to DMing me, to asking if I give them my skype ID so I can call into a bridge to help them debug an issue at midnight. We need to highlight this is not OK.
Personally, I really like the PowerDNS rule for open source support [1] - it sets expectations, and the base requirements from someone looking for help.
> the success, at least to me, was measured by the number of users
That is a valid metric, but just one. I personally measured the success of the project based on what people were using it (e.g. I would rather wikimedia vs 20 startups), but that metric is really person specific.
1 - https://blog.powerdns.com/2016/01/18/open-source-support-out...