Post

❓"When can we expect this feature" Please refrain from asking this question towards open source maintainers. You generally shouldn't "expect" anything. I don't often agree with DHH but his take on OSS being a gift, not something you're entitled to, is something I relate with.

9 reposts81 likes

Yes, people are so demanding at times it really grinds my gears. If you care enough, isn’t it your problem not mine to solve? I clearly built the project and haven’t needed it until now, so why do you expect me to build something I don’t need?

I bump into some strong senses of entitlement on my OSS projects from time to time. I usually point them out, even though I feel a bit preachy Fwiw sometimes people seem genuinely apologetic, and I chalk it up to a language/communication issue

As a non-maintainer I totally agree, but what happens a lot to me lately when trying to contribute through bug fixes, is that I'm the one being ghosted. What is your take on that? Am I entitled to feedback from (active) maintainers after I've put in time and effort into the issue and fix?

Entitled is a strong word, but maintainers generally try to get through notifications on their own time. There's likely going to be an answer, but it could take weeks for various reasons. Sometimes things fall through the cracks so it's okay to ask again after some time.

For example I have ~ 100 GitHub notifications (already deduped so it's 100 different issues / discussions / PRs) to look at because I didn't get to do anything for 3 weeks: work, life, other priorities etc. It just happens and the last thing I'd need is someone getting angry because it takes so long

Dominik 🔮@tkdodo.eu

😔 I apologize for being quite behind on my open source work. I haven't had the time to do anything in weeks. My inbox is about to overflow, and there are so many issues, PRs and discussions I want to look at. 🎄 As things go quieter over the holidays, I plan to ramp up and get some things done 🚀

Getting angry is inexcusable! Thats exactly why every time I write a follow-up comment, asking for feedback, in an issue that hasn't been answered for weeks, I ask myself this question. The last thing I want is to put pressure on the maintainer, but it's often difficult to formulate it that way.

I feel like it should be mandatory that every dev has a repository with at minimum 200 stars to learn what it’s like to maintain OSS on some scale. Help develop that sense of empathy when people open issues and ghost or act all entitled.