I think this is one of these cases where talking in abstract terms does not help people agree.
What I am hearing is if you remove context (and timing, lets say it is part of context) then there is no good or bad. But who said to remove context? Arent we saying then there is good and bad depending on context?
Many people, including myself, would agree in the abstract, while at the same time some situations being very clear once down to a real example.
It reminds me of people claiming pain is an illusion or facts not existing (very edgy), until someone slaps them in the face to prove "I did slap you, that is a fact". I think that is reality, and specific examples are easier.
How do you make good or bad resolvable? Is a piece of code being used by Tyson Foods okay? A vegetarian software engineer who contributed to the package might say “no, that use contributes to the killing of animals for food, which is bad.”
If you need to evaluate all the context to know whether a license is usable, it makes it extremely hard for “good guys” to use code under that license. (It’s generally very easy for “bad guys” to just use it quietly.)
It is not a computer program, but a an ethics problem. We can solve it by thinking of the context and the ethics of it.
I realize it is the topic of this thread, but OP did not mention anything in relation to licenses, and was just talking about good and bad not existing objectively (without context).
I think, if we came with a specific situation, most people with similar values might reach the same good/bad verdict, and a small minority might reach a different one.
I believe the Tyson Foods example is overly simplistic and still too abstract, because one can be vegetarian for many reasons, and these would affect the "verdict". In the real world, if we were working on that piece of software the question would be: Does the implementation of this specific hr SAP module for Tyson foods by me, a vegetarian against animals suffering unnecessarily, etc. as opposed as the abstract idea of any piece of code and any vegetarian. If a friend called you: I have this situation at work, they are asking me to write software to do x and I feel bad about it, etc. etc. I bet it would not be difficult to know what is right and wrong. Another aspect of it is, we could agree something is wrong (bad) and you might still do it. That does not mean there is no objective reality, just that you might not have options or that your values might not be the ones you think (or say) they are, for example.
But in a typical FOSS scenario, your decision to open source the code and Tyson Foods decision to use it are decoupled. You don't know who all the potential users are when you open source it, so you can't consider all the concrete cases and make sure that the license reflects them. In the same way Tyson Foods isn't going to contact all the creators of libraries they want to use and ask if their concrete use case is in line with the creator's ethics.
Agreed. This would be a logistical nightmare on both ends. Especially if the licenses can be revoked if and when Tyson Foods decides to change some of their policies and/or the author decides to change their political views.
I believe that this would effectively make sure that nobody uses these licenses.
> I think, if we came with a specific situation, most people with similar values might reach the same good/bad verdict, and a small minority might reach a different one.
All you doing is agreeing how the context of the situation is determining if the action is "good" or "bad" (which was my point)
What I am hearing is if you remove context (and timing, lets say it is part of context) then there is no good or bad. But who said to remove context? Arent we saying then there is good and bad depending on context?
Many people, including myself, would agree in the abstract, while at the same time some situations being very clear once down to a real example.
It reminds me of people claiming pain is an illusion or facts not existing (very edgy), until someone slaps them in the face to prove "I did slap you, that is a fact". I think that is reality, and specific examples are easier.
P.S. I would add values into the context.