[PROJECT ONBOARDING] Kubeflow

[amye]

Welcome to CNCF Project Onboarding!
This is an issue created to help onboard your project into the CNCF after the TOC has voted to accept your project.
We would like to complete onboarding within one month of acceptance.

From the project side, please ensure that you:

• Understand the project proposal process and reqs: https://github.com/cncf/toc/blob/main/process/project_proposals.md#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
• Review the online programs guidelines: https://github.com/cncf/foundation/blob/master/online-programs-guidelines.md
• Understand the trademark guidelines: https://www.linuxfoundation.org/legal/trademark-usage
• Understand the license allowlist: https://github.com/cncf/foundation/blob/master/allowed-third-party-license-policy.md#approved-licenses-for-allowlist
• Is your project working on written, open governance? see https://contribute.cncf.io/maintainers/governance/
• Slack: Are your slack channels migrated to the Kubernetes or CNCF Slack? (see https://slack.com/help/articles/217872578-Import-data-from-one-Slack-workspace-to-another for more details)
• Is your project in its own separate neutral github organization?
• Submitted a Pull request to add your project as a sandbox project to https://landscape.cncf.io
• Create maintainer list + add to aggregated https://maintainers.cncf.io list by submitting a PR to it
• Artwork: Submit a pull request to https://github.com/cncf/artwork with your artwork
• Domain: transfer domain to the CNCF - https://jira.linuxfoundation.org/plugins/servlet/theme/portal/2/create/63

Things that CNCF will need from the project:

• Provide emails for the maintainers added to https://maintainers.cncf.io in order to get access to the maintainers mailing list and ServiceDesk - [email protected] is the best email to send those to
• Trademarks: transfer any trademark and logo mark assets over to the LF - https://github.com/cncf/foundation/tree/master/agreements has agreements
• GitHub: ensure 'thelinuxfoundation' and 'caniszczyk' are added as initial org owners, this helps us make sure we have continuity of GH ownership that we will onboard to our GitHub Enterprise instance: https://github.com/enterprises/cncf
• GitHub: ensure DCO or CLA are enabled for all GitHub repositories of the project
• GitHub: ensure that that the CNCF Code of Conduct (or your adopted version of it) are explicitly referenced at the project's README on GitHub
• Website: ensure LF footer is there and website guidelines followed (if your project doesn't have a dedicated website, please adopt those guidelines to the README file of your project on GitHub).
• Website: Analytics transferred to [email protected]
• OpenSSF Best Practices Badge: Start on an OpenSSF Best Practices Badge https://bestpractices.coreinfrastructure.org/en

Things that the CNCF will do or help the project to do:

• Devstats: add to devstats https://devstats.cncf.io/
• Insights: add to LFX Insights https://insights.v3.lfx.linuxfoundation.org/
• Marketing: update relevant intro + slide decks
• 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
• Book time with the team with http://project-meetings.cncf.io
• Adopt a license scanning tool, like FOSSA or Snyk

[amye]

@mrbobbytables - catching up here!

[zijianjoy]

cc Current kubeflow steering committee : @jbottum @theadactyl @james-jwu

[zijianjoy]

Looking at the task Devstats: add to devstats https://devstats.cncf.io/, looks like we already have kubeflow in the dashboard, https://kubeflow.devstats.cncf.io/d/8/dashboards?orgId=1&refresh=15m, do we consider this item done?

[amye]

Yep, that's already taken care of, this issue is just to track everything for onboarding.

[zijianjoy]

Thanks @amye !

Regarding the task of Ensure your project meets the CNCF IP Policy: https://github.com/cncf/foundation/blob/master/charter.md#11-ip-policy, kubeflow side has an ongoing issue to track its progress: kubeflow/community#614

[amye]

Thanks @amye !

Regarding the task of Ensure your project meets the CNCF IP Policy: https://github.com/cncf/foundation/blob/master/charter.md#11-ip-policy, kubeflow side has an ongoing issue to track its progress: kubeflow/community#614

This actually looks like it's a Code of Conduct adoption issue?

[zijianjoy]

@amye You are right, it should be related to GitHub: ensure that that the [CNCF Code of Conduct](https://github.com/cncf/foundation/blob/master/code-of-conduct.md) (or your adopted version of it) are explicitly referenced at the project's README on GitHub task.

[amye]

@zijianjoy - we can probably work on the rest of these tasks as we get that sorted out.
Anything we can help with?

[zijianjoy]

@amye The OSPO on Google side has reached out to CNCF about the IP transfer, however, I don't have visibility to the progress. If that is finished, we can mark this item as done. Please let me know if this is not the case and I can reach out to CNCF for help.

[amye]

There's a thread with the right people for trademarks!

[annajung]

PR cncf/foundation#662 is open for the following:

Create maintainer list + add to aggregated https://maintainers.cncf.io/ list by submitting a PR to it

[annajung]

Issue kubeflow/community#656 can be used to track progress for the following:

Understand the project proposal process and reqs: https://github.com/cncf/toc/blob/main/process/project_proposals.md#introduction

Understand the services available for your project at CNCF https://www.cncf.io/services-for-projects/

Review the online programs guidelines: https://github.com/cncf/foundation/blob/master/online-programs-guidelines.md

Understand the trademark guidelines: https://www.linuxfoundation.org/legal/trademark-usage

Understand the license allowlist: https://github.com/cncf/foundation/blob/master/allowed-third-party-license-policy.md#approved-licenses-for-allowlist

[annajung]

Roles

Roles within Kubeflow are defined in the community membership doc, where it lists 4 roles: member, reviewer, approver subproject owner, and the requirements and responsibilities of each role.

• Community membership

Working Groups

There are multiple working groups under the Kubeflow org that are responsible for different components of the project. Working Group charter, governance, and requirements can be found at /kubeflow/community/wgs

• List of Working Groups
• Working Group Charter Guide
• Working Group Governance Requirements
• Working Group roles and organization
• Creation and Retirement of Working Group

Leadership

Kubeflow community accepted a proposal of three governance groups: Kubeflow Steering Committee (KSC), Kubeflow Conformance Committee (KCC), and Kubeflow Technical Oversight Committee (KTOC), as part of their open governance effort.

In addition to the proposal of the three governance groups, Kubeflow has 3 interim steering committees responsible for establishing KSC, KCC, and KTOC charters.

At this time, the KSC charter has been defined by the interim steering committees and there is a PR kubeflow/community#650 open for community review and feedback. Once the PR is merged or in parallel, the Kubeflow community is planning to hold the first KSC election.

• Proposal of three governance
• Interim Kubeflow Steering Committee
• KSC Charter

All governance related can be found at kubeflow/community repo

@amye Does this meet this following requirement?

Is your project working on written, open governance? see https://contribute.cncf.io/maintainers/governance/

[annajung]

@amye could you clarify if this is a hard requirement? There is a concern regarding migrating > 9,000 users in the current Kubeflow slack workspace to CNCF and possibly to one flat channel under CNCF when there are multiple active channels within the current slack workspace for different purposes. (ref kubeflow/community#615)

Also, Kubeflow slack workspace is currently under the free plan which deletes messages after a certain amount of days. Due to this issue, many community members have been asking to find an alternative or move to a paid plan to ensure the messages are stored and searchable in the future.

Instead of migrating to the CNCF workspace, is there a way CNCF can help with managing a paid plan for the current Kubeflow workspace? Or is there any other alternative you can suggest?

Slack: Are your slack channels migrated to the Kubernetes or CNCF Slack? (see https://slack.com/help/articles/217872578-Import-data-from-one-Slack-workspace-to-another for more details)

[terrytangyuan]

Just to share our experience from Argo project Slack channel migration. We had a very popular Slack workspace dedicated to Argo, but we eventually switched to CNCF Slack and closed the Argo Slack workspace. We prefixed all Slack channels with "argo-" so it's easy to identify and search for relevant channels. Some main ones are listed here: https://argoproj.github.io/community/join-slack

Some quick stats on major channels:

• #argo-cd: 12k members
• #argo-workflows: 6k members
• #argo-events: 2.5k members
• #argo-rollouts: 2.7k members
• #argo-contributors: 1k members
• #argo-announcements: 2k members

Overall, the migration was quite successful, easier to find for existing CNCF users, and easier to collaborate with CNCF ecosystem projects. Hope this helps.

[zijianjoy]

but we eventually switched to CNCF Slack and closed the Argo Slack workspace.

Hello @terrytangyuan , thank you for sharing your experience. Would you like to elaborate the process of such migration?

• What action did Argo Slack users need to take for such migration?
• How does the permission configuration look like for Argo- channels? (Does the argo steering committee have permission to manage/create argo- channel?)
• How much percentage of Slack users did we successfully migrate to CNCF slack?

[terrytangyuan]

Would you like to elaborate the process of such migration?

We archived the channels in the original Slack workspace on a schedule one by one. See argoproj/argoproj#47 for details. We announced/reminded regularly, started supporting users in CNCF channels, and eventually the old Slack workspace became inactive.

What action did Argo Slack users need to take for such migration?
They could just visit the link to join CNCF Slack and different channels: https://argoproj.github.io/community/join-slack. Once joined, they no longer have to go back to the original Slack workspace since nobody was responding to questions there.

How does the permission configuration look like for Argo- channels? (Does the argo steering committee have permission to manage/create argo- channel?)

I think only CNCF can manage existing channels. You can create new channels but at some point CNCF will take over.

How much percentage of Slack users did we successfully migrate to CNCF slack?

I don't remember the exact number but we had thousands of users in the old Slack. Once we migrated, it would just become more popular over time if marketing/communication was done regularly. It was quite successful for us at least.

[annajung]

These items are complete, thank you!

Provide emails for the maintainers added to https://maintainers.cncf.io/ in order to get access to the maintainers mailing list and ServiceDesk - [email protected] is the best email to send those to

An email was sent on Nov 7th and confirmation was also received.

Is your project in its own separate neutral github organization?

The kubeflow project is already in a separate neutral GitHub org, under Kubeflow

[terrytangyuan]

GitHub: ensure DCO or CLA are enabled for all GitHub repositories of the project

@zijianjoy The KSC also decided to use DCO going forward so can we disable CLA check and enable DCO App at org level going forward.

[zijianjoy]

GitHub: ensure DCO or CLA are enabled for all GitHub repositories of the project

@zijianjoy The KSC also decided to use DCO going forward so can we disable CLA check and enable DCO App at org level going forward.

Thanks, I have enabled DCO in kubeflow repos. I will give it a few days to test it out that DCO is being enforced across Kubeflow and people are able to develop using the new approach. Then we will decide on when to disable CLA.

[zijianjoy]

Update: We have done the following list of items, please update issue description accordingly, thank you!

Status	Requirement	Relevant issues/PR
Done	Ensure your project meets the CNCF IP Policy: https://github.com/cncf/foundation/blob/master/charter.md#11-ip-policy	kubeflow/community#661
Done	OpenSSF Best Practices Badge: Start on an OpenSSF Best Practices Badge https://bestpractices.coreinfrastructure.org/en	coreinfrastructure/best-practices-badge#2076
Done	GitHub: ensure that that the CNCF Code of Conduct (or your adopted version of it) are explicitly referenced at the project's README on GitHub	kubeflow/community#658
Done	Website: ensure LF footer is there and website guidelines followed (if your project doesn't have a dedicated website, please adopt those guidelines to the README file of your project on GitHub).	kubeflow/website#3622

[Cmierly]

@zijianjoy I've updated the checklist and it should be accurate as of today!

[rimolive]

I believe this item is done.

 Insights: add to LFX Insights https://insights.v3.lfx.linuxfoundation.org/

Based on the following: https://insights.lfx.linuxfoundation.org/foundation/cncf/overview?project=kubeflow

[krook]

@rimolive Thank you. I marked the Insights task complete.

[krook]

FYI, details on Insights now that you're onboarded.

• Insights documentation
• Insights support
• Insights feedback

[krook]

@rimolive @zijianjoy @terrytangyuan,

It looks like we're very close to closing out this checklist. The remaining items are:

• Domain: transfer domain to the CNCF - https://jira.linuxfoundation.org/plugins/servlet/theme/portal/2/create/63
• Book time with the team with http://project-meetings.cncf.io
• Adopt a license scanning tool, like FOSSA or Snyk

The first one should be straightforward. You can use [email protected] as the "LF Stakeholder email".

The second one is completely optional but let us know if you want to hop on Zoom to answer any other questions. @castrojo is already available to attend your meeting on Jul 19 to discuss CNCF resources available.

The third @RobertKielty can help you with.

[zijianjoy]

Hello @krook , thank you for following up on this issue.

Regarding transfer domain to the CNCF: I have created https://cncfservicedesk.atlassian.net/servicedesk/customer/portal/1/CNCFSD-2127 and is currently pending for Shah Ahmadzai to share an update.

Regarding license scanning tool, KFP (Kubeflow Pipelines) is currently using the following tools for scanning license:

• Frontend: We are using yarn license and license-checker: https://github.com/kubeflow/pipelines/blob/master/frontend/gen_licenses.js
• Backend: We are using https://github.com/google/go-licenses for license scanning.

[RobertKielty]

There is a Kubeflow Team is now on FOSSA.

Two registered maintainers and one additional contributor have sucessfully accepted invites to join the CNCF Organizaion on FOSSA and I have addedm them to the team as Team Admins.

The maintainers are @rimolive @StefanoFioravanzo
@tarilabs has also been added as a Team Admin.

[tarilabs]

Two registered maintainers and one additional contributor have sucessfully accepted invites to join the CNCF Organizaion on FOSSA and I have addedm them to the team as Team Admins.

[tarilabs]

Not sure if applicable, but I'd also wire the loop here, we need to find the owner of the "Main" Kubeflow YouTube channel, as the KF community currently can only manage the "community channel (ex-kubeflow dojo)"

• YouTube Kubeflow (main) channel: owner? kubeflow/community#745

[juliusvonkohout]

There is a Kubeflow Team is now on FOSSA.

Two registered maintainers and one additional contributor have sucessfully accepted invites to join the CNCF Organizaion on FOSSA and I have addedm them to the team as Team Admins.

The maintainers are @rimolive @StefanoFioravanzo @tarilabs has also been added as a Team Admin.

Does it make sense to add more people?

[tarilabs]

Does it make sense to add more people?

yes, as was also called out here:

If you are a Kubeflow member reading this issue and you need to be added in the FOSSA tool, you can reach out to myself, @rimolive and @terrytangyuan to be added in the existing group, or ask a SC representative to manage the service desk request for you/your KF project.

You can let me know your FOSSA login, happy to add you to the FOSSA team mentioned in #196
Please note I cannot invite for a FOSSA login (that is CNCF Service Desk ticket, for which KF SC representative can manage for you) but happy to do the chore work on the FOSSA side.

[thesuperzapper]

@RobertKielty @tarilabs I seem to be on the CNCF FOSSA, but I'm not in the kubeflow team.

[tarilabs]

@RobertKielty @tarilabs I seem to be on the CNCF FOSSA, but I'm not in the kubeflow team.

done 👍

[juliusvonkohout]

@tarilabs i am on fossa as well with my github tag @gmail.com

[zijianjoy]

Domain: transfer domain to the CNCF - https://jira.linuxfoundation.org/plugins/servlet/theme/portal/2/create/63

Update: Google has completed domain transfer to CNCF, Rudy Grigar on the CNCF side has confirmed that the transfer is successful.

I believe we can mark this issue as completed. Truly appreciate everyone on contributing their effort to make this happen!

[thesuperzapper]

Domain: transfer domain to the CNCF - https://jira.linuxfoundation.org/plugins/servlet/theme/portal/2/create/63

Update: Google has completed domain transfer to CNCF, Rudy Grigar on the CNCF side has confirmed that the transfer is successful.

I believe we can mark this issue as completed. Truly appreciate everyone on contributing their effort to make this happen!

@zijianjoy who then has DNS access to update the domain now?

[Cmierly]

With the domain transfer complete, Kubeflow has now completed Onboarding!
Congrats!

[terrytangyuan]

Thank you everyone for helping with this! Truly a team effort!

[thesuperzapper]

@Cmierly just to clarify, we have some DNS changes that we actually need on kubeflow.org, is this now only possible by CNCF staff?