Welcome to the KubeStellar Contribution Guide! We are excited to have you here.
You can join the community via our Slack channel.
This section provides information on the Code of Conduct, guidelines, terms, and conditions that define the KubeStellar contribution processes. By contributing, you are enabling the success of KubeStellar users, and that goes a long way to make everyone happier, including you. We welcome individuals who are new to open-source contributions.
There are different ways you can contribute to the KubeStellar development:
Documentation: Enhance the documentation by fixing typos, enabling semantic clarity, adding links, updating information on changelogs and release versions, and implementing content strategy. Note that the KubeStellar documentation is consolidated into its own repository now.
Code: Indicate your interest in developing new features, modifying existing features, raising concerns, or fixing bugs.
Before you start contributing, familiarize yourself with our community Code of Conduct.
The KubeStellar GitHub organization is a collection of the different KubeStellar repositories that you can start contributing to.
Ensure that you comply with the rules and policy guiding the repository contribution indicated in the Developer Certificate of Origin (DCO).
If you are contributing via the GitHub web interface, navigate to the Settings section of your forked repository and enable the Require contributors to sign off on web-based commits setting. This will allow you to automatically sign off your commits via GitHub directly, as shown below.

If you are contributing via the command line terminal, run the git commit --signoff --message [commit message] or git commit -s -m [commit message] command when making each commit. For more detailed information about signing and signing off on commits, including steps to create signing keys and use both the -s and -S options, see Sign-off and Signing Contributions.
Read the resources to gain a better understanding of the contribution processes.