|
Size: 5276
Comment:
|
Size: 5183
Comment: remove broken link
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 61: | Line 61: |
| * [[http://www.liafa.jussieu.fr/~labbe/Sage/how-to-contribute/|How to Contribute to Sage]] |
Welcome to Sage
The open-source alternative to Magma, Maple, Mathematica, and MATLAB!
Sage is a Python-based framework which provides a unified environment for nearly 100 open-source packages related to mathematics research and education. In addition to a consistent interface to these packages, Sage also provides new functionality built by letting these various packages work together. We're building the car, not reinventing the wheel.
There are hundreds of Sage developers around the world. Most of these are mathematicians who use Sage for research and education. As the project grows, we have greater and greater need for contributions from serious programmers. We've compiled a few suggestions to whet your appetite here; further details and more ideas can be found at the links below, or by contacting the Sage developer list.
Suggestions for developers with programming background
Package Interfaces
Improve the matplotlib interface, and related graphics issues. Converting between matplotlib Figures and sage GraphicsObjects, for example, is currently not possible. Converting 3D plots to 2D GraphicsObjects is not possible. There are a lot of other broken or undocumented things here too.
Improve the gap interface. In particular, convert gap's iterators to native Sage objects
- Improve other interfaces -- email the developer list for further suggestions.
Doctesting/building
Add functionality to build the Sage reference manual in parallel, or to easily build a subset of the manual. Some familiarity with Python docbuilding and Sphinx will be required here.
Add more automated testing of the Sage library, through randomized tests, and improvements to the Patch Buildbot.
Algorithms
- Algorithms for fast computation that you may have seen in a computer science book are not just of theoretical interest here -- they're central to Sage's mission! Before you start work on one of these, be sure that it doesn't already exist in one of Sage's components. If it does, work on improving the interface with that component rather than reimplementing the algorithm.
Sage startup and usage
Sage does a lot at startup, related to the startup of its many components. Good ideas for improving the startup time are needed.
Rework sage build scripts, so that everything is built "in place", maybe using setuptools, and thus achieve significant size reduction of sage build. Some ideas are discussed in this thread.
There are a number of startup options for building, testing, etc. These have evolved in a somewhat disorganized manner over time, and need to be better unified, organized, and documented. Some specific ideas are mentioned in comments to this related ticket
Cygwin Port
Currently Sage runs on Windows only as a virtual machine, through the VMware Player. This is viewed by many as a major barrier to new users, and work is ongoing to produce a Cygwin port. Here is a list of the remaining tickets for this issue. Some of these require a lot of work, but some are simple, and several are simple for someone with a Windows programming background.
Further information
To learn about the Sage program, these links will give you a good overview:
If you are interested in development, the following links will help:
Mentoring
The Sage community is interested in mentoring new developers. If you have specific questions, go ahead and ask the developer mailing list. If you're excited about the project but aren't sure where to start, send a brief description of your background and interests and someone with related experience will volunteer to mentor you! You can do this either on the mailing list, or at the Sage support Q&A site Ask Sage.