Hacker News new | ask | show | jobs
by geofft 3135 days ago
Google corporate policy, to the best of my knowledge (I do not and have never worked for Google but I asked lots of questions when evaluating an offer), is that it's significantly easier to let Google retain copyright on your open source work, and if it's on GitHub you have to host your repo at github.com/google if Google retains copyright.

("Forks" with no code changes ending up at the top of HN, as if they signaled a major shift in corpprate strategy, are an excellent example of why I think this is a bad policy. For all we know some Google employee PR'd a typo fix they noticed one weekend and has since deleted the branch.)

1 comments

Google's policies are actually mostly open too, so you don't have to guess :) (they are linked from the open source page).

They are now a bit out of date, a few things have been simplified/relaxed (generally, the goal is as little process as possible).

Then again, people also like to super-duper parse the words in the docs, which are not really written to be parsed that way.