4 ms·
That is some excellent and honest language to describe why you put that in the contract the way that you did. Often people don't understand why it's there, and
by oneplane 10y ago
That is some excellent and honest language to describe why you put that in the contract the way that you did. Often people don't understand why it's there, and assume malicious intent to "steal" the private work of employees, but as shown in this case, it's simply an IP issue that cannot easily be resolved in a different way as far as you know. Reading your comments on the various places this discussion is happening, your clear and honest answers make me (and probably others) like GitLab even more!
- tastythrowaway2 10y agoYou are incorrect in your assumption that it cannot easily be resolved. It would be trivial to declare it limited to a smaller domain - specifically the domain in which gitlab operates. As it stands now it is limitless in scope. as pointed out by many others, this is not reasonable.
- oneplane 10y agoIf that is the case, you should definitely offer your legal advice to GitLab.
- tastythrowaway2 10y agoI happily would but would like to retain the option to mow my own lawn.