|
Size: 6735
Comment:
|
Size: 6163
Comment: Remove "major external pages"
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 1: | Line 1: |
| ## page was renamed from MyStartingPage ## page was renamed from drkirkby ## page was renamed from MyStartingPage |
= SageMath Wiki = |
| Line 5: | Line 3: |
| = ACCESS = | This is the wiki for the [[https://www.sagemath.org|Sage - Mathematics Software System]] project. There are other [[ThingsCalledSage]]. |
| Line 7: | Line 5: |
| * '''To access the wiki, use your trac account.''' See http://trac.sagemath.org/sage_trac/ for how to get a trac account. (Spammers: Please don't waste your time trying to get an account, since you have to write an email to a human and convince them you are actually a Sage developer.) | This wiki is mainly used by developers for organization of e.g. SageDays and discussion of long-term projects. Since it ''is'' a wiki, pages should be made to last over many, and frequent, changes. If an external link is made, please attach relevant files/content to avoid broken links. |
| Line 9: | Line 7: |
| = Sage Wiki = This is the wiki for the [[http://www.sagemath.org|Sage - Mathematics Software System]] project. It helps in organizing development, projects and meetings. ||[[#sagedays|Sage Days]] || [[#messagingsites|Message Boards, Chatrooms]] || |
||<tablestyle="font-size: 0.8em;">||<#F7819F>❤ || You can help by becoming a [[https://github.com/sponsors/sagemath|sponsor]]|| |
| Line 15: | Line 10: |
| = License and Copyright = By making an explicit contribution to the [[http://www.sagemath.org/|Sage]] wiki (or the [[http://www.sagemath.org/documentation.html|Sage documentation]]), one certifies that one's contribution is licensed under the [[http://creativecommons.org/licenses/by-sa/3.0/|Creative Commons 3.0 BY-SA license]]. |
||<tablestyle="font-size: 0.8em;">||<#74DF00>Information || Since version 9.0, Sage is using '''Python 3'''. See [[Python3-Switch]] for more information.|| |
| Line 22: | Line 14: |
| = SageDays, Sage Workshops, other activities = <<Anchor(sagedays)>> == Past and future Workshops == * Upcoming Workshops <<Include(Workshops, , from="^##start-include$", to="^----$")>> * [[Workshops | All Workshops]], including past and future Sage Days, Bug Days, Doc Days, Review Days, Education Days, and some other Sage-related events. |
|
| Line 23: | Line 21: |
| = FAQ: Frequently Asked Questions = | == Sage Release Tours (version 9.0 and later) == |
| Line 25: | Line 23: |
| * [[faq|Sage FAQ - Frequently Asked Questions]] | * [[ReleaseTours]] |
| Line 27: | Line 25: |
| == Google Summer of Code == | |
| Line 28: | Line 27: |
| = News = | * [[GSoC|Google Summer of Code]] |
| Line 30: | Line 29: |
| * [[SAGE_in_the_News|Sage In the News and Blogs]] <<Anchor(sagedays)>> = Events/Upcoming Research Workshops = * [[days32|Sage Days 32: Bug Days (near Seattle), August 21-25, 2011]] * [[days33|Sage Days 33: Women in Sage (near Seattle), September 19-23, 2011]] * [[days34|Sage Days 34: Singular Days (Kaiserslautern, Germany), September 26-30, 2011]] * Sage Days X, for some X > 34: likely April 2012, South Korea. Contact DanDrake for more information. * [[HowToHostASageDays|Hosting]] --- Advice to future hosts [[Workshops | Past and future workshops]], including Sage Days, Bug Days, Doc Days, Review Days, and Education Days. |
== Hosting a workshop == * [[HowToHostASageDays|How To Host A Sage Days]] --- Advice to future hosts * [[HowToSpreadSageDuringAWorkshop|How to Spread Sage During a Workshop]] --- Advice to future hosts |
| Line 47: | Line 34: |
| The most up-to date list of Sage developers is on our [[https://trac.sagemath.org/sage_trac/wiki#AccountNamesMappedtoRealNames|list of developers on the Sage trac wiki]]. | |
| Line 48: | Line 36: |
| [[http://www.sagemath.org/development-map.html|Overview of all registered Sage developers on a world map]] The following list is very incomplete and only contains those developers who added themselves to this wiki. The [[http://trac.sagemath.org/sage_trac/wiki#AccountNamesMappedtoRealNames|list of developers on the Sage trac wiki]] contains more than 300 people. [[WilliamStein|William Stein]], [[David_Joyner|David Joyner]], [[MichaelAbshoff|Michael Abshoff]], [[MartinAlbrecht|Martin Albrecht]], [[TomBoothby|Tom Boothby]], [[IftikharBurhanuddin|Iftikhar Burhanuddin]], [[AlexClemesha|Alex Clemesha]], [[DidierDeshommes|Didier Deshommes]], [[DavidHarvey|David Harvey]], [[YiQiang|Yi Qiang]], [[RobertMiller|Robert Miller]], [[OndrejCertik|Ondřej Čertík]], [[jaapspies|Jaap Spies]], [[MarshallHampton|Marshall Hampton]], [[JacobMitchell|Jacob Mitchell]], [[CraigCitro|Craig Citro]], [[GlennTarbox|Glenn Tarbox]], [[NicolasThiéry| Nicolas M. Thiéry]], [[ThierryMonteil|Thierry Monteil]] Here is a [[http://wiki.wstein.org/2008/summer/employ|list of students employed to work fulltime on Sage during Summer 2008]] * [[CommunityManagement|community management]] |
[[https://www.sagemath.org/development-map.html|Overview of (many) Sage developers on a world map]] |
| Line 61: | Line 40: |
| [[https://groups.google.com/group/sage-support|sage-support]], [[https://groups.google.com/group/sage-devel|sage-devel]], [[https://groups.google.com/group/sage-release|sage-release]], [[https://groups.google.com/group/sage-announce|sage-announcements]], [[https://groups.google.com/group/sage-edu|sage-edu]] for teaching using Sage, [[https://groups.google.com/group/sage-finance|sage-finance]] for finance, [[https://groups.google.com/group/sage-coding-theory|sage-coding-theory]] for coding theory, [[https://groups.google.com/group/sage-nt|sage-nt]] for number theory, and [[https://groups.google.com/group/sage-combinat-devel|sage-combinat-devel]]. | |
| Line 62: | Line 42: |
| * [[http://groups.google.com/group/sage-support|support]] * [[http://groups.google.com/group/sage-devel|developers]] * [[http://groups.google.com/group/sage-release|releases]] * [[http://groups.google.com/group/sage-announce|announcements]] * [[http://groups.google.com/group/sage-edu|teaching]] using Sage * [[http://groups.google.com/group/sage-dsageng|Distributed and Parallel Sage]] * [[http://groups.google.com/group/sage-finance|Sage Finance]] * IRC channel: {{{#sagemath}}} on [[http://freenode.net/|freenode ]] (`chat.freenode.net`) * The Sage website contains links to [[http://www.sagemath.org/development-groups.html | other discussion mailing lists]]. |
[[https://zulip.sagemath.org | Zulip]] group chat server for realtime collaboration on Sage (like Slack). Fairly low-activity. |
| Line 72: | Line 44: |
| !SageMath has a presence on some [[Social Networks]]. The Sage website contains links to [[https://www.sagemath.org/development-groups.html | other discussion mailing lists]]. |
|
| Line 75: | Line 50: |
| The [[devel | development wiki]] page and the [[http://www.sagemath.org/doc/developer/ | Developers' Guide]] contain information on Sage development suitable for beginners as well as experienced developers. Beginners' pages include: | Development is handled using "tickets" on the [[https://trac.sagemath.org/sage_trac/|trac server]]. |
| Line 77: | Line 52: |
| * [[http://www.sagemath.org/doc/faq/faq-contribute.html | Development FAQ]] * [[http://www.sagemath.org/doc/developer/trac.html | Trac guidelines]] by Michael Abshoff * [[firefox-trac | Cool tricks]] for Firefox/trac integration * Recent release tours: ` ` [[ReleaseTours/sage-4.3.1 | 4.3.1]], ` ` [[ReleaseTours/sage-4.3 | 4.3]], ` ` [[ReleaseTours/sage-4.1.1 | 4.1.1]],` ` [[ReleaseTours/sage-4.1 | 4.1]],` ` [[ReleaseTours/sage-4.0.2 | 4.0.2]],` ` [[ReleaseTours/sage-4.0.1 | 4.0.1]],` ` [[ReleaseTours/sage-4.0 | 4.0]],` ` [[ReleaseTours | more]]. |
The main developer doc is the [[https://www.sagemath.org/doc/developer/ | Developers' Guide]]. |
| Line 82: | Line 54: |
| Note: [[http://trac.sagemath.org/sage_trac/|See the trac server]] for patches awaiting review. | Release notes (higher level than change logs) are collaboratively prepared at [[ReleaseTours]]. [[Infrastructure|Development/project infrastructure]] = Special Discussion Pages = * [[Coding_Theory|Coding Theory in Sage]] * [[Debate/Collective infrastructure management]] * [[Python3-compatible code|Writing Python 3 compatible code]] * [[OptiPolyGeom|Optimization and Polyhedral Geometry in Sage]] * [[asksage retagging]] * [[Conda|Using Conda to build SageMath]] |
| Line 85: | Line 68: |
| = Recent Non-SageDays Workshops/Events that involved/impacted Sage = | = Features = |
| Line 87: | Line 70: |
| * [[http:/combinat/SageCombinatWorkshopOrsay|Sage-Combinat Workshop in Orsay]], January 26-30, 2009 * [[http://modular.math.washington.edu/msri06/|MSRI Workshop on Modular Forms]], Berkeley, CA, July 31 -- Aug 11, 2006 * [[http://sage.math.washington.edu/msri07|MSRI Workshop on Interactive Parallel Computation]], Berkeley, CA, Jan 29 -- Feb 2, 2007 |
* [[http://www.sagemath.org/tour.html|sagemath.org: SageMath Feature Tour]] * [[Interfaces|Sage wiki: SageMath interfaces to and from other software]] |
| Line 91: | Line 73: |
= Tips and Tricks = * [[Tips]] * [[UsingSquashFS]] * [[SagemathLive]] * [[Send corrected worksheets to each student]] = Data = * [[data|Put (links to) interesting data you compute using Sage here]] = Images / Plotting / Art = * [[pics|Code to make cool images]] * [[plot|Sage plotting]] |
== Demonstrations of Graphical Capabilities == |
| Line 110: | Line 76: |
| * [[animate|Animate Demos]] * [[http://tug.ctan.org/pkg/sagetex|SageTeX - Put some sage into your TeX]] |
* [[K3D-tools|K3D-jupyter 3D visualisation in jupyter notebook]] |
| Line 113: | Line 78: |
| = Packages = | |
| Line 114: | Line 80: |
| = Other Sage items = | == New-style SPKGs == |
| Line 116: | Line 82: |
| * [[days13/projects/sagenewbie|Sage primers]] * [[sagenb|list of institutions and projects using the Sage]] * [[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]]s * [[SAGE_Reviews|Sage Reviews]] * [[Teaching_using_SAGE|Teaching using Sage]] * [[Teaching_with_SAGE|Teaching with Sage]] * [[quickref|Sage Quick Reference Cards]] * [[DocumentationProject|Documentation Project]] * [[Comparisons]] * [[SAGE_in_the_News|Sage in the News]] * [[Publications_using_SAGE|Publications using Sage]] * [[Talks| Talks and Presentations about Sage]] * [[SageForHighSchool|Sage for High school usage]] (see here for [[HighSchoolDesign|development page]]) * [[dynamics|Dynamical systems with Sage]] (Note -- wikis are ''not'' written in HTML. Use the GUI Mode (in Firefox) or read the wiki help links at the top.) |
There is a single authoritative place to learn about the specific set of packages (new-style SPKGs) that Sage uses: The [[https://github.com/sagemath/sage/tree/develop/build/pkgs|SAGE_ROOT/build/pkgs/]] directory in the Sage distribution. Each SPKG is represented by a subdirectory. The structure of these subdirectories is explained in the [[https://doc.sagemath.org/html/en/developer/packaging.html|Developer's Guide|]]. Since Sage 9.2, the [[https://doc.sagemath.org/html/en/reference/spkg/|spkg section of the Sage reference manual]] is automatically generated from the information in `SAGE_ROOT/build/pkgs/`. ([[https://trac.sagemath.org/ticket/29655|Trac #29655]] improves the formatting of this information.) Use the following shell commands below to access the information from the `SAGE_ROOT/build/pkgs` directory of your copy of Sage: * Standard packages: `./sage -standard` * Installed packages: `./sage -installed` * Optional packages available: `./sage -optional` * Experimental packages available: `./sage -experimental` * Details about an SPKG: `./sage -info <SPKG>` For some advanced package tools, use `./sage -package` == External packages == * SageMathExternalPackages * [[CodeSharingWorkflow|On development models for sharing (experimental) code]] = About this wiki = '''Editing the wiki.''' Page editing uses the MoinMoin syntax. To edit the wiki, you will need a log in using your [[https://trac.sagemath.org/#legacy-account-request|legacy sage-trac account]] account; a !GitHub account cannot be used for this. If you edit an existing page with a long history, a key question is: "If someone opens this page tomorrow, will they be able to tell which information is current and which is outdated?" Edit accordingly. '''SageWiki maintenance.''' The [[SageWikiMaintenance page]] attempts to reorganize the wiki, which has accumulated many outdated pages. '''License and Copyright.''' Contributions to the [[https://www.sagemath.org/|Sage]] wiki and to the [[https://doc.sagemath.org|Sage documentation]] are licensed under the [[https://creativecommons.org/licenses/by-sa/3.0/|Creative Commons 3.0 BY-SA license]]. By contributing, you agree to place your contribution under that license. |
SageMath Wiki
This is the wiki for the Sage - Mathematics Software System project. There are other ThingsCalledSage.
This wiki is mainly used by developers for organization of e.g. SageDays and discussion of long-term projects. Since it is a wiki, pages should be made to last over many, and frequent, changes. If an external link is made, please attach relevant files/content to avoid broken links.
❤ |
You can help by becoming a sponsor |
Information |
Since version 9.0, Sage is using Python 3. See Python3-Switch for more information. |
Contents
SageDays, Sage Workshops, other activities
Past and future Workshops
- Upcoming Workshops
Sage Days 124.7 — Sessions at the 8th International Congress on Mathematical Software, July 22-25, 2024, Durham (UK)
Sage Days 125 — combinatorics, number theory, dynamical systems and geometry, January 29th - February 1st, 2024, Le Teich, near Bordeaux, France
Sage Days 126 - August 31-September 2, 2024, Chennai, India
All Workshops, including past and future Sage Days, Bug Days, Doc Days, Review Days, Education Days, and some other Sage-related events.
Sage Release Tours (version 9.0 and later)
Google Summer of Code
Hosting a workshop
How To Host A Sage Days --- Advice to future hosts
How to Spread Sage During a Workshop --- Advice to future hosts
People
The most up-to date list of Sage developers is on our list of developers on the Sage trac wiki.
Overview of (many) Sage developers on a world map
Mailing Lists / Chat Rooms
sage-support, sage-devel, sage-release, sage-announcements, sage-edu for teaching using Sage, sage-finance for finance, sage-coding-theory for coding theory, sage-nt for number theory, and sage-combinat-devel.
Zulip group chat server for realtime collaboration on Sage (like Slack). Fairly low-activity.
SageMath has a presence on some Social Networks.
The Sage website contains links to other discussion mailing lists.
Development
Development is handled using "tickets" on the trac server.
The main developer doc is the Developers' Guide.
Release notes (higher level than change logs) are collaboratively prepared at ReleaseTours.
Development/project infrastructure
Special Discussion Pages
Features
Demonstrations of Graphical Capabilities
Packages
New-style SPKGs
There is a single authoritative place to learn about the specific set of packages (new-style SPKGs) that Sage uses: The SAGE_ROOT/build/pkgs/ directory in the Sage distribution. Each SPKG is represented by a subdirectory. The structure of these subdirectories is explained in the Developer's Guide.
Since Sage 9.2, the spkg section of the Sage reference manual is automatically generated from the information in SAGE_ROOT/build/pkgs/. (Trac #29655 improves the formatting of this information.)
Use the following shell commands below to access the information from the SAGE_ROOT/build/pkgs directory of your copy of Sage:
Standard packages: ./sage -standard
Installed packages: ./sage -installed
Optional packages available: ./sage -optional
Experimental packages available: ./sage -experimental
Details about an SPKG: ./sage -info <SPKG>
For some advanced package tools, use ./sage -package
External packages
About this wiki
Editing the wiki. Page editing uses the MoinMoin syntax. To edit the wiki, you will need a log in using your legacy sage-trac account account; a GitHub account cannot be used for this. If you edit an existing page with a long history, a key question is: "If someone opens this page tomorrow, will they be able to tell which information is current and which is outdated?" Edit accordingly.
SageWiki maintenance. The SageWikiMaintenance page attempts to reorganize the wiki, which has accumulated many outdated pages.
License and Copyright. Contributions to the Sage wiki and to the Sage documentation are licensed under the Creative Commons 3.0 BY-SA license. By contributing, you agree to place your contribution under that license.