[SANDBOX PROJECT ONBOARDING] Copa (formerly Copacetic)

[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:

• [x] Understand the project proposal process and reqs: https://github.com/cncf/toc/blob/main/process/project_proposals.md#introduction
• [x] Understand the services available for your project at CNCF https://www.cncf.io/services-for-projects/
• [x] Ensure your project meets the CNCF IP Policy: https://github.com/cncf/foundation/blob/master/charter.md#11-ip-policy
• [x] Review the online programs guidelines: https://github.com/cncf/foundation/blob/master/online-programs-guidelines.md
• [x] Understand the trademark guidelines: https://www.linuxfoundation.org/en/trademark-usage/
• [x] Understand the license allowlist: https://github.com/cncf/foundation/blob/master/allowed-third-party-license-policy.md#approved-licenses-for-allowlist
• [x] Is your project working on written, open governance? see https://contribute.cncf.io/maintainers/governance/
• [x] 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)
• [x] Is your project in its own separate neutral github organization?
• [x] Submitted a Pull request to add your project as a sandbox project to https://landscape.cncf.io
• [x] Create maintainer list + add to aggregated https://maintainers.cncf.io list by submitting a PR to it
• [x] Artwork: Submit a pull request to https://github.com/cncf/artwork with your artwork
• [x] 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 - project-onboarding@cncf.io 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
• [x] 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
• [x] GitHub: ensure DCO or CLA are enabled for all GitHub repositories of the project
• [x] 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
• [x] 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).
• [x] Website: Analytics transferred to projects@cncf.io
• [x] 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:

• [x] Devstats: add to devstats https://devstats.cncf.io/
• [x] Insights: add to LFX Insights https://insights.v3.lfx.linuxfoundation.org/
• [x] Marketing: update relevant intro + slide decks
• [x] Events: update CFP + Registration + CFP Area forms
• [x] ServiceDesk: confirm maintainers have read https://www.cncf.io/services-for-projects/
• [x] CNCF Welcome Email Sent to confirm maintainer list access
• [ ] Book time with the team with http://project-meetings.cncf.io
• [x] 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)
• [x] Adopt a license scanning tool, like FOSSA or Snyk

[salaxander]

• [x] Understand the project proposal process and reqs: https://github.com/cncf/toc/blob/main/process/project_proposals.md#introduction
• [x] Understand the services available for your project at CNCF https://www.cncf.io/services-for-projects/
• [x] Ensure your project meets the CNCF IP Policy: https://github.com/cncf/foundation/blob/master/charter.md#11-ip-policy
  • [x] Review the online programs guidelines: https://github.com/cncf/foundation/blob/master/online-programs-guidelines.md
  • [x] Understand the trademark guidelines: https://www.linuxfoundation.org/en/trademark-usage/
  • [x] Understand the license allowlist: https://github.com/cncf/foundation/blob/master/allowed-third-party-license-policy.md#approved-licenses-for-allowlist
  • [x] Is your project working on written, open governance? see https://contribute.cncf.io/maintainers/governance/
  • [x] 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)
  • [x] Is your project in its own separate neutral github organization?
  • [x] Submitted a Pull request to add your project as a sandbox project to https://landscape.cncf.io/
  • [x] 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
  • [x] 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 - project-onboarding@cncf.io 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
  • [x] 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
  • [x] GitHub: ensure DCO or CLA are enabled for all GitHub repositories of the project
  • [x] 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
  • [x] 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).
  • [x] Website: Analytics transferred to projects@cncf.io
  • [x] 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:

• [x] Devstats: add to devstats https://devstats.cncf.io/
  • [x] Marketing: update relevant intro + slide decks
  • [x] 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/
  • [x] 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)
  • [x] Adopt a license scanning tool, like FOSSA or Snyk

[Cmierly]

Thank you, @salaxander ! I have updated the tasks to reflect the ones completed so far.

[salaxander]

@amye @Cmierly - our Slack channel is currently on the OCI Slack. Given that OCI is under LF, does that work? We can migrate it to the CNCF Slack if that's preferred.

[lukaszgryglicki]

DevStats instance added.

[Cmierly]

@amye @Cmierly - our Slack channel is currently on the OCI Slack. Given that OCI is under LF, does that work? We can migrate it to the CNCF Slack if that's preferred.

Hi! migrating to the CNCF or Kubernetes Slack is preferred

[amye]

Reasons for that: everyone will be able to find you in CNCF or OCI! We can help move things over.

[lukaszgryglicki]

Also added to All CNCF (example of commits dashboards with 5 new Sandbox projects selected) DevStats instance, here are Project Health(s) dashboards: link 1, link 2.

[salaxander]

Reasons for that: everyone will be able to find you in CNCF or OCI! We can help move things over.

Sounds great! Happy to move over to the CNCF account if you can provide instructions. Thanks!

[amye]

@RobertKielty to assist on Slack moves!

[RobertKielty]

Hi @salaxander DM on k8s or CNCF Slack I'll take a look.

[RobertKielty]

Setting up FOSSA now brb

[RobertKielty]

@salaxander I have DM'd you on CNCF Slack to get the conversation going on Slack setup.

[RobertKielty]

I accepted the FOSSA Invite on behalf of the cncf-copacetic-maintainers...

... once the user is added by FOSSA I will add that to the Copacetic team there.

[Cmierly]

Hi @salaxander ! Checking in on how things are going for Copacetic! Did you successfully migrate your Slack? We'd also like to get you on the landscape ASAP so please don't hesitate to reach out with any questions you might have!

[salaxander]

Hey @Cmierly - we'd really love to get on there ASAP, but we're still waiting on this service desk ticket.

[salaxander]

@Cmierly @amye Checking in on this service desk ticket again. We opened it over 2 months ago now and it's blocking our ability to get on landscape etc. Anything we can do on our side to help get that moving again?

Thanks!

[amye]

So the logo's with design still - we should be able to get you up on the landscape with the placeholder logo you have now!

[salaxander]

So the logo's with design still - we should be able to get you up on the landscape with the placeholder logo you have now!

Thanks for the update! That would work

[Cmierly]

@salaxander If you would like to use the placeholder logo to get Copacetic on the landscape, please submit a PR to add your project.

Once we get word from design, we will update the logo and add it to the artwork repo!

[krook]

Hello @salaxander,

In order to onboard the CNCF GitHub Enterprise account, we’ll need to invite the Copacetic organization. However it looks like it’s already associated with an existing GHE account. Can you please release it from that other GHE account?

Once you accept the invitation, we can then confirm thelinuxfoundation is an owner, and then onboard you to LFX Insights (which is a matter of adding an app, similar to adding the DCO bot) which uses read only, public data to drive the reports on the Insights dashboard.

That would mark both of these checklist items as up-to-date and complete (and it supersedes the need to add Chris and I as owners):

• [ ] GitHub: ensure thelinuxfoundation, caniszczyk, and krook are added as initial org owners, this helps us make sure we have continuity of GH ownership while we onboard you to our GitHub Enterprise instance: https://github.com/enterprises/cncf
• [ ] Insights: add to LFX Insights https://insights.v3.lfx.linuxfoundation.org/

You can learn more about Insights here:

• Insights documentation

Please let me know if you have any questions about onboarding GHE and Insights.

[salaxander]

Hey @krook - I'm working on figuring out how to leave that enterprise org. In the meantime, @caniszczyk and @thelinuxfoundation are both org owners. I'll add you as well.

[krook]

Thanks @salaxander. It's showing that it's part of the Microsoft Collaboration GitHub Enterprise account.

An owner in that MS account can remove the Copacetic org at which point I can invite you to the CNCF GHE account.

[krook]

Hi @salaxander while we're still waiting on the GHE transfer, we can still go ahead and onboard you to Insights with thelinuxfoundation's owner access as is. Any issues with us going forward with that?

[salaxander]

Hey @krook, that should be totally fine. Thanks!

[salaxander]

@krook the project-copacetic org has been removed from the "Microsoft Collaborations" GHE account, so we should be all good to proceed now.

[krook]

Great, thank you @salaxander. Just sent the invite. And you're also onboarded to Insights now so I checked that off the list.

[RobertKielty]

Added copacetic to CNCF Slack.

[RobertKielty]

Reached out on the OCI Copa channel to let them know that we intend to move them across to the CNCF Slack

I will source admin rights to do an export of the OCI channel and then import those messages into the new one on Slack.

[RobertKielty]

Slack Channel Migration complete!

1. OCI copa channel message content exported
2. Imported messages from OCI into the #copactic channel on the CNCF Workspace.
3. Renamed the #copacetic channel on the CNCF Workspace to #copa (mainly taking the stance that the artwork and the Landscape entry both referenced the project as Copa so I am rowing in behind that)
4. I have renamed the title of this issue to indicate that Copa is now the preferred project name and that it was formerly refered to as Copacetic.

[Cmierly]

thanks @RobertKielty ! Updated the checklist

[krook]

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

• Insights documentation
• Insights support
• Insights feedback

[RobertKielty]

Hi @ashnamehrotra @sozercan and @miahacybersec

I have setup a team for the copa project on FOSSA and I would like to add one or all of you to that team so that the project can be scanned for CNCF license policy compliance.

DM me on Slack with the email addresses that you would like me to use to setup your accounts their and I will then send out the invites.

[RobertKielty]

Set up an Copa org on Snyk on the CNCF Snyk Group

[RobertKielty]

@ashnamehrotra I have invited you join to the Copa org on the CNCF Snyk group. Let me know how that goes.

[ashnamehrotra]

@RobertKielty I was able to join, thank you!

[RobertKielty]

@ashnamehrotra imported @jeremyrickard as a Team Member who has imported the copa and copa actions repo! Thank you both for getting this over the line! Marked as complete on the task list.