How to contribute to Scilab
First Step: Legal aspects
Second step: Technical aspects
Guidelines
- You need to work from the Scilab master.
- Update from the master branch often since it is moving fast.
Want to fix a bug yourself?
It is pretty easy and detailed on this page: How to close a bug in Scilab
Not a Scilab Contributor? Send us your modifications
If you are not a Scilab Contributor, you have to send us a patch that we will apply against the master or a specific branch.
Once all your changes are recorded in your local repository (using git commit), run the command:
# git format-patch origin
This command will generate a <commit comment>.patch file per commit. Then just send us these files (or attached them to the bug report) and we will apply these changes against the master.
If it is a feature listed on the page Ideas of development for Scilab, send an email to dev@lists.scilab.org with a brief explanation of your work.
Scilab Contributor? Commit your modifications
If your code does not break Scilab (for example a new module which can be disabled), you can commit as you like.
If there is a risk that it will break Scilab for a while, please restrain to commit as long as it is not working.
Don't forget that Scilab is supported under three different operating system (Apple Mac OS X, GNU/Linux and Microsoft Windows). While Mac & Linux are very similar, Windows is very different. Don't hesitate to send an email on the developer mailing list if you need help.
Development
We have a few rules in the code. See the dedicated URLs:
See you have any questions, do not hesitate to contact us.