org icon indicating copy to clipboard operation
org copied to clipboard

Published 20 hours ago • verified publisher icon kubernetes

REQUEST: Migrate https://github.com/oracle/cluster-api-provider-oci

Open joekr opened this issue 3 years ago • 11 comments

New repo, staging repo, or migrate existing

migrate existing with a possible rename to cluster-api-provider-oracle-cloud

Is it a staging repo?

no

Requested name for new repository

cluster-api-provider-oci

Which Organization should it reside

kubernetes-sigs

Who should have admin access?

@shyamradhakrishnan, @arindam-bandyopadhyay, @joekr, @Djelibeybi

Who should have write access?

@shyamradhakrishnan, @arindam-bandyopadhyay, @joekr, @Djelibeybi

Who should be listed as approvers in OWNERS?

OWNERS file has been added here https://github.com/oracle/cluster-api-provider-oci/pull/81

Who should be listed in SECURITY_CONTACTS?

SECURITY_CONTACTS file has been added here https://github.com/oracle/cluster-api-provider-oci/pull/81

What should the repo description be?

Kubernetes Cluster API Provider for Oracle Cloud Infrastructure

What SIG and subproject does this fall under?

cluster-api

Please provide references to appropriate approval for this new repo

  • All contributors must have signed the CNCF Individual CLA or CNCF Corporate CLA - Corporate CLA signed
  • Boilerplate text across all files should attribute copyright as follows: "Copyright <Project Authors>" if no CLA was in place prior to donation - we have an open PR to do this once migrated https://github.com/oracle/cluster-api-provider-oci/pull/81
  • Additions of the standard Kubernetes header to code created by the contributors can occur post-transfer, but should ideally occur shortly thereafter. - we have an open PR to do this once migrated https://github.com/oracle/cluster-api-provider-oci/pull/81
  • Should contain template files as per the kubernetes-template-project. - PR https://github.com/oracle/cluster-api-provider-oci/pull/81
  • sig-cloud-provider Group approved migrating this repo request https://docs.google.com/document/d/1mgZxjDbnSv74Vut1aHtWplG6vsR9zu5sqXvQN8SPgCc

Additional context for request

  • Slack channel created: #cluster-api-oci

joekr avatar May 05 '22 15:05 joekr

Hi, @joekr! Excited you're here and I have one question around the fun topic of "naming things". I'm concerned that we might create confusion since "OCI" in an upstream Kubernetes context is commonly used for "Open Container Initiative" as seen in:

  • https://opencontainers.org/faq/
  • https://github.com/opencontainers
  • https://github.com/opencontainers/distribution-spec
  • https://kubebyexample.com/en/learning-paths/container-fundamentals/standards/oci-specifications
  • https://github.com/oras-project

In looking at the names on https://cluster-api.sigs.k8s.io/reference/providers.html#infrastructure it seems usually the company name is used, and very occasionally a project name or acronym.

Would cluster-api-oc or cluster-api-oracle serve the same purpose but avoid the possible ambiguity? Thanks.

bridgetkromhout avatar May 25 '22 17:05 bridgetkromhout

Howdy @bridgetkromhout 👋 🤠

I will update the issue to ask to have the repo name changed from cluster-api-provider-oci to cluster-api-provider-oracle-cloud-infrastructure upon donation to help clear up confusion. This also helps keep our naming consistent as well 😄 https://www.oracle.com/in/cloud/

joekr avatar May 26 '22 13:05 joekr

+1 for the transfer on my side.

neolit123 avatar May 31 '22 16:05 neolit123

@joekr it looks like everyone set for owners/admin/write access are not org members, could you open up requests for org membership? If it'd speed things along, just need 1 person to start (feel free to use me as a sponsor to start the ball rolling)

Also do you have permission to migrate the repo? We have a temporary org (https://github.com/kubernetes-purgatory) that we invite external folk to is a staging ground before migrating into the org. For companies it might be an internal github admin.

/assign

mrbobbytables avatar Jun 12 '22 21:06 mrbobbytables

I've requested membership thanks 😄 https://github.com/kubernetes/org/issues/3499

I don't have permission to migrate. I'll track down the person we will want to handle that.

joekr avatar Jun 13 '22 15:06 joekr

@mrbobbytables I don't have permission but @Julia3072 or @spavlusieva will have access to be able to transfer.

joekr avatar Jun 15 '22 12:06 joekr

@Julia3072 @spavlusieva - can one of you ack on here to confirm adding to the other org?

mrbobbytables avatar Jun 20 '22 19:06 mrbobbytables

@shyamradhakrishnan https://github.com/kubernetes/org/issues/3509 has been added as a member

joekr avatar Jun 21 '22 12:06 joekr

Just checking in, is this still something to be pursued? we need to transfer the repo to the intermediary org before we can bring it in here.

mrbobbytables avatar Sep 14 '22 16:09 mrbobbytables

@mrbobbytables yes, we are actively working on this, albeit slowly. In order to donate we have to get a lot of sign off, which we are working on.

joekr avatar Sep 14 '22 17:09 joekr

No worries! just wanted to double check

mrbobbytables avatar Sep 14 '22 17:09 mrbobbytables

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue or PR as fresh with /remove-lifecycle stale
  • Mark this issue or PR as rotten with /lifecycle rotten
  • Close this issue or PR with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

k8s-triage-robot avatar Dec 13 '22 17:12 k8s-triage-robot

We are still working on getting approval to migrate.

joekr avatar Dec 13 '22 17:12 joekr

/remove-lifecycle stale

joekr avatar Dec 13 '22 17:12 joekr

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue or PR as fresh with /remove-lifecycle rotten
  • Close this issue or PR with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

k8s-triage-robot avatar Jan 12 '23 18:01 k8s-triage-robot

/remove-lifecycle rotten

joekr avatar Jan 12 '23 19:01 joekr

Sorry, I promise we are working on this. 😞

joekr avatar Jan 12 '23 19:01 joekr

@joekr Hi! Any update about this ? Can we freeze this issue until things are unlocked on your side ?

ameukam avatar Mar 01 '23 07:03 ameukam

I'm still trying to get approval on my end. Sorry it has taken so long. Feel free to freeze it.

joekr avatar Mar 01 '23 11:03 joekr

/lifecycle frozen

ameukam avatar Mar 01 '23 11:03 ameukam

We're going on about a year now - is this still ongoing?

mrbobbytables avatar Apr 25 '23 13:04 mrbobbytables

.... I know ... I know ....

It is still ongoing internally. If this is causing issues on your all's end lets close this then I can reopen it or create a new one. Sorry for the delay.

joekr avatar Apr 25 '23 14:04 joekr

So this doesn't continue to cause issues I'll close this for now. Then just create a new issue when we are actually ready.

joekr avatar Apr 27 '23 12:04 joekr