Changes between Version 25 and Version 26 of WikiStart


Ignore:
Timestamp:
04/01/11 15:08:41 (10 years ago)
Author:
dlove
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • WikiStart

    v25 v26  
    44
    55The Son of Grid Engine is a community project to continue Sun's old
    6 [http://gridengine.sunsource.net gridengine]
    7 [http://www.gnu.org/philosophy/free-sw.html free software] project,
    8 now that Oracle have taken it over, are not contributing their source, and
    9 may close down the Sunsource web site.
     6gridengine
     7[http://www.gnu.org/philosophy/free-sw.html free software] project
     8that used to live at http://gridengine.sunsource.net,
     9now that Oracle have shut down the site and are not contributing
     10code.  It will maintain copies of as much as possible/useful from old
     11site.  Currently we do not have the old mail archives online, though
     12articles from the old gridengine-users list from the last five years
     13or so will be available soon, and Oracle have promised to donate
     14artifacts from the old site, so we should be able to get complete
     15copies of everything.
    1016
    1117The idea is to encourage sharing, in the spirit of the original
     
    1420ideas for improvement, especially any ideas for encouraging contribution.
    1521
    16 Pending adding to this site, you can look at the
    17 [http://gridengine.sunsource.net old gridengine site]
    18 for extra documentation etc. as long as it's there.  Currently anything
    19 for the gridengine v6.2u5 release will apply to this effort.  (The
     22Currently any information you find
     23for the gridengine v6.2u5 release will apply to this effort, including the
    2024[http://wikis.sun.com/display/gridengine62u5/Home v6.2u5 wiki documentation]
    21 isn't too easily findable from there.)
    22 
    23 This wiki isn't currently editable, but should be eventually.
     25and pointers therefrom, including the
     26[http://gridengine.info gridengine.info site] and its wiki.  There may
     27eventually also be useful info at the
     28[http://forums.oracle.com/forums/forum.jspa?forumID=859 Oracle Grid Engine Forum].
     29You should note its
     30[http://www.oracle.com/html/terms.html terms of use] before posting
     31there; they include even relinquishing
     32[https://secure.wikimedia.org/wikipedia/en/wiki/Moral_rights_%28copyright_law%29 moral rights].
     33
     34This wiki isn't currently generally editable, but will be when spam
     35protection is in place.  If you're a known past contributor to
     36gridengine and would like to help, please [#Contact get in touch] for access.
    2437
    2538== News ==
     
    2740* 2010-11-15: URLs of the form `http://arc.liv.ac.uk/repos/hg/`//repo// and `http://arc.liv.ac.uk/repos/git/`//repo// now work for hg and git respectively.
    2841
    29 * 2010-11-14: You can now access the repos with Mercurial (`hg`) at the same URLs as with `darcs`, e.g. {{{hg clone http://arc.liv.ac.uk/repos/darcs/sge/}}}.  (They should probably be aliased to avoid confusion.)  You can also pull with `git`, but the relevant URL is the darcs one with `/.git` appended, e.g. {{{git clone http://arc.liv.ac.uk/repos/darcs/sge/.git}}}.  Servers are not currently available for hg or git, so pulling may be relatively slow; also mirroring currently isn't automatic, so the hg and git repos may be somewhat out-of-date.  Also note that pulls with git or hg leave scripts not executablesee the amended build instructions.
     42* 2010-11-14: You can now access the repos with Mercurial (`hg`) at the same URLs as with `darcs`, e.g. {{{hg clone http://arc.liv.ac.uk/repos/darcs/sge/}}}.  (They should probably be aliased to avoid confusion.)  You can also pull with `git`, but the relevant URL is the darcs one with `/.git` appended, e.g. {{{git clone http://arc.liv.ac.uk/repos/darcs/sge/.git}}}.  Servers are not currently available for hg or git, so pulling may be relatively slow; also mirroring currently isn't automatic, so the hg and git repos may be somewhat out-of-date.  Also note that pulls with git or hg leave scripts not executable — see the amended build instructions.
    3043
    3144* 2010-11-14: Most jar files have been expunged since several from the sunsource repository are copyleft, and can't be distributed as-were.  Since this involved re-writing history in the `arco` and `nbgui` repos, if you pulled from them, you'll need to do it again, unfortnuately.
     
    3750There are several distinct source [source:/ repositories] converted
    3851from the last Sunsource CVS versions of the same name.  The `sge` one
    39 actually only goes back to the `V60` tagi.e. not including
    40 version 5.3and also has some re-buildable files removed, to keep it a bit more
     52actually only goes back to the `V60` tag — i.e. not including
     53version 5.3 — and also has some re-buildable files removed, to keep it a bit more
    4154manageable.  Only the repository trunk was converted in each
    4255case, but see [#History History].
     
    5770The repositories are maintained under
    5871[http://darcs.net/ darcs],[[FootNote(Darcs is a nice distributed version control system, but doesn't currently scale so well with a repository of this size and age.  It's fine for looking at the change history and recording new changes, but currently slow at producing diffs for previous changes, for instance.)]]
    59 but are mirrored to Mercurial and gitsee [#News News].
     72but are mirrored to Mercurial and git — see [#News News].
    6073To clone the sge repo, get
    61 a [http://wiki.darcs.net/Binaries recent version of darcs]at least
    62 version 2 and preferably 2.5and then run
     74a [http://wiki.darcs.net/Binaries recent version of darcs] — at least
     75version 2 and preferably 2.5 — and then run
    6376{{{
    6477darcs get --lazy --set-scripts-executable http://arc.liv.ac.uk/repos/darcs/sge
     
    8396Building the source is currently rather a pain,
    8497which is something to improve urgently.  With appropriate development
    85 packages installed—they need documenting—it should build on GNU/Linux
     98packages installed — they need documenting — it should build on GNU/Linux
    8699in Bourne shell with something like this:
    87100{{{
     
    106119[source:/sge/source/README.aimk README.aimk] in the source tree, and
    107120ignore any inappropriate references to the sunsource web site, at
    108 leastthose documents need review in the absence of a better build
     121least — those documents need review in the absence of a better build
    109122system.
    110123
     
    145158== History ==
    146159
    147 The [http://gridengine.sunsource.net/source/browse/gridengine/ original CVS repo]
    148 is currently still available if you need more history, and has been
    149 mirrored in case it disappears, along with copies of items in the
    150 [http://gridengine.sunsource.net/servlets/ProjectIssues issue-tracker]
    151 (‘Issuezilla’), sometimes referred to as ‘IZ’, and the general
    152 material on the sunsource web site.  The active issues have been transferred
     160As well as the partial gridengine-users mail archive the original CVS
     161repositories have been mirrored completely, along with copies of all
     162the items in the old issue tracker — ‘Issuezilla’, sometimes referred to
     163as ‘IZ’, and the general material on the sunsource web site.  They
     164will be put online eventually, partly pending asking for the original
     165data from Oracle, to minimize possible data loss in the process.
     166
     167However, the active IZ issues have been transferred
    153168to the [ticket: issue tracker] here, though some have somewhat suffered in the
    154 process; I only discovered after the fact that they were
     169process; unfortunately I only discovered after the fact that they were
    155170accessible as an XML dump.
    156 If the Sunsource mailing list archive disappears, you can still use
    157 at least [http://gridengine.markmail.org MarkMail] and
    158 [http://dir.gmane.org/gmane.comp.clustering.gridengine.users Gmane],
    159 but it would be good if we could stash a dump of the email history too
    160 somehow.
    161 
    162 == Copyright ==
    163 
    164 Concerning copying the Sunsource material,
    165 see the [http://www.sunsource.net/TUPPCP.html Sunsource terms].
     171[http://gridengine.markmail.org MarkMail] appears to have complete
     172archives of the gridengine mail lists currently online, though with a
     173less than ideal interface, and
     174[http://dir.gmane.org/gmane.comp.clustering.gridengine.users Gmane]
     175has gridengine-users from 2006 onwards via HTTP and NTP.
     176
     177== Copyright and Naming ==
     178
     179The Sunsource material has been copied according to the original
     180Sunsource terms (online copy pending).
    166181Material here has an explicit or implicit copyright under the same
    167 terms, i.e. code with no explicit terms is covered by a BSD licence,
     182terms, i.e. code with no explicit terms is covered by the SISSL,
    168183and other contributions have a permissive licence.  Any explicit
    169 licence must be under a
    170 [http://www.gnu.org/philosophy/free-sw.html free software] licence
    171 compatible with any material it modifies.  The source code is
     184licence must be a
     185[http://www.gnu.org/philosophy/free-sw.html free software] or free
     186documentation one,
     187compatible with any material it modifies.  The original source code is
    172188obviously under the original (rather odd!)
    173 [http://gridengine.sunsource.net/Gridengine_SISSL_license.html SISSL licence]
     189[http://arc.liv.ac.uk/repos/darcs/sge/LICENCES/SISSL SISSL],
    174190except for some essentially ‘third party’ stuff like `qmake`.
     191
     192The appendix to the SISSL requires a conformance test to use names
     193like ‘Grid Engine’ for a modified version.  There aren't any known
     194deviations in the current source from the behaviour of the
     195originally-downloaded Grid Engine source, apart from a re-numbering of
     196the GDI protocol to reflect a change in that.  Before an actual
     197release, it will be necessary either to get Oracle's blessing or to
     198run the test suite against (probably) the 6.2u5 release.  Changes to
     199the GDI, or anything else that breaks the tests, will require a
     200compatibility mode controlled by an environment variable.
    175201
    176202== Related ==