5 ms·
This attitude is horrifying to me. As both a project maintainer and a contributor, this is part of the toxic new attitude that has resulted in me no longer spe
by freedomben 6y ago
This attitude is horrifying to me.
As both a project maintainer and a contributor, this is part of the toxic new attitude that has resulted in me no longer spending my valuable time opening bug reports against projects. If my hard work is going to be looked at as an insult or entitled request, go to hell. That sort of rudeness is shocking to me.
In projects I maintain, I get my share of spammy low effort requests and I ignore them or reply with a polite "Need more info" or "no time for now". It's not really that big of a deal.
For other projects that I use and appreciate, I have also spent hours before gathering useful debug information, only for it to be completely ignored. If I spend hours building a nice report for you and you won't spend 5 minutes reading it and two minutes responding with "sorry but I'm too busy" then who is the entitled one here? Further for you to look at it as an insult?
I rarely even send PRs these days because those often rot for months or years.
This is not a user problem, this is a people problem. Please people, lets make these types of people into the minority in open source. Please, let's give each other the benefit of the doubt. Let's appreciate effort on both sides. Don't be a doormat, but don't lose your humanity either.
In short, let's be great to one another.
- julianmarq 6y ago> If I spend hours building a nice report for you and you won't spend 5 minutes reading it and two minutes responding with "sorry but I'm too busy" then who is the entitled one here? Further for you to look at it as an insult? You? The other maintainer didn't ask you to do that. You're not entitled to even a minute of another person's time just because you unilaterally decided to dedicate hours of yours on something. > I rarely even send PRs these days because those often rot for months or years. Mind you, I've rarely sent PRs, but when I do, I do it with the intention to help. Only around half of the PRs I've ever sent were merged, and most of the others were left open without review. You know what I think about them? Nothing, I just conclude that the maintainer is probably too busy or my proposed changes are not within the goals of the project. I then move on and don't let it eat at me. > let's be great to one another. I think that includes giving other maintainers the benefit of the doubt. That includes not taking being ignored as a personal insult, I think.
- gpanders 6y ago> You? The other maintainer didn't ask you to do that. You're not entitled to even a minute of another person's time just because you unilaterally decided to dedicate hours of yours on something. This is just basic human decency. If someone puts in effort to help you or contribute to something you've created, just be a decent person and respond to them. It costs you nothing. There's a difference between being entitled to something and just doing something because it's the right thing to do. No one is entitled to my gratitude because they hold the door open for me. I didn't ask them to do that. But I say "thank you" anyway because it's the right thing to do and the world would be a worse place if we were all assholes to each other always worrying about what we are and aren't "entitled" to. This is the whole spirit of open source software. If you don't want to be bothered by other people putting in effort to collaborate with you, then don't make your project open source, or just keep it closed to issues and PRs altogether.
- freedomben 6y agoThank you, very well said. That example was exactly the kind of thing I had in mind. If we just extended the same human decency that we all do in meat space to cyber space, these things wouldn't be problems.
- throwaway413 6y agoThe problem is, people are no longer extending these basic human decencies to one another in even just meat space.
- Retric 6y agoIt’s got nothing to do with basic human decency. A maintainer is donating their time to a project and can work on whatever they feel like. It’s perfectly reasonable to not include any contact information whatsoever or simply stop paying attention when people try and contact them. OSS isn’t some ongoing obligation, and can freely be ignored for months or years at a time. If you’re not happy, feel free to fork the project.
- gravypod 6y agoSomething that I wish more people did when they don't have the time to do a bunch of debugging for an issue they don't experience is dropping a pointer for others. If the response was "I don't have time to work on fixing this. If you wanted to fix this I think it would be in $package and maybe $file. You can create unit tests for this in $place". Or even better "I've added a unit test into master as ignored that is failing right now, if someone can step through and debug this I'd merge it". It takes a lot of energy but it's a great way to create a community.
- wildmanx 6y agoI agree that it's bad. But not because the maintainer is an asshole. It's because the maintainer doesn't understand the real leverage he has when doing open source. So it's actually more sad than bad. Bad for him, in fact. When you write something to solve your problem (which he correctly states), then publishing it "for free" just because the mere act of doing so comes at almost no cost and even consider it as some kind of philanthropy ("You are welcome, by the way"), that's all really missing the point. Of course you are free to do that, but you are really missing out on the big lever the open source approach hands you. And that lever is that other people come and help the maintainer _for f*ing free_. They encounter a bug and report it -- that's free labor right there! They help him make his software better by pointing out a problem that he likely overlooked. And they help him document problems for other users to be aware of. And often times they help him by providing a patch or a suggestion. They do all of this for free. That's the whole point of open source. Not providing some piece of software for free. That was there already with "Freeware". But the real power comes from the lever. Put it out in the open and have the whole world help you. Linus Torvalds understood that all too well, and still does. He's not a philanthropist. He's pretty rude and selfish (he admits that about himself), and that's exactly why the open source approach worked so well for him.
- jitendrac 6y agoTotally agree. In fact,I do think of Linus Totvald,as a really great maintainer of project. he clearly know when to say no, and when to criticize someone who needed to be. people should read some of his reply in mailings, some of them are gems of communications.
- CaptArmchair 6y agoThat depends entirely on the intention with which an author decides to publish their code as open source. That intention could be to forge an active connection with a community of users, or it could simply be to just get it out there to anyone's benefit, rather then have it gathering dust in some private git repository, with no further engagements or obligations on the author's part. The open source license included with the code doesn't say anything about the author's intentions at all. > That's the whole point of open source. The whole point of adding an open source license to your code is to share code with others with virtually no strings attached. That is, neither from the user's side, but also from the author's side. Everything else is just custom and market dynamics. > Linus Torvalds understood that all too well, and still does. He's not a philanthropist. He's pretty rude and selfish (he admits that about himself), and that's exactly why the open source approach worked so well for him. When Linus decided to push the GPL on his code, he couldn't possibly predict or foreshadow that his little hobby project would end up being this successful. His original intention was simply to gather as much feedback as he could to improve his project. In fact, it would take until version 0.12 before he'd add the "GNU copyleft" license. And that's only after some people pointed out to him "Have you considered adding a copyleft license?" [1] [1] https://mirrors.edge.kernel.org/pub/linux/kernel/Historic/old-versions/RELNOTES-0.12 https://mirrors.edge.kernel.org/pub/linux/kernel/Historic/ol... The open source approach worked well for him because it facilitated the spread of Linux towards key people in large public institutions and commercial organizations for whom Linux simply, accidentally happened to be a good, cost effective fit. Linux was released in 1991 and barely a few years later, with Dell, Red Hat, IBM offering commercial support and Red Hat and VA Linux having IPO's around 1999. Linux wasn't just successful because "open source". It was successful because it turned out to be the right product at the right time at the right place. And that's what really drives development.
- underdeserver 6y agoIn short, it's a matter of attitude. No, you're not obligated to respond to bug reports, but bug reports do provide value to your project, and not acknowledging that value is just as rude as their expectation that you fix it. The correct way to address this is an auto responder that says "Thank you for the bug report - we appreciate it; however, as this is a volunteer project, we do not guarantee a response, timely or otherwise. If you have a commercial, pressing need for this bug to be solved, we suggest filing a paid support ticket here: <link>." An important point is that reviewing a PR is also a time-consuming effort, the only difference is that it requires time on the submitter's part as well; I would be wary of recommending submitting a PR without talking to me first, since I may not have time to review it either, and then you've just wasted your time.
- freedomben 6y agoI completely agree. I've had to turn away PRs that came out of the blue and went a direction I didn't want to take. It sucks when that happens. But when it does, I thank the person and explain the decision. It's not what they want to hear, but it's a lot more respectful of their effort than silence or writing a blog post about how annoying they are.
- jitendrac 6y agoI agree,its not a nice way. Rather repo owner should encourage people to submit it as bug report and not the support ticket. later they should add tags like "volunteer contribution required","Sponsor requested". such tags to bug will do both things implicitly.
- davesque 6y agoThis is like acting insulted when your favorite famous person doesn't feel like talking when you run into them on the street. It's nothing personal, they just don't have the mental energy to treat every fan interaction as something special. The analogy isn't perfect for open source, but do you get my point? The fact that your PRs go unnoticed is not meant to be an insult nor should it be seen as one. It's just the simple fact that one person doesn't have the resources individually to serve potentially thousands of users in a community. And they certainly won't prioritize anything that doesn't make them money like their day job. Why should they? Would you? All it takes is a moment's pondering to see that this is true.
- freedomben 6y agoI agree, but if a person is too busy to even look at project things, I think they should make that clear. It wouldn't take long to throw something into the README.md or CONTRIBUTING.md explaining the situation. They don't though. My speculation is because if they did then nobody is going to use the project.
- GordonS 6y ago> I rarely even send PRs these days because those often rot for months or years As an OSS developer myself, something I'm not keen on is getting PRs out of the blue - if it's something I don't want, or an approach I don't like, it's just really, really awkward. I don't know if this is how you already approach PRs, but IME a good approach is to first open an issue outlining the problem/feature and how you intend to approach it. This starts a discussion with the maintainers, and may or may not later lead to a PR from you, depending on whether your plans fit in with the maintainer's.
- freedomben 6y agoThanks, I wholeheartedly agree. It sucks to get a PR that was clearly work that you want to reject because it's a direction you didn't want to go, has big flaws, or would be hard to maintain. I'm mostly talking about simple PRs, little bug fixes, even documentation improvements. But even big PRs, all I ask is basic human courtesy that we provide each other in meat space. It's totally fine to say, "Thanks but I'm sorry we won't accept this." especially when it's out of the blue. What isn't fine is being rude. It's wrecking the community.
- hombre_fatal 6y agoAlso, reviewing the PR and doing the people management along with it is a lot of work. And more work than doing it yourself. It’s certainly not free labor that costs maintainers nothing like people suggest in these comments. It’s more like having to work with a coworker who was employed for a couple days in difficulty and credentializing in what they left behind.
- freedomben 6y agoTotally agree. I think a "I'm sorry I don't have the bandwidth to look at this right now, but thank you for your contribution" would be perfectly fine IMHO. It's polite and decent, but still respects the maintainer.
- throwaway78123 6y agoThis. It feels like the "Old World" of open source was mostly about passionate people developing (and open sourcing) software for other similarly passionate people (think of some of the great projects on Freshmeat 20 years ago). I am not saying it was perfect but there used to be some sort of etiquette. Now the demographic has changed drastically. On the "maintainer" side you have a lot more people just dumping their stuff on Github (public repos were the only one free) and only want to collect the positive ("feel good", resume padding). On the "Consumer" side you have way more people that completely abuse online helping channels such as StackOverflow, or Github issues (how many times have I seen someone say "hello it does not work can you help me"). It reminds me on how IT departments evolved in Corporations where years of abuse lead IT departments to develop a very conservative defense mechanism that basically leads to the function being solely self serving. I am shocked reading this thread that it has become completely ok to flat out ignore legitimate and well researched/documented bug reports. Feels like we are throwing the baby with the water here.
- Mountain_Skies 6y agoI'm seeing "x accepted pull requests" on resumes frequently now. Not every PR is made in good faith nor made with the same motivation as the maintainer. Someone making dozens of individual PRs for things like adding CONST to variables whose future use they do not understand is a drain on the maintainer's time. For the person making the pull requests, they get a low effort way to pad their number of accepted pull requests, many of which are not in alignment with the goals of the maintainer or the project.
- freedomben 6y agoTotally agree. I by no means think all PRs or issues are equal. That's basically what I'm irritated about with this post! The new attitude that I hate is treating everything as crap, spam, or entitlement. Politely refuse low effort and unuseful PRs. Don't throw the baby out with the bath water.
- TuringNYC 6y agoI think it is about how bugs are submitted. I see bugs on GitHub that are like "BUG FIX IT NOW" (entitled) vs "I noticed a bug when testing v1.17 on Ubuntu 16.04 while using Python 2.6" (constructive)
- freedomben 6y agoTotally agree, but the people complaining about bug reports rarely ever acknowledge the difference, and they often treat them all the same. Take for example OP, who would say essentially "Pay me first" outright without even considering the bug.