Differences between revisions 13 and 40 (spanning 27 versions)
Revision 13 as of 2009-12-24 10:14:01
Size: 2231
Editor: Minh Nguyen
Comment: typo in link to release management page
Revision 40 as of 2023-02-23 20:20:48
Size: 4248
Editor: mkoeppe
Comment: remove Trac stuff
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
= Sage Developer Center =

Welcome to the Sage developer center!

Note: Developers should check https://github.com/sagemath/sage/issues?q=is%3Aopen+sort%3Aupdated-desc+ at least one per week. That's where development actually happens.

TODO:

Organize, sage-devel.

 * [[faq | Sage FAQ - Frequently Asked Questions]]
 * [[Tips]]
 * [[data | Put (links to) interesting data you compute using Sage here]]
 * [[pics | Code to make cool images]]
 * [[plot | Sage plotting]]
 * [[art | Art - posters, banners, etc]]
 * [[interact | Interact Demos]]
 * [[http://tug.ctan.org/pkg/sagetex | SageTeX - Put some sage into your TeX]]
 * [[standard_packages_available_for_SAGE | standard packages available for Sage]]
 * [[optional_packages_available_for_SAGE | optional packages available for Sage]]
 * [[experimental_packages_available_for_SAGE | experimental packages available for Sage]]
 * [[Sage_Spkg_Tracking | SPKG changelog and descriptions]]
 * [[OSCAS]]
 * [[SAGE_Reviews | Sage Reviews]]
 * [[Teaching_using_SAGE | Teaching using Sage]]
 * [[Teaching_with_SAGE | Teaching with Sage]]
 * [[DocumentationProject | Documentation Project]]
 * [[Comparisons]]
 * [[SAGE_in_the_News | Sage in the News]]
 * [[Publications_using_SAGE | Publications using Sage]]
 * [[Talks | Talks and Presentations about Sage]]
 * [[Software|Ideas for Software to Integrate With Sage]]
 * [[Software_that_may_be_useful]]
 * [[devel/ReleaseManagement|Release Management]]
 * [[SEP|Sage Enhancement Proposals]]
 * [[Software_surveys]]
 * [[debian|Sage in Debian]]
 * [[HowToBeginSageDevelopment|How to begin Sage development]]
 * [[combinat/HelpOnTheDoc|Docstring Docummentation]] for help on the format (ReSTructured text) used in the docstrings, including special Sage doctest conventions
 * [[JavascriptResources | JavaScript and related resources]]
 * [[PythonResources | Python and Cython resources]]
 * [[SageUsability | Sage Usability Improvements List]]
 * [[SageNotebook | Technical Overview of the Sage Notebook]]

= Sage developer center =
Line 3: Line 49:
This wiki page helps in organizing the development of Sage. Information and links to Sage development should be organized under "devel/". For answers to commonly asked questions, see the [[faq | FAQ]]. This wiki page helps in organizing the development of Sage. Information and links to Sage development should be organized under "devel/". For answers to commonly asked questions, see the [[http://www.sagemath.org/doc/faq/ | FAQ]].
Line 5: Line 51:
Note: The [[http://trac.sagemath.org/sage_trac/ |trac server]] contains patches awaiting review. Michael Abshoff wrote a set of [[devel/TracGuidelines | general guidelines]] for using the trac server. See also the [[http://www.sagemath.org/doc/developer/trac.html | Developers' Guide]] for further information on using the trac patch server.
Line 14: Line 59:
 * [[SageClusterGuidelines | Sage cluster guidelines]] --- guidelines for using machines on the Sage cluster
Line 16: Line 60:
 * [[UpdateCopyright | Update the copyright notice]] = Sage development =
Line 18: Line 62:
 * [[Software | Ideas for software to integrate with Sage]] Much of the Sage library is written in Python. Some performance critical parts of the Sage library is written in Cython. Information is available to help [[devel/BeginSageDevelopment | beginners on developing]] the Sage library. Also consult the list of [[devel/PythonCythonResources | Python and Cython resources]] for beginner to advanced information on the Python and Cython languages. You can also do [[devel/FunctionalProgramming | functional programming with Python and Sage]].
Line 20: Line 64:
 * [[Software_that_may_be_useful | Software that may be useful]]  * [[http://www.sagemath.org/doc/faq/faq-contribute.html | Frequently asked questions regarding Sage development]]
Line 22: Line 66:
 * [[SEP | Sage Enhancement Proposals]] ||<#FFFF66>Please write Python3-compatible code (see [[Python3-compatible code]])||
Line 24: Line 68:
 * [[Software_surveys | Software surveys]]
Line 26: Line 69:
 * [[DebianSAGE | Sage in Debian]] = Miscellaneous =
Line 28: Line 71:
 * [[HowToBeginSageDevelopment | How to begin Sage development]]  * [[devel/SoftwareToIntegrate | Ideas for software to integrate with Sage]]
Line 30: Line 73:
 * [[devel/nonASCII | non-ASCII characters]] in source files  * [[devel/UsefulSoftware | Software that may be useful]]
Line 32: Line 75:
 * [[firefox-trac | Cool tricks]] for better Firefox/trac integration  * [[devel/SEP | Sage Enhancement Proposals]]
Line 34: Line 77:
 * [[combinat/HelpOnTheDoc | Docstring documentation]] for help on the format (ReSTructured text) used in the docstrings, including special Sage doctest conventions  * [[devel/SoftwareSurveys | Software surveys]]
Line 36: Line 79:
 * [[JavascriptResources | JavaScript and related resources]]  * [[devel/DebianSage | Sage in Debian]]
Line 38: Line 81:
 * [[PythonResources | Python and Cython resources]]  * [[devel/SageTasks | Sage usability task list]]
Line 40: Line 83:
 * [[SageUsability | Sage usability improvements list]]  * [[devel/BuildFarm | Build farm]]
Line 42: Line 85:
 * [[SageTasks | Sage usability task list]]  * [[devel/LatexToWorksheet | Latex document conversion to Sage worksheets]]
Line 44: Line 87:
 * [[SageNotebook | Technical overview of the Sage notebook]]  * [[SharingYourBranch | Sharing your branch of Sage development]]

 * [[prerequisitesUbuntu | List of Ubuntu packages required to build Sage]]

Sage Developer Center

Welcome to the Sage developer center!

Note: Developers should check https://github.com/sagemath/sage/issues?q=is%3Aopen+sort%3Aupdated-desc+ at least one per week. That's where development actually happens.

TODO:

Organize, sage-devel.

Sage developer center

Welcome to the Sage developer center!

This wiki page helps in organizing the development of Sage. Information and links to Sage development should be organized under "devel/". For answers to commonly asked questions, see the FAQ.

Release management

Each release cycle of Sage is managed by at least one release manager. For example, a release manager produces the various alpha and rc releases for the sage-x.y.z release cycle. Release management is a complex task. The release management page contains a rough set of guidelines for Sage release management. If you want to help out with release management, please subscribe to the sage-release mailing list.

Sage development

Much of the Sage library is written in Python. Some performance critical parts of the Sage library is written in Cython. Information is available to help beginners on developing the Sage library. Also consult the list of Python and Cython resources for beginner to advanced information on the Python and Cython languages. You can also do functional programming with Python and Sage.

Please write Python3-compatible code (see Python3-compatible code)

Miscellaneous

devel (last edited 2023-02-23 20:20:48 by mkoeppe)