Contribute to Avalanche
How to Contribute Back to the Avalanche Community
The last step to become a real continual learning super-hero ⚡ is to fall into a radioactive dump.☢️ Just kidding, it's much easier than that: you need to contribute back to Avalanche!
There are no superheroes that are not altruistic!
First of all, if you haven't already. After you've familiarized with the Avalanche codebase you have two roads ahead of you:
You can start working on a (we have dozen of them!)
You can and propose yourself to work on it.
In any of the two cases you'd need to follow the steps below:
and #avalanche-dev channel (optional but recommended)
⭐_Star_ + 👁️_watch_ the repository.
The following rules should be respected:
Use PEP8 coding style and work within the 80 columns limit.
Always pull before pushing a commit.
Try to assign to yourself one issue at a time.
Also, before making your PR make sure that the following commands return without any errors:
Otherwise fix them and run again these commands until everything is working correctly. You should also check if everything is working on GPUs, using the env variable USE_GPU=True:
Faster integrity checks can be run with the env variable FAST_TEST=True :
Contribute to the Avalanche documentation
Apart from the code, you can also contribute to the Avalanche documentation 📚! We use to write the documentation, so both code and text can be smoothly inserted, and, as you may have noticed, all our documentation can be run on !
To contribute to the documentation you need to follow the steps below:
The notebooks are contained in the folder notebooks. The folder structure is specular to the documentation, so do not create or delete any folder.
Detect the notebook that you want to edit and do all the modifications 📝
Commit the changes and open a pull request (PR).
🤝 Run it on Google Colab
You can run this chapter and play with it on Google Colaboratory:
