Regarding PR and paying, people fork the code and make the changes they need.
They send PRs to avoid merge conflicts in the future. i.e it is in your best interest to get your code merged.
You are not obligated to send PRs. You can fork and let it sit there.
Regarding community management, past a certain scale you should charge for it. People often feel entitled and will waste your time instead of reading doc.
Majority of OSS projects rely on a handlful of individuals; often 1 or 2 people handling everything.
I completely understand the spirit of this.
OSS is not charity or altruism. Share your code out of self interest (e.g contributions, forks, bug detection etc.) If you get nothing out of it, unsubscribe from notifications.
You are not obligated to send PRs. You can fork and let it sit there.
Regarding community management, past a certain scale you should charge for it. People often feel entitled and will waste your time instead of reading doc. Majority of OSS projects rely on a handlful of individuals; often 1 or 2 people handling everything.
I completely understand the spirit of this.
OSS is not charity or altruism. Share your code out of self interest (e.g contributions, forks, bug detection etc.) If you get nothing out of it, unsubscribe from notifications.
You don't owe people your time, skills, energy.