3 ms·
> The author completely glosses over the social contracts involved in gift giving. First, social contracts with gift giving vary widely across the world. It's
by BeetleB 5y ago
> The author completely glosses over the social contracts involved in gift giving.
First, social contracts with gift giving vary widely across the world. It's a good reason they should be ignored here.
Second, as made very clear in the book Influence by Cialdini, the common social contract with giving gifts is reciprocity - and it holds even when the gift is crappy and/or unwanted.
So if you're going to invoke social contracts, do address all aspects of that contract.
You will also find significant disagreement on what the actual gift here is. For many, the gift is the code, not the capability. I'm giving the world this code. I provide some information about it. Whoever chooses to take it is expected to evaluate it and see if it fits their purposes.
Finally, regarding the potluck/party scenario, a more comparable example is a community potluck where everyone in the city is invited and can bring dishes, with no constraints whatsoever. People will show up, and happily tell everyone what's in their dish and how they made it. Most of them will openly say "I really can't claim this won't harm you" and "I'm not sure what entails proper cooking." You listen to each one and decide if you want to eat it.
Obviously, no one would ever run a potluck that way. You are using that fact to bash the developers, when you're not realizing the obvious: Potlucks/parties are a very poor analogy! Indeed, if you want to stick to the potluck analogy, then as an organizer, you definitely would put some rules in place - rules that would (and should) preclude most open source SW from being used in your product.