Differences between revisions 45 and 56 (spanning 11 versions)
Revision 45 as of 2009-02-19 23:47:32
Size: 3237
Comment:
Revision 56 as of 2009-03-01 17:41:47
Size: 3570
Comment:
Deletions are marked like this. Additions are marked like this.
Line 5: Line 5:
Line 6: Line 7:
== NEWS ==
Line 7: Line 9:
=== NEWS: July 25-29: *-Combinat 2009 ===  * July 25-29: *-Combinat 2009
Line 9: Line 11:
We will hold an International Sage Workshop on [[http:/combinat/FPSAC09|Free and Practical Software for Algebraic Combinatorics]] at RISC, Linz, Austria, right after [[http://www.risc.uni-linz.ac.at/about/conferences/fpsac2009/|FPSAC'09]].    We will hold an International Sage Workshop on [[http:/combinat/FPSAC09|Free and Practical Software for Algebraic Combinatorics]] at RISC, Linz, Austria, right after [[http://www.risc.uni-linz.ac.at/about/conferences/fpsac2009/|FPSAC'09]].
Line 11: Line 13:
=== NEWS: 2009-02-20: Submission of a software demonstration request for FPSAC 2009 ===
[[attachment:.2009-07-20-FPSAC.tex|Source]] / [[attachment:2009-07-20-FPSAC.pdf|PDF]]
 * 2009-02-20: Submission of a software demonstration request for FPSAC 2009 [[attachment:2009-07-20-FPSAC.pdf|PDF]], [[attachment:.2009-07-20-FPSAC.tex|LaTeX Source]] [[attachment:2009-07-20-FPSAC.bbl|LaTeX bibliography]]
Line 14: Line 15:
=== NEWS: January 26-30: Sage-Combinat workshop in Orsay ===
Line 16: Line 16:
We held [[http:/combinat/SageCombinatWorkshopOrsay|Sage-Combinat Workshop]] in Orsay on the last week of January 2009.  * January 26-30: [[http:/combinat/SageCombinatWorkshopOrsay|Sage-Combinat Workshop in Orsay]]
Line 18: Line 18:
=== NEWS: 2008-06-19: MuPAD-Combinat join forces with Sage ===  * 2008-06-19: MuPAD-Combinat join forces with Sage
Line 20: Line 20:
Sage-combinat was born as a partial port of [[http://mupad-combinat.sf.net|MuPAD-Combinat]]. After months of discussions and experiments, an enthusiastic consensus emerged in the MuPAD-Combinat community to join Sage. Sage-combinat henceforth became the natural successor of {{{MuPAD-Combinat}}}.     Sage-combinat was born as a partial port of [[http://mupad-combinat.sf.net|MuPAD-Combinat]]. After months of discussions and experiments, an enthusiastic consensus emerged in the MuPAD-Combinat community to join Sage. Sage-combinat henceforth became the natural successor of {{{MuPAD-Combinat}}}.
Line 22: Line 22:
The transition is going to be a massive investment: seven years of hard work to port over! However a lot of experience was gained since 2000, and most of the design is now pretty clear. By sharing the work the transition will hopefuly be relatively quick.    The transition is going to be a massive investment: seven years of hard work to port over! However a lot of experience was gained since 2000, and most of the design is now pretty clear. By sharing the work the transition will hopefuly be relatively quick.
Line 24: Line 24:
See the [[http:/combinat/RoadMap|road map and current status]] of the port.    See the [[http:/combinat/RoadMap|road map and current status]] of the port.
Line 28: Line 28:
=== Who are we? === == Who are we? ==
Line 30: Line 30:
* [[http:/combinat/Contributors|Contributors]]  * [[http:/combinat/Contributors|Contributors]]
Line 32: Line 32:
* [[http:/combinat/Institutions|Institutions and sponsors]]  * [[http:/combinat/Institutions|Institutions and sponsors]]
Line 34: Line 34:
=== How to participate and contribute ===
* Join our mailing list: http://groups.google.com/group/sage-combinat-devel.
----
Line 37: Line 36:
* Post bug reports, suggestion, patches on the [[http://sagetrac.org/sage_trac/milestone/sage-combinat|Sage-Combinat trac server]] or on the [[http://groups.google.com/group/sage-combinat-devel|mailing list]]. == How to participate and contribute ==
Line 39: Line 38:
* Cite Sage-Combinat when you use it for research publications (TODO: provide a standard citation here).
Line 41: Line 39:
* The collection of patches is managed using a [[http://sage.math.washington.edu:2144/|patch server]] (mercurial queues). Use it to try out the latest experimental features, or contribute your own patches! === Communication ===
 * Join our mailing list: http://groups.google.com/group/sage-combinat-devel.
Line 43: Line 42:
 * [[http:/combinat/MercurialStepByStep|Step by step tutorial]] (in particular, how to '''download Sage-Combinat''')  * Post bug reports, suggestions, patches on the [[http://sagetrac.org/sage_trac/milestone/sage-combinat|Sage-Combinat trac server]] or on the [[http://groups.google.com/group/sage-combinat-devel|mailing list]].
Line 45: Line 44:
 * [[http:/combinat/Mercurial|Technical background on the Sage-Combinat patch server (messy)]].  * Cite Sage-Combinat when you use it for research publications (TODO: provide a standard citation here).
Line 47: Line 46:
* Have a look and participate to [[http:/combinat/DesignDiscussion|design discussions]]. === Code ===
Line 49: Line 48:
* Contribute to the list of [[http:/combinat/Weirdness|quirks and weirdness issues]] in the {{{*-Combinat}}} design.  * The collection of patches is managed using a [[http://combinat.sagemath.org/patches/|patch server]] (mercurial queues). Use it to try out the latest experimental features, or contribute your own patches! (You may still need to access to the [[http://sage.math.washington.edu:2144/|old patch server]])

 * Please read the [[http:/combinat/MercurialStepByStep|Step by step tutorial]] (in particular, how to '''download Sage-Combinat''')

 * For the curious: [[http:/combinat/Mercurial|Technical background on the Sage-Combinat patch server (messy)]].

=== Design ===

 * Have a look and participate to [[http:/combinat/DesignDiscussion|design discussions]].

 * Contribute to the list of [[http:/combinat/Weirdness|quirks and weirdness issues]] in the {{{*-Combinat}}} design.

=== Documentation ===

 * From sage 3.4 on, the documentation system is based on ReST/Sphinx. Here are some [[HelpOnTheDoc|help about the new doc system]]

Sage-combinat

Sage-combinat is a collection of experimental patches (i.e. extensions) on top of Sage, developed by a community in algebraic combinatorics. Its main purpose is to improve Sage as an extensible toolbox for computer exploration, and foster code sharing between researchers in this area. The intent is that most of those patches eventually will get integrated into sage as soon as they are mature enough, with a typical short life-cycle of a few weeks. In other words: just install Sage, and you will benefit from all the Sage-combinat development, except for the latest bleeding edge features.


NEWS

  • July 25-29: *-Combinat 2009
  • 2009-02-20: Submission of a software demonstration request for FPSAC 2009 PDF, LaTeX Source LaTeX bibliography

  • January 26-30: Sage-Combinat Workshop in Orsay

  • 2008-06-19: MuPAD-Combinat join forces with Sage
    • Sage-combinat was born as a partial port of MuPAD-Combinat. After months of discussions and experiments, an enthusiastic consensus emerged in the MuPAD-Combinat community to join Sage. Sage-combinat henceforth became the natural successor of MuPAD-Combinat.

    • The transition is going to be a massive investment: seven years of hard work to port over! However a lot of experience was gained since 2000, and most of the design is now pretty clear. By sharing the work the transition will hopefuly be relatively quick.

      See the road map and current status of the port.


Who are we?


How to participate and contribute

Communication

Code

Design

Documentation

combinat (last edited 2022-04-05 01:35:07 by mkoeppe)