3 ms·

IANAL. Make sure you put in a carveout for every repo you have in GitHub. It helps to have a lot of public ones, then roll in your private ones into the list.

IANAL. Make sure you put in a carveout for every repo you have in GitHub. It helps to have a lot of public ones, then roll in your private ones into the list. Even if you have to pivot one of your private accounts, you get legal cover for working on it. Odds are the legal team won't bother checking on the contents of every single enumerated repo, and it would be insane to not hire you when you have those repos. I recommend claiming that you might have to do some work on any of these repos because other people might ask for support for those libraries. You can also make that claim for a private repo, too. Insist that your employer provide a work only laptop. Obviously, never put any of your private repo code on your work laptop.

deleted 4y ago
[deleted]
gnicholas 4y ago
I wonder how this would work if you have a bunch of shell repos where you can add whatever you want later. That is, your employer surely wouldn't be fine with you creating a competing product based on trade secrets that you were exposed to as an employee, just because it resides in a repo that existed prior to your employment. > it would be insane to not hire you when you have those repos. My hiring at a large software company was delayed for weeks because of two enumerated carveouts related to software that had nothing to do with the company's business. And this was when I was being hired as a lawyer! I can imagine for devs or PMs they would be even more sensitive.
- throwawaymaths 4y ago
  I was also delayed for weeks, but it's worth it. If they really put up a stink then you don't want to work there. > And this was when I was being hired as a lawyer! I can imagine for devs or PMs they would be even more sensitive. Really? Doing this as a dev is pretty normalized, I would have guessed a lawyer asking for it would be more scrutinized (do you notice a dog in the room if it's brown or if it's purple)

deleted 4y ago

[deleted]

gnicholas 4y ago

I wonder how this would work if you have a bunch of shell repos where you can add whatever you want later. That is, your employer surely wouldn't be fine with you creating a competing product based on trade secrets that you were exposed to as an employee, just because it resides in a repo that existed prior to your employment. > it would be insane to not hire you when you have those repos. My hiring at a large software company was delayed for weeks because of two enumerated carveouts related to software that had nothing to do with the company's business. And this was when I was being hired as a lawyer! I can imagine for devs or PMs they would be even more sensitive.

throwawaymaths 4y ago
I was also delayed for weeks, but it's worth it. If they really put up a stink then you don't want to work there. > And this was when I was being hired as a lawyer! I can imagine for devs or PMs they would be even more sensitive. Really? Doing this as a dev is pretty normalized, I would have guessed a lawyer asking for it would be more scrutinized (do you notice a dog in the room if it's brown or if it's purple)