Development
++ We are interested in any contribution. There are many ways how you can + contribute: +
-
+
- + If you wrote anything interesting using SymPy, please send us a patch with the + code (see below for more information). + + +
- + If you found a bug (or just want to let us know what you think), tell us on the + mailinglist. You can also + add a bug report (or a comment) into the issues. + +
- You can blog about how you use SymPy. +
- You can help us write documentation (just send us a patch). +
- You can help people on our mailinglist. +
- You can help with reviewing patches. +
- You can send us patches with bug fixes or new features. +
+ The best way to contribute code or documentation is to send us a patch. +
+How to Send a Patch
++ The best way is to send a github pull request + against the sympy/sympy repository. + We'll review it and push it in. +
+ ++ If you need help with git, github, pull requests, patches, coding, SymPy or + anything related, just send us an email to the mailinglist + or ask on IRC (our channel is #sympy at freenode), we'll help. + Also, you can read our instructions + + how to prepare patches using git and github. +
+ ++ The github pull request is a preferred method, as that makes it easy for us to + review and push the code in. That said, + you can also clone the latest git repository (see the link on the right), prepare a branch with + your code, upload it somewhere (for example github) and send us a link to the sympy-patches + mailinglist, or you can even send us raw patches --- but it will be more work + for us to integrate it. +
+ ++ SymPy has a broad development team: + + http://docs.sympy.org/0.7.1/aboutus.html#sympy-development-team + , send us a patch and your name will appear there too. +
+ +Sources of the Webpages
++ Sources of these webpages are at: + http://github.com/sympy/sympy.github.com +
+ Feel free to send us patches with improvements. +