Hacker News new | past | comments | ask | show | jobs | submit login

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!

You 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.

If that is the case, you should definitely offer your legal advice to GitLab.

I happily would but would like to retain the option to mow my own lawn.

Applications are open for YC Winter 2020

Guidelines | FAQ | Support | API | Security | Lists | Bookmarklet | Legal | Apply to YC | Contact