News for hackers. Stuff that matters.
Re:The Bun Shell by lambda on Sunday January 21, 2024 @02:49AM (#39076516)
Being in the Google GitHub org doesn't mean "by Google", it means "by someone who works at Google."
Re:The Bun Shell by redder23 on Sunday January 21, 2024 @04:28AM (#39076954)
To me its the same thing, they are paid my Google to code stuff the is put in their org and not their private accounts/orgs so to me this IS in fact "by Google".
Re:The Bun Shell by ycuser2 on Sunday January 21, 2024 @02:52AM (#39076534)
But doesn't he get paid by Google to code this?
Re:The Bun Shell by atorodius on Sunday January 21, 2024 @03:21AM (#39076641)
They do, otherwise it won’t be in that repo
Re:The Bun Shell by FiloSottile on Sunday January 21, 2024 @04:40AM (#39077028)
No, something being under github.com/google means the person who started it was paid by Google, not paid by Google to code this. Google contracts (like most tech contracts in the US) have ridiculously broad IP assignment clauses, so unless you go through a lengthy process to request Google disown something, they own anything you code, and they insist you open source your things under github.com/google.

You decide your own definitions, but that's very different from "Gmail by Google" or even "Go by Google" in my book. Note how the main author has "Ex-Google" in their bio, too.

Re:The Bun Shell by shubhamkrm on Sunday January 21, 2024 @09:07AM (#39078518)
Not necessarily. You can write open source code in your own time and publish under Google org on GitHub. This is the recommended process if you don’t care about retaining the copyright to your code.

If someone does want to retain copyright, there’s another process for getting approval.