Earlier quoted context omitted.
> But it isn't nice when someone complains they're not getting a thank you for something they choose to do willingly and weren't asked to do. If you benefit from something someone else does, you owe them a debt of gratitude. It's not a legal debt, and it's not denominated in dollars and cents... but you shouldn't be surprised that there are norms of repaying this debt in various ways and that people/entities that exc…
> If you benefit from something someone else does, you owe them a debt of gratitude. It's not a legal debt, and it's not denominated in dollars and cents... but you shouldn't be surprised that there are norms of repaying this debt in various ways Yes and this is what I'm criticizing. If I am in dept, then say so and make it explicit to me before I take the dept unknowingly, otherwise I'm sorry, but I will in turn sha…
Welp, good luck with that. There's tens of thousands of social rules that are understood by 99% of people, and you're not going to find an explicit list somewhere of how far to stand away from someone when talking to them, to what kinds of initial conversations are appropriate, to saying "thank you" after someone gives you something, to attributing an idea to someone else, etc. And failing to follow them will rapidly earn you scorn.
> For example, what is Amazon supposed to do here? Should they offer a job? Pay up some amount of money? Cancel their project? Put a banner on amazon.com thanking the contributor?
If the product is 98% built upon some open source stuff, you put in the 2nd or 3rd paragraph description that it's "built upon" or "powered by" or "makes use of." Even a footnote might be OK. This is pretty obviously the right thing to do, and it's also helpful to your users in understanding what your product is.