4 ms·
You have the option of having Google own the code, and in return you can work on it using Google hardware, work on it while at work, use other google code or di
by yuriks 9y ago
You have the option of having Google own the code, and in return you can work on it using Google hardware, work on it while at work, use other google code or discuss it with your coworkers freely.
Or you can ask to retain ownership of your project, but then you don't get to do any of the above. This option is also sometimes (thanks DannyBee for correcting me) not available if your project is considered to be too similar to some critical Google interest. The basic idea is outlined here: https://opensource.google.com/docs/iarc/ https://opensource.google.com/docs/iarc/
- DannyBee 9y ago"This option is also not available if your project is considered to be too similar to something Google's working on (due to obvious IP issues.)" Speaking as an IARC committee member, this is not quite correct. We have in fact, approved plenty of stuff that is close to what google is working on. For example, we've approved plenty of search engines. (The overall approval rate is >96% last i looked). It's not so simple that i can easily draw principled bright lines for you though :)
- shallot_router 9y agoOut of curiosity, what are the kinds of projects that IARC won't approve?
- DannyBee 9y agoAn example would be those where the person is really trying to get the IP to create a separate company that competes with Google in some area, and then quit. Yes, this happens. It's not even that we care or don't care in that case, we are just literally the wrong forum.