Differences between revisions 3 and 147 (spanning 144 versions)
Revision 3 as of 2011-08-17 08:45:56
Size: 1931
Editor: jakemarino
Comment:
Revision 147 as of 2023-08-30 11:49:08
Size: 4305
Editor: tmonteil
Comment:
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
Before his entrance into politics, the name of Coriolanus evoked awe. His battlefield accomplishments showed him as a man of great bravery - something which we can learn and integrate into our job interview tips. Since the citizens knew little about him, all kinds of legends became attached to his name. The moment he appeared before the Roman citizens, however, and spoke his mind, all that grandeur and mystery vanished. He bragged and blustered like a common soldier. He insulted and slandered people, as if he felt threatened and insecure. Suddenly he was not at all what the people had imagined. The discrepancy between the legend and the reality proved immensely disappointing to those who wanted to believe in their hero. The more Coriolanus said, the less powerful he appeared - a person who cannot control his words shows that he cannot control himself, and is unworthy of respect. When it comes to your interview, remember this piece of job interview advice - don't oversell yourself, and know when to stop talking and let the other side have their say. = SageMath Wiki =
Line 3: Line 3:
Had Coriolanus listened to his mentor's job interview advice and said less, the people would never have had cause to be offended by him, would never have known his true feelings. He would have maintained his powerful aura, would certainly have been elected consul, and would have been able to accomplish his antidemocratic goals. But the human tongue is a beast that few can master. It strains constantly to break out of its cage, and if it is not tamed, it will run wild and cause you grief. Power cannot accrue to those who squander their treasure of words. This is a wiki for the [[https://www.sagemath.org|Sage - Mathematics Software System]] project. There are other [[ThingsCalledSage]].
Line 5: Line 5:
Oysters open completely when the moon is full; and when the crab sees one it throws a piece of stone or seaweed into it and the oyster cannot close again so that it serves the crab for meat. Such is the fate of him who opens his mouth too much and thereby puts himself at the mercy of the listener. If you want to '''edit the wiki''' or '''change your password''', do not hesitate to request an account by sending an email at [email protected]

There is another [[https://github.com/sagemath/sage/wiki|Sage Wiki on GitHub]].

||<tablestyle="font-size: 0.8em;">||<#F7819F>❤ || You can help by becoming a [[https://github.com/sponsors/sagemath|sponsor]]||


||<tablestyle="font-size: 0.8em;">||<#74DF00>Information || Since version 9.0, Sage is using '''Python 3'''. See [[Python3-Switch]] for more information.||

<<TableOfContents>>

= 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.

== Google Summer of Code ==

 * [[GSoC|Google Summer of Code]]

== 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

= People =
The most up-to date list of Sage developers is on our [[https://www.sagemath.org/development-map.html|Sage developer map]]

Some people still maintain their [[https://wiki.sagemath.org/CategoryHomepage|wiki homepages]].

<<Anchor(messagingsites)>>
= Mailing Lists / Chat Rooms =

The main active mailing lists are [[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]]; see [[https://www.sagemath.org/development-groups.html |complete list of lists]].

[[https://zulip.sagemath.org | Zulip]] group chat server for realtime collaboration on Sage (like Slack). Fairly low-activity.

!SageMath has a presence on some [[Social Networks]].

= Development =

!SageMath development has moved to our [[https://github.com/sagemath/sage|GitHub repository sagemath/sage]].

Release notes (higher level than change logs) are collaboratively prepared at [[ReleaseTours]].

= Special Discussion Pages =

 * [[Coding_Theory|Coding Theory in Sage]]
 * [[Python3-compatible code|Writing Python 3 compatible code]]
 * [[OptiPolyGeom|Optimization and Polyhedral Geometry in Sage]]

= Features and Packages =

 * [[http://www.sagemath.org/tour.html|sagemath.org: SageMath Feature Tour]]
 * [[SageMathExternalPackages|Packages included with SageMath and external packages]]
 * [[Interfaces|Sage wiki: SageMath interfaces to and from other software]]

== Demonstrations of Graphical Capabilities ==
 * [[art|Art - posters, banners, etc]]
 * [[interact|Interact Demos]]
 * [[interactive|Interactive Visualization]]
 * [[K3D-tools|K3D-jupyter 3D visualisation in jupyter notebook]]

= 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; a !GitHub account cannot be used for this. 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. 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. [[https://github.com/sagemath/sage/issues/33725|Pages related to development are being transferred to the Sage Wiki on GitHub or merged in our developer guide.]]

'''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 a wiki for the Sage - Mathematics Software System project. There are other ThingsCalledSage.

If you want to edit the wiki or change your password, do not hesitate to request an account by sending an email at [email protected]

There is another Sage Wiki on GitHub.

You can help by becoming a sponsor

Information

Since version 9.0, Sage is using Python 3. See Python3-Switch for more information.

SageDays, Sage Workshops, other activities

Past and future Workshops

  • Upcoming Workshops

  • All Workshops, including past and future Sage Days, Bug Days, Doc Days, Review Days, Education Days, and some other Sage-related events.

Google Summer of Code

Hosting a workshop

People

The most up-to date list of Sage developers is on our Sage developer map

Some people still maintain their wiki homepages.

Mailing Lists / Chat Rooms

The main active mailing lists are sage-support, sage-devel, sage-release; see complete list of lists.

Zulip group chat server for realtime collaboration on Sage (like Slack). Fairly low-activity.

SageMath has a presence on some Social Networks.

Development

SageMath development has moved to our GitHub repository sagemath/sage.

Release notes (higher level than change logs) are collaboratively prepared at ReleaseTours.

Special Discussion Pages

Features and Packages

Demonstrations of Graphical Capabilities

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; a GitHub account cannot be used for this. 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. 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. Pages related to development are being transferred to the Sage Wiki on GitHub or merged in our developer guide.

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.

SageWiki (last edited 2023-08-30 11:49:08 by tmonteil)