Do we keep the Google Allstar Prod bot? about community HOT 8 CLOSED

@dprotaso would like to turn off the Google version of this, and then opt-in to an OpenSSF or CNCF-hosted Allstar bot instead of the Google-managed one.

@thisisnotapril , can you help take this out of the "Google projects" list?

@knative/productivity-leads for the action / OpenSSF / CNCF replacement.

from community.

I sent a follow-up today to our Github team to get this org delisted as a Google-owned org so that the bot shouldn't be doing its thing. I will keep you posted! In the meantime you are welcome to delete and ignore as needed.

from community.

I'm not sure where the policy is defined, but I tend to agree that we shouldn't be keeping binaries checked in to our source control:

• It's hard to review / audit these commits
• They will tend to bloat the repo (hard to undo what's done, but at least avoid adding more and possibly remove the ones already there.
• We'd need to build new automation for publishing these into the repo (vs using GitHub releases or our existing publish-to-GCS mechanisms)

from community.

but I tend to agree that we shouldn't be keeping binaries checked in to our source control
+1 on this.

The repo should not have any binary files, for the examples shared with *.jar this can be downloaded by user actions very common for maven wrapper jars

from community.

Docs fix: knative/docs#5366

from community.

This seems to have configuration in https://github.com/knative/.allstar

from community.

/assign @thisisnotapril

from community.

Apologies for the delay; things got a little hectic here. :)
If you remove the google-admin user and Googlebot, this should do the trick and remove the others. We prefer the org owners to do this since it is not our org anymore. If you run into any issues with this, please let me know!

from community.