Org: Repo donation: Pluies/zeitgeist --> Release Engineering

[justaugustus]

New Repo, Staging Repo, or migrate existing

https://github.com/Pluies/zeitgeist

Requested name for new repository

zeitgeist

Which Organization should it reside

kubernetes-sigs

If not a staging repo, who should have admin access

@kubernetes/sig-release-admins

If not a staging repo, who should have write access

@kubernetes/sig-release-admins + @Pluies

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

Covered in https://github.com/Pluies/zeitgeist/pull/7

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

Covered in https://github.com/Pluies/zeitgeist/pull/7

What should the repo description be

Zeitgeist: the language-agnostic dependency checker

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

SIG Release / Release Engineering subproject

Approvals

Approving as a SIG Release Chair after discussing donation with @Pluies.
Adding other @kubernetes/sig-release-leads for approvals.

Additional context for request

Zeitgeist was created by @Pluies and is inspired by @yastij's script to manage external dependencies and extended to include checking with upstream sources to ensure dependencies are up-to-date.

@yastij -- let us know if you'd be interested in helping maintain as well!

TODO

• [x] (@Pluies) Merge https://github.com/Pluies/zeitgeist/pull/7
• [x] (@Pluies) Add boilerplate header text to all files
• [x] (@Pluies) Sign the CLA

cc: @kubernetes/release-engineering
/sig release
/area release-eng dependency
Slack tracking: https://kubernetes.slack.com/archives/C2C40FMNF/p1599121368081100

[k8s-ci-robot]

@justaugustus: The label(s) area/release-eng cannot be applied, because the repository doesn't have them

In response to this:

New Repo, Staging Repo, or migrate existing

https://github.com/Pluies/zeitgeist

Requested name for new repository

zeitgeist

Which Organization should it reside

kubernetes-sigs

If not a staging repo, who should have admin access

@kubernetes/sig-release-admins

If not a staging repo, who should have write access

@kubernetes/sig-release-admins + @Pluies

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

Covered in https://github.com/Pluies/zeitgeist/pull/7

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

Covered in https://github.com/Pluies/zeitgeist/pull/7

What should the repo description be

Zeitgeist: the language-agnostic dependency checker

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

SIG Release / Release Engineering subproject

Approvals

Approving as a SIG Release Chair after discussing potential donation with @chuckha yesterday.
Adding other @kubernetes/sig-release-leads for approvals.

Additional context for request

Zeitgeist was created by @Pluies and is inspired by @yastij script to manage external dependencies and extended to include checking with upstream sources to ensure dependencies are up-to-date.

@yastij -- let us know if you'd be interested in helping maintain as well!

cc: @kubernetes/release-engineering
/sig release
/area release-eng dependency

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.

[justaugustus]

cc: @kubernetes/owners
/assign @nikhita

[nikhita]

Needs the following things before we can transfer the repo:

• The Kubernetes boilerplate header needs to be added to all files - https://github.com/kubernetes/kubernetes/tree/master/hack/boilerplate

• Template files like code-of-conduct, etc need to be added. Also, needs addition of this section - https://github.com/kubernetes/kubernetes-template-project#community-discussion-contribution-and-support to the README. All template files can be found at https://github.com/kubernetes/kubernetes-template-project.

[nikhita]

Ah, just saw that https://github.com/Pluies/zeitgeist/pull/7 addressed the second point. Thanks @justaugustus!

[justaugustus]

* The Kubernetes boilerplate header needs to be added to all files - https://github.com/kubernetes/kubernetes/tree/master/hack/boilerplate

@nikhita -- I purposely skipped this part, as our docs mention this can be added shortly after migration. More so, legally, I wasn't sure if that needed to be added by the repo owner. If it's actually cool for me to add it, I can update the PR with the boilerplate text.

Additions of the standard Kubernetes header to code created by the contributors can occur post-transfer, but should ideally occur shortly thereafter.

ref: https://github.com/kubernetes/community/blob/master/github-management/kubernetes-repositories.md#rules-for-donated-repositories

[nikhita]

I purposely skipped this part, as our docs mention this can be added shortly after migration.

Yes, we can technically do this after migration as well. Ideally, we try to get it in before migration to ensure all boxes are ticked though. :woman_shrugging:

More so, legally, I wasn't sure if that needed to be added by the repo owner.

You are right! It needs to be added by the repo owner from a legal standpoint. In this case, @pluies would need to add them.

[justaugustus]

@Pluies -- you'll also need to sign the CLA (Contributor License Agreement).
Details here: https://github.com/kubernetes/community/blob/master/CLA.md#how-do-i-sign

Let us know if you have any questions! :)

[justaugustus]

You are right! It needs to be added by the repo owner from a legal standpoint. In this case, @Pluies would need to add them.

SGTM! Added a TODO section for Florent in the issue description.

[Pluies]

Thank you both for the guidance – here is the PR adding the boilerplate for review :) https://github.com/Pluies/zeitgeist/pull/8

[Pluies]

I went to sign the CLA and realised I had already signed it in February 2019, so it should be all good! 🤞

[justaugustus]

@nikhita -- it sounds like we've got everything we need from Florent. What's up next?

[nikhita]

@Pluies since this is a user-owned repo vs an org-owned repo, we'll need to first transfer the repo to a dummy org for moving to k-sigs (GitHub doesn't allow adding admins to user-owned repos).

Can you move the repo to https://github.com/kubernetes-purgatory when you get a chance? I can then move it to @kubernetes-sigs.

[Pluies]

Hi @nikhita ,
All done! Zeitgeist is now in https://github.com/kubernetes-purgatory/zeitgeist :)

[nikhita]

Repo has been transferred - https://github.com/kubernetes-sigs/zeitgeist :tada:

Created:

• https://github.com/kubernetes/org/pull/2179 - to add GitHub teams to grant access
• https://github.com/kubernetes/community/pull/5104 - to add the repo to sigs.yaml

Once both PRs merge, we can close this issue.

---

@Pluies in order to get write access on the repo, you'll need to apply for membership to the @kubernetes-sigs org. https://github.com/kubernetes/community/blob/master/community-membership.md#member has instructions on how to apply. :)

[yastij]

@Pluies @justaugustus - happy to help maintain it !

[nikhita]

Teams have been granted access and all PRs have merged. Closing!

[justaugustus]

Thanks everyone. You all rock!

[justaugustus]

Follow-up PR adding @Pluies and @yastij is here: https://github.com/kubernetes/org/pull/2180

[Pluies]

Thanks for getting this done! 🙏

@Pluies in order to get write access on the repo, you'll need to apply for membership to the @kubernetes-sigs org. https://github.com/kubernetes/community/blob/master/community-membership.md#member has instructions on how to apply. :)

I think I've got everything on the checklist done... Except for the sponsors! And that should be arranged before opening the PR, so – @justaugustus and @nikhita , would you be happy to be sponsoring my application by any chance? :)

[nikhita]

Yes, feel free to count me in! :)

On Tue, Sep 8, 2020 at 8:09 PM Florent Delannoy [e-mail]
wrote:

Thanks for getting this done! 🙏

@Pluies https://github.com/Pluies in order to get write access on the
repo, you'll need to apply for membership to the @kubernetes-sigs
https://github.com/kubernetes-sigs org.
https://github.com/kubernetes/community/blob/master/community-membership.md#member
has instructions on how to apply. :)

I think I've got everything on the checklist done... Except for the
sponsors! And that should be arranged before opening the PR, so –
@justaugustus https://github.com/justaugustus and @nikhita
https://github.com/nikhita , would you be happy to be sponsoring my
application by any chance? :)

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/kubernetes/org/issues/2172#issuecomment-688922358,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AD24BUFADOIBXC7LI3TU3GDSEY62JANCNFSM4QUPIEAQ
.

[justaugustus]

@Pluies -- you can go ahead and file a membership request for kubernetes-sigs and we can sort membership there.

Nikhita, @tpepper, and I are all at VMware, so you'll need one more non-VMware sponsor, which I'm sure either of the other SIG Release leads (@saschagrunert, @alejandrox1) will be happy to provide. :)

[saschagrunert]

Yes, happy to sponsor as well. 👍

[Pluies]

Thank you @nikhita @justaugustus @saschagrunert - PR open at https://github.com/kubernetes/org/issues/2181 :)