9 ms·
If you are relying on unpaid open source code for commercial work, you should fully understand what that means for you: > This software is provided 'as-is', wi
by account42 4y ago
If you are relying on unpaid open source code for commercial work, you should fully understand what that means for you:
> This software is provided 'as-is', without any express or implied warranty. In no event will the authors be held liable for any damages arising from the use of this software.
(from the zlib license, but others have similar disclaimers)
If that is a problem for you, negotiate a different contract up front - with the maintainer or someone else willing to do the work. That probably means paying them.
If you don't then no, the maintainer is not required to invest the time and money you are unwilling to into maintaining your pet feature or "fix".
- danwee 4y agoYou are right, but in practice that's not what happens. Companies do not rely on open source libraries, the developers working for such companies do. I can give you a realistic example. If you want to use Kafka and Go, your probably only option is to use https://github.com/confluentinc/confluent-kafka-go https://github.com/confluentinc/confluent-kafka-go. Its LICENSE explicitly says "no warranty". Now, what if I find a bug in the library? Only two realistic solutions from my side: 1. I submit the issue and hope for the maintainers to fix it 2. I dig deeper and try to fix the issue. I submit the PR None of the above scenarios are guaranteed to have a happy ending. The issue could be ignored, or piled up among thousand of other (maybe higher prio) issues. My solution may not be optimal and could be rejected (or if it's optimal, nobody is taking a look at it, and it could remain open for weeks/months). > If that is a problem for you, negotiate a different contract up front - with the maintainer or someone else willing to do the work. That probably means paying them. In the real world that would mean that I go to my manager and asks them to pay money to the maintainers of confluent-kafka-go to fix the issue I found. I don't think my manager would approve that, but let's imagine he does. The guys at confluent-kafka-go may not want money to fix the issue. These guys have probably already jobs that pay them well, and they work on the library at will. Note: I'm talking about confluent-kafka-go, which I know is behind the Confluent software company. But I could as well be talking about libraries maintained by individuals like https://github.com/edenhill/librdkafka https://github.com/edenhill/librdkafka
- 2muchcoffeeman 4y agoBut then it’s too bad right? Why should the maintainers care?
- ricardobeat 4y agoBecause you release open source software to help others, in the same way others have helped you with theirs. Where has all the empathy gone?
- deleted 4y ago[deleted]
- zaphar 4y agoI sometimes release software under an OSS license. I sometimes take patches from people. Other times I reject them because it's not the direction I want to take the project. I sometimes use software under an OSS license. Sometimes I submit patches for fixes and they get accepted after appropriate amounts of reviews. Sometimes I maintain an internal fork for years before my fix lands. Sometimes I choose a different solution because my projects needs no longer align with the software's direction. At no point do I ever think it's a great idea to bully an OSS maintainer into my way of thinking. I have all kinds of empathy for both groups but the rules of engagement here are very clear and anyone who thinks they should be different is just going to be hurt in the long run.
- lanstin 4y agoI release open source software so other people can use my work if it would help them help themselves. The code took some work and its nice for it to be known, but i dont have time to help anyone with anything, what with a corporate job and kids. the people expecting more seem to be saying it would be better not to release code that one has no intention of helping people with, but that world is strictly worse.
- ricardobeat 4y agoNote that the baseline being discussed here, and in the article, is accepting a patch, not writing a bug fix or new feature yourself. If every bugfix mandates a fork, the whole ecosystem becomes impossible. So the answer to you question is yes: unless you explicitly label something as a research project, one-time release, no patches welcome, we’re better off without it in the long run, as the sea of dead npm packages shows.
- stupidcar 4y agoAs I said, as a developer working on a software project for your employer, you often inherit dependencies you had no say in. Nor can you force your employer to negotiate a contract with the maintainer. Don't get me wrong: I'm not arguing the maintainer has any responsibility to fix your issue. I'm only saying that the situation for the developer facing the bug is not always as simple as the article implies. Their choices are constrained by factors outside their control, and they are under pressure to deliver. It's this pressure that explains some of the frustration and anger that can bubble up in open source discussions. I don't think there's an easy solution, but more empathy on all sides might be a start.
- hypfer 4y ago> As I said, as a developer working on a software project for your employer, you often inherit dependencies you had no say in. Well y'know... you're kinda being paid for that. That literally is your job. You're given money to deal with that. It is not a matter of "empathy" for a FOSS maintainer to do your job for you.
- hampereddustbin 4y agoIf commanded, sure, but in many cases your job would actually be to communicate the changing environment to management so they may allocate more resources or pay the maintainer or whatever middleman company to upkeep the required software. Silently trying to plow through problems of these magnitudes will cause the project to be late and still cost the same. It's bad for everyone
- marcus_holmes 4y agothis. As a dev, this is not your problem. If you had a dependency forced on you, and that dependency has issues that the maintainers are not willing to deal with, then escalate the problem to your manager. Of course, if you included a dependency because you thought it was a good idea, and it turns out to not be a good idea, then that's a different problem. You'll have to let management know that you'll need some time to refactor the code to remove the dependency. That could be a difficult conversation, but the answer is still not "hassle the maintainer to fix my problem"
- deleted 4y ago[deleted]
- MuffinFlavored 4y ago> If you are relying on unpaid open source code for commercial work, you should fully understand what that means for you: I don't want to say "easier said than done" but... imagine doing `npm install` for like... Webpack, React. Start adding a few React related libraries You're talking exposure to... hundreds (thousands) of "free" open source projects. Obviously nobody owes anything to anybody in terms of "let me dedicate my free time away from my family/friends/my other hobbies/my personal sanity" to make sure the package I publish online is as perfect as possible. It just gets muddy/gray. Is there a sense of entitlement for the unpaid generosity of library providers? Almost surely. "You published something, it got popular, now you are telling everybody who needs help fix it yourself or f*ck off". It's just a weird source of conflict. People publish packages hoping they get used/become popular. Then they got popular and get overloaded by issues/requests and either embrace it or get combative.
- tremon 4y agoThis software is provided 'as-is', without any express or implied warranty You're creating a distinction where there is none. Commercial software has the exact same disclaimer.