upvote
Generally, this disclaimer is required for products that are released under the "Google" name but without any kind of support guarantees for enterprise customers.

That or it's a personal project that IARC decided could live in the workspace project.

Disc: Former Googler

reply
> but without any kind of support guarantees for enterprise customers

Also known as every single Google product

reply
I'm still confused, @googleworkspace is not affiliated with Google?

Seems like it was made by Google employee: https://justin.poehnelt.com/posts/rewrite-your-cli-for-ai-ag...

reply
I think an official project from Google would be hosted under https://github.com/google, a GitHub Org which contains 2,800 repositories and has more than 500 Google employees as member.

googleworkspace/cli appears to be more of a hobby project developed by a single Google employee.

reply
Most projects under the "google" org will have exactly the same disclaimer about not being official Google products.
reply
Crazy.

And this project uses "google" in its org, so I would assume it is offical or at least lawyers are running toward the owner with lawsuits.

reply
But at least they are under the Google organization. Thing is anyone could create an organization, name it something like "googlesomething", use Google logos, and design it in a way that some users might believe it has an official connection.
reply
Couldn't Google do a cease and desist for that kind of impersonation?
reply
I think so, but it could be enough for someone to create such an organization, share it on HN for malicious purposes, such as infecting devices, and have it taken down only afterward. I'm not saying that's what happened here, but it does illustrate a potential attack vector.
reply
Google operates across so many verticals that it's difficult to argue a side project is outside the scope of Google’s business and therefore Google could argue it has copyright over the work. To make it easier for engineers to keep contributing to open source, there’s a fairly straightforward path to release code through a Google-owned repository (if you look at github.com/google it is full of personal projects alongside official ones).

There is an official process where an engineer can apply to a committee to have Google waive any copyright claim. That requires additional work so if your goal is simply to publish the code as open source and you do not mind it living under the Google org, using the Google repo path is usually much faster.

Disclaimer: ex-googler, not a lawyer, not arguing whether or not the situation with copyright assignment is legally enforceable or not/good or bad/etc.

reply
It's by Google, but it's open source and comes with no SLAs.
reply
Yeah that github name made my spider senses tingle, large scale credentials harvesting?
reply
Also the use of the google logo.

Edit: Oh, I think this actually is an official account. Very confusing

reply