Everybody who uses Sage is encouraged to contribute something back to Sage at some point. You could:
This document tells you what you need to know to do all the above, from reporting bugs to modifying and extending Sage and its documentation. We also discuss how to share your new and modified code with other Sage users around the globe.
Here are brief overviews of each part; for more details, see the extended table of contents below. No matter where you start, good luck and welcome to Sage development!
Trac server: all changes go through the the Sage Trac server at some point. It contains bug reports, upgrade requests, changes in progress, and those already part of Sage today. Click here for more information.
Importantly, you will need to create a trac account in order to contribute.
Source code: You need your own copy of Sage’s source code to change it. Go there to get it and for instructions to build it.
If you have never worked on software before, pay close attention to the prerequisites to compile on your system.
Conventions: read our conventions and guidelines for code and documentation.
For everything related to manuals, tutorials, and languages, click here.
Git (revision control): To share changes with the Sage community, you will need to learn about revision control; we use the software Git for this purpose.
Sage uses git for version control.
Putting your local changes on a Trac ticket.
When git trac is not enough.
All changes to Sage source code require a ticket on the Sage trac server.
This work is licensed under a Creative Commons Attribution-Share Alike 3.0 License.