5 ms·
What the court decides with regards to damages and similar issues is a bit fuzzy of course. But the original claim was "That way they are absolutely sure that
by viraptor 5y ago
What the court decides with regards to damages and similar issues is a bit fuzzy of course.
But the original claim was "That way they are absolutely sure that there will never be a problem." - and for that one, it's obviously not true - it's going to be a problem in the situation I described. It may be a mistake with a good faith assumption, and there may be agreements because it's a trivial amount of code. But it's not going to be "haha, that person did a little bit of fraud, let's ignore it".
- skissane 5y ago> What the court decides with regards to damages and similar issues is a bit fuzzy of course. It isn't just fuzzy what the court will decide with regards to damages – I think it is also (at least sometimes) going to be fuzzy with respect to what the court will decide as to the substance of the dispute. > But the original claim was "That way they are absolutely sure that there will never be a problem." - and for that one, it's obviously not true You can never be absolutely sure there isn't going to be a problem. But you can't be sure there is going to be one either. > But it's not going to be "haha, that person did a little bit of fraud, let's ignore it". There isn't necessarily any fraud involved here. The employee may have a good faith (even if mistaken) belief that they are allowed to submit the code to the open source project. The open source project may have a good faith and reasonable belief that they are legally allowed to receive it. In that scenario, neither party is committing any fraud. And if the employer later decides they don't agree with what happened, there is no guarantee the employer will necessarily always win a case against the open source project.