[SANDBOX PROJECT ONBOARDING] Open Policy Registry (OPCR)

[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/
• 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, 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

[lukaszgryglicki]

DevStats page added.

[ogazitt]

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.

Thanks!

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

OPCR is licensed under Apache-2: https://github.com/opcr-io/policy/blob/main/LICENSE

• 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)

We have a slack - does it makes sense to create a new channel?

• Is your project in its own separate neutral github organization?

Yes - https://github.com/opcr-io

• Submitted a Pull request to add your project as a sandbox project to https://landscape.cncf.io

cncf/landscape#2940

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

cncf/foundation#489

• Have added your project to https://github.com/cncf/contribute

Looks like this repo is now archived?

• 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

[ogazitt]

CII best practices: https://bestpractices.coreinfrastructure.org/en/projects/6859

Maintainers emails: gert@aserto.com, dani@aserto.com

[amye]

Invites are sent! I will pick back up on the rest of these.

[amye]

We have a slack - does it makes sense to create a new channel?
We can help migrate that, you should have invites to Servicedesk now!

[ogazitt]

Hi @amye, Happy New Year!

We have more of these done :)

• 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)

Projects like Open Policy Agent have their own slack, and newer sandbox projects like OpenFGA have a Discord - see discussion. We're not necessarily against creating a channel in the CNCF Slack, but it seems duplicative of the community slack we already have.

• 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

cncf/artwork#395

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

We're ready to transfer openpolicycontainers.com. Are there any additional instructions on how to fill this out? What should we use for LF stakeholder email and community stakeholder email?

Our assumption is that once the transfer is complete, the site can still be hosted in Netlify (i.e. the transfer won't mess with the DNS settings / CNAME records that netlify requires).

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

Is there a source file (like a word or google doc) that we can modify, or do we need to buy Acrobat?

• GitHub: ensure 'thelinuxfoundation' and 'caniszczyk' are added as initial org owners, this helps us make sure we have continuity of GH ownership

done!

• 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).

done!

• Website: Analytics transferred to projects@cncf.io

done!

• 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]

"Projects like Open Policy Agent have their own slack, and newer sandbox projects like OpenFGA have a Discord - #209. We're not necessarily against creating a channel in the CNCF Slack, but it seems duplicative of the community slack we already have."
CNCF + Kubernetes are the funded slack instances.

"We're ready to transfer openpolicycontainers.com. Are there any additional instructions on how to fill this out? What should we use for LF stakeholder email and community stakeholder email?"
You're the community stakeholder, you can use projects@cncf.io for the LF stakeholder email (it's more than just me!)

[ogazitt]

"Projects like Open Policy Agent have their own slack, and newer sandbox projects like OpenFGA have a Discord - #921 (comment). We're not necessarily against creating a channel in the CNCF Slack, but it seems duplicative of the community slack we already have."

CNCF + Kubernetes are the funded slack instances.

We're not seeking funding the current slack instance. So let's leave it as-is and create a channel in the CNCF slack later if necessary?

"We're ready to transfer openpolicycontainers.com. Are there any additional instructions on how to fill this out? What should we use for LF stakeholder email and community stakeholder email?"

You're the community stakeholder, you can use projects@cncf.io for the LF stakeholder email (it's more than just me!)

Awesome - thanks!

[ogazitt]

@amye I'm not sure I received the invitation to the Service Desk... perhaps because I wasn't one of the maintainers I initially added to the list. I just updated the maintainers here: cncf/foundation#495

[ogazitt]

Artwork is merged: cncf/artwork#395

[ogazitt]

[x] Trademarks: transfer any trademark and logo mark assets over to the LF - https://github.com/cncf/foundation/tree/master/agreements has agreements

@amye I just created a version of this for Open Policy Containers and docusigned it over to projects@cncf.io.

[amye]

[x] Trademarks: transfer any trademark and logo mark assets over to the LF - https://github.com/cncf/foundation/tree/master/agreements has agreements

@amye I just created a version of this for Open Policy Containers and docusigned it over to projects@cncf.io.

Ah, better to send a PDF and we'll return a fully executed copy to you.

[ogazitt]

[x] Trademarks: transfer any trademark and logo mark assets over to the LF - https://github.com/cncf/foundation/tree/master/agreements has agreements
@amye I just created a version of this for Open Policy Containers and docusigned it over to projects@cncf.io.

Ah, better to send a PDF and we'll return a fully executed copy to you.

Thanks @amye, I just emailed it to projects@cncf.io. Thanks!

[amye]

Checking in here: "We're not seeking funding the current slack instance. So let's leave it as-is and create a channel in the CNCF slack later if necessary?"
You should migrate to CNCF to let the community come ask questions!

[amye]

@ogazitt -- I'm looking through projects@cncf.io and there isn't a OCPR trademark agreement in there, so let's do this. Send a PDF to project-onboarding@cncf.io and I'll get it docusigned internally. Thanks!

[Cmierly]

Hi @ogazitt !
My name is Crystal and I am the new project coordinator in charge of onboarding sandbox projects!

I can now confirm we have your trademark agreement so I went ahead and checked that task off.
There are only two tasks that need completing:

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)
and
Adopt a license scanning tool, like FOSSA or Snyk

the third open task will be handled on our end. Please keep an eye out for more information regarding LFX Insights!

[krook]

the third open task will be handled on our end. Please keep an eye out for more information regarding LFX Insights!

LFX Insights provides projects with more visibility into their community dynamics around contributors, organizations, issues, and pull request metrics. It v3 uses crowd.dev under the hood to gather data about certain repositories in a GitHub organization.

The way it does this is through an app installed (similar to the DCO bot) at the organization level. This is then connected to one or more public repos under the organization. You can see technical details here.

The LFX team will install it on behalf of your project using the Linux Foundation id GitHub id you granted access to earlier, so no action is needed on the project maintainer side. Once your project is onboarded, you'll see data flowing into the dashboards at the LFX Insights v3 site.

[ogazitt]

Adopt a license scanning tool, like FOSSA or Snyk

Can you enable Snyk on the repos in opcr-io, or is this something we should handle? I believe you have a free plan that may be good to utilize?

[krook]

@ogazitt can you please double check that thelinuxfoundation is set as an Owner of the https://github.com/opcr-io organization?

[ogazitt]

@caniszczyk is an owner, and I believe he was going to add thelinuxfoundation. I believe it's part of the CNCF Enterprise organization.

[krook]

Thanks @ogazitt. It is indeed part of the CNCF org, so that's good. But we will still need the org owner bit on the thelinuxfoundation id if you could please apply that.

[ogazitt]

Thanks @ogazitt. It is indeed part of the CNCF org, so that's good. But we will still need the org owner bit on the thelinuxfoundation id if you could please apply that.

We had invited that ID in the past, but the invitation expired. I just invited thelinuxfoundation again - hopefully you can see it!

[Cmierly]

Adopt a license scanning tool, like FOSSA or Snyk

Can you enable Snyk on the repos in opcr-io, or is this something we should handle? I believe you have a free plan that may be good to utilize?

Hi @ogazitt !
Did you still need help getting this completed?

[ogazitt]

Adopt a license scanning tool, like FOSSA or Snyk

Can you enable Snyk on the repos in opcr-io, or is this something we should handle? I believe you have a free plan that may be good to utilize?

Hi @ogazitt ! Did you still need help getting this completed?

Yes, would love to get help setting up Snyk on the repo.

[Cmierly]

Alrighty!
@RobertKielty do you think you could jump in and help get them going?

[krook]

Bump @RobertKielty

[ogazitt]

@RobertKielty is there anything you need from us to enable this?

[krook]

@RobertKielty is this one set up for license scanning? Can we mark that complete? It's the last onboarding step, assuming the dangling Slack question is resolved...

[RobertKielty]

I have sent out invites to the maintainers for both FOSSA and Snyk.

@ogazitt Let me know if you have a preference for either service. (you can choose either or both!)

If you want to go with FOSSA please let me know.

For FOSSA, I have to add you to the team opcr team that I created there as the invite is not tied to the team. Once I have done that an invited maintainer can add project repos there so that they are scanned for compliance with the CNCF License policy.

For Snyk, you can just go ahead and add your code repos for scanning.

[Cmierly]

@ogazitt Hi!
Have you had the chance to look over the license scanning tool options? We would be happy to help with anything you might need!

[RobertKielty]

Hi @ogazitt, I checked the OPCR Organization in Snyk and there were 4 pending invites, presumably dating from May 31st.

I have deleted those pending invites and I have just resent out 10 fresh email invites to all maintainer emails in the maintainer list

@ogazitt @mihaibuzgau @carabasdaniel @florindragos @gertd @gimmyxd @viovanov @oanatmaria @apoland @noashavit please check your inboxes and accept the invitation to join the CNCF Snyk service instance.

To mark this task complete I need just one maintainer to accept the invite to join Snyk and import all of the repos into Snyk so we can see a license scan report on all of your repos.

@Cmierly please review the maintainers list above and update our internal records, many thanks.

[ogazitt]

Hi Robert, thanks for the reminder - I thought we had accepted it, but this must have slipped through the cracks. I tried to join just now via my ogazitt account but got the following error: [image: Screenshot 2024-11-18 at 8.12.38 AM.png] -- Omri Gazitt

…

On Mon, Nov 18, 2024 at 5:00 AM Robert Kielty ***@***.***> wrote: Hi @ogazitt <https://github.com/ogazitt>, I checked the OPCR Organization in Snyk and there were 4 pending invites, presumably dating from May 31st. I have deleted those pending invites and I have just resent out 10 fresh email invites to all maintainer emails in the maintainer list <https://github.com/opcr-io/policy/blob/main/MAINTAINERS.md> @ogazitt <https://github.com/ogazitt> @mihaibuzgau <https://github.com/mihaibuzgau> @carabasdaniel <https://github.com/carabasdaniel> @florindragos <https://github.com/florindragos> @gertd <https://github.com/gertd> @gimmyxd <https://github.com/gimmyxd> @viovanov <https://github.com/viovanov> @oanatmaria <https://github.com/oanatmaria> @apoland <https://github.com/apoland> @noashavit <https://github.com/noashavit> please check your inboxes and accept the invitation to join the CNCF Snyk service instance. To mark this task complete I need just one maintainer to accept the invite to join Snyk and import all of the repos into Snyk so we can see a license scan report on all of your repos. @Cmierly <https://github.com/Cmierly> please review the maintainers list above and update our internal records, many thanks. — Reply to this email directly, view it on GitHub <#162 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAH2QAZ4ILKPW2A7KHHG4NL2BHQGJAVCNFSM6AAAAABO47TGAGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIOBSHE4DCNJVGQ> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[krook]

@ogazitt it looks like we have one remaining task here to close out onboarding, which is to migrate your Slack channels to the CNCF workspace.

I see you're on the free plan. The benefits of joining the CNCF instance is that it's a paid plan and it makes it easier for developers to find you there.

Argo was able to move their very large instance over and we can help with import/export.

[ogazitt]

@ogazitt it looks like we have one remaining task here to close out onboarding, which is to migrate your Slack channels to the CNCF workspace.

I see you're on the free plan. The benefits of joining the CNCF instance is that it's a paid plan and it makes it easier for developers to find you there.

Argo was able to move their very large instance over and we can help with import/export.

One question about this - I see projects like Open Policy Agent hosting their own community slack workspaces (e.g. openpolicyagent.slack.com), so I assumed that this was optional?

I prefer leaving the OPCR slack where it is, but if it's a requirement, it would be great if you could create a new slack channel for #openpolicycontainers in the CNCF workspace, and we can just start there (and announce that we've created this new channel on our existing slack).

[krook]

Thanks @ogazitt. Marking OPCR onboarding complete now 🎉