Live data from Hacker News

Why we never thank open source maintainers

windsooon.github.io

61–70 of 229 posts

Re: Why we never thank open source maintainers

#61

Earlier quoted context omitted.

Thats the fee for my part-time freelance consulting. 200 is on the low end.

Huh, I'm way undercharging.

The higher you charge, the more horrible your consultancy job will be generally ;-) I've found €200 to be the sweet spot between actually doing useful tech work and being in nonsense meetings all day.

Re: Why we never thank open source maintainers

#62

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…

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…

I very much agree with your first point, largely because, would you fancy that, that's the original *nix philosophy.

Re: Why we never thank open source maintainers

#65

Earlier quoted context omitted.

Huh, I'm way undercharging.

The higher you charge, the more horrible your consultancy job will be generally ;-) I've found €200 to be the sweet spot between actually doing useful tech work and being in nonsense meetings all day.

What sort of tech work do you do, though? Nobody is going to pay 200 EUR for frontend development, say.

Re: Why we never thank open source maintainers

#66
I received a lot of help when I was implementing mailman from Mark Shapiro a few years back. I asked what I could do in thanks and he pointed me to his public Amazon wish list. I purchased something off of that for him. I try to make sure I am thanking people for their work that I am benefitting from.

Re: Why we never thank open source maintainers

#67
post #51
post #20

Earlier quoted context omitted.

The problem is that it is hard to transfer money over the internet. I just wanted to know what bureaucratic hurdles one has to jump in Germany to even be able to receive donations on your webpage. I don't want to go into the gory details, but just come with something that I say for years very often: The surest way to become a terrorist very fast is to read up into law. And this is only for being legally able to recei…

> Yes, of course one could use some fancy cryptocurrency I paid a bug bounty to someone in Germany from Canada with Bitcoin. I guess I'm a terrorist now.

I don't know much about Canadian law, so I cannot say that you did a criminal act.

But I would wager that the receiver (accidentally!) did tax fraud, since the legal situation around taxation of Bitcoin payments in Germany is not really clear. I can nearly say for sure that if he is not a professional who specializes in international taxation laws (or at least has access to an expert in this area) he probably did a criminal act (which does not imply that he will be prosecuted etc.).

Also I would bet he did something wrong in the accounting of these donation (which can easily happen, since there are so many formal details to consider - do something wrong and you are in trouble). Again a source for big legal trouble. This will rarely be prosecuted, but is nearly always a sword of Damocles.

Re: Why we never thank open source maintainers

#68
post #27
post #13

Earlier quoted context omitted.

> 'Hi, can you implement ? Thanks!' Answer with an estimate based on your hourly rate.

Honestly, this exudes arrogance, even if the intention is completely free of ill will. It's better to say a clear NO ("I will not add this feature" or "I cannot implement this at this time"), and let them figure if they want to pay/use something else on their own, than to talk down to users.

> Honestly, this exudes arrogance, even if the intention is completely free of ill will.

I would rather say that asking to "implement " for free exudes several more magnitudes of arrogance.

Re: Why we never thank open source maintainers

#69
I thank authors and maintainers and I expect others do too. I just don't do it publicly.

I've thanked authors of small projects which are unique and useful to me just by dropping a short email (not en masse) - Not out of some obligation, but because it's an encouraging thing to receive. I want them to know someone is finding utility in what they have done and appreciates it enough to tell them.

I don't think the larger projects are in need of this though, it would just become noise. This is probably just the cynical misanthrope in me speaking but I can't help but think it looks more like a popularity contest when it's public like this... not that i'm suggesting it could be done any other way for large projects, but then, who is going to read all of them if it's a large project?

Re: Why we never thank open source maintainers

#70
post #38

Earlier quoted context omitted.

> People _pay_. From our experience ( http://sheetjs.com/ , our major open source library is https://github.com/SheetJS/js-xlsx ), even with multinational corporations, they move heaven and earth to find another free solution, or spend in-house time to hack together a solution and try to sucker you into helping them, but paying is by and large the last option.

From my experience in the medium business world (maybe 500 people total?), paying is the only option. Open source is evil. Maintaining things is evil. Writing your own code is evil. Just shell out $x,000 for support. If I could find a way to say "Yeah, we can get 'support' for this open source library for $xxx per month" my life would be much easier.

[deleted]
Post reply on HN