Changes between Version 12 and Version 13 of WikiStart


Ignore:
Timestamp:
03/11/10 17:01:22 (10 years ago)
Author:
dlove
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • WikiStart

    v12 v13  
    1010
    1111The idea is to encourage sharing, in the spirit of the original
    12 project and informed by long experience of free software projects
    13 and scientific computing support.  Please contribute and share any
    14 ideas for improvement, especially ideas for encouraging contributions.
     12project, and informed by long experience of free software projects
     13and scientific computing support.  Please contribute, and share code or
     14ideas for improvement, especially any ideas for encouraging contribution.
    1515
    16 As long as it's there, you can look at the
     16Pending adding to this site, you can look at the
    1717[http://gridengine.sunsource.net old gridengine site]
    18 for extra documentation etc. Currently anything
     18for extra documentation etc. as long as it's there. Currently anything
    1919for the gridengine v6.2u5 release will apply to this effort.  (The
    2020[http://wikis.sun.com/display/gridengine62u5/Home v6.2u5 wiki documentation]
    2121isn't too easily findable from there.)
    2222
    23 Note that this wiki isn't currently editable, but should be eventually.
     23This wiki isn't currently editable, but should be eventually.
    2424
    2525== !Repositories/Source ==
    … …  
    2929actually only goes back to the `V60` tag—i.e. not including
    3030version 5.3—and also has some re-buildable files removed, to keep it a bit more
    31 manageable.  Note that only the trunk of repository trunk was converted.
     31manageable.  Only the trunk of repository trunk was converted in each
     32case, but see [#history History].
    3233
    33 These are currently just available under [http://darcs.net/ darcs], but
    34 are intended to be mirrored eventually, at least to Mercurial.  Darcs is a
    35 nice distributed version control system, but doesn't currently scale
    36 so well with a repository of this size and age.  It's fine for
    37 looking at the change history and recording new changes, but currently
    38 slow at producing diffs for previous changes, for instance.
     34Also, some files are omitted from those in the head of the sunsource `sge` repo
     35as follows;  any others missing  are probably a mistake unless they're noted in
     36the change history:
     37* `www` top-level directory:  Not really relevant for a distribution, although some of it can probably be converted into useful documentation for distribution later;
     38* `review` top-level directory:  Just a set of tick sheets for Sun internal use;
     39* `gep` top-level directory:  The portal, which may not actually be functional now, and is anyway based on a proprietary server;
     40* HTML documentation: This is either rebuild-able (like Javadocs) and/or probably not useful outside the gridengine web site (like HTML-ized man pages).
     41
     42The repositories are currently just available under
     43[http://darcs.net/ darcs], but are intended to be mirrored eventually,
     44at least to Mercurial.  (Darcs is a nice distributed version control
     45system, but doesn't currently scale so well with a repository of this
     46size and age.  It's fine for looking at the change history and
     47recording new changes, but currently slow at producing diffs for
     48previous changes, for instance.)
    3949
    4050To clone the sge repo, get
    4151a [http://wiki.darcs.net/Binaries recent version of darcs]—at least
    42 version 2 and preferably 2.4—and then run
     52version 2 and preferably 2.5—and then run
    4353{{{
    4454darcs get --lazy --set-scripts-executable http://arc.liv.ac.uk/repos/darcs/sge
    … …  
    5060The head of the source tree is actually available directly via the
    5161`Repository URL` links for each repository, and if you
    52 really need all the current source without darcs, this should do the trick:
     62really need all the current source without a darcs client, this should
     63do the trick:
    5364{{{
    5465wget -e robots=off -r -X /repos/darcs/sge/_darcs -np http://arc.liv.ac.uk/repos/darcs/sge
    5566find arc.liv.ac.uk/repos/darcs/ -name index.html\\?\* | xargs rm
    5667}}}
    57 
    58 The files omitted from those in the head of the sunsource `sge` repo are
    59 the following;  any others missing  are probably a mistake unless they're noted in
    60 the change history:
    61 * `www` top-level directory:  Not really relevant for a distribution, although some of it can probably be converted into useful documentation for distribution later;
    62 * `review` top-level directory:  Just a set of tick sheets for Sun internal use;
    63 * `gep` top-level directory:  The portal, which may not actually be functional now, and is anyway based on a proprietary server;
    64 * HTML documentation: This is either rebuild-able (like Javadocs) and/or probably not useful outside the gridengine web site (like HTML-ized man pages).
    6568
    6669== Building ==
    … …  
    9194== Bug reporting, patches, and mail lists ==
    9295
    93 There aren't currently any accessible mail lists associated with the
    94 project, but should be soon, and unfortunately you can't currently reply to
    95 any mail from the tracker, such as notifications of tickets.  You can
    96 create an account
     96There aren't yet any mail lists associated with this
     97project, but should be soon.  Also you can't currently reply to
     98any mail from the tracker, such as notification from the
     99tracker.  You can create an account
    97100to put tickets in the [ticket: issue tracker], or use the `tourist`
    98 account with `sge` as the password.  If you do use tourist, it may be useful
    99 to put a mail address in the report in case of queries.
     101account with `sge` as the password.  If you are a tourist, it may be useful
     102to put a mail address in the report for contact about it.
    100103
    101104It will eventually be possible to make bug reports by mail in the
    102105convenient, time-honoured fashion.
    103106
    104 The best way to send patches is to record them in your local darcs
     107The best way to send patches is to record them in a clone darcs
    105108repository and use `darcs send`.  Until arrangements are made for
    106109direct contributions, they will be pushed into the main repository by
    107110hand if they look reasonable.  Otherwise, you can attach normal
    108111patches to tickets or just mail (see [#contact Contact]) them, maybe
    109 even against the 6.2u5 source, if you have any already.
     112even against the 6.2u5 source, if you have them read-made.
    110113
    111114If you record changes with darcs, make the patch name a useful short
    … …  
    116119imported tickets have that reference.
    117120
    118 == History ==
     121== History == #history
    119122
    120 The original CVS repo is currently still
    121 available if you need more history, and has been mirrored in case it
    122 disappears, along with copies of items in the
     123The [http://gridengine.sunsource.net/source/browse/gridengine/ original CVS repo]
     124is currently still available if you need more history, and has been
     125mirrored in case it disappears, along with copies of items in the
    123126[http://gridengine.sunsource.net/servlets/ProjectIssues issue-tracker]
    124 (‘Issuezilla’) and the material on the sunsource
    125 web site.  The active issues have been transferred
    126 to the [ticket: issue tracker] here, but some have somewhat suffered in the
     127(‘Issuezilla’), sometimes referred to as ‘IZ’, and the general
     128material on the sunsource web site.  The active issues have been transferred
     129to the [ticket: issue tracker] here, though some have somewhat suffered in the
    127130process; I only discovered after the fact that they were
    128131accessible as an XML dump.
    … …  
    135138== Copyright ==
    136139
    137 If you have copyright concerns about copying the Sunsource material,
    138 note the [http://www.sunsource.net/TUPPCP.html Sunsource terms].
     140Concerning copying the Sunsource material,
     141see the [http://www.sunsource.net/TUPPCP.html Sunsource terms].
    139142Material here has an explicit or implicit copyright under the same
    140143terms, i.e. code with no explicit terms is covered by a BSD licence,
    … …  
    142145licence must be under a
    143146[http://www.gnu.org/philosophy/free-sw.html free software] licence
    144 that is compatible with any material it modifies.  The source code is
    145 obviously under the original
     147compatible with any material it modifies.  The source code is
     148obviously under the original (rather odd!)
    146149[http://gridengine.sunsource.net/Gridengine_SISSL_license.html SISSL licence]
    147150except for some essentially ‘third party’ stuff like `qmake`.
    … …  
    151154There's another project,
    152155[http://sourceforge.net/projects/gridscheduler/ Open Grid Scheduler],
     156or ‘gridscheduler’,
    153157which is also continuing work on gridengine but has
    154 different aims.  Unlike this one, it doesn't use a distributed
    155 revision control system, and doesn't include repository history from
     158different aims.  Unlike this one, its repository doesn't use a distributed
     159revision control system, and doesn't include history from
    156160before the gridengine v6.2u5 release, or the documentation.  It would
    157 be better if there was only one, but I want those things missing from
    158 gridscheduler (and more, like a bug-tracker that doesn't involve
    159 creating accounts);  I assume others will too, for ease of
     161be better if there was only one project, but this satisfies the need
     162for those things missing from OGS (and more, like a
     163bug-tracker that doesn't involve creating accounts), which should ease
    160164contributing.
    161165
    162 The `sge` source here is currently basically a considerable superset of
    163 gridscheduler.  It includes the changes from it, or close
     166The `sge` source here is currently a superset of
     167OGS's.  It includes the changes from it, or close
    164168equivalents, plus some important fixes for persistent or immediate crashes
    165 in some circumstances and other less important ones, as well as documentation.
    166 It's currently more likely to be broken than gridscheduler, though.
     169in some circumstances, and other less important changes, as well as the
     170man page documentation.
     171It is currently more unstable than OGS, but breakage should get
     172fixed, at least if it isn't inherited from the original code base.
    167173
    168174== Contact == #contact
    … …  
    170176In the current absence of mail lists,
    171177please send queries, contributions, &c to: Dave Love,
    172 `d.love(SGE)@liverpool.ac.uk`.  In case our spam-blocking
    173 appears to defeat you, I'm also `fx(SGE)@gnu.org`.
     178`d.love(SGE) @ liverpool.ac.uk`.  In case our spam-blocking
     179appears to defeat you, I'm also `fx(SGE) @ gnu.org`.
    174180— [http://www.gnu.org/philosophy/rms-hack.html Happy hacking]
    175181