Its not blocked, it's just pending priority/decision which we don't have right now.

We'll get back to it when/if relevant.

I'm still uncomfortable about having the whitelist in the open, but I understand 's concerns about it becoming hard to edit. I'd block this until we get a solution for OVIRT-1154.

What do we decide on this? Keep the mirror? Delete the mirror and leave the gerrit project as is? Delete the mirror and lock down the project?

ovirt-site is a Github project, not Gerrit, so the comparison isn't relevant.
jenkins-whitelist is an infra project and as all infra repos, managed in Gerrit.

The same reason we won't accept engine or vdsm patches from GitHub because they are managed in Gerrit, we can't accept it for this project.
It happens that 99% percent of patches or requests are done via Gerrit currently, So I don't see a strong reason to move the jenkins-whitelist to GitHub.

New projects like 'ovirt-web-ui' that existing only in GitHub are already supported, so you can't say we don't support PRs from GitHub.

As for making it private repo on Gerrit, we can consider it, though unless you can spoof yourself into Gerrit with fake email, not sure if its needed.

On Sun, Feb 26, 2017 at 5:47 PM, Barak Korren (oVirt JIRA) <

Any ovirt patch on github contains the email address of the author.

There is no privacy, and there should be no privacy on free software
project.

This change is not needed and very wrong; we should make it easy to add
someone to the whitelist.

The correct change would be to accept pull requests on github, like
ovirt-site.

Nir