Thank you for helping us make our vision a reality! All contributions are welcome; from bug reports, codefixes, and new features!
Corteza projects are Apache 2.0 licensed and accept contributions via GitHub pull requests.
Cover the terminology for the development process and versioning.
Cover the Git and GitHub ground rules regarding branch naming and conventions.
When you wish to start working on a code contribution, assign yourself to a GitHub issue. If there is no issue, create one beforehand.
A quick summary on How to Write a Git Commit Message:
- Separate subject from body with a blank line
- Limit the subject line to 50 characters
- Capitalize the subject line
- Do not end the subject line with a period
- Use the imperative mood in the subject line
- Wrap the body at 72 characters
- Use the body to explain what and why vs. how
Corteza server is the back-end of the Corteza ecosystem. The core logic is written in GO, using go-chi for the routing.
Communication between the Corteza server and web applications is done using the REST API and web sockets. Communication between back-end services (Corteza server and Corredor) is done using gRPC.
The Developer Guide/Corteza Server covers the development setup, the project structure, and the feature insight documents.
The web applications are written in Vue.js and provide the user interface to interact with the entire system. The repositories:
- corteza-webapp-one
- corteza-webapp-admin
- corteza-webapp-compose
- corteza-webapp-workflow
- corteza-webapp-reporter
- corteza-webapp-discovery
Communication between the Corteza server and web applications is done using the REST API and web sockets.
The Developer Guide/Corteza Web Applications covers the development setup, the project structure, and the feature insight documents.
The documentation is written in AsciiDoc and compiled using Antora. The source code is available on the GitHub cortezaproject/corteza-docs repository; the generated output is available on the documentation page.
The Developer Guide/Documentation covers the conventions, writing guidelines, as well as some examples to help you get started.
Please submit any bug reports on the issues section of the corresponding GitHub repository. If you are unsure where to submit the issue, or you are unsure if this is a feature; reach out to us on our forum.
Feature and improvement requests should be submitted on our forum. Before opening a new topic, search around to see if there are any similar topics that would cover your case.
By contributing to this project you agree to the Developer Certificate of Origin (DCO). This document was created by the Linux Kernel community and is a simple statement that you, as a contributor, have the legal right to make the contribution. See the DCO file for details.