Changes between Version 4 and Version 5 of WikiStart


Ignore:
Timestamp:
27/10/10 11:46:58 (9 years ago)
Author:
dlove
Comment:

--

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
    23[[PageOutline]]
    3 This is a community project to continue the old
    4 [http://gridengine.sunsource.net Sun Grid Engine]
     4
     5This is a community project to continue the old Sun
     6[http://gridengine.sunsource.net gridengine]
    57[http://www.gnu.org/philosophy/free-sw.html free software] project,
    6 now that Oracle have taken it over and are not contributing to it and
     8now that Oracle have taken it over, are not contributing their source, and
    79may well close down the Sunsource web site.
    810
    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!
     11The idea is to encourage sharing, in the original spirit of the
     12project and on the basis of long experience of free software projects
     13and scientific computing support.  Please contribute and share any
     14ideas for improvement, especially for encouraging contributions.
    1215
    1316As long as it's there, look at the
     
    4144}}}
    4245which 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
     46source.  The head of the
    5147source tree is actually available directly via the `Repository URL` links
    5248for each repository.  If you
     
    6965The original CVS repo is currently still
    7066available 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
     67disappears, along with copies of items in the issue-tracker (though
     68only as HTML dumps of the pages), and the material on the sunsource
     69web site.  The active ones have been transferred
    7370to the [ticket: issue tracker] here, but have somewhat suffered in the
    7471process.  If the Sunsource mailing list archive disappears, you can still use
     
    7673[http://dir.gmane.org/gmane.comp.clustering.gridengine.users Gmane],
    7774but it would be good if we could arrange a dump of them.
     75
     76== Copyright ==
     77
     78If you have copyright concerns about copying the Sunsource material,
     79note the [http://www.sunsource.net/TUPPCP.html Sunsource terms].
     80Material here has an explicit or implicit copyright under the same
     81terms, i.e. code with no explicit terms is covered by a BSD licence,
     82and other contributions have a permissive licence.  Any explicit
     83licence must be under a
     84[http://www.gnu.org/philosophy/free-sw.html free software] licence
     85that is compatible with any material it modifies.  The source code is
     86obviously under the original
     87[http://gridengine.sunsource.net/Gridengine_SISSL_license.html SISSL licence]
     88except for some essentially ‘third party’ stuff like `qmake`.
    7889
    7990== Building ==
     
    89100}}}
    90101
    91 == Bug tracking and mail lists ==
     102== Bug reporting, patches, and mail lists ==
    92103
    93104There aren't currently any accessible mail lists associated with the
    94105project, 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.
     106in 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
     109The best way to send patches is to record them in your local darcs
     110repository and use `darcs send`.  Until arrangements can be made for
     111direct contributions, they will be pushed into the main repository by
     112hand if they look reasonable.  You could also just mail (see [#contact
     113Contact]) normal patches, maybe even against the 6.2u5 source, if you
     114have any already, or attach them to a ticket.
     115
     116If you record changes with darcs, make the patch name a useful short
     117summary of the patch, and include the number of any ticket it fixes in
     118the form {{{fix #}}}//N//, where //N// is the ticket number.  If it
     119also refers to an item //N// in the sunsource Issuezilla system, it's
     120useful to include that also in the form IZ//N// even though the
     121imported tickets have that reference.
     122
     123When reviewing tickets imported from Issuezilla, note that any
     124hyperlinks appearing in the main description are bogus unless they are
     125normal URLs, and some of the tickets have the summary messed up due to
     126the way they were imported, which is probably not worth fixing now.
    97127
    98128== Related ==
     
    100130There's another project,
    101131[http://sourceforge.net/projects/gridscheduler/ Open Grid Scheduler],
    102 which is also continuing work on gridengine but seems to
    103 have different aims.  Unlike this one, it doesn't use a distributed
     132which is also continuing work on gridengine but has
     133different aims.  Unlike this one, it doesn't use a distributed
    104134revision control system, and doesn't include repository history from
    105135before the gridengine v6.2u5 release, or the documentation.  It would
     
    115145It's currently more likely to be broken than gridscheduler, though.
    116146
    117 == [=#contact Contact] ==
     147== Contact == #contact
    118148
    119149In the current absence of mail lists,
     
    121151`d.love(SGE)@liverpool.ac.uk`.  In case our spam-blocking
    122152appears to defeat you, I'm also `fx(SGE)@gnu.org`.
     153— [http://www.gnu.org/philosophy/rms-hack.html Happy hacking]
    123154
    124 — [http://www.gnu.org/ Happy hacking]
     155{{{
     156#!comment
     157Local Variables:
     158mode: trac-wiki
     159End:
     160}}}