4 ms·
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-c
by ivanjermakov 7mo ago
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-agents/ https://justin.poehnelt.com/posts/rewrite-your-cli-for-ai-ag...
- hrmtst93837 7mo ago[flagged]
- jsnell 7mo agoMost projects under the "google" org will have exactly the same disclaimer about not being official Google products.
- hrmtst93837 7mo ago[flagged]
- abustamam 7mo agoCouldn't Google do a cease and desist for that kind of impersonation?
- hrmtst93837 7mo ago[flagged]
- eudiwjfie 7mo ago[dead]
- krzyk 7mo agoCrazy. 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.
- tuckerman 7mo agoGoogle 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.