Earlier quoted context omitted.
In contracts most terms are not defined. This allows the judge to interpret them according to their common meaning, for example https://en.wikipedia.org/wiki/Patch_(computing) I don't think most people will consider an entire program a patch. Having us sign off on every patch defeats the intent of the clause. The intent is to give our customers a way to submit merge requests on https://gitlab.com/gitlab-org/gitlab-ee…
> In contracts most terms are not defined. The GPL is one that I know that spells it out [1]: > This License applies to any program or other work which contains a notice placed by the copyright holder saying it may be distributed under the terms of this General Public License. The "Program", below, refers to any such program or work, and a "work based on the Program" means either the Program or any derivative work un…
I do wonder how would you define the patch file? How would you prevent people splitting up the changeset into multiple patch files?
I hope the intent of our license is clear. Most people and organizations want to do the right thing.