JSAGE

JSAGE Publication Procedure

1. Submit your software

  • All code submissions must be licensed under OSI approved open source license. No exceptions will be made.
  • Submitting additions to the SAGE library: Submit your code to one of the editors via email as a Mercurial patch bundle or plain text Mercurial patch. In some cases code submitted not as a bundle will be accepted.
  • Submitting new software packages: This is more complicated; please contact one of the editors and describe the software you would like to submit to SAGE.

2. Feedback

  • A referee (either one of the editors or someone chosen by an editor) will review your work. This is not anonymous. The referee will provide feedback about the quality of the submission:
    • Does it make sense for publication in JSAGE?
    • Is it sufficiently well documented?
    • Is the theory on which the algorithms depend solid.
    • Is the source code comprehensible and maintainable?
    • Are copyright statements and authorship clearly stated in the code.

3. Response

  • If the referee decides that the submission is suitable for publication in JSAGE, the author and referee work together to make all necessary changes.

4. Publication

The final decision for all software submissions to SAGE rests with the managing editor.
  • When the referee/response process is complete, all relevant patches are made available to the managing editor. These patches should include author statements and mention any referees or editors that were involved in refereeing the submission.
  • When possible, we strongly encourage JSAGE authors to also contribute corresponding mathematical research articles to these endorsed journals.
  • Citing your paper. For example
     Carl Witty, {\em Implementation of Interval Arithmetic} (500 lines of
     code), JSAGE, Feb 2007, available since SAGE version 2.1,
     \url{http://www.sagemath.org}.
    

See also what the twisted developers do.