[SANDBOX PROJECT ONBOARDING] Capsule

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

[amye]

@bsctl, @prometherion, @MaxFedotov, @oliverbaehler - dropping a note in here.
Landscape is important - this will get you listed on the sandbox projects page!

[prometherion]

👋🏻 just a brief update on this: we're actively working on CLASTIX's repository with an umbrella issue while we track the required steps.

We have a doubt about the project which is using some API types with the previous organization name, such as capsule.clastix.io: although moving the repository over to a new organization is not a big problem, at the current time, seamless migration of the API type is not yet in place since it requires a sizeable amount of time and resources, such as writing converters, and ensuring these work properly without side effects giving the amount of organizations using it in production environments.

Is it acceptable to postpone the removal of any CLASTIX mention from the code base to preserve backward compatibility with previous production installations?

[prometherion]

A new organization (Project Capsule) has been created, as well as the GitHub profiles have been invited (@caniszczyk @thelinuxfoundation).

[maxgio92]

I think that the task:

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

is already completed by cncf/tag-contributor-strategy@284b73a.

[maxgio92]

The task:

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

is ready for review:

• issue: New Capsule project for sandbox onboarding  foundation#647
• PR: new(project-maintainers.csv): add capsule project foundation#648

[Cmierly]

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

I have updated the task list for you and will look into your maintainer list PR ASAP

If you have any questions or concerns regarding onboarding tasks, please don't hesitate to reach out!

[maxgio92]

Hi @Cmierly,
thank you.

I think that the following goals have been achieved. You can review them:

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

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

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

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

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

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

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

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

9. 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

[Cmierly]

Thanks! I've updated the task list!

[maxgio92]

Thank you @Cmierly.
Also the goals:

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

• Ensure your project meets the CNCF IP Policy: https://github.com/cncf/foundation/blob/master/charter.md#11-ip-policy

are now achieved :)

[prometherion]

• Provide emails for the maintainers added to https://maintainers.cncf.io in order to get access to the maintainers mailing list and ServiceDesk

I've just sent the email to the proper email address.

[maxgio92]

Hi @Cmierly, I'd have a question about:

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

You will install the LFX Insights app in the GitHub repository after the project is migrated to the new GitHub organization, isn't it?

[prometherion]

• CII: Start on a CII best practices badge https://bestpractices.coreinfrastructure.org/en

This has been already implemented.

[krook]

You will install the LFX Insights app in the GitHub repository after the project is migrated to the new GitHub organization, isn't it?

Correct. More details on this:

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.

[prometherion]

Is your project in its own separate neutral github organization

Capsule is now available on its neutral organization: https://github.com/projectcapsule

@thelinuxfoundation has not yet accepted the invitation.

[krook]

Thank you @prometherion.

I've sent an invitation to the org owners to join the CNCF GitHub Enterprise umbrella org.

Once you accept that, we can onboard @thelinuxfoundation id onto it.

[bsctl]

Accepted, thanks @krook

[prometherion]

@krook the @thelinuxfoundation invitation was withdrawn, I just resent it back.

[prometherion]

@Cmierly I sent the GA invitation to the account projects@cncf.io account with the administrator role.

Wondering if this is enough, or if we should move entirely the property: in this latter case, do you have a specific guide for GA4?

[maxgio92]

Hello @amye,
I think that the following points:

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

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

can be considered completed.

You can give it a check, respectively, at:

• https://github.com/projectcapsule/capsule.
• https://capsule.clastix.io/

Thank you

[maxgio92]

Hi @amye,
I think that also the following goal:

• Adopt a license scanning tool, like FOSSA or Snyk

you can give it a try here.

Thank you

[Cmierly]

Hi @maxgio92 !
I have gone ahead and updated the task list for you.
Thank you so much for the updates and please don't hesitate to ask if you have any questions regarding the remaining tasks that need to be completed!

[maxgio92]

Hi @Cmierly,
yes, we're working on the remaining points.

In the meantime you can consider the task

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

completed, as we don't have registered trademarks. cc @bsctl @prometherion

I'll update you as soon as possible, thank you.

[Cmierly]

Hi @maxgio92 !
If your project doesn't have any registered trademarks then you will need to submit a no registered trademark agreement agreement

[krook]

Added to LFX Insights

• Insights documentation
• Insights support
• Insights feedback

[maxgio92]

Thank you @krook and @Cmierly. I'll be back ASAP

[prometherion]

The artwork item has been completed via cncf/artwork#440

[bsctl]

@Cmierly Hello Crystal, how to submit the no registered trademark agreement to CNCF? It's a signed PDF, need to send it through an email? Thank you.

[Cmierly]

@bsctl
That's great! You can send it over to: project-onboarding@cncf.io

[bsctl]

@Cmierly I guess

Is your project working on written, open governance?

see this and

Trademarks: transfer any trademark and logo mark assets over to the LF

are completed now.

[oliverbaehler]

We are currently redesigning our documentation, we don't have any analytics in place. Does CNCF provide us with an analytics ID?

Website: Analytics transferred to projects@cncf.io

For DNS transfer of projectcapsule.dev we have to wait some time:

ICANN imposes a 60-day lock after each transfer to another registrar, due to that you will only be able to transfer your domain to another registrar in 57 days.

[prometherion]

We are currently redesigning our documentation, we don't have any analytics in place. Does CNCF provide us with an analytics ID?

We have a Google analytics, used formerly for capsule.clastix.io

I think we can ask through the CNCF Service Desk to create the GA account, so we can inject the tracking code.

[maxgio92]

Hi @amye, I think that the point about the open governance can be considered completed, by projectcapsule/capsule@e983c19.

[oliverbaehler]

@amye can be markee as completed:

• Domain: transfer domain to the CNCF

See https://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fjira.linuxfoundation.org%2Fservicedesk%2Fcustomer%2Fportal%2F2%2FIT-26743%3Fsda_source%3Dnotification-email&data=05%7C02%7C%7C6e1b31586f1b483a49f208dc6eaf07b1%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C638506945240350800%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C&sdata=o%2B1xo0lO8RhOLEJnNfqdKssUvNysrrhuebCDWsQz5P8%3D&reserved=0

[amye]

@Cmierly can take it from here!

[oliverbaehler]

@Cmierly We dont have any analytics for the new domain transfered to the CNCF. I don't know if a new analytics id is issued by the CNCF or how we can resolve this last task.

[krook]

@nate-double-u what's the guidance on analytics? That seems like the last step here.

[nate-double-u]

Let's open a service desk ticket to track the work.

Looking back through the discussion it looks like there may already be an existing google analytics account, if that's true and it's not one of the old UA projects, then we can transfer ownership to projects@cncf.io. If there isn't any existing data, or if it is one of those old UA accounts, then we can just go ahead and create a new GA4 Site ID and share out the info and invite any one who needs access.

[oliverbaehler]

@nate-double-u we don't have a existing google analytics account for that site. We registered the Domain just some weeks ago and are in the process of redesigning the entire webpage. Could you go ahead and create a GA4 Site ID or is that done via ticket?

[nate-double-u]

I'd prefer to do it via ticket as I may not be the one to do the work -- but I'm also happy to open it on your behalf if you've not got access yet (would just need your email address, which I can probably get from @krook)

[krook]

I'd prefer to do it via ticket as I may not be the one to do the work -- but I'm also happy to open it on your behalf if you've not got access yet (would just need your email address, which I can probably get from @krook)

Just pinged it to you in Slack.

[nate-double-u]

A Google analytics property has been created, the tracking number is G-4YLJ6T1Z8F

I couldn't use the hotmail email address provided as Google refused to use it saying it was "an alternate" for a gmail address, and so I used it instead. Please confirm you got the invite @oliverbaehler.

<!-- Google tag (gtag.js) --> 
<script async src="https://www.googletagmanager.com/gtag/js?id=G-4YLJ6T1Z8F"></script> 
<script> window.dataLayer = window.dataLayer || []; function gtag(){dataLayer.push(arguments);} gtag('js', new Date()); gtag('config', 'G-4YLJ6T1Z8F'); </script>

[oliverbaehler]

@nate-double-u I have added the GA:
https://github.com/projectcapsule/website/pull/10/files

Can you check if it's tracking?
Havent gotten an invite. tbh i am also confused with these analytics.. :D
I have one mail that coreshawty@gmail.com

[oliverbaehler]

@krook @nate-double-u remains there anything from our side which needs to be done?

[krook]

@nate-double-u can we mark this final item complete now?

• Website: Analytics transferred to projects@cncf.io

[nate-double-u]

Google Analytics is set up and collecting data now.

@oliverbaehler, I've invited your Baehler.Oliver@gmail.com, and I've just added your coreshawty@gmail.com account as well. Please let me know if you're unable to access.

@krook, we can check this off now: Website: Analytics transferred to projects@cncf.io

[krook]

@oliverbaehler one additional question:

The CNCF has the https://projectcapsule.dev/ domain which is hosting a site for Capsule.

But there's also an (earlier?) one that is at https://capsule.clastix.io/

Is it possible to have the clastix.io one just forward to projectcapsule.dev?

[bsctl]

@krook we will take care of that.

[krook]

Excellent. We can follow up on that separately. But with everything else complete for onboarding we can mark this complete 🎉