[INCUBATING PROJECT ONBOARDING] Istio

[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/en/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
• Have added your project to https://github.com/cncf/contribute
• 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
• 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
• GitHub: ensure DCO or CLA are enabled for all GitHub repositories of the project
• GitHub: ensure that hat 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 projects@cncf.io
• CII: Start on a CII 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/
• 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, welcome email has monthly project sync details
• Create space for meetings/events on https://community.cncf.io, e.g., https://community.cncf.io/pravega-community/ - (https://github.com/cncf/communitygroups/blob/main/README.md#cncf-projects)
• Adopt a license scanning tool, like FOSSA or Snyk

[amye]

@craigbox - maintainers emails are the biggest thing to help here!

[craigbox]

Who does one normally list as a maintainer? We have ~87 listed here. Kubernetes seems to only have listed its Steering members.

[amye]

Correct, these are the people who should be added to your maintainer list + they get voting rights in an election.

[craigbox]

...is it OK to have 87 be listed for voting purposes? Not all will need service desk access.

[amye]

No, establishing a steering committee is probably your best move.

[dims]

LOL no to 87 :)

[lukaszgryglicki]

DevStats page added.

[lukaszgryglicki]

Added Istio DevStats instance, and added Istion in All CNCF - those are Project Health & Projects Health dashboards that include Istio.

[craigbox]

• 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/en/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?
  Istio does not intend to migrate to the CNCF Slack at this time.
• 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
• Have added your project to https://github.com/cncf/contribute
• 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
• 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
  In progress
• GitHub: ensure DCO or CLA are enabled for all GitHub repositories of the project
  In progress
• GitHub: ensure that hat 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 projects@cncf.io
  In progress
• CII: Start on a CII 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/
• 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, welcome email has monthly project sync details
• Create space for meetings/events on https://community.cncf.io, e.g., https://community.cncf.io/pravega-community/ - (https://github.com/cncf/communitygroups/blob/main/README.md#cncf-projects)
• Adopt a license scanning tool, like FOSSA or Snyk

[therealmitchconnors]

Maintainer list submitted at cncf/foundation#468

[therealmitchconnors]

FWIW, I'm struggling to clearly see what on the task list has been completed and what remains. I don't have access to modify the checklist. Can the access be opened, or can someone with access mark off the completed tasks?

[amye]

FWIW, I'm struggling to clearly see what on the task list has been completed and what remains. I don't have access to modify the checklist. Can the access be opened, or can someone with access mark off the completed tasks?

Unfortunately, no - comments in here are best!

[therealmitchconnors]

Status Update: I've hit a few snags in slack migration, and am waiting on support here: https://cncfservicedesk.atlassian.net/servicedesk/customer/portal/1/CNCFSD-1522

[kfaseela]

Add CNCF logo to Istio readme : istio/istio#42795

[kfaseela]

Add link to the CNCF Code of Conduct: istio/community#944

[craigbox]

We believe this issue is ready to close. We have been maintaining our own copy of the checklist which you are welcome to copy.

Remaining issues:

• The Google CLA is enabled on all repos; we have a plan to flip over to the LF CLA (largely the same process Kubernetes followed) after the next release.
• I'm told we can't add projects@cncf.io as an admin to Google Analytics since it's a group, and not a person. We're raising a service desk ticket for that.

[amye]

Best to have direct confirmation in here for items that are closed!

Invite nwaddington@linuxfoundation.org in the alternative, projects@cncf.io is an account.

[craigbox]

Did you click the link for "own copy of the checklist?" It points to a comment further up this thread, as we never got access to edit the actual checklist ourselves. 😊

[amye]

I'm checking in on Trademarks as it's marked above.
FOSSA/Synk?
Any desire for a space in community.cncf.io?

[craigbox]

We will raise a ticket for community.cncf.io at a later date, and I believe we already have a solution for linting for licenses.

[craigbox]

@amye Did you get what you needed re. trademarks?

[amye]

We will raise a ticket for community.cncf.io at a later date, and I believe we already have a solution for linting for licenses.

Yes, just waiting to hear on Slack.

[craigbox]

Can we leave the decisiona s "We are sticking with Istio Slack" for now , and then revisit options at a later date?

[amye]

Can we leave the decisiona s "We are sticking with Istio Slack" for now , and then revisit options at a later date?

Sure! Did we resolve Google Analytics? projects@cncf.io is an account that can accept invites.

[craigbox]

For access to our analytics dashboard, please go to https://eng.istio.io/webanalytics.
If you see "Can't access this report", you will need to join the istio-team-drive-access group, which is a public group.

We can't transfer the Google Analytics account today, because it was created within Google and it can't be shared with non-Google.com addresses. Longer term we will solve this problem — either by finding a way to transfer the account to an external domain, or by creating a brand new account and using it going forward — but we hope that this dashboard is enough to meet the requirement and close the onboarding issue!

[amye]

For access to our analytics dashboard, please go to https://eng.istio.io/webanalytics. If you see "Can't access this report", you will need to join the istio-team-drive-access group, which is a public group.

We can't transfer the Google Analytics account today, because it was created within Google and it can't be shared with non-Google.com addresses. Longer term we will solve this problem — either by finding a way to transfer the account to an external domain, or by creating a brand new account and using it going forward — but we hope that this dashboard is enough to meet the requirement and close the onboarding issue!

We should likely finish this, you'll end up with incomplete project reporting without it.

[craigbox]

We will definitely finish this, but the quick method will not give us the history we would probably like to keep. We don't want to hold up closing this issue based on the intention to do the right thing, which is the slow method! (Francis is researching if a team at Google can move the account from Google-internal to public.)

[Xunzhuo]

Hey @amye, I missed the ServiceDesk invitation.

Can you help a check on it?

[amye]

Hey @amye, I did not recieve any ServiceDesk invitation even if we have submitted cncf/foundation#468 (comment)

Can you help a check on it?

Right, and the followup for that was:

Please send an email to cncf-maintainer-changes@cncf.io with their emails to get everyone added to ServiceDesk and maintainers lists.

Drop an email to cncf-maintainer-changes@cncf.io if you've missed the invite.

[craigbox]

Hi @Xunzhuo; we have listed all Istio maintainers in the CSV but access to the CNCF service desk is limited to Steering Committee members. Thanks!