Contribute to Knative

This is the starting point for becoming a contributor - improving code, improving docs, giving talks, etc. Here are a few ways to get involved.

Prerequisites

If you want to contribute to Knative, you must do the following:

• Before you can make a contribution, you must fill out the Google Contributor License Agreement (CLA) using the same email address you used to register for Github. For more information, see Contributor license agreements.

• Read the Knative contributor guide.

• Read the Code of conduct.

For more information about how the Knative community is run, see About the Knative community.

Contribute to the code

Knative is a diverse, open, and inclusive community. Development takes place in the Knative org on GitHub.

Your own path to becoming a Knative contributor can begin in any of the following components, look for GitHub issues marked with the good first issue label.

• Knative Serving:

  • For how to get started contributing, see the Serving development workflow.
  • For good starter issues, see Serving issues.

• Knative Eventing:

  • For how to get started contributing, see the Eventing development workflow.
  • For good starter issues, see Eventing issues.

• Knative Client (kn):

  • For how to get started contributing, see the Client development workflow.
  • For good starter issues, see Client issues.

• Documentation:

  • For how to get started contributing, see the Docs contributor guide.
  • For good starter issues, see Documentation issues.

Contribute code samples to the community

Do you have a Knative code sample that demonstrates a use-case or product integration that will help someone learn about Knative?

Beyond the official documentation there are endless possibilities for combining tools, platforms, languages, and products. By submitting a tutorial you can share your experience and help others who are solving similar problems.

Community tutorials are stored in Markdown files under the code-samples/community. These documents are contributed, reviewed, and maintained by the community.

Submit a Pull Request to the community sample directory under the Knative component folder that aligns with your document. For example, Knative Serving samples are under the serving folder. A reviewer will be assigned to review your submission. They’ll work with you to ensure that your submission is clear, correct, and meets the style guide, but it helps if you follow it as you write your tutorial.

• Contribute code samples: Share your samples with the community.

• Link existing code samples: Link to your Knative samples that live on another site.

Learn and connect

Using or want to use Knative? Have any questions? Find out more here:

• Knative users group: Discussion and help from your fellow users.

• Knative developers group Discussion and help from Knative developers.

• Knative Slack: Ping @serving-help or @eventing-help if you run into issues using Knative Serving or Eventing and chat with other project developers. See also the Knative Slack guidelines.

• Twitter: Follow us on Twitter to get the latest news!

• Stack Overflow questions: Knative tagged questions and curated answers.

Community Meetup

This virtual event is designed for end users, a space for our community to meet, get to know each other, and learn about uses and applications of Knative.

Catch up with past community meetups on our YouTube channel.

Stay tuned for new events by subscribing to the calendar (iCal export file) and following us on Twitter.

More ways to get involved

Even if there’s not an issue opened for it, we can always use more testing throughout the platform. Similarly, we can always use more docs, richer docs, insightful docs. Or maybe a cool blog post? And if you’re a web developer, we could use your help in spiffing up our public-facing web site.

Bug reports and friction logs from new developers are especially welcome.