Context Navigation

Changes between Version 4 and Version 5 of WikiStart

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

Legend:

: Unmodified
: Added
: Removed
: Modified

WikiStart

-                      v4
+                      v5
+= Welcome to the Son of Grid Engine project (SGE) =
+= Welcome to the __S__on of __G__rid __E__ngine project (SGE) =
 [[PageOutline]]
+This is a community project to continue the old
+[http://gridengine.sunsource.net Sun Grid Engine]
+This is a community project to continue the old Sun
+[http://gridengine.sunsource.net gridengine]
 [http://www.gnu.org/philosophy/free-sw.html free software] project,
 now that Oracle have taken it over and are not contributing to it and
+now that Oracle have taken it over, are not contributing their source, and
 may well close down the Sunsource web site.
+The idea is to encourage sharing, on the basis of long experience of
+free software projects and scientific computing support.  Please
+contribute!
+The idea is to encourage sharing, in the original spirit of the
+project and on the basis of long experience of free software projects
+and scientific computing support.  Please contribute and share any
+ideas for improvement, especially for encouraging contributions.
 As long as it's there, look at the
 …
 }}}
 which will create a directory `sge` of the current
+source.  You can send changes recorded there with
+`darcs send` for pushing by hand if they look reasonable until arrangements
+can be made for direct contributions.
+You could also just mail (see [#contact Contact]) normal
+patches, maybe even
+against the 6.2u5 source, if you have any already.
+The head of the
+source.  The head of the
 source tree is actually available directly via the `Repository URL` links
 for each repository.  If you
 …
 The original CVS repo is currently still
 available if you need more history, and has been backed up in case it
+disappears, along with copies of items in the issue-tracker, though
+only as HTML dumps of the pages.  The active ones have been transferred
+disappears, along with copies of items in the issue-tracker (though
+only as HTML dumps of the pages), and the material on the sunsource
+web site.  The active ones have been transferred
 to the [ticket: issue tracker] here, but have somewhat suffered in the
 process.  If the Sunsource mailing list archive disappears, you can still use
 …
 [http://dir.gmane.org/gmane.comp.clustering.gridengine.users Gmane],
 but it would be good if we could arrange a dump of them.
+== Copyright ==
+If you have copyright concerns about copying the Sunsource material,
+note the [http://www.sunsource.net/TUPPCP.html Sunsource terms].
+Material here has an explicit or implicit copyright under the same
+terms, i.e. code with no explicit terms is covered by a BSD licence,
+and other contributions have a permissive licence.  Any explicit
+licence must be under a
+[http://www.gnu.org/philosophy/free-sw.html free software] licence
+that is compatible with any material it modifies.  The source code is
+obviously under the original
+[http://gridengine.sunsource.net/Gridengine_SISSL_license.html SISSL licence]
+except for some essentially ‘third party’ stuff like `qmake`.
 == Building ==
 …
 }}}
 == Bug tracking and mail lists ==
+== Bug reporting, patches, and mail lists ==
 There aren't currently any accessible mail lists associated with the
 project, but should be soon.  You can create an account to put tickets
+in the [ticket: issue tracker], or use the `tourist` account with `sge` as the
+password.
+in the [ticket: issue tracker], or use the `tourist` account with
+`sge` as the password, but there will eventually be a bugs email list.
+The best way to send patches is to record them in your local darcs
+repository and use `darcs send`.  Until arrangements can be made for
+direct contributions, they will be pushed into the main repository by
+hand if they look reasonable.  You could also just mail (see [#contact
+Contact]) normal patches, maybe even against the 6.2u5 source, if you
+have any already, or attach them to a ticket.
+If you record changes with darcs, make the patch name a useful short
+summary of the patch, and include the number of any ticket it fixes in
+the form {{{fix #}}}//N//, where //N// is the ticket number.  If it
+also refers to an item //N// in the sunsource Issuezilla system, it's
+useful to include that also in the form IZ//N// even though the
+imported tickets have that reference.
+When reviewing tickets imported from Issuezilla, note that any
+hyperlinks appearing in the main description are bogus unless they are
+normal URLs, and some of the tickets have the summary messed up due to
+the way they were imported, which is probably not worth fixing now.
 == Related ==
 …
 There's another project,
 [http://sourceforge.net/projects/gridscheduler/ Open Grid Scheduler],
 which is also continuing work on gridengine but seems to
 have different aims.  Unlike this one, it doesn't use a distributed
+which is also continuing work on gridengine but has
+different aims.  Unlike this one, it doesn't use a distributed
 revision control system, and doesn't include repository history from
 before the gridengine v6.2u5 release, or the documentation.  It would
 …
 It's currently more likely to be broken than gridscheduler, though.
 == [=#contact Contact] ==
+== Contact == #contact
 In the current absence of mail lists,
 …
 `d.love(SGE)@liverpool.ac.uk`.  In case our spam-blocking
 appears to defeat you, I'm also `fx(SGE)@gnu.org`.
+— [http://www.gnu.org/philosophy/rms-hack.html Happy hacking]
+— [http://www.gnu.org/ Happy hacking]
+{{{
+#!comment
+Local Variables:
+mode: trac-wiki
+End:
+}}}