[PROJECT ONBOARDING] k3s

[amye]

Welcome to CNCF Project Onboarding!

Please ensure that you:

• Understand the project proposal process and reqs: https://github.com/cncf/toc/blob/master/process/project_proposals.adoc#introduction
• Understand the services available for your project at CNCF https://www.cncf.io/services-for-projects/
• Ensure your project meets the CNCF IP Policy: https://github.com/cncf/foundation/blob/master/charter.md#11-ip-policy
• Has your project adopted open governance already? see http://opengovernance.dev

Formal onboarding:

• Domain: transfer domain to CNCF/LF (ITx)
• Trademarks: transfer any trademark and logo mark assets over to the LF
• GitHub: ensure 'thelinuxfoundation' and 'caniszczyk' are added as initial org owners
• Artwork: Ensure logos present on https://github.com/cncf/artwork
• Website: ensure LF footer is there and website guidelines followed, analytics transferred
• Create maintainer list + added to aggregated https://maintainers.cncf.io list - OWNERS file needed
• Devstats: add to devstats https://devstats.cncf.io/
• Marketing: update relevant intro + slide decks
• Trail Map: update CNCF trail map if relevant (incubating projects and above)
• Update https://landscape.cncf.io
• Events: update CFP + Registration + CFP Area forms
• ServiceDesk: confirm maintainers have read https://www.cncf.io/services-for-projects/
• CNCF Welcome Email Sent to confirm maintainer list access
• Schedule monthly project sync with CNCF staff

[amye]

@cjellick - we'll be tracking work in here.

[lukaszgryglicki]

Is this project going to use a separate GitHub org? Like k3s?

[caniszczyk]

yes we still need to find the right place k3sproject

…

On Thu, Aug 20, 2020 at 2:46 AM Łukasz Gryglicki ***@***.***> wrote: Is this project going to use a separate GitHub org? Like k3s? — You are receiving this because you were assigned. Reply to this email directly, view it on GitHub <#276>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAAPSIOODUZEEFWZ7F4M3NLSBTIHFANCNFSM4QFHOX2Q> .

-- Cheers, Chris Aniszczyk http://aniszczyk.org +1 512 961 6719

[lukaszgryglicki]

Thanks, let me know if I can already assume that org name will be k3sproject?

[lukaszgryglicki]

DevStats page added: https://k3s.devstats.cncf.io, also in "All CNCF" projects health dashboard: https://all.devstats.cncf.io/d/53/projects-health-table.

Company affiliations will be researched starting next week.

[cjellick]

We previously secured the GH org k3s-io (https://github.com/k3s-io) for this purpose. Does that work?

Note that no code repositories have been transferred to it yet. That'll take some time to coordinate and execute.

[cjellick]

I'm CCing @davidnuzik as he'll be helping to track the onboarding work on our end.

[caniszczyk]

@cjellick filed k3s-io/k3s#2189

That organization would work, the "-" drives me crazy in the name but your choice :)

Let us know what you need from us, we have a checklist here: #276

[davidnuzik]

Domain transfer and trademark transfer in progress. I am keeping an eye on these two tasks and will take point on ensuring these two tasks are completed. Additionally, I may assist Craig later with other tasks, as needed.

[amye]

Domain transfer is complete, marking.

[amye]

@davidnuzik: checking in on:

• Trademarks: transfer any trademark and logo mark assets over to the LF
• GitHub: ensure 'thelinuxfoundation' and 'caniszczyk' are added as initial org owners

Thanks!

[davidnuzik]

@amye updates per your query:

• Trademarks: under Rancher legal review currently, in progress and being looked at today. Likely can expect a response today or tomorrow.
• Github: This should already be done, see https://github.com/orgs/k3s-io/people -- this is where the k3s project will get transferred to so its outside of the /rancher/ org. We still need to wrap some things up before this transfer can be done. I don't have an ETA yet but I know we want to at least get k3s v1.19.1+k3s1 release out the door which is planned for this Friday although it could slip into next week.

[davidnuzik]

Update on:

• Trademark document: This has been sent for CNCF review via email.

[amye]

Last thing!
The website footer! https://www.envoyproxy.io/ is a good example.

[davidnuzik]

In progress :) It's moving along but need up to 2 weeks - we are at a critical point trying to get a few huge releases out.

[davidnuzik]

Following up. The below item is in flight. My apologies for the delay on this.

• Website: ensure LF footer is there and website guidelines followed, analytics transferred
  If all goes well this will be done by end of this week.

[davidnuzik]

Website task is complete. All that remains is to complete migrating over to neutrally owned k3s-io github org. This is being tracked via k3s-io/k3s#2189

[caniszczyk]

repos aren't fully migrated over k3s-io/k3s#2189

[caniszczyk]

@amye the k3s website should also have the rancher header stripped from it

[davidnuzik]

@caniszczyk I will see to the removal of the Rancher header from the k3s.io website. rancherlabs/k3s-website#59
Update: Done. We have removed the rancher-header div.

[caniszczyk]

FYI you can still mention that the project originated from Rancher, like say Envoy does with Lyft: https://www.envoyproxy.io/ https://github.com/cncf/foundation/blob/master/website-guidelines.md "It is OK to say that, e.g., “Prometheus was originally created by Soundcloud” or “Kubernetes builds upon 15 years of experience of running production workloads at Google,” but the origin company should not otherwise be referred to on the project homepage."

…

On Mon, Nov 30, 2020 at 12:08 PM David Nuzik ***@***.***> wrote: @caniszczyk <https://github.com/caniszczyk> I will see to the removal of the Rancher header from the k3s.io website. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#276>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAAPSIKSQJYLSNS35SSCUGDSSQJVZANCNFSM4QFHOX2Q> .

-- Cheers, Chris Aniszczyk http://aniszczyk.org +1 512 961 6719

[amye]

Confirming that the header is gone, closing again.