Hacker News Reader

Comment by justinwp | Hacker News Reader

You are assuming that it was "personally" releasing something and that the process wasn't followed.

You continue to dance around this question on this post - did you or did you not follow Google's open source approval process[1]? Did you have an approved Ariane/Launcher2 entry?

1: https://opensource.google/documentation/reference/releasing/...

Yes

Did you have your launch approved? So did you follow the process?

Why isn't it under google's username on github?

Why does the repo say "This is not an officially supported Google product."?

Is it actually approved by Google or not?

You need to actually answer these questions instead of dodging them.

Are you the "serious consequences for ____" guy?

The reason you think he's "dodging" the questions is because you clearly don't know anything about the situation, like the fact that it was published under the github organization used by the workgroup he was in, same as a lot of other software the group authored.

Why is the repo still there if it's such an egregious violation of Google's policies?

> Why isn't it under google's username on github?

It's under "googleworkspace", one of Google's GitHub organizations (linked on https://developers.google.com/workspace).

> Why does the repo say "This is not an officially supported Google product."?

This seems to be boilerplate that Google puts on open-source releases, e.g: https://github.com/GoogleContainerTools/kaniko

It's not saying that it's not released by Google, but that it's not an officially supported Google product. I presume to make it clear that it's not covered by support agreements/bug bounties/etc. in the way products like Google Docs would be.

> Is it actually approved by Google or not?

It went through the launch/approval process (https://news.ycombinator.com/item?id=48655744) and was announced by Justin's manager.

Reply on news.ycombinator.com