Test-infra: Incubating a new project at kubernetes-sigs

[dhilipkumars]

Hi All,

We have incubated a new project into kubernetes-sigs sponsored by scheduler-sig. We have a couple of questions.

1. Are k8s bots already configured to look at other organizations? If no what is the procedure to do that?
2. Do we have an example project that has configured Bots , CI & CD pipe-line for projects outside k/*?

cc: @kubernetes/sig-scheduling-misc @shivramsrivastava @deepak-vij @timothysc

[BenTheElder]

1) yes, we have repos in a couple orgs, but if we add a new org we have to
configure it (EG sending webhooks to an app must be configured on each org
or repo) where is this project exactly?

2) yes, see EG https://github.com/kubernetes-sig-testing/frameworks

On Thu, Mar 8, 2018, 07:58 Dhilip [e-mail] wrote:

Hi All,

We have incubated a new project into kubernetes-sigs sponsored by
scheduler-sig. We have a couple of questions.

1. Are k8s bots already configured to look at other organizations? If
   no what is the procedure to do that?
2. Do we have an example project that has configured Bots , CI & CD
   pipe-line for projects outside k/*?

cc: @kubernetes/sig-scheduling-misc
https://github.com/orgs/kubernetes/teams/sig-scheduling-misc
@shivramsrivastava https://github.com/shivramsrivastava @deepak-vij
https://github.com/deepak-vij @timothysc https://github.com/timothysc

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/kubernetes/test-infra/issues/7184, or mute the thread
https://github.com/notifications/unsubscribe-auth/AA4Bq5uKwZQMkOXthzYgbPfJ1V3Y4-yvks5tcVUngaJpZM4Si6Kk
.

[dhilipkumars]

The project is here: https://github.com/kubernetes-sigs/scheduling_poseidon

[stevekuznetsov]

Do we want that under kubernetes-sig-scheduling ?

[stevekuznetsov]

/assign @spiffxp

[BenTheElder]

We need to get @spiffxp or someone else with the appropriate GitHub permissions to set up the webhook for Prow, then we can enable plugins, test jobs, and the merge automation as desired.

[dhilipkumars]

Do we want that under kubernetes-sig-scheduling ?
@timothysc Is there a scheduler sig specific org just like the one for testing?

[stevekuznetsov]

@dhilipkumars yes: https://github.com/kubernetes-sig-scheduling

[dhilipkumars]

@stevekuznetsov that organization looks more appropriate for this project, but i will defer it to Tim and Bobby on why they chose this organization instead.
cc: @timothysc @bsalamat

[bsalamat]

I am fine with hosting the Poseidon project in SIG scheduling repo, but these SIG repos are very new and I am not aware of the details of their locations, etc. @timothysc has set up this repo. He should be able to help.

[resouer]

What's the relationship of:
https://github.com/kubernetes-sig-scheduling
and
https://github.com/kubernetes-sigs?

An will https://github.com/kubernetes-incubator be deprecated?

Will be appreciate if anyone can provide more context and background ...

[spiffxp]

ref: https://github.com/kubernetes/community/blob/master/kubernetes-repositories.md

Please use kubernetes-sigs. An org level webhook is already setup, and most plugins are enabled (ref #6623). At this point if you have additional plugins you want to setup for your repo (ie: approval, trigger), you can PR them in via changes to prow/plugins.yaml and prow/config.yaml same as we allow for kubernetes/* and kubernetes-incubator/*

The creation of all of the other kubernetes-sig-foo orgs was a landgrab on our part in case we wanted to head that direction. We used kubernetes-sig-testing as an experiment, but have since decided to to move ahead with kubernetes-sigs instead. It's easier to administer one org than ~30

We will migrate kubernetes-sig-testing/frameworks to kubernetes-sigs/testing_frameworks

I'm looking and not finding much int the way of official looking docs on incubator being retired, or kubernetes-sigs being the place, so I'll open up some issues to follow up. Let me know if this has answered your questions @resouer @dhilipkumars

[timothysc]

We will migrate kubernetes-sig-testing/frameworks to kubernetes-sigs/testing_frameworks

done.

We should nuke the other orgs too.

[dhilipkumars]

@spiffxp and @timothysc Thanks, both of you for the clarification, I was thinking this is kubernetes-sigs was an older org and our project needs to move.

Closing the issue