[INCUBATING PROJECT ONBOARDING] Knative

[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.adoc#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 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 [email protected]
• 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/
• NEW: 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
• Work with the project to be added to store.cncf.io
• Work with the project to submit a session to the maintainer track for KubeCon

[amye]

Welcome @thisisnotapril, @pmorie, @lance!

[thisisnotapril]

@amye we'd like to discuss our options re: DCO and CNCF CLA. Is there a lawyercat that could talk to Steering about these options?

[amye]

@amye we'd like to discuss our options re: DCO and CNCF CLA. Is there a lawyercat that could talk to Steering about these options?

Maybe - what's the issue initially? We're happy for projects to use either, #easycla is the channel in CNCF slack that has that team to help migrate to the CLA tool provided by Linux Foundation.

[thisisnotapril]

We want to understand the implications of using DCO and if LF/CNCF has a preference? I know a lot of folks would like DCO but I don't know how that might impact our current processes.

[caniszczyk]

We don't really have a preference, you can use one or the other. I will say 95% of CNCF projects just use DCO as there is no "legal paperwork" that has to be signed (which can be a blocker for organizations). The downside of DCO is that you have to sign off each commit (git commit -s) and some folks get a bit annoyed by that and you have to be clear in your CONTRIBUTING.md file that CONTRIBUTORS need to do this too. Overall, I personally favor DCO over CLAs as it's simply a lower barrier to contribution imho

…

On Wed, Mar 2, 2022 at 1:53 PM April Kyle Nassi ***@***.***> wrote: We want to understand the implications of using DCO and if LF/CNCF has a preference? I know a lot of folks would like DCO but I don't know how that might impact our current processes. — Reply to this email directly, view it on GitHub <#218>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAAPSIN2TC34U2DKOJSC2JDU57BMXANCNFSM5PX4IWKA> . You are receiving this because you were assigned.Message ID: ***@***.***>

-- Cheers, Chris Aniszczyk https://aniszczyk.org

[thisisnotapril]

Thank you @caniszczyk that's super helpful!

[vaikas]

Woot Woot!!!

[csantanapr]

cc @dims

[csantanapr]

Welcome @thisisnotapril, @pmorie, @lance!

Thanks, @amye for the warm welcome! including @itsmurugappan which is a member of knative steering representing end-users

[csantanapr]

@amye In which git repo do we update to add knative to this webpage? https://www.cncf.io/projects/
Is that the same as Submitted a Pull request to add your project as a sandbox project to https://landscape.cncf.io/ ?

[amye]

@amye In which git repo do we update to add knative to this webpage? https://www.cncf.io/projects/ Is that the same as Submitted a Pull request to add your project as a sandbox project to https://landscape.cncf.io/ ?

Correct, Landscape populates the project page

[lukaszgryglicki]

DevStats test and prod pages added, will add this project to All CNCF as well - ETA for this is tomorrow. Also created affiliations research task - will import this once completed.

[vaikas]

@amye how can we check off things that have been completed? We don't seem to have the magic powers to do so.

[amye]

@amye how can we check off things that have been completed? We don't seem to have the magic powers to do so.

Comments in here when they're done work fine!

[lukaszgryglicki]

Knative added to "All CNCF" DevStats instances on both test & prod.

[csantanapr]

You can mark this one done

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

Knative now shows up incubating https://landscape.cncf.io/card-mode?project=incubating

[csantanapr]

@lukaszgryglicki about devstats
which repo is this configured?
Does it cover our 2 github orgs?
Knative and knative-sandbox?
The logo is not showing as Knative logo

[lukaszgryglicki]

knative and knative-sandbox GitHub orgs. For log to show, you need to add logos to cncf/artwork repos - as all other CNCF projects. do.

[csantanapr]

Thank you @lukaszgryglicki for the quick response, I was not aware of the logo requirement. We have Knative logo files and we add them there.

[lukaszgryglicki]

Follow any other project for that, DevStats needs those https://github.com/cncf/artwork/tree/master/projects/kuma/icon/color - replace kuma with knative:

• https://github.com/cncf/artwork/blob/master/projects/kuma/icon/color/kuma-icon-color.png
• https://github.com/cncf/artwork/blob/master/projects/kuma/icon/color/kuma-icon-color.svg

[csantanapr]

@amye When you have a chance could you address the last two checkboxes above and close this issue?

[amye]

Slack is still in migration, will leave that.

[Cmierly]

Hi @csantanapr !
My name is Crystal and I'm the new project coordinator in charge of onboarding sandbox projects!

I just confirmed that your Slack has successfully migrated so I went ahead and checked off that task for you!

All we need now is for you to adopt a license scanning tool! If you have any questions regarding that, please don't hesitate to ask! I would be happy to help.

[amye]

@RobertKielty - this may already be done!

[RobertKielty]

@amye Yes! Knative have a team setup already.

I'm setting @Cmierly up in FOSSA right now. I will provide training, resources and access so they have full visiability on the community setup.

[RobertKielty]

However, there are no projects setup in the Knative team, so @Cmierly is spot on here.

The project should add their repos and we can help them with that.

@amye I could do the new setup that we did for KubeArmor? And I can start to write that up as a process this week to share with the wider community? What do you think?

[amye]

Do it

[aliok]

@RobertKielty is there anything we need to do as the Knative community, or are you doing it for us?

[RobertKielty]

@aliok Thanks for reaching out. I can work on this to add the knative code repos to the team that has been set up in FOSSA.

We have a new way of doing this where we setup a GitHub profile for the project and associate it with the email address tied to cncf-knative-maintainers list in groups.io

I might need to work with a GitHub knative org owner to create that profile in GitHub. I'll ping you on Slack to arrange that.

[aliok]

Related to FOSSA: knative/community#962 (comment)

[RobertKielty]

I have updated the Knative team in FOSSA

I have sent out an invite to the cncf-knative-maintainers group and I have accepted that invite. (Invite still pending in FOSSA as I write this, I'll check back in a few hours to see if it is accepted)

Once invite is accepted next step will be to add projects to the team for scanning.

[RobertKielty]

@aliok I just now resent the invite from FOSSA it will go to the maintainers list in groups. Can I ask you to accept that invite please?

[RobertKielty]

I have accepted the FOSSA invite on behalf of the project, next step is to create a project profile in GitHub for FOSSA to use.

[csantanapr]

@RobertKielty thank you so much for helping with FOSSA Im admin for both of the github orgs in knative “knative” and “knative-extensions” ping me on cncf slack and we can work on the config you need on github profile

[csantanapr]

I met with @RobertKielty today and we configured FOSSA with Knative

[RobertKielty]

Had a huddle with @csantanapr on cncf-slack (Thanks for your help and feedback on this, very useful for the whole community!)

We hooked up the Knative Automation Profile to FOSSA by adding the maintainers email addr from groups.io to that profile.

Notes for CNCF Projects Team [@amye @jeefy @Cmierly @idvoretskyi ]:
For new projects we could follow the Knative convention of having a GitHub Profile named,

• {PROJECT-NAME Automation}

noting that more than one email addr can be associated with that Profile.

Notes for FOSSA End Users
When adding a project in FOSSA select the org where the target repo resides first.

[krook]

Hello Knative maintainers and @Cmierly. The final step is to add the Knative org and main repo (serving) to LFX Insights.

This is done by adding a GitHub app to the Knative organization (similar to the DCO bot).

Once we add it public, read-only, data will flow into the LFX Insights v3 dashboard.

[krook]

Hello again Knative maintainers. thelinuxfoundation id has accepted the GitHub organization owner invite.

That means we're now ready and able to add the read-only LFX Insights GitHub app to the org and repos.

This would be the very last step needed before onboarding is complete.

@aliok any questions or concerns from the KSC/maintainers before we go ahead and do that?

Insights documentation can be found here.

[aliok]

Checking with Knative SC/TOC folks.

[krook]

@aliok looks like they are OK with it based on the linked issue?

[aliok]

Thanks @krook . We're good!
If there are concerns (I doubt it), we can always revert the changes.

[krook]

Excellent, thank you @aliok

[aliok]

@krook

Looks nice, is it possible to mark some users as bots? Seems like they are all counted as well: https://insights.lfx.linuxfoundation.org/foundation/cncf/overview?project=knative&bestPractice=false

cc @ReToCode

We have another GH organization: https://github.com/knative-extensions

Can we also get this included?

[krook]

@krook

Looks nice, is it possible to mark some users as bots? Seems like they are all counted as well: https://insights.lfx.linuxfoundation.org/foundation/cncf/overview?project=knative&bestPractice=false

cc @ReToCode

We have another GH organization: https://github.com/knative-extensions

Can we also get this included?

Some bots are excluded by default, and others can be hidden using a checkbox flag in the report views. If there are other bots still showing as regular users we can update on the admin side (this will eventually be user configurable)

Hi @aliok, unfortunately we can't yet do multiple GitHub orgs per project yet in Insights. We'll need to revisit this in the future.

[krook]

@Cmierly it looks like adding to Insights was the final checkmark here. Anything else needed before we call the onboarding complete?

[Cmierly]

@krook Nope! With the open GH question being answered and them being added to Insights, Knative is now done with onboarding!