Differences between revisions 8 and 9
Revision 8 as of 2019-01-08 11:16:41
Size: 1575
Editor: chapoton
Comment: delete jsage
Revision 9 as of 2022-04-05 01:57:47
Size: 0
Editor: mkoeppe
Comment: outdated
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
A package that should become part of the core of Sage must meet the following requirements:

== License ==
 * GPL version 2+ compatible license. (This will be publicly revisited around Jan 15, 2009.)

== Build Support ==
The package must build on our supported architectures and compilers [and intended port targets]:

 * Linux: x86, x86_64, Itanium, ppc, ppc64, Sparc (gcc 3.4-4.3)
 * Apple Mac OS X: ppc, ppc64, x86, x86-64 (Xcode 2.5+)
 * Microsoft Windows: x86, x86_64 MSVC 2005/Intel Fortran [MinGW or Cygwin support is insufficient!]
 * Solaris 10: Sparc, x86, x86_64 (Sun Forte 12)

Remarks:

 * Some Sage developers are willing to help you port to OSX, Solaris and Windows. But this is no guarantee and you or your project are expected to do the heavy lifting and also support those ports upstream if there is no Sage developer who is willing to share the burden.

Potential future ports:

 * FreeBSD: x86, x86-64
 * OpenBSD: x86, x86-64
 * HPUX: Itanium
 * AIX: PPC64
 * ARM: OSX

== Quality ==

The package should be "better" than anything else (that passes the two above criteria) and an argument should be made for this. The comparison should be made to both Python and other software. Criteria in passing the quality test include:

 * Speed
 * Documentation
 * Usability
 * Memory leaks
 * Maintainable
 * Reasonable build time, size, dependencies

== Voting ==
 * A certain number of sage-devel +1 votes (and sage-support votes)
 * Every spkg *must* be available as an optional spkg until at least 5 people download it.