Live data from Hacker News

Why we never thank open source maintainers

windsooon.github.io

201–210 of 229 posts

Re: Why we never thank open source maintainers

#201

Earlier quoted context omitted.

Ways I deal with this as an open source maintainer of various projects: 1. Severely restrict the scope of the project (i.e. do one thing and do it well) 2. Don't feel guilty about saying "no" 3. Realize that people have no malicious intent or are lazy when they request . It's just like a normal customer in a business: they often have no idea of the cost and difficulties in implementing things. That's okay, it's my du…

It would be nice if github made it easy for people to assign a $ bounty to every issue and when it's marked complete payouts are automatic. There are a bunch of issues in various open source projects where I would easily drop $100 on a bounty.

[deleted]

Re: Why we never thank open source maintainers

#202

Earlier quoted context omitted.

Ways I deal with this as an open source maintainer of various projects: 1. Severely restrict the scope of the project (i.e. do one thing and do it well) 2. Don't feel guilty about saying "no" 3. Realize that people have no malicious intent or are lazy when they request . It's just like a normal customer in a business: they often have no idea of the cost and difficulties in implementing things. That's okay, it's my du…

It would be nice if github made it easy for people to assign a $ bounty to every issue and when it's marked complete payouts are automatic. There are a bunch of issues in various open source projects where I would easily drop $100 on a bounty.

This is potentially a great idea. It doesn't necessarily have to be a github feature. It could be a third party platform, kind of a Patreon or Kickstarter for open source bugs.

But I think the platform would need to be scalable in some way. Maybe no one will fix it for your $100, but maybe if the bounty were crowd funded, it would get fixed when the bounty got high enough to be worthwhile for the amount of time and effort involved.

When I was an active participant on Cyburbia, the site owner was paying for hosting out of pocket and he was resistant to commercializing it and was equally resistant to taking donations. He talked about commercialization as "becoming a sellout" and taking donations as "I don't want to do a PBS style begathon annually." He worked for the government and seemed just unable to wrap his head around good monetization.

People would complain that the site was slow and kludgey. As it got more popular, the level of hosting service he could afford was not really meeting demand. He would crab at complainers that they needed to be more appreciative of the free service that he was paying for out of pocket and make it clear he could not afford more.

I felt there was an obvious solution: Post a page saying it takes $x to cover better hosting for a year. I can't afford that out of pocket. If you want to see site performance improve, kick in a few bucks. When it hits $y, I will upgrade the hosting service. Then point people to that page when they complained.

I see a lot of potential for your idea. It could be a means to turn complaints into a money stream to help improve open source without victimizing contributors.

As someone who did a lot of volunteer work over the years, I came to resent the idea that I should do everything for free. If we value this stuff, we should be willing to pay people to work on it. Finding a means to do so even though it is voluntary can be challenging, but shouldn't be show stopping. We just have to be creative.

Re: Why we never thank open source maintainers

#204

Earlier quoted context omitted.

Because being annoyed doesn't affect them, only you. Choosing to experience negative emotion because someone does something is self-harm. When you are entitled to something, you expect it, and you can't expect something and be truly appreciative of it at the same time. When you don't expect good though, the bad doesn't upset you, and the good, you actually genuinely appreciate.

I didn't expect anything, but your comments still let me down, and I find you annoying.

What he's talking about is putting yourself in a mindset of very low expectations to maximize your own happiness.

For example, if your baseline "expectation" of people is that they will be rude and shitty, then you won't become annoyed when someone is rude and shitty to you. And when someone is nice to you, they have exceeded your expectations and it makes you happy.

So what you perhaps "expected" is that people generally would not be rude, which led to your disappointment when you encountered a rude person, which ultimately just generated annoyance/unhappiness for yourself (i.e. their rudeness is static regardless of how it made you feel).

The point is not really to go around bleakly expecting everything to be shit all the time, but just in general, the lower your expectations are, the less power you give people to disappoint and upset you, and the more you appreciate people for exceeding your expectations. It's not really about whether it's "right" or "wrong" to be annoyed at them but just a mindset shift for your own contentment.

Re: Why we never thank open source maintainers

#205

As the maintainer of a reasonably popular library, I actually get irritated by a lot of 'thanks', because they are in the form of this sentence: 'Hi, can you implement ? Thanks!' Usually from people who have never contributed anything. Honestly, being thanked in any shape or form does nothing for me, Id rather have users be more considerate of our time and not abuse issues and the community for supporting their lazin…

Do you wish for people to not at all tell you what features they would find attractive, or should they do so in some other way?

Re: Why we never thank open source maintainers

#206

Earlier quoted context omitted.

Ways I deal with this as an open source maintainer of various projects: 1. Severely restrict the scope of the project (i.e. do one thing and do it well) 2. Don't feel guilty about saying "no" 3. Realize that people have no malicious intent or are lazy when they request . It's just like a normal customer in a business: they often have no idea of the cost and difficulties in implementing things. That's okay, it's my du…

It would be nice if github made it easy for people to assign a $ bounty to every issue and when it's marked complete payouts are automatic. There are a bunch of issues in various open source projects where I would easily drop $100 on a bounty.

I believe this is what bountysource.com is for. I haven't tried it, though, and I'm not sure how completion is evaluated.

Seems problematic to let the bounty-poster decide if something is completed, but also to put it on a third party to put in the time to verify for various pieces of software they might not be familiar with (and worse to put it on the second party who implements).

Re: Why we never thank open source maintainers

#207
post #16

As the maintainer of a reasonably popular library, I actually get irritated by a lot of 'thanks', because they are in the form of this sentence: 'Hi, can you implement ? Thanks!' Usually from people who have never contributed anything. Honestly, being thanked in any shape or form does nothing for me, Id rather have users be more considerate of our time and not abuse issues and the community for supporting their lazin…

Send them quotes back: "I'm glad you liked it, I have X hours to dedicate to project Y this month. If you'd like, I'm willing to work on that feature for you under terms Z". People _pay_. You'd be surprised just how much of Chromium and other open ssource projects is written by consulting companies paid by third parties to solve a use case.

I run a small seven figure revenue business and I have paid more than one open source maintainer/contributor for work done. Definitely don't be afraid to ask; but I usually offer upfront. I'm an ex-developer so I usually offer the help I can with the keyboard, but know that it's limited compared to most of the really good developers out there maintaining a real project, so I offer time + money.

The problem is getting single open source maintainers to commit - and followthrough - with support. They are often way too busy with their job to actually be professional with support and adhere to even a loose SLA.

Re: Why we never thank open source maintainers

#208
post #23

As the maintainer of a reasonably popular library, I actually get irritated by a lot of 'thanks', because they are in the form of this sentence: 'Hi, can you implement ? Thanks!' Usually from people who have never contributed anything. Honestly, being thanked in any shape or form does nothing for me, Id rather have users be more considerate of our time and not abuse issues and the community for supporting their lazin…

Done incorrectly, this can sound passive aggressive, but I suggest adding a short notice in your README: - Feature requests should follow ((list your rules)). All requests that don't follow the rules will be ((closed|ignored)) - ((The maintainers of this project)) will only add new features ((at their leisure)). If you cannot contribute a pull request for ((feature X)), make a feature request ((following the rules on…

I do this at work in my social media channels and such. I clearly state the rules of engagement and delete 99.999% of communication that doesn't fit the list.

(Sometimes I'll answer communication from those who don't get it right, almost always they are high-profiled individuals you occasionally have to break a rule for. [I also usually regret it. Maybe I'll learn someday.])

Re: Why we never thank open source maintainers

#209
post #150
post #23

Earlier quoted context omitted.

Done incorrectly, this can sound passive aggressive, but I suggest adding a short notice in your README: - Feature requests should follow ((list your rules)). All requests that don't follow the rules will be ((closed|ignored)) - ((The maintainers of this project)) will only add new features ((at their leisure)). If you cannot contribute a pull request for ((feature X)), make a feature request ((following the rules on…

Can you provide a link to an example of doing this or something similar?

If you mean something like contribution guidelines, then they're everywhere. Here's one of mine as an example: https://github.com/benhowell/react-grid-gallery/blob/master/...

Re: Why we never thank open source maintainers

#210
post #182

Earlier quoted context omitted.

I don't want any thank you notes. Never asked and never will. I just don't like people who are rude, and I find them annoying. I don't know what's wrong with feeling annoyed by them being rude to me.

Because being annoyed doesn't affect them, only you. Choosing to experience negative emotion because someone does something is self-harm. When you are entitled to something, you expect it, and you can't expect something and be truly appreciative of it at the same time. When you don't expect good though, the bad doesn't upset you, and the good, you actually genuinely appreciate.

"Choosing to experience negative emotion because someone does something is self-harm."

Hi :-) Fascinating comment. Do you really live that, or just it's something you read/heard and aspire to?

Trying to unpack that a little: Calling experiencing negative emotion (i.e. feeling bad) "choosing to experience negative emotion" seems psychobabble. Do you choose all your feelings? I doubt it. So, you will never feel bad because of anything anyone does, because why would you, and that would be self-harm. All that just strikes me as jargon out of a bad self-help book. It doesn't sound human, but like a robot, or maybe a guru. (e.g. Nisargadatta: 'In my world, nothing ever goes wrong.') I guess that's why gurus/monks/priests aren't supposed to have wives, girlfriends, careers, possessions etc. Because ordinary humans do get upset about stuff. And feel good about stuff. The way you call people "someone" and reduce most of life to "someone doing something" I find absolutely chilling.

That last bit about expectation sounds likes the ridiculous pessimism I thought made sense as a child. If you expect things to turn out for the worst, you will never be disappointed. That was before I realized that in life your attitude makes a huge difference to how things turn out. In the real/everyday world of someones doing somethings anyway.

Post reply on HN