|
Size: 1955
Comment:
|
Size: 7376
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. | = Sage 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 the wiki for the [[http://www.sagemath.org|Sage - Mathematics Software System]] project. This 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. |
| 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. ---- CategoryHomepage |
<<TableOfContents>> = SageDays and Sage Workshops = <<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. == 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 [[http://trac.sagemath.org/sage_trac/wiki#AccountNamesMappedtoRealNames|list of developers on the Sage trac wiki]]. [[http://www.sagemath.org/development-map.html|Overview of (many) Sage developers on a world map]] <<Anchor(messagingsites)>> = Mailing Lists / Chat Rooms = * [[http://groups.google.com/group/sage-support|sage-support]] * [[http://groups.google.com/group/sage-devel|sage-devel]] * [[http://groups.google.com/group/sage-release|sage-release]] * [[http://groups.google.com/group/sage-announce|sage-announcements]] * [[http://groups.google.com/group/sage-edu|sage-edu]] for teaching using Sage * [[http://groups.google.com/group/sage-dsageng|sage-dsageng]] for Distributed and Parallel Sage * [[http://groups.google.com/group/sage-finance|sage-finance]] for finance * [[http://groups.google.com/group/sage-coding-theory|sage-coding-theory]] for coding theory * [[http://groups.google.com/group/sage-nt|sage-nt]] for number theory * [[http://groups.google.com/group/sage-combinat-devel|sage-combinat-devel]] * 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]]. = Development = Development is handled using "tickets" on the [[http://trac.sagemath.org/sage_trac/|trac server]]. The main developer doc is the [[http://www.sagemath.org/doc/developer/ | Developers' Guide]]. The [[devel | development wiki]] also contain some (currently out-of-date) information on Sage development. See also this recent [[CodeSharingWorkflow|discussion on SageMath development workflow]]. = Special Discussion Pages = * [[Coding_Theory|Coding Theory in Sage]] * [[Debate/Collective infrastructure management]] * [[CodeSharingWorkflow|On development models for sharing (experimental) code]] * [[Python3-compatible code|Writing Python 3 compatible code]] see also [[PortingToPython3|matplotlib experience Porting to Python 3]] = Demonstrations of Graphical Capabilities (mostly out-of-date) = * [[art|Art - posters, banners, etc]] * [[interact|Interact Demos]] * [[http://tug.ctan.org/pkg/sagetex|SageTeX - Put some sage into your TeX]] * [[K3D-tools|K3D-jupyter 3D visualisation in jupyter notebook]] = Packages = These lists are possibly out-of-date. Use the listed Sage command for the newest information: * [[standard_packages_available_for_SAGE|Standard packages available for Sage]] (`./sage -standard`) * [[optional_packages_available_for_SAGE|Optional packages available for Sage]] (`./sage -optional`) * [[experimental_packages_available_for_SAGE|Experimental packages available for Sage]] (`./sage -experimenta`) * [[Sage_Spkg_Tracking|SPKG changelog and descriptions]] = ''OUT OF DATE! NEEDS UPDATED!'' * [[Tips]] * [[UsingSquashFS]] * [[SagemathLive]] * [[Send corrected worksheets to each student]] * [[SageAppliance|Working with the Sage Virtual Machine (VirtualBox)]] (See also: [[SageApplianceV4|previous version of the Sage VM]]) * [[InstallingGapPackages|Installing GAP packages]] * [[faq|Sage FAQ - Frequently Asked Questions (Out-of-date)]] * [[SAGE_in_the_News|Sage In the News and Blogs (Out-of-date)]] * [[sagenb|List of institutions and projects using Sage]] * [[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]] * [[GSoC|Google Summer of Code]] * [[SageLiveUSB|Inventory Live USB running sage]] * [[GrantEurope|asking for a european grant]] * [[IpythonNotebook|What is missing to use ipython notebook ?]] * [[Infrastructure]] * [[Fight spam on asksage]] * [[Classify old-style packages]] * [[SageAppliance|Using Sage within virtualbox]] * [[Distribution]] * [[Social Networks]] * [[CommunityManagement|Collection of stories on Open Source community management]] Alphabetical listing of things to do (out-of-date and general organise) - mrennekamp * [[aix]] which talks of porting sage to AIX * All SEP's (Sage Enhancement Proposal) were / need to be removed, as to keep information on Trac * [[ams]] booths at AMS / MAA meetings ('08 and '09) and an '09 special session * [[art]] duplicates many things, but need to put ALL SAGE ARTWORK EVER MADE into this wiki page ... also broken links * [[Tips/bash-completion]] one of many [[Tips]], so not sure what to do with it * [[BLAD]] BLAD integration in Sage 'This wiki page is about the integration of the Bibliothèques Lilloises d'Algèbre Différentielle in Sage.' 2011 * [[bruhat]] project from 2008, S sub n under bruhat order * take all Bugdays and put each into ONE page * [[buildbot]] -- merge subpages * [[bug]] -- add content to describe Bug Days in general * [[cando]] documents "What Sage Can Do" -- decide what to do with it. current version is from 2008. * (all) Categories - eg [[CategoryFrameworkAndCleanup]] and [[DsageNg]] * [[Chile]] - tiny page for "events in Chile" * [[Classify old-style packages]] is a to-do list for the wiki ... I'm (mrennekamp) sure that this is duplicated somewhere * [[CodeOfConduct]] not sure why there; would like to see go to official documentation * [[CodeSharingWorkflow]] N. Thiery's musings on workflow development. Nothing wrong, but would help to collaborate. * [[coercion]] = About this wiki = '''Editing the wiki.''' Page editing uses the MoinMoin syntax. To edit the wiki, log in using your [[http://trac.sagemath.org/sage_trac/|sage-trac]] account. Getting an account involves convincing a human by email that you not a spammer. '''License and Copyright.''' Contributions to the [[http://www.sagemath.org/|Sage]] wiki and to the [[http://doc.sagemath.org|Sage documentation]] are licensed under the [[http://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. |
Sage Wiki
This is the wiki for the Sage - Mathematics Software System project. This 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.
Contents
SageDays and Sage Workshops
Past and future Workshops
- Upcoming Workshops
Sage Days 127 -- TU Vienna, Austria (February 22-25, 2025); theme: using SageMath for Algebra, Combinatorics, and Probability
Sage Days 128 — combinatorics, number theory, dynamical systems and geometry, February 10-14, 2025, Le Teich, near Bordeaux, France
All Workshops, including past and future Sage Days, Bug Days, Doc Days, Review Days, Education Days, and some other Sage-related events.
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-edu for teaching using Sage
sage-dsageng for Distributed and Parallel Sage
sage-finance for finance
sage-coding-theory for coding theory
sage-nt for number theory
IRC channel: #sagemath on freenode (chat.freenode.net)
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.
The development wiki also contain some (currently out-of-date) information on Sage development. See also this recent discussion on SageMath development workflow.
Special Discussion Pages
Demonstrations of Graphical Capabilities (mostly out-of-date)
Packages
These lists are possibly out-of-date. Use the listed Sage command for the newest information:
Standard packages available for Sage (./sage -standard)
Optional packages available for Sage (./sage -optional)
Experimental packages available for Sage (./sage -experimenta)
= OUT OF DATE! NEEDS UPDATED!
Working with the Sage Virtual Machine (VirtualBox) (See also: previous version of the Sage VM)
Sage for High school usage (see here for development page)
Alphabetical listing of things to do (out-of-date and general organise) - mrennekamp
aix which talks of porting sage to AIX
- All SEP's (Sage Enhancement Proposal) were / need to be removed, as to keep information on Trac
ams booths at AMS / MAA meetings ('08 and '09) and an '09 special session
art duplicates many things, but need to put ALL SAGE ARTWORK EVER MADE into this wiki page ... also broken links
Tips/bash-completion one of many Tips, so not sure what to do with it
BLAD BLAD integration in Sage 'This wiki page is about the integration of the Bibliothèques Lilloises d'Algèbre Différentielle in Sage.' 2011
bruhat project from 2008, S sub n under bruhat order
- take all Bugdays and put each into ONE page
buildbot -- merge subpages
bug -- add content to describe Bug Days in general
cando documents "What Sage Can Do" -- decide what to do with it. current version is from 2008.
(all) Categories - eg CategoryFrameworkAndCleanup and DsageNg
Chile - tiny page for "events in Chile"
Classify old-style packages is a to-do list for the wiki ... I'm (mrennekamp) sure that this is duplicated somewhere
CodeOfConduct not sure why there; would like to see go to official documentation
CodeSharingWorkflow N. Thiery's musings on workflow development. Nothing wrong, but would help to collaborate.
About this wiki
Editing the wiki. Page editing uses the MoinMoin syntax. To edit the wiki, log in using your sage-trac account. Getting an account involves convincing a human by email that you not a spammer.
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.