Welcome to naas's contributing guide!
- To acquire knowledge and skills
- To find amazing people who share similar interests.
- To advance your career.
- To track down a mentor who can assist you in achieving your goals.
- To be happy! (It truly works)
- Because in addition to every stated above, we want to promote your contributions on social networks to skyrocket your reputation and personal branding
- Because we are also looking for ways to give back more and more to our contributors. Our ultimate goal would be that you could be able to get a revenue stream out of it
- And because it is damn fun to innovate in the notebook space
The following are some areas where one can contribute:
The most popular area for contributions is templates because all you need is a notebook and awesome-notebooks to publish your work. Here is a list of simple good first issues available in the templates repository.
Fill out the form (Recommended)
By submitting issues and pull requests to the many GitHub repositories maintained by the Jupyter-Naas organization, you can also independently contribute to the project. Open an account on naas.ai It’s free 👉 https://app.naas.ai. For any kind of contribution, having a naas account is more than helpful, it will help you to:
- Test notebooks (for writing content or even doing code review)
- Setup some automation for yourself
- Receive credits thanks to your contributions (WIP)
- Review the latest product update and give feedback.
Take a look at the community roadmap. Our community roadmap gives insights on the ongoing and upcoming work. Feel free to comment under a good first issue you'd like to work on and we'll assign it to you.
We also really appreciate your support on social media (<-see links on the navigation bar). We try to push as much informative, educative, and entertaining but sometimes also provocative content as we can. Because communication comes first, code second.
Note that at Naas 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:
fix:to patch a bug
feat:to introduce a new feature
docs:to document a feature or a fix
style:to change the UX design of a feature
refactor:to change the way a feature works
test:to add unitary tests to the project
This commit convention applies to Naas and Naas drivers repository.