4 ms·
My general advice on this is to never rely on other people reading your mind. It's a path to frustration for you and the other people. In this article I see a
by jmull 4y ago
My general advice on this is to never rely on other people reading your mind. It's a path to frustration for you and the other people.
In this article I see a lot of phrases where OP is hoping other people share the same perspective. Like, "Hopefully we agree that...", "I want to argue here...", "Users... shouldn’t expect..."
It's just not going to happen like that automatically, though.
I suggest that if, as an open source author, you're seeing seeing potential for broad usage of your project, spend some time to think about what you're willing (and able) to give, and make an explicit statement to that effect (and put it somewhere that potential new users will see it).
I suggest that if you're considering using an open source project in something, spend a few minutes to think about what you will do if you get no more support than what is explicitly promised and/or paid for (which means no support in most cases). If that's not acceptable for your project, then don't use it.
(Oh, and sadly, I think this the purpose of this article is a bit hopeless. I think there are thoughtful people that will read this and take it to heart, but those people are probably only causing a tiny fraction of the unpleasantness that open source maintainers experience.)
- jacobtomlinson 4y agoAuthor of the article here. Thanks for this comments, really great points and sadly I agree with everything you’ve said. Although I would say many projects snowball into something bigger than the creator imagined so upfront planning about how much time you can put into something is hard. I wrote this post with the intention of directly sharing it with folks in issues when situations flare up from time to time in the projects I work on. I never imaged it getting shared on HN.