UMRELLA: Move Cluster API provider for DigitalOcean to Upstream

[xmudrii]

User story

On Cluster-API meetings held on 8/22 and 9/19, we have discussed about making Cluster API provider for DigitalOcean as an Cluster-API project and moving it from kubermatic to kubernetes-sigs organization.

The feedback overall is positive, but we need to fulfill the ownership requirement. The latest requirement is to have multiple owners from the multiple companies.

It is up to follow on this issue and to discuss how we can continue the process.

Prerequisites

• Add CONTRIBUTING.md (Add contributing guidelines #91)
• Establish OWNERS and OWNER_ALIASES files (Establish OWNERS and OWNERS_ALIASES files #107, Update OWNERS to match cluster-api OWNERS state #112)
• Add SECURITY_CONTACTS file (Add SECURITY_CONTACTS #108)
• Add copyright boiler plate header to all files (Add copyright boilerplate header to all files #110)
• Add script to verify boilerplate header (Add script to verify boilerplate header #111)
• License Auditing
• Creating an issue on kubernetes/org (Create repository for cluster-api-provider-digitalocean as a SIG Cluster Lifecycle subproject kubernetes/org#196)
• Enabling the Circle CI status contexts as required in kubernetes/test-infra (prow: add required contexts and merge method for Cluster-API DO provider kubernetes/test-infra#9938)
• Update prow/config.yaml in kubernetes/test-infra to set merge method (prow: add required contexts and merge method for Cluster-API DO provider kubernetes/test-infra#9938)
• Disable integration with Kubermatic internal Prow
• Ensure relevant webhooks are enabled.
  • cncf-cla webhook
  • prow's webhook
• Update CONTRIBUTING.md to mention Kubernetes slack channels.
• Find how to correctly handle Docker images
• Update README and docs to use new repository URL
• Update Go import paths to sigs.k8s.io/cluster-api-provider-digitalocean/...
• Update sigs.yaml file in kubernetes/community (sigs.yaml: add DO Cluster-API provider as SIG Cluster Lifecycle subproject kubernetes/community#2864)

Acceptance criteria

• Cluster-API provider for DigitalOcean is upstreamed.

[xmudrii]

Testing does Prow works after migration.

/meow boxes

[k8s-ci-robot]

@xmudrii:

In response to this:

Testing does Prow works after migration.

/meow boxes

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[xmudrii]

Relevant webhooks (Prow and CNCF CLA check) are enabled at the organization level.

CircleCI is enabled, but we need to make contexts work. The plan is to move to Prow as soon as possible.

I've updated issue with some more points that we should resolve before considering migration done.

[xmudrii]

@nikhita Is it okay to close this issue? I'm going to take care of updating the contributing guidelines later today and we can create a follow up for license auditing.

[nikhita]

Sgtm.

/close

[k8s-ci-robot]

@nikhita: Closing this issue.

In response to this:

Sgtm.

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.