Changes between Version 4 and Version 5 of WikiStart
- Timestamp:
- 27/10/10 11:46:58 (10 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
WikiStart
v4 v5 1 = Welcome to the Son of Grid Engine project (SGE) = 1 = Welcome to the __S__on of __G__rid __E__ngine project (SGE) = 2 2 3 [[PageOutline]] 3 This is a community project to continue the old 4 [http://gridengine.sunsource.net Sun Grid Engine] 4 5 This is a community project to continue the old Sun 6 [http://gridengine.sunsource.net gridengine] 5 7 [http://www.gnu.org/philosophy/free-sw.html free software] project, 6 now that Oracle have taken it over and are not contributing to itand8 now that Oracle have taken it over, are not contributing their source, and 7 9 may well close down the Sunsource web site. 8 10 9 The idea is to encourage sharing, on the basis of long experience of 10 free software projects and scientific computing support. Please 11 contribute! 11 The idea is to encourage sharing, in the original spirit of the 12 project and on the basis of long experience of free software projects 13 and scientific computing support. Please contribute and share any 14 ideas for improvement, especially for encouraging contributions. 12 15 13 16 As long as it's there, look at the … … 41 44 }}} 42 45 which will create a directory `sge` of the current 43 source. You can send changes recorded there with 44 `darcs send` for pushing by hand if they look reasonable until arrangements 45 can be made for direct contributions. 46 You could also just mail (see [#contact Contact]) normal 47 patches, maybe even 48 against the 6.2u5 source, if you have any already. 49 50 The head of the 46 source. The head of the 51 47 source tree is actually available directly via the `Repository URL` links 52 48 for each repository. If you … … 69 65 The original CVS repo is currently still 70 66 available if you need more history, and has been backed up in case it 71 disappears, along with copies of items in the issue-tracker, though 72 only as HTML dumps of the pages. The active ones have been transferred 67 disappears, along with copies of items in the issue-tracker (though 68 only as HTML dumps of the pages), and the material on the sunsource 69 web site. The active ones have been transferred 73 70 to the [ticket: issue tracker] here, but have somewhat suffered in the 74 71 process. If the Sunsource mailing list archive disappears, you can still use … … 76 73 [http://dir.gmane.org/gmane.comp.clustering.gridengine.users Gmane], 77 74 but it would be good if we could arrange a dump of them. 75 76 == Copyright == 77 78 If you have copyright concerns about copying the Sunsource material, 79 note the [http://www.sunsource.net/TUPPCP.html Sunsource terms]. 80 Material here has an explicit or implicit copyright under the same 81 terms, i.e. code with no explicit terms is covered by a BSD licence, 82 and other contributions have a permissive licence. Any explicit 83 licence must be under a 84 [http://www.gnu.org/philosophy/free-sw.html free software] licence 85 that is compatible with any material it modifies. The source code is 86 obviously under the original 87 [http://gridengine.sunsource.net/Gridengine_SISSL_license.html SISSL licence] 88 except for some essentially ‘third party’ stuff like `qmake`. 78 89 79 90 == Building == … … 89 100 }}} 90 101 91 == Bug trackingand mail lists ==102 == Bug reporting, patches, and mail lists == 92 103 93 104 There aren't currently any accessible mail lists associated with the 94 105 project, but should be soon. You can create an account to put tickets 95 in the [ticket: issue tracker], or use the `tourist` account with `sge` as the 96 password. 106 in the [ticket: issue tracker], or use the `tourist` account with 107 `sge` as the password, but there will eventually be a bugs email list. 108 109 The best way to send patches is to record them in your local darcs 110 repository and use `darcs send`. Until arrangements can be made for 111 direct contributions, they will be pushed into the main repository by 112 hand if they look reasonable. You could also just mail (see [#contact 113 Contact]) normal patches, maybe even against the 6.2u5 source, if you 114 have any already, or attach them to a ticket. 115 116 If you record changes with darcs, make the patch name a useful short 117 summary of the patch, and include the number of any ticket it fixes in 118 the form {{{fix #}}}//N//, where //N// is the ticket number. If it 119 also refers to an item //N// in the sunsource Issuezilla system, it's 120 useful to include that also in the form IZ//N// even though the 121 imported tickets have that reference. 122 123 When reviewing tickets imported from Issuezilla, note that any 124 hyperlinks appearing in the main description are bogus unless they are 125 normal URLs, and some of the tickets have the summary messed up due to 126 the way they were imported, which is probably not worth fixing now. 97 127 98 128 == Related == … … 100 130 There's another project, 101 131 [http://sourceforge.net/projects/gridscheduler/ Open Grid Scheduler], 102 which is also continuing work on gridengine but seems to103 havedifferent aims. Unlike this one, it doesn't use a distributed132 which is also continuing work on gridengine but has 133 different aims. Unlike this one, it doesn't use a distributed 104 134 revision control system, and doesn't include repository history from 105 135 before the gridengine v6.2u5 release, or the documentation. It would … … 115 145 It's currently more likely to be broken than gridscheduler, though. 116 146 117 == [=#contact Contact] ==147 == Contact == #contact 118 148 119 149 In the current absence of mail lists, … … 121 151 `d.love(SGE)@liverpool.ac.uk`. In case our spam-blocking 122 152 appears to defeat you, I'm also `fx(SGE)@gnu.org`. 153 — [http://www.gnu.org/philosophy/rms-hack.html Happy hacking] 123 154 124 — [http://www.gnu.org/ Happy hacking] 155 {{{ 156 #!comment 157 Local Variables: 158 mode: trac-wiki 159 End: 160 }}}