REQUEST: migrate kong/blixt

[shaneutt]

New repo, staging repo, or migrate existing

migrate existing (https://github.com/kong/blixt)

Is it a staging repo?

no

Requested name for new repository

blixt

Which Organization should it reside

kubernetes-sigs

Who should have admin access?

shaneutt, astoycos, robscott, mlavacca

Who should have write access?

shaneutt, astoycos, robscott, mlavacca

Who should be listed as approvers in OWNERS?

shaneutt, astoycos, robscott, mlavacca

Who should be listed in SECURITY_CONTACTS?

shaneutt, astoycos, robscott, mlavacca

What should the repo description be?

A Layer 4 load-balancer for Gateway API conformance testing and examples

What SIG and subproject does this fall under?

SIG Network Gateway API

Please provide references to appropriate approval for this new repo

Discussion in https://groups.google.com/g/kubernetes-sig-network/c/z_N1cLTUO8M/m/l6gO6qLeAgAJ

Additional context for request

No response

[shaneutt]

@thockin, @aojea seemed like everyone was generally positive in the email thread, but wanted to check in with you to see if you're OK with explicitly approving this or if you feel there's more discussion we need to have first?

[astoycos]

/assign @thockin
/assign @robscott
/assign @aojea

(assigning folks from the google groups thread)

Thanks for opening the issue @shaneutt!

[robscott]

Thanks @shaneutt, this request LGTM, but have one request pre-migration: Can you make it slightly more clear that this is never intended to be used for production? It's already clearly stated that the current state of blixt is experimental, but it would be helpful to clarify that production use is permanently out of scope for this project.

[shaneutt]

Thanks @shaneutt, this request LGTM, but have one request pre-migration: Can you make it slightly more clear that this is never intended to be used for production? It's already clearly stated that the current state of blixt is experimental, but it would be helpful to clarify that production use is permanently out of scope for this project.

It is now right at the top of the README.md, let us know if this is sufficient: kubernetes-sigs/blixt@ce90612

[robscott]

LGTM, thanks @shaneutt!

[thockin]

No objections

/lgtm
/approve

[mrbobbytables]

/hold

Just a note - we should not proceed on next donation steps till the GPL license question is answered in cncf/foundation#474

[shaneutt]

@mrbobbytables given the precedents that have already been set with eBPF inclusion in the CNCF we (the Blixt maintainers) have opted to re-license under dual-licensed GPLv2 + BSD-2-Clause:

kubernetes-sigs/blixt#79

As I understand it since this is already an accepted license for projects, it should now be the case that we no longer need cncf/foundation#474 is that correct?

[k8s-triage-robot]

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

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

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

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

/lifecycle stale

[shaneutt]

We are still waiting on the CNCF for this, but it is not stale just taking a while.

/remove-lifecycle stale

[shaneutt]

@mrbobbytables cncf/foundation#474 is now resolved, may we unhold this and move forward?

[mrbobbytables]

yup!

[mrbobbytables]

@shaneutt who from kong has rights to transfer the repo? I'll need to add them to an intermediary org and then we can move it over

[devonl-kong]

@mrbobbytables I will be transferring ownership of the repo. CC: @shaneutt

[mrbobbytables]

kk @devonl-kong I'll shoot you an invite to kubernetes-purgatory, our temp org for transfers.

[devonl-kong]

Thanks @mrbobbytables, the move has been completed. https://github.com/kubernetes-purgatory/blixt

[shaneutt]

At this point I think we're all set, I think the repository has everything in it that's required as of this morning. @mrbobbytables can we close this, or do we have anything remaining we need to do?

[mrbobbytables]

We are good to close!
/close

[k8s-ci-robot]

@mrbobbytables: Closing this issue.

In response to this:

We are good to close!
/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.