Migrate existing repo to kubernetes-sigs

[logicalhan]

Migrate existing repository

https://github.com/jpbetz/auger

Requested name for new repository

auger

Which Organization should it reside

kubernetes-sigs

If not a staging repo, who should have admin access

@logicalhan, @ehashman, @dashpole, @brancz, @jpbetz, @lilic

If not a staging repo, who should have write access

@logicalhan, @ehashman, @dashpole, @brancz, @jpbetz, @lilic

If not a staging repo, who should be listed as approvers in OWNERS

@logicalhan, @ehashman, @dashpole, @brancz, @jpbetz, @lilic

If not a staging repo, who should be listed in SECURITY_CONTACTS

@logicalhan, @ehashman, @dashpole, @brancz, @jpbetz, @lilic

What should the repo description be

Directly access data objects stored in etcd by kubernetes.

Encodes and decodes Kubernetes objects from the binary storage encoding used to store data to etcd. Supports data conversion to YAML, JSON and Protobuf.

Automatically determines if etcd data is stored in JSON (kubernetes 1.5 and earlier) or binary (kubernetes 1.6 and newer) and decodes accordingly.

What SIG and subproject does this fall under in sigs.yaml

SIG-Instrumentation

Approvals

https://docs.google.com/document/d/1FE4AQ8B49fYbKhfg4Tx0cui1V0eI4o3PxoqQPUwNEiU/edit#bookmark=id.2oxueh6uc3as

[logicalhan]

/sig instrumentation
/cc @jpbetz @brancz @lilic @ehashman @dashpole

[ehashman]

👍 We discussed in the 2021-07-22 SIG Instrumentation meeting: https://docs.google.com/document/d/1FE4AQ8B49fYbKhfg4Tx0cui1V0eI4o3PxoqQPUwNEiU/edit#heading=h.4wufkfwwyr6x

[lilic]

👍 sounds great!

[mrbobbytables]

/assign

[k8s-triage-robot]

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

[nikhita]

/remove-lifecycle stale

@logicalhan Apologies for the delayed response. There are a few things we'll need to address before this can be migrated over to kubernetes.

• One of the contributors (@paramsiddharth) has not signed the CNCF CLA. They'll need to sign the CLA for the repo to be migrated over. @paramsiddharth you can find the instructions for signing the CLA here.

• There is a typo in the OWNERS file name right now (s/OWNER/OWNERS). Without this fix, PRs cannot be approved.

• The CONTRIBUTING.md needs to the format in the template file. Right now, the doc says "contributing to service catalog" so that'll need to be fixed as well.

• The "community, discussion and support" and the "code of conduct" sections should be added to the README.md as in this template file.

Once these issues are addressed, please ping us again and we can help migrate the repo.

[paramsiddharth]

...

• One of the contributors (@paramsiddharth) has not signed the CNCF CLA. They'll need to sign the CLA for the repo to be migrated over. @paramsiddharth you can find the instructions for signing the CLA here.
  ...

@nikhita Thank you for the notification, I just finished signing the CLA. Please verify and let me know anything else I need to do for the migration.

[k8s-triage-robot]

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

[mrbobbytables]

/remove-lifecycle stale
This fell off our radar :x Just double checking...do you still want to proceed with the migration?

[paramsiddharth]

/remove-lifecycle stale This fell off our radar :x Just double checking...do you still want to proceed with the migration?

@logicalhan @jpbetz Thoughts? I suppose we should proceed with the migration, shouldn't we?

[jpbetz]

Yeah, I think we should proceed.

[paramsiddharth]

/remove-lifecycle stale

@logicalhan Apologies for the delayed response. There are a few things we'll need to address before this can be migrated over to kubernetes.

• One of the contributors (@paramsiddharth) has not signed the CNCF CLA. They'll need to sign the CLA for the repo to be migrated over. @paramsiddharth you can find the instructions for signing the CLA here.
• There is a typo in the OWNERS file name right now (s/OWNER/OWNERS). Without this fix, PRs cannot be approved.
• The CONTRIBUTING.md needs to the format in the template file. Right now, the doc says "contributing to service catalog" so that'll need to be fixed as well.
• The "community, discussion and support" and the "code of conduct" sections should be added to the README.md as in this template file.

Once these issues are addressed, please ping us again and we can help migrate the repo.

@nikhita Are any of these still pending?

[mrbobbytables]

The OWNERS file, the template files and something else that was missed - There are 5 files that are missing kubernetes author headers:

Dockerfile
Makefile
cmd/analyze.go
cmd/checksum.go
main.go

[mrbobbytables]

Just a reminder ping, once those files are updated we should be able to proceed with migration.

[logicalhan]

/cc @jpbetz

[logicalhan]

/reopen

[k8s-triage-robot]

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]

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]

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:

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

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

/close

[k8s-ci-robot]

@k8s-triage-robot: Closing this issue.

In response to this:

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:

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

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

/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.

[logicalhan]

/reopen

[k8s-ci-robot]

@logicalhan: Reopened this issue.

In response to this:

/reopen

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.

[k8s-triage-robot]

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

This bot triages issues 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:

• Reopen this issue with /reopen
• Mark this issue as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

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

/close not-planned

[k8s-ci-robot]

@k8s-triage-robot: Closing this issue, marking it as "Not Planned".

In response to this:

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

This bot triages issues 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:

• Reopen this issue with /reopen
• Mark this issue as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

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

/close not-planned

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.

[ehashman]

@logicalhan what's going on with this?