Congratulations on the GPL for GRASS! Those of us
who are contributors, but not part of the GRASS
development team may need clarification, however.
In the case of r.le, this software was never officially
contributed to GRASS, so in one sense it should not at
this point be part of the GRASS GPL.
However, my intention is to continue to make r.le freely
available, and so there may be an advantage to adding
the GPL to it directly. The GPL would allow GRASS
to include r.le source code of course, and I would
have no problem with this.
We are seeking funding to upgrade r.le to make use
of floating point and true zero in GRASS 5.0.
What is the relationship we GRASS contributors should
develop? Should we add the GPL license to our code
at the outset, then let GRASS include the code as the
GPL license allows?
Also, how does the GPL affect the development and sale
of Blackland GRASS?
Bill Baker
Univ. of Wyoming
-----Original Message-----
From: neteler@geog.uni-hannover.de [mailto:neteler@geog.uni-hannover.de]
Sent: Thursday, October 28, 1999 10:23 AM
To: grass@cecer.army.mil
Subject: Re: Announce: new GRASS 5 beta4 on Tuesday, 26. October
Great.
I would like to post a note about the new GPL status on Slashdot, but
apparently the copyright information at the Baylor website does not yet
reflect this new development, so I have no authority or reference to back
me
up.
Regards,
Duncan C. Kinder
dckinder@mountain.net
Hi Duncan!
Here is the reference:
Check this site:
http://www.geog.uni-hannover.de/grass/
Or that new one:
http://grass.baylor.edu
(the new baylor site is unreachable from here :-(( "down or busy")
Cheers
Markus Neteler