[SANDBOX PROJECT ONBOARDING] HAMi

[Cmierly]

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 into the Sandbox.

We would like your project to complete onboarding within one month of acceptance.

Please track your progress by using "Quote reply" to create your own copy of this checklist in an issue, so that you can update the status as you finish items.

Review and understand

• The Technical Leadership Principles that outlines the expected behavior for any maintainer in a leadership role.
• The project proposal process and requirements.
• The services available for your project at the CNCF.
• The CNCF IP Policy.
• The trademark guidelines.
• The license allowlist.
• The online program guidelines.
• Optional: Book time with CNCF staff for any onboarding questions.

Contribute and transfer

• Move your project to its own separate neutral GitHub organization. This will make it transferable to the CNCF's GitHub Enterprise account. If it's already in a GHE account, you will need to remove it from that first.
• Accept the invite to join the CNCF GitHub Enterprise account. We'll then add thelinuxfoundation as an organization owner to ensure neutral hosting of your project.
• Migrate your Slack channels (if any) to the Kubernetes or CNCF Slack workspace. CNCF staff can help.
• Submit a pull request to add your project as a Sandbox project to the Cloud Native Landscape by updating landscape.yml following these instructions.
• Transfer your domain to the CNCF. The "LF Stakeholder email" is [email protected].
• Transfer any trademark and logo assets to the Linux Foundation.
• Submit a pull request with your artwork.
• Transfer website analytics to [email protected]. CNCF staff can help.

Update and document

• Ensure that DCO (preferred) or CLA are enabled for all GitHub repositories of the project.
• Ensure that that the CNCF Code of Conduct (or your adopted version of it) are explicitly referenced at the project's README on GitHub.
• Ensure LF footer is on your website and guidelines are followed (if your project doesn't have a dedicated website, please adopt those guidelines for the README file).
• Create a maintainer list and add it to the aggregated CNCF maintainer list via pull request.
• Provide emails for the maintainers to get access to the maintainers mailing list and Service Desk. Email them to [email protected].
• Start working on written, open governance.
• Start on an OpenSSF Best Practices Badge.

CNCF staff tasks

• Add the project to DevStats.
• Add the project to CLOmonitor.
• Add the project to LFX Insights. This is done by adding a read-only app to your GitHub organization once it's in CNCF GHE.
• Add the project to LFX Project Control Center.
• Add a license scanning tool, like FOSSA or Snyk.
• Invite developers to the #maintainers-circle Slack channel.
• Send a welcome email to confirm maintainer list access.

[wawa0210]

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 into the Sandbox.

We would like your project to complete onboarding within one month of acceptance.

Please track your progress by using "Quote reply" to create your own copy of this checklist in an issue, so that you can update the status as you finish items.

Review and understand

• The project proposal process and requirements.
• The services available for your project at the CNCF.
• The CNCF IP Policy.
• The trademark guidelines.
• The license allowlist.
• The online program guidelines.
• Optional: Book time with CNCF staff for any onboarding questions.

Contribute and transfer

• Move your project to its own separate neutral GitHub organization. This will make it transferable to the CNCF's GitHub Enterprise account. If it's already in a GHE account, you will need to remove it from that first.
• Accept the invite to join the CNCF GitHub Enterprise account. We'll then add thelinuxfoundation as an organization owner to ensure neutral hosting of your project.
• Migrate your Slack channels (if any) to the Kubernetes or CNCF Slack workspace. CNCF staff can help.
• Submit a pull request to add your project as a Sandbox project to the Cloud Native Landscape by updating landscape.yml following these instructions.
  • update HAMi sandbox information landscape#4016
• Transfer your domain to the CNCF. The "LF Stakeholder email" is [email protected].
• Transfer any trademark and logo assets to the Linux Foundation.
• Submit a pull request with your artwork.
  • Add HAMi artwork artwork#503
• Transfer website analytics to [email protected]. CNCF staff can help.

Update and document

• Ensure that DCO (preferred) or CLA are enabled for all GitHub repositories of the project.
  • DCO has been installed
• Ensure that that the CNCF Code of Conduct (or your adopted version of it) are explicitly referenced at the project's README on GitHub.
  • https://github.com/Project-HAMi/HAMi?tab=coc-ov-file
• Ensure LF footer is on your website and guidelines are followed (if your project doesn't have a dedicated website, please adopt those guidelines for the README file).
  • update hami sandbox project Project-HAMi/HAMi#465
• Create a maintainer list and add it to the aggregated CNCF maintainer list via pull request.
  • add HAMi maintainers foundation#851
• Provide emails for the maintainers to get access to the maintainers mailing list and Service Desk. Email them to [email protected].
• Start working on written, open governance.
  • https://github.com/Project-HAMi/community/blob/main/governance.md
• Start on an OpenSSF Best Practices Badge.
  • Add OpenSSF Best Practices Badge Project-HAMi/HAMi#467
  • support code Coverage Analytics Project-HAMi/HAMi#473

CNCF staff tasks

• Add the project to DevStats.
  • https://hami.devstats.cncf.io/
• Add the project to CLOmonitor.
  • https://clomonitor.io/projects/cncf/hami
• Add the project to LFX Insights. This is done by adding a read-only app to your GitHub organization once it's in CNCF GHE.
• Add the project to LFX Project Control Center.
• Add a license scanning tool, like FOSSA or Snyk.
• Invite developers to the #maintainers-circle Slack channel.
  • [SANDBOX PROJECT ONBOARDING] HAMi #132
• Send a welcome email to confirm maintainer list access.

[wawa0210]

@Cmierly friendly ping

Now HAMi is preparing to migrate slack data and needs cncf to help create a slack group. Thank you very much.

[krook]

Now HAMi is preparing to migrate slack data and needs cncf to help create a slack group. Thank you very much.

@RobertKielty can you please assist?

[wawa0210]

@RobertKielty friendly ping

This is the maintainers information of hami, can you help add it to the #maintainers-circle Slack channel

Maintainer	Email	Emplolyer
Li Mengxuan	[email protected]	4Paradigm
Xiao Zhang	[email protected]	DaoCloud
Wang Leibo	[email protected]	HuaweiCloud

[lukaszgryglicki]

DevStats instance ready.

[lukaszgryglicki]

Project added do Project Health and All Projects Health.

[archlitchi]

@Cmierly help me, i need some support

For this task:
Transfer any trademark and logo assets to the Linux Foundation.

Question:
We haven't registered any trademarks yet. so i guess this task is passed naturally?

And for this task:
Transfer website analytics to [email protected]
Question:
Our website is run on a VPS(IP: 193.203.215.25) by using command 'npm run serve'. so it probably doesn't have a website analytics. how can i pass this task?

[RobertKielty]

@Cmierly I've updated the maintainers list for the HAMi project as per this comment

[RobertKielty]

I have added @wawa0210 and @william-wang to the #maintainers-circle just now. Looks like Li Mengxuan had been added before now.

[RobertKielty]

@wawa0210 @william-wang @archlitchi the HAMi project can choose between Snyk or FOSSA as static code checkers that the project can use to comply with the CNCF's third party license policy on each commit to code repos.

Can you let me know which service you would prefer to use?

[wawa0210]

@wawa0210 @william-wang @archlitchi the HAMi project can choose between Snyk or FOSSA as static code checkers that the project can use to comply with the CNCF's third party license policy on each commit to code repos.

Can you let me know which service you would prefer to use?

Maybe FOSSA is a good choice for HAMi

[cynthia-sg]

Project has been added to CLOMonitor

[wawa0210]

@wawa0210 @william-wang @archlitchi the HAMi project can choose between Snyk or FOSSA as static code checkers that the project can use to comply with the CNCF's third party license policy on each commit to code repos.

Can you let me know which service you would prefer to use?

friendly ping, will cncf provide a FOSSA account, or should I use a personal account?

[idvoretskyi]

@wawa0210 we will, @RobertKielty is happy to assist.

[RobertKielty]

@wawa0210 I have set up a HAMi FOSSA Team on CNCF FOSS

I have managed to send out two invites.

Please accept the invites first, let me know when you have and wait for me to add your accounts to the CNCF FOSSA HAMi team.

It is important that the email addresses that you have supplied to us are assocaited with a GH account thathas read write access to your projects code repos.

When your CNCF FOSSA User account is set up you can then add your code repos to FOSSA for scanning.

[wawa0210]

@wawa0210 I have set up a HAMi FOSSA Team on CNCF FOSS

I have managed to send out two invites.

Please accept the invites first, let me know when you have and wait for me to add your accounts to the CNCF FOSSA HAMi team.

It is important that the email addresses that you have supplied to us are assocaited with a GH account thathas read write access to your projects code repos.

When your CNCF FOSSA User account is set up you can then add your code repos to FOSSA for scanning.

Sorry, I didn't receive the invitation email. Could you please confirm it again? Thanks a lot.

[wawa0210]

@RobertKielty

How to transfer Slack channels? Can you help me? Thanks

Also, I didn’t receive the email from FOSSA [email protected]

[wawa0210]

friendly ping @RobertKielty @idvoretskyi @cynthia-sg

The following tasks are left to do

• Migrate your Slack channels (if any) to the [Kubernetes or CNCF Slack workspace]
• Add a license scanning tool, like FOSSA or Snyk.

[idvoretskyi]

@wawa0210 for the Slack channels, please file a ticket to the CNCF ServiceDesk, we'll handle it there.

With FOSSA/Snyk - @RobertKielty is happy to assist!

[RobertKielty]

I have just sent out invites for team to both FOSSA and Snyk. Let me know when the invites are accepted.

[wawa0210]

I have just sent out invites for team to both FOSSA and Snyk. Let me know when the invites are accepted.

I received an invitation email from Snyk, but not from FOSSA

[wawa0210]

@wawa0210 for the Slack channels, please file a ticket to the CNCF ServiceDesk, we'll handle it there.

I doesn't have access to Jira on cncfservicedesk.atlassian.net. Need help

[Cmierly]

@wawa0210 for the Slack channels, please file a ticket to the CNCF ServiceDesk, we'll handle it there.

I doesn't have access to Jira on cncfservicedesk.atlassian.net. Need help

I'll look into this today!

[RobertKielty]

@wawa0210 I have sent you a direct message on Cloud Native Slack (using wawa0219) feel free to repond to me there if you like.

I would like to review the work already done on getting license scans done.

I can see we have the main repo added to the HAMi team in Snyk. (there are two License issues reported that will need to be reviewed and addressed) Project HAMi license scan results

There are 12 repos over on https://github.com/orgs/Project-HAMi/repositories?type=all

All 12 repos will need to be scanned.

Using Snyk to scan all the repos in the Project-HAMi GH org would allow us to mark this task complete.

But I am happy to get you setup on FOSSA if you prefer.

[RobertKielty]

Worked with @wawa0210 today and they now have an account on the HAMi team we setup on CNCF FOSSA. @wawa0210 Thank you for your cooperation and patience today!

When the 12 repos are added to FOSSA we can call this task done.

[RobertKielty]

For Slack migration, I have signed up to the current HAMi Slack to review the channels there.

We have a small number of candidate channels to migrate with a message history dating back to April 8th this year.

We have

• All (全体)
• Random (全体)
• opensource
• dev

We should look at migrating opensource and dev accross. Suggested steps

On HAMi Slack

1. rename dev and opensource channels tp HAMi-dev and HAMi-opensource
2. Get a Workspace Owner to export HAMi-dev and HAMi-opensource; channel message history and membership. In order to get a full export that include the users the HAMi Slack account MUST BE an Owner account. An Admin account will not work for this.

Then reach out to me and share the export file with me. I will then attempt to import it to the CNCF Slack.

[wawa0210]

For Slack migration, I have signed up to the current HAMi Slack to review the channels there.

We have a small number of candidate channels to migrate with a message history dating back to April 8th this year.

We have

• All (全体)
• Random (全体)
• opensource
• dev

We should look at migrating opensource and dev accross. Suggested steps

On HAMi Slack

1. rename dev and opensource channels tp HAMi-dev and HAMi-opensource
2. Get a Workspace Owner to export HAMi-dev and HAMi-opensource; channel message history and membership. In order to get a full export that include the users the HAMi Slack account MUST BE an Owner account. An Admin account will not work for this.

Then reach out to me and share the export file with me. I will then attempt to import it to the CNCF Slack.

Thank you for your very patient guidance. The slack export data has been sent to you via slack.

[RobertKielty]

FOSSA - all projects imported!
Slack - two channels imported we encountered the usual User importation issues so instead we imported the message history without merging the users. @wawa0210 will announce the switch over to the cloud naitve worspace in the HAMi workspace.

[wawa0210]

FOSSA - all proects imported Slack - two channels imported we enoucntered the usual User importation issues to instead we imported the message history without mergin the users so that the migration happened. @wawa0210 will announce the swicth over to the cloud naitve worspace in the HAMi workspace.

Very nice cooperation, very patient. We also work together as a team. I found that I urgently need to improve my English speaking skills 😄

[RobertKielty]

@wawa0210 yes it was great to collaborate with you today! Your English is way better thank my Mandarin, no worries there! 😄

I should have LFX Insights app intructions for you tomorrow, and I've shared the CI/CD resourcing questions with my colleagues on the Project Team, I should have guidance for you tomorrow on that.

[Cmierly]

@Cmierly help me, i need some support

For this task: Transfer any trademark and logo assets to the Linux Foundation.

Question: We haven't registered any trademarks yet. so i guess this task is passed naturally?

And for this task: Transfer website analytics to [email protected] Question: Our website is run on a VPS(IP: 193.203.215.25) by using command 'npm run serve'. so it probably doesn't have a website analytics. how can i pass this task?

Hi!
Sorry about the late reply but you will need to fill out the "no reg trademark" agreement in order for this task to be marked off.

[wawa0210]

fill out the "no reg trademark" agreement

Thanks. We didn't register trademark for HAMi, Could you please guide us on how we fill out the "no reg trademark" agreement?

[Cmierly]

@wawa0210 We are working on a new process for receiving trademark agreements. I will update you once we have more information.
I apologize for the delay!