Thank you for your interest in contributing! We love community contributions.
Contribution guidelines are listed below. If you're unsure about how to start contributing or have any questions even after reading them, feel free to ask us on Slack in the # 03_contributions..
However, for those who want a bit more guidance on the best way to contribute to Naas, read on. This document will cover what we're looking for. By addressing the points below, the chances that we can quickly merge or address your contributions will increase.
Please follow our Code of conduct in the context of any contributions made to Naas.
Commit convention
We follow the Conventional Commits specification. It is a lightweight convention on top of commit messages. It provides an easy set of rules for creating an explicit commit history; which makes it easier to write automated tools on top.
In Naas, we use the following commit elements to communicate:
1.
fix: to patch a bug
2.
feat:to introduce a new feature
3.
docs: to document a feature or a fix
4.
style: to change the UX design of a feature
5.
refactor:to change the way a feature works
6.
test:to add unitary tests to the project
This commit convention applies to Naas and Naas drivers repository.
Areas for contribution
Templates Database
Templates Database
Naas on Notion
Other areas of contributions are:
Documentation
Naas drivers (python package for integrations)
Naas features (micro-services on top of Jupyter Notebooks)