5 ms·
I’ve started thinking about it like there’s 3 kinds of people who I interact with in my opensource work: collaborators, customers and leeches. Collaborators co
by josephg 6y ago
I’ve started thinking about it like there’s 3 kinds of people who I interact with in my opensource work: collaborators, customers and leeches.
Collaborators contribute their time, energy and skill into the opensource ecosystem too - either by submitting good code to my project or donating their time to other projects I might reciprocally use.
Customers / benefactors make money using my project and pay me some of that money to keep the lights on.
Everyone else is a leech. They just want something for free and get irate when they get called out for it.
The trick with support requests / issues is they can be opened by anyone. You can tell the customers apart from everyone else easily, but is the person filing an issue looking to contribute in turn, or are they a leech wanting free support? A well written bug report is also a love note, after all. I still don’t have a good metric; but I’m definitely drawn to some filed issues more than others.
- einpoklum 6y agoI write Free Software. My users aren't leeches and I wouldn't insult them that way. (There are leeches who try to get you to solve their problems for them as opposed to reporting bugs, but that's a tiny minority.)
- josephg 6y agoI worked at a company a few years ago which (like everyone else) uses a software stack packed full of opensource code. There was a simple indexing service in our infrastructure which I designed so we could opensource it in turn. When it was ready, the legal team refused to let me opensource it and that was that. I felt really gross about that decision for awhile and it took me months to figure out why. My take now is that I was complicit in a parasitic use of opensource maintainers’ free support to fix issues we ran into. Despite that workplace choosing to never being part of the community, we pretended we were so we could get free support for our free software without giving back in any way. In retrospect I wish I’d pushed harder on the legal team. Or suggested we sponsor some projects as an alternative.
- loopz 6y agoA good bugreport and good followup on questions, is also collaboration. Those will only strengthen the code or documentation in some way. When people ask you to fix their problem, without providing any useful information or relevance to the software, it's hoping for free support. For companies offering free support, it sometimes makes sense to dive that deep into userland. For individuals you need a clear model what you're willing to do and how, as something that at first may seem fun and engaging, can quickly become too much and draining over time.
- noir_lord 6y agoI'd say it's more Collaborators, Customers, Users and Leeches. Depending on the project I fall into one of the first three, I might send a PR, I might suggest we buy/pay a maintainer or I might just be using your library as a dependency of a different package, I'm never the last one.
- ddevault 6y agoWell put - I'm going to start using this analogy myself. The only people who matter to a project are contributors and customers, and mostly the former. A smart maintainer invests 100% of their energy into this group, and 0% into the leeches. The software will obviously be better if you invest your time and energy into the needs of people who give back to the project.