state of kubernetes-incubator/kube-aws

[Lubomir I. Ivanov]

hello,

in today's (28.07.2020) SIG Cluster Lifecycle meeting we discussed the
state of the kubernetes-incubator/kube-aws project.

TL;DR for those who have not been following the recent discussions:
- the kube-aws maintainers wished to move the project out of
k-incubator to k-sigs (graduate).
- SIG ContribEx want to sunset k-incubator and kube-aws is one of the
last two projects in there.

SIG Cluster Lifecycle latest stance is that kube-aws has not been part
of the SIG landscape of projects and it has not reported it's state to
the SIG. under different circumstances kube-aws could have been
graduated to a k-sigs (org) subproject but at this point we would
prefer if it moves to its own organization.

in fact this organization already exists and the maintainers are
willing to go that route (based on private discussions):
github.com/kube-aws

the main benefit discussed with the maintainers of being under k-sigs
for them is the CI / bot integration and for those we kindly ask
ContribEx or members of other SIGs to help the kube-aws maintainers if
they happen to ask for such help.

we should close the pending issue (moving kube-aws to k-sigs):
https://github.com/kubernetes/org/issues/2004

and help kube-aws move to github.com/kube-aws/kube-aws

thank you
lubomir
--

[Christoph Blecker]

Hi Lubomir,

Thanks for sending this! It looks like they already have a fork of the repo. They can contact GitHub support per docs, to request that it be separated from the current upstream repo. Then we'll move the kubernetes-incubator/kube-aws repo to kubernetes-retired.

As for CI, that's trickier.. what are they looking for exactly? Some of the functionality can be duplicated with GitHub Actions, or another CI system like Travis, etc. However, we are trying to keep prow.k8s.io limited to only Kubernetes project repos itself.

Cheers,

Christoph

--
You received this message because you are subscribed to the Google Groups "kubernetes-sig-contribex" group.
To unsubscribe from this group and stop receiving emails from it, send an email to kubernetes-sig-con...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/kubernetes-sig-contribex/CAGDbWi97nj8p9tNPh3J1z9vxMVtxufy3bn9S_T5rU7nv5M6Ceg%40mail.gmail.com.

[Lubomir I. Ivanov]

On Tue, 28 Jul 2020 at 20:49, Christoph Blecker <cble...@gmail.com> wrote:
>
> Hi Lubomir,
> Thanks for sending this! It looks like they already have a fork of the repo. They can contact GitHub support per docs, to request that it be separated from the current upstream repo. Then we'll move the kubernetes-incubator/kube-aws repo to kubernetes-retired.
>

this seems straightforward.

> As for CI, that's trickier.. what are they looking for exactly? Some of the functionality can be duplicated with GitHub Actions, or another CI system like Travis, etc. However, we are trying to keep prow.k8s.io limited to only Kubernetes project repos itself.
>

AFAIK (the kube-aws maintainers should correct me), they wanted to use
the CLA bot, but apparently this can be done with this standalone app:
https://github.com/apps/cla-bot.
for the LGTM / approve / CI functionality they could end up running a
separate instance of prow, or just have e.g. custom GitHub actions.

temporary, manual merging of PRs was also considered.

lubomir
--

[Christoph Blecker]

The current CLA bot that the LF uses is closed source (working on it), and wouldn't really apply anymore if the project moves out from the Kubernetes project. But yeah, there are other CLA bots, or options like using a DCO if the maintainers want legal protections of some kind. I'm not a lawyer and can't give advice in that regard.

Do we have a timeline of how long the kube-aws maintainers will need to get things hooked up on their side?

Cheers,

Christoph

[Lubomir I. Ivanov]

On Tue, 28 Jul 2020 at 21:10, Christoph Blecker <cble...@gmail.com> wrote:
>
> The current CLA bot that the LF uses is closed source (working on it), and wouldn't really apply anymore if the project moves out from the Kubernetes project. But yeah, there are other CLA bots, or options like using a DCO if the maintainers want legal protections of some kind. I'm not a lawyer and can't give advice in that regard.
>

this is something that they definitely need to consider. once the
subproject is no longer governed by k8s and the CNCF, the CLA is no
longer applicable and DCO seems like a viable option.
one day they could apply for CNCF adoption as a standalone project and
request CLA from their contributors again.

> Do we have a timeline of how long the kube-aws maintainers will need to get things hooked up on their side?

i have notified the maintainers on private slack with a request that
they reply to this email thread to confirm their agreement.

given the existing fork and given we want to sunset incubator ASAP, i
think ideally ContribEx should define a timeline for the actions that
have to be taken on the k8s org side and i don't see any major
blockers for these actions.

lubomir
--

[Yusuke KUOKA]

Hi Christoph,

Could you move the current repo to `kube-aws` org instead? The fork is there just for testing various automation to be used after the move, not meant to be a persistent repo for the project.

I've already moved the fork somewhere else, so I believe you can move the repo to kube-aws org right now.

Best,

Yusuke

2020年7月29日水曜日 2時49分48秒 UTC+9 Christoph Blecker:

To unsubscribe from this group and stop receiving emails from it, send an email to kubernetes-sig-contribex+unsub...@googlegroups.com.

[Yusuke KUOKA]

Hi,

As you might have already discussed in today's SIG meeting, we kube-aws maintainers are willing to move to our own github org.

Could anyone(maybe Christoph?) with the admin priv on the current kube-aws repo move it to `kube-aws` org? After that there should be no blocker for other tasks.

We appreciate whoever worked for the incubator. I believe the incubator had been a great place to build kube-aws and contribute back our "thanks" to the k8s community.

We also appreciate everyone in scl helped moving this project.

Thanks,

Yusuke

2020年7月29日水曜日 3時19分24秒 UTC+9 Lubomir I. Ivanov:

[Lubomir I. Ivanov]

Yusuke, looks like your last email did not make it to the ContribEx
mailing list.
adding it on CC.

ContribEx, it contains questions for the group WRT moving the kube-aws
project, please see below.

lubomir
--

> --
> You received this message because you are subscribed to the Google Groups "kubernetes-sig-cluster-lifecycle" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to kubernetes-sig-cluster...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/kubernetes-sig-cluster-lifecycle/ec83ffaa-4836-495f-b2c8-e20452eeea83o%40googlegroups.com.

[Christoph Blecker]

Hi Yusuke,

For clarity, we will not be moving the *existing* repo out to github.com/kube-aws. We will archive that repo (make it read only) and you can continue maintaining it as a fork. You can change the readme and such of the current repo to point to the new location where the project will live on. Once that is done, you'll also need to move over any issues/PRs you want to keep.

We'd like to get the current repo archived by September 30 at the latest. Please let me know if you have any questions, or if you are ready for us to archive the current location sooner.

Thanks!

Christoph

You received this message because you are subscribed to the Google Groups "kubernetes-sig-contribex" group.
To unsubscribe from this group and stop receiving emails from it, send an email to kubernetes-sig-con...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/kubernetes-sig-contribex/CAGDbWi__WxKKR5mecvvquZPbw9%2BdSVN71Bk9xM%2BBn-veJ%2B_3iw%40mail.gmail.com.