Org: Move LWKD into Kubernetes Orgs

[jberkus]

New Repo, Staging Repo, or migrate existing

Migrate Existing

from: https://github.com/lwkd/lwkd.github.io

Requested name for new repository

lwkd

Which Organization should it reside

kubernetes-sigs

If not a staging repo, who should have admin access

The new repo should belong to the Contributor Marketing subproject of ContribEx.

@jberkus, @coderanger
@mbbroberg
@mrbobbytables

If not a staging repo, who should have write access

In addition to the above:
sig-contributor-experience-leads

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

@jberkus, @coderanger
@mbbroberg
@mrbobbytables
sig-contributor-experience-leads

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

N/A (it's a website), but if required the same list as above.

What should the repo description be

Use existing description here: https://github.com/lwkd/lwkd.github.io/blob/main/README.md

After migration, I will update it.

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

This is a publication under the Contributor Marketing project of SIG-ContribEx

Approvals

Approved by Contributor Marketing Group in regular meeting, Friday, March 19th: https://docs.google.com/document/d/1KDoqbw2A6W7rLSbIRuOlqH8gkoOnp2IHHuV9KyJDD2c/edit#

Additional context for request

This is a repository backing a jekyll website. After creation of the new repo, I'll need to change the DNS to point to the new location. Netlify support is not required, as the website is entirely static and has a simple workflow.

Also, because LWKD publishes on Mondays, we need to do the migration bits on a Wednesday-Friday.

Ownership of the domains will be migrated to the CNCF after the repository is moved.

[jberkus]

Related issue here: https://github.com/kubernetes/community/issues/5582

[mrbobbytables]

/approve

[nikhita]

@jberkus The prerequisites listed in https://github.com/kubernetes/community/blob/master/github-management/kubernetes-repositories.md#rules-for-donated-repositories must be completed before we can migrate the repo.

[coderanger]

I think the only thing we need to check off is the template-y files. The only contributor to the repo not already on this thread is one commit from @scollier who I think is under the RedHat CCLA from their past k/k PRs.

[nikhita]

The only contributor to the repo not already on this thread is one commit from @scollier who I think is under the RedHat CCLA from their past k/k PRs.

Yeah, I see contributions to k/k from @scollier so we should be good CLA-wise. :+1:

[jberkus]

@nikhita making note that the link to the project-templates repo needs to be in the issue template for donating repos here. I'll get to it later if you don't first.

[nikhita]

@nikhita making note that the link to the project-templates repo needs to be in the issue template for donating repos here. I'll get to it later if you don't first.

Created #2635

@jberkus @coderanger reminder about adding template files to the lwkd repo :)

[jberkus]

@nikhita hey, I've been going through these requirements, and realized there's one that may be wonky: as a content repository, rather than code, LWKD is Creative Commons Share-Alike. Does it need to be relicensed to Apache in order to be accepted?

[jberkus]

I've also added CONTRIBUTING.md and code-of-conduct.md. It's not clear that the other files in the template repo are applicable. Can you please explain which ones are?

[mrbobbytables]

@jberkus CC is fine, k/website is as well: https://github.com/kubernetes/website/blob/master/LICENSE

[jberkus]

So, from Project Template:

RELEASE.md: there are no releases, what do we put in this?

SECURITY/SECURITY_CONTACTS: since there's no code, what do we do here? Just redirect people to kubernetes-security?

[mrbobbytables]

I wouldn't worry about release.md, its not applicable

For security_contacts, I'd just list the owners. It's more a point of contact if someone does discover a security thing even if there isn't really a chance of one occurring.

[jberkus]

OK, LWKD repo should meet all requirements, now, please check?

[nikhita]

Created https://github.com/lwkd/lwkd.github.io/pull/98 to fix the template files.

I also noticed that the repo has a TRADEMARK file - https://github.com/lwkd/lwkd.github.io/blob/main/TRADEMARK. I don't know how to handle this for the migration.

@swinslow @caniszczyk can you please advise?

[caniszczyk]

We'd have to transfer the ownership of the mark to CNCF:
https://github.com/cncf/foundation/tree/master/agreements

On Wed, May 12, 2021 at 10:50 PM Nikhita Raghunath @.*>
wrote:

Created lwkd/lwkd.github.io#98
https://github.com/lwkd/lwkd.github.io/pull/98 to fix the template
files.

I also noticed that the repo has a TRADEMARK file -
https://github.com/lwkd/lwkd.github.io/blob/main/TRADEMARK. I don't know
how to handle this for the migration.

@swinslow https://github.com/swinslow @caniszczyk
https://github.com/caniszczyk can you please advise?

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

--
Cheers,

Chris Aniszczyk
http://aniszczyk.org

[coderanger]

We don't actually have a legal entity so I'm not sure who can sign that, but I assume Josh?

[caniszczyk]

If there's no legal entity, if you just transfer over the domain and repos,
we should be OK.

It's low risk for us so I'm happy to waive the paperwork.

On Wed, May 12, 2021 at 10:58 PM Noah Kantrowitz @.*>
wrote:

We don't actually have a legal entity so I'm not sure who can sign that,
but I assume Josh?

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

--
Cheers,

Chris Aniszczyk
https://aniszczyk.org

[jberkus]

I can also sign over the trademark if you want me to. Not sure that's really necessary as the employee of a CNCF sponsor, though.

[jberkus]

(that file only really exists because, for a short time in 2018, there was a competing and hostile newsletter)

[caniszczyk]

Not necessary in this case, lmk when you want to do any domain/github repo
transfer dances.

On Thu, May 13, 2021 at 5:08 PM Josh Berkus @.*>
wrote:

(that file only really exists because, for a short time in 2018, there was
a competing and hostile newsletter)

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

--
Cheers,

Chris Aniszczyk
https://aniszczyk.org

[jberkus]

@caniszczyk Our plan was to move the repo first, then transfer the domain. That way I can change the DNS before we hand over control.

[jberkus]

FYI: this issue is currently waiting on infra team availability.