Changes between Version 12 and Version 13 of WikiStart
- Timestamp:
- 03/11/10 17:01:22 (10 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
WikiStart
v12 v13 10 10 11 11 The idea is to encourage sharing, in the spirit of the original 12 project and informed by long experience of free software projects13 and scientific computing support. Please contribute and share any14 ideas for improvement, especially ideas for encouraging contributions.12 project, and informed by long experience of free software projects 13 and scientific computing support. Please contribute, and share code or 14 ideas for improvement, especially any ideas for encouraging contribution. 15 15 16 As long as it's there, you can look at the16 Pending adding to this site, you can look at the 17 17 [http://gridengine.sunsource.net old gridengine site] 18 for extra documentation etc. Currently anything18 for extra documentation etc. as long as it's there. Currently anything 19 19 for the gridengine v6.2u5 release will apply to this effort. (The 20 20 [http://wikis.sun.com/display/gridengine62u5/Home v6.2u5 wiki documentation] 21 21 isn't too easily findable from there.) 22 22 23 Note that this wiki isn't currently editable, but should be eventually.23 This wiki isn't currently editable, but should be eventually. 24 24 25 25 == !Repositories/Source == … … 29 29 actually only goes back to the `V60` tag—i.e. not including 30 30 version 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. 31 manageable. Only the trunk of repository trunk was converted in each 32 case, but see [#history History]. 32 33 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. 34 Also, some files are omitted from those in the head of the sunsource `sge` repo 35 as follows; any others missing are probably a mistake unless they're noted in 36 the 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 42 The repositories are currently just available under 43 [http://darcs.net/ darcs], but are intended to be mirrored eventually, 44 at least to Mercurial. (Darcs is a nice distributed version control 45 system, but doesn't currently scale so well with a repository of this 46 size and age. It's fine for looking at the change history and 47 recording new changes, but currently slow at producing diffs for 48 previous changes, for instance.) 39 49 40 50 To clone the sge repo, get 41 51 a [http://wiki.darcs.net/Binaries recent version of darcs]—at least 42 version 2 and preferably 2. 4—and then run52 version 2 and preferably 2.5—and then run 43 53 {{{ 44 54 darcs get --lazy --set-scripts-executable http://arc.liv.ac.uk/repos/darcs/sge … … 50 60 The head of the source tree is actually available directly via the 51 61 `Repository URL` links for each repository, and if you 52 really need all the current source without darcs, this should do the trick: 62 really need all the current source without a darcs client, this should 63 do the trick: 53 64 {{{ 54 65 wget -e robots=off -r -X /repos/darcs/sge/_darcs -np http://arc.liv.ac.uk/repos/darcs/sge 55 66 find arc.liv.ac.uk/repos/darcs/ -name index.html\\?\* | xargs rm 56 67 }}} 57 58 The files omitted from those in the head of the sunsource `sge` repo are59 the following; any others missing are probably a mistake unless they're noted in60 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).65 68 66 69 == Building == … … 91 94 == Bug reporting, patches, and mail lists == 92 95 93 There aren't currently any accessible mail lists associated with the94 project, but should be soon , and unfortunatelyyou can't currently reply to95 any mail from the tracker, such as notification s of tickets. You can96 create an account96 There aren't yet any mail lists associated with this 97 project, but should be soon. Also you can't currently reply to 98 any mail from the tracker, such as notification from the 99 tracker. You can create an account 97 100 to put tickets in the [ticket: issue tracker], or use the `tourist` 98 account with `sge` as the password. If you do usetourist, it may be useful99 to put a mail address in the report in case of queries.101 account with `sge` as the password. If you are a tourist, it may be useful 102 to put a mail address in the report for contact about it. 100 103 101 104 It will eventually be possible to make bug reports by mail in the 102 105 convenient, time-honoured fashion. 103 106 104 The best way to send patches is to record them in your localdarcs107 The best way to send patches is to record them in a clone darcs 105 108 repository and use `darcs send`. Until arrangements are made for 106 109 direct contributions, they will be pushed into the main repository by 107 110 hand if they look reasonable. Otherwise, you can attach normal 108 111 patches to tickets or just mail (see [#contact Contact]) them, maybe 109 even against the 6.2u5 source, if you have any already.112 even against the 6.2u5 source, if you have them read-made. 110 113 111 114 If you record changes with darcs, make the patch name a useful short … … 116 119 imported tickets have that reference. 117 120 118 == History == 121 == History == #history 119 122 120 The original CVS repo is currently still121 available if you need more history, and has been mirrored in case it 122 disappears, along with copies of items in the123 The [http://gridengine.sunsource.net/source/browse/gridengine/ original CVS repo] 124 is currently still available if you need more history, and has been 125 mirrored in case it disappears, along with copies of items in the 123 126 [http://gridengine.sunsource.net/servlets/ProjectIssues issue-tracker] 124 (‘Issuezilla’) and the material on the sunsource125 web site. The active issues have been transferred126 to the [ticket: issue tracker] here, butsome have somewhat suffered in the127 (‘Issuezilla’), sometimes referred to as ‘IZ’, and the general 128 material on the sunsource web site. The active issues have been transferred 129 to the [ticket: issue tracker] here, though some have somewhat suffered in the 127 130 process; I only discovered after the fact that they were 128 131 accessible as an XML dump. … … 135 138 == Copyright == 136 139 137 If you have copyright concerns aboutcopying the Sunsource material,138 note the [http://www.sunsource.net/TUPPCP.html Sunsource terms].140 Concerning copying the Sunsource material, 141 see the [http://www.sunsource.net/TUPPCP.html Sunsource terms]. 139 142 Material here has an explicit or implicit copyright under the same 140 143 terms, i.e. code with no explicit terms is covered by a BSD licence, … … 142 145 licence must be under a 143 146 [http://www.gnu.org/philosophy/free-sw.html free software] licence 144 that iscompatible with any material it modifies. The source code is145 obviously under the original 147 compatible with any material it modifies. The source code is 148 obviously under the original (rather odd!) 146 149 [http://gridengine.sunsource.net/Gridengine_SISSL_license.html SISSL licence] 147 150 except for some essentially ‘third party’ stuff like `qmake`. … … 151 154 There's another project, 152 155 [http://sourceforge.net/projects/gridscheduler/ Open Grid Scheduler], 156 or ‘gridscheduler’, 153 157 which is also continuing work on gridengine but has 154 different aims. Unlike this one, it doesn't use a distributed155 revision control system, and doesn't include repositoryhistory from158 different aims. Unlike this one, its repository doesn't use a distributed 159 revision control system, and doesn't include history from 156 160 before the gridengine v6.2u5 release, or the documentation. It would 157 be better if there was only one , but I want those things missing from158 gridscheduler (and more, like a bug-tracker that doesn't involve 159 creating accounts); I assume others will too, for ease of 161 be better if there was only one project, but this satisfies the need 162 for those things missing from OGS (and more, like a 163 bug-tracker that doesn't involve creating accounts), which should ease 160 164 contributing. 161 165 162 The `sge` source here is currently basically a considerablesuperset of163 gridscheduler. It includes the changes from it, or close166 The `sge` source here is currently a superset of 167 OGS's. It includes the changes from it, or close 164 168 equivalents, 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. 169 in some circumstances, and other less important changes, as well as the 170 man page documentation. 171 It is currently more unstable than OGS, but breakage should get 172 fixed, at least if it isn't inherited from the original code base. 167 173 168 174 == Contact == #contact … … 170 176 In the current absence of mail lists, 171 177 please send queries, contributions, &c to: Dave Love, 172 `d.love(SGE) @liverpool.ac.uk`. In case our spam-blocking173 appears to defeat you, I'm also `fx(SGE) @gnu.org`.178 `d.love(SGE) @ liverpool.ac.uk`. In case our spam-blocking 179 appears to defeat you, I'm also `fx(SGE) @ gnu.org`. 174 180 — [http://www.gnu.org/philosophy/rms-hack.html Happy hacking] 175 181