Request to create new bare repository kubernetes-sigs/nodus on behalf of sig-scheduling

[ConnorDoyle]

New Repo, Staging Repo, or migrate existing

Migrate existing repository

Requested name for new repository

nodus

Which Organization should it reside

kubernetes-sigs

If not a staging repo, who should have admin access

• @ConnorDoyle
• @bsalamat

If not a staging repo, who should have write access

• @ConnorDoyle
• @bsalamat

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

• @ConnorDoyle
• @bsalamat

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

• @ConnorDoyle
• @bsalamat

What should the repo description be

"Simulated large clusters for Kubernetes scheduler validation."

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

This is a new subproject for sig-scheduling called nodus podens

Approvals

This project was demonstrate at the public sig-scheduling community meeting on March 28, 2019 where we also discussed donation to the kubernetes org. See meeting minutes here: https://docs.google.com/document/d/13mwye7nvrmV11q9_Eg77z-1w3X7Q1GTbslpml4J7F3A/edit#bookmark=id.ec3hugviwj29

The sig-scheduling charter states that subproject creation is at the sole discretion of the sig tech leads (@bsalamat).

Thanks!

[nikhita]

@ConnorDoyle Apologies for the late reply, this somehow missed my radar!

Few questions:

• The issue says that an existing repo is supposed to be migrated...but also to create a bare repo. I'm confused. :) Is the bare repo intended to be populated with contents of an existing repo? In that case, we would prefer directly migrating the existing repo after ensuring that it satisfies our requirements.

• The meeting notes don't explicitly call out an approval from a SIG lead (feel free to send me a link, if I missed it though!). Would it be possible to send out an email to the sig-scheduling mailing list with a lazy conensus asking for approval from a SIG lead and/or asking one of the leads to lgtm here?

[nikhita]

/assign

[ConnorDoyle]

Thanks for taking a look @nikhita!

The issue says that an existing repo is supposed to be migrated...but also to create a bare repo.

Yes, apologies for the confusion. In the (distant) past for incubator projects we used to push an entire history to a bare repo. We can also transfer ownership of the existing repository. Either way is ok with me. For now the code is here: https://github.com/IntelAI/nodus and I've just made the repo public now that we have cleared our internal SDL process.

meeting notes don't explicitly call out an approval

I posted a message to the sig-scheduling mailing list this morning asking for input. I have separately pinged @bsalamat in our offline discussions but I believe Kubecon and the aftermath may have kept him busy with other things.

[nikhita]

Thanks, @ConnorDoyle! I'll wait for approval on the mailing list. 👍

To save time later, I audited requirements needed for migrating repos. Few points about them:

• Everyone who has contributed to the repo needs to have signed the CNCF CLA. @Ajay191191 and @scttl don't have the CLA signed.
  @Ajay191191 and @scttl: In order to migrate the nodus repo, could you sign the CNCF CLA? Instructions for it are here.

• Kubernetes repos need to have certain template files. Can you add code-of-conduct.md, CONTRIBUTING.md, OWNERS and SECURITY_CONTACTS files according the https://github.com/kubernetes/kubernetes-template-project template?

• I ran a FOSSA license scan on the repo and it was green. 👍

• While the existing licenses are ok, all files need the Kubernetes boilerplate header. Can you add these as well? Boilerplate headers for different file extensions can be found here.
  (Btw Script to automatically add licence headers repo-infra#82 might prove useful to automatically update these 😄 )

[scttl]

Apologies for the delay here @nikhita but I've now signed the CNCF CLA.

[nikhita]

@scttl Awesome, thanks for following up! I can confirm that your CLA is signed. 👍

[nikhita]

@ConnorDoyle 👋 Just wanted to check if there are any updates on this?

[ConnorDoyle]

Ajay signed the CLA last week and I’ll post back once the repo updates are complete

[spiffxp]

@ConnorDoyle ping to see where we're at on this

[nikhita]

Closing this due to lack of activity. Please reopen when the repo creation is approved and we'll create the repo. :)

/close

[k8s-ci-robot]

@nikhita: Closing this issue.

In response to this:

Closing this due to lack of activity. Please reopen when the repo creation is approved and we'll create the repo. :)

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