@tsandall yes I would do that

adding @marccampbell who was also interested in this project

@tsandall - Regarding number 3 - do you have a CNCF CLA bot on the OPA Github org already? cc @caniszczyk

@tsandall - regarding number 1 - can we simply complete an org transfer for the repo from Azure to the OPA Github org?

@lachie83 I'm not familiar with org transfers, but happy to help out if needed. We don't have a CLA bot installed in the OPA org (my understanding is that CNCF makes it unnecessary but I'm not a lawyer...)

email Linux Foundation Helpdesk helpdesk@rt.linuxfoundation.org and cc me to get the CLA bot installed in the OPA org (make sure 'thelinuxfoundation' is an owner of the org).

The LF IT team is a bit barebones at the moment due to the holidays so it may take some time.

Email sent. @lachie83 I don't have your email so I just copied Nikhil and Chris.

Thanks @tsandall. I contacted @caniszczyk and he mentioned that we can go DCO for OPA and that there is no requirement to have CLA.

I've confirmed that we do indeed need CLA on this repository. Let me work with the CNCF to understand the process of adding the CNCF CLA bot to this repo.

@lachie83 OK -- to be clear, do you mean this repo (i.e., open-policy-agent/opa) or the new repo that this issue is about (e.g., open-policy-agent/kubernetes-policy-controller)?

/cc

@tsandall - Ihor has provided me with the details to add the CNCF CLA bot to the new repository. How would you like to proceed?

@lachie83 I'm not familiar with the org transfer process. Is there something you need from me to make it happen? I can add you as an owner in the OPA organization if necessary.

If we want to do an org transfer the repository name would remain the same. Is that okay? I would need repo admin access to setup the CLA before we accept any contributions. Pros for this approach is that all issues and PRs would remain intact.

Ooph. Naming is hard. I hadn't thought about changing the name. I assume we could do that later?

I think it would be good to keep the issues/PRs intact.

I've sent you an invite to the OPA organization. Let me know if you need elevated privileges.

Received. I'm just making sure everything is in order then I will initiate the transfer. We will probably need a team of admins created in GH for that specific repo once transferred.

Great. I'll set up the admin team once the repo has been transferred.

@lachie83 just a quick heads up, I've given you "owner" permission in the OPA org. You should be able to do the transfer any time now. Let me know if there's anything preventing you.

Thanks @tsandall. I'm going to action the transfer tomorrow.

@tsandall I've transferred the repo. Currently working on the CLA bot. I've also create a new maintainers team but haven't yet granted admin privs for maintainers on that repo. I'll leave that to you if you choose to do so.

Hey @tsandall. The repo has been transferred here - https://github.com/open-policy-agent/kubernetes-policy-controller. The following two items are still outstanding:

1. Fix CLA bot - It's triggering but we aren't getting a respond in the check on the PR. We cannot merge ANY contributions until this happens. See [test] Test commit for CLA bot gatekeeper#36
2. We need to DISABLE the DCO bot for all repos in the OPA org and selectively add it for everything but THIS repo (I know it's a pain - I wish you could do an exclusion). Would you like to do that, otherwise I'm happy to BUT it means that all subsequent repos that are added to this org will need to be manually activated to enable the DCO bot to function.

hey all, thanks for driving this to completion.

@caniszczyk just to clarify, you're saying DCO should be enabled on all repos including the new one?

@caniszczyk has fixed the CLA bot so we are done here.

Confirming that we will leave both DCO and CLA bots enabled on this repo.

@tsandall Please close if you feel we have me the requirements of this issue.

LGTM!