Assigning to mmoss based on our discussion earlier.

The current repository is https://team.git.corp.google.com/clusterfuzz-team%2Fsheriffbot#

I don't have strong opinions on which repository we end up putting this in, except that I do want it to be public. If you run into any trouble with this, or some cleanup is needed on the Sheriffbot side, let me know. I'd like to make sure this is done before we start doing major work on new features.

should we opensource all rules or we should keep a subset internal? (the planned migration of merge approval logic, for example)

We should open-source everything that's not explicitly private, given that these tools are going to be taking action on bugs that will be visible to the world.

Agreed. We also discussed this a bit from a security standpoint, and I don't see any significant advantage to using a chrome-internal repository in any of these cases.

This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

No longer on the Chrome team, e-mail me @google.com if any attention still required from me here, otherwise good luck!