Welcome to the Kyma community. Here you can find information on how to join the community, get involved, and improve Kyma code and documentation.
Before you proceed, review the Code of Conduct and contact us on Slack for any questions or concerns.
Go directly to the section that you are most interested in:
Kyma is a cloud-native application development framework which allows you to connect and extend products in a quick and modern way, using serverless computing and microservice architecture. Read more about the product here.
If you are interested in the Kyma product management, architecture, and the operational responsibility philosophy, see the Kyma Manifesto.
Kyma is also on social media. Visit the website and follow Kyma on Twitter, and LinkedIn.
We are an open-source community and the number of contributors is growing. Meet the Kyma team members who are the regular contributors and the Kyma founders.
Before you start to contribute, review the CONTRIBUTING.md document. To understand better the way the Kyma community works, read the governance model and learn about the Special Interest Groups and Working Groups in Kyma.
All contributors follow the recommended Git workflow that relies on forks, branches, rebasing, and squashing. Review it to ensure that you contribute high-quality code and content to the project.
To request a feature or report a bug, go to the given repository's issue tracker and raise an issue using one of the available templates.
The owners of the repository will review your issue and provide you with their feedback. If you are not certain which repository your issue refers to, open it in the kyma repository.
Feel invited to join the public SIG Core meetings where you can contribute to the Kyma development and help us drive it forward. Contact the Kyma team directly on Slack to exchange ideas, ask questions, receive hints and tips, and extend your experience with Kyma.
You can also find these guidelines and templates in the community repository:
- Naming conventions
- Document templates
- Overview of the content strategy and content guidelines
- Release process details
- Decisions made by Kyma team members and the SIG Core.
- Coding standards
There are also internal guidelines for the Kyma team members. They contain a folder, file, and document structure required for a skeleton Kyma repository.
The community is relentless about Kyma security. To report a security issue, send an email with details directly to kyma-security@googlegroups.com instead of using a public issue tracker.