6 ms·
Thanks for putting this up here :-) (I handle both processes) The copyright process usually takes around 6 weeks, but new open source projects can be released i
by cdibona 14y ago
Thanks for putting this up here :-) (I handle both processes) The copyright process usually takes around 6 weeks, but new open source projects can be released in days (and patches much faster)
- brlewis 14y agoThe open source thing I can understand. The part for non-open-source projects is hard for me as an outsider. I can't see how any employee can have a web-oriented side project that doesn't compete with some Google service. You have a social network, a blogging platform, photo sharing, video sharing, online music, PAAS, code hosting, etc., etc. What area are you not in?
- fpgeek 14y agoTo this outsider, your question sounds like exactly the reason Google needs this sort of process. Even if an employee were working in an area that was theoretically competitive with something, an official determination by Google should trump theoretical arguments - providing valuable certainty to both sides.
- brlewis 14y agoI can understand the need for the process; I just don't understand how Google ever decides it's OK.
- cdibona 14y agoWe have a small group from code of conduct/conflicts, open source, android and folks who represent a few other strategic groups at Google and we simply requests one by one. Most of the time it isn't a problem and we grant the request. Getting everyone together regularly can be a bit more difficult, that's why it takes longer.
- DannyBee 14y agoWe actually decide it's okay the vast majority of the time. (I can't give you exact stats, but i really do mean "vast majority")
- packetslave 14y agoSee also http://news.ycombinator.com/item?id=1970191 http://news.ycombinator.com/item?id=1970191 for when cdibona talked about this before.