5 ms·

Even something you create in the weekend belongs to google when you are in contract with them ?

by jpic 8y ago

q3k 8y ago
Yes. At least according to their contract in Ireland (and other locations, from what I've asked).
- soVeryTired 8y ago
  Has that ever been tested in court? Sounds a bit too draconian to me (but then IANAL).
  - q3k 8y ago
    Not from what I researched. But then again, would you like to go to court against Google lawyers? I wouldn't.
microtherion 8y ago
Some good discussion here: https://news.ycombinator.com/item?id=2208056 https://news.ycombinator.com/item?id=2208056 Bottom line is that at least in California, employees theoretically have the right to IP developed in their own time on their own hardware, but in practice, there are numerous caveats, and litigation can be extremely risky. One of the caveats is that the invention should not overlap with a company's "existing or anticipated line of business", and with the FAANGs being such behemoths, that can cover almost any form of software development.
- BayAreaSmayArea 8y ago
  Something that comes up in these discussions is the concept of “company time”. Company resources is clear cut, but what is company time for a salaried employee? How does that change with being a remote employee? I’ve moved to a strategic product role and honestly work less than an hour a day on average and seldom go into the office. If I decide to work on a side project does that restrict me from git commits between 8-5?
  - thecatspaw 8y ago
    > Company resources is clear cut, but what is company time for a salaried employee? Usually salary comes with an expectation of hours per week/month, and usually also comes with a software where you write down your hours, to track overtime, minus time, etc. So all the time you write down in that system, counts as companytime.
    - BayAreaSmayArea 8y ago
      Interesting, I haven’t had a timesheet since I was an intern during college almost 20 years ago. I didn’t realize that timesheets we’re still a common part of being a salaried employee in tech.
      - ipsi 8y ago
        It depends what you do - I've always had to timesheet, but that's because I was working for clients, so we had to at the very least make sure we were estimating correctly, or, at my current job, that we're billing the hours I actually work. It's not too onerous, since I only work for one client at a time, and time spent not at work is uncommon and usually in big chunks (e.g. an hour or two for a doctor's visit, days or weeks for vacation).
    - notJim 8y ago
      You've had this at tech jobs? I've definitely never had to track time at any of my tech jobs (nor have I ever been eligible for overtime .)
      - thecatspaw 8y ago
        Yes, switzerland requires time tracking, including a requirement of certain break times if your shift is long enough.
branksy 8y ago
Like many companies, yes. However, unlike many companies, they actually have a process where you can submit your "weekend projects" for Google to review and "gain back" explicit ownership of them. Basically Google just checks to make sure it's not competing with anything Google's already doing, and then contractually assigns it back to you. (And anecdotally, if it does compete, you may be offered the opportunity to join said team, since it shows you're passionate about it.)
- delroth 8y ago
  It's also pretty easy to contribute to FOSS projects on your own time, as long as you're OK with Google being the owner of your contributions (I personally don't care since it's open source licensed anyway). https://opensource.google.com/docs/patching/ https://opensource.google.com/docs/patching/ is an almost fully public version of the process Googlers have to follow to contribute stuff to open source projects. Disclaimer: works at Google, maintains some FOSS code in my own time, both under my own copyright for some projects and under Google's copyright for others.
  - drewmate 8y ago
    Have you encountered any project maintainers uneasy with the idea of Google "owning" that part of the source code? In practice it doesn't matter, but that part kind of confuses me.
- q3k 8y ago
  This still kills the possibility of quickly collaborating with someone on a project in your free time. Any time you want to even start working on something together, you have to wait a couple of days for approval. This simply doesn't work if you want to be active in a hackerspace or any other community where you iterate on projects quickly.
  - joshuamorton 8y ago
    >This still kills the possibility of quickly collaborating with someone on a project in your free time. Any time you want to even start working on something together, you have to wait a couple of days for approval. This depends on the project. If you and the project maintainer are ok with Google maintaining copyright over the code, there's a self-approval process that takes ~2 minutes. And of course, that's only necessary if I'm working on the side project using company resources. If I'm not, I literally can't do the self-approval. There's only an issue if you want to maintain copyright should you want to monetize your product. Most hobby projects won't encounter those issues.

Even something you create in the weekend belongs to google when you are in contract with them ?

by jpic 8y ago

Even something you create in the weekend belongs to google when you are in contract with them ?

q3k 8y ago

Yes. At least according to their contract in Ireland (and other locations, from what I've asked).

soVeryTired 8y ago
Has that ever been tested in court? Sounds a bit too draconian to me (but then IANAL).
- q3k 8y ago
  Not from what I researched. But then again, would you like to go to court against Google lawyers? I wouldn't.

microtherion 8y ago

Some good discussion here: https://news.ycombinator.com/item?id=2208056 https://news.ycombinator.com/item?id=2208056 Bottom line is that at least in California, employees theoretically have the right to IP developed in their own time on their own hardware, but in practice, there are numerous caveats, and litigation can be extremely risky. One of the caveats is that the invention should not overlap with a company's "existing or anticipated line of business", and with the FAANGs being such behemoths, that can cover almost any form of software development.

BayAreaSmayArea 8y ago
Something that comes up in these discussions is the concept of “company time”. Company resources is clear cut, but what is company time for a salaried employee? How does that change with being a remote employee? I’ve moved to a strategic product role and honestly work less than an hour a day on average and seldom go into the office. If I decide to work on a side project does that restrict me from git commits between 8-5?
- thecatspaw 8y ago
  > Company resources is clear cut, but what is company time for a salaried employee? Usually salary comes with an expectation of hours per week/month, and usually also comes with a software where you write down your hours, to track overtime, minus time, etc. So all the time you write down in that system, counts as companytime.
  - BayAreaSmayArea 8y ago
    Interesting, I haven’t had a timesheet since I was an intern during college almost 20 years ago. I didn’t realize that timesheets we’re still a common part of being a salaried employee in tech.
    - ipsi 8y ago
      It depends what you do - I've always had to timesheet, but that's because I was working for clients, so we had to at the very least make sure we were estimating correctly, or, at my current job, that we're billing the hours I actually work. It's not too onerous, since I only work for one client at a time, and time spent not at work is uncommon and usually in big chunks (e.g. an hour or two for a doctor's visit, days or weeks for vacation).
  - notJim 8y ago
    You've had this at tech jobs? I've definitely never had to track time at any of my tech jobs (nor have I ever been eligible for overtime .)
    - thecatspaw 8y ago
      Yes, switzerland requires time tracking, including a requirement of certain break times if your shift is long enough.

branksy 8y ago

Like many companies, yes. However, unlike many companies, they actually have a process where you can submit your "weekend projects" for Google to review and "gain back" explicit ownership of them. Basically Google just checks to make sure it's not competing with anything Google's already doing, and then contractually assigns it back to you. (And anecdotally, if it does compete, you may be offered the opportunity to join said team, since it shows you're passionate about it.)

delroth 8y ago
It's also pretty easy to contribute to FOSS projects on your own time, as long as you're OK with Google being the owner of your contributions (I personally don't care since it's open source licensed anyway). https://opensource.google.com/docs/patching/ https://opensource.google.com/docs/patching/ is an almost fully public version of the process Googlers have to follow to contribute stuff to open source projects. Disclaimer: works at Google, maintains some FOSS code in my own time, both under my own copyright for some projects and under Google's copyright for others.
- drewmate 8y ago
  Have you encountered any project maintainers uneasy with the idea of Google "owning" that part of the source code? In practice it doesn't matter, but that part kind of confuses me.
q3k 8y ago
This still kills the possibility of quickly collaborating with someone on a project in your free time. Any time you want to even start working on something together, you have to wait a couple of days for approval. This simply doesn't work if you want to be active in a hackerspace or any other community where you iterate on projects quickly.
- joshuamorton 8y ago
  >This still kills the possibility of quickly collaborating with someone on a project in your free time. Any time you want to even start working on something together, you have to wait a couple of days for approval. This depends on the project. If you and the project maintainer are ok with Google maintaining copyright over the code, there's a self-approval process that takes ~2 minutes. And of course, that's only necessary if I'm working on the side project using company resources. If I'm not, I literally can't do the self-approval. There's only an issue if you want to maintain copyright should you want to monetize your product. Most hobby projects won't encounter those issues.