<div dir="ltr">I agree with Martin and Helmut. <div><br></div><div>In my experience, the bulk of the existing GIS users are using Windows and those using GIS professionally are often in work environments where the use of virtual machines or installation of other OS's is prohibited. </div>
<div><br></div><div>The unfortunate fact is that many GIS users have not been exposed to an OS environment other than Windows. Requiring them to load/learn another OS just to run this GIS software would be a fairly high bar for the average user. Without a Windows port, GRASS will simply not be available to a majority of institutional/mainstream GIS users.</div>
<div><br></div><div>If the goal is to expand the user base of GRASS, the maintaining a Windows port is an excellent method. </div><div><br></div><div>Doug</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">
On Wed, Jul 2, 2014 at 7:40 AM, Helmut Kudrnovsky <span dir="ltr"><<a href="mailto:hellik@web.de" target="_blank">hellik@web.de</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Martin Landa wrote<br>
> Hi,<br>
><br>
> 2014-07-02 13:22 GMT+02:00 Moritz Lennert <<br>
<br>
> mlennert@.worldonline<br>
<br>
> >:<br>
<div class="">>> [Starting a new thread as this is an important point on its own. Original<br>
>> mail is [1].]<br>
>><br>
>> On 02/07/14 01:10, Glynn Clements wrote:> But in the longer term, should<br>
>> we<br>
>> be claiming to support a platform<br>
>>> for which we appear to have no active developers?<br>
>><br>
>> I think that the question merits discussion. In my teaching experience it<br>
>> has been very helpful to have a MS Windows version to allow students with<br>
>> MS<br>
>> Windows machines to install the software on these machines. I also have<br>
>> colleagues who, for different reasons, are quite resistant to installing<br>
>> another OS on their machines, but would like to use GRASS. So, generally,<br>
>> I<br>
>> think that there should be a MS Windows port of GRASS.<br>
><br>
> we simply _must_ support as much as possible GRASS on Windows. It's<br>
> crucial for us, without users there is no need for developing<br>
> software.<br>
><br>
> Martin<br>
<br>
</div>I concur with Martin! supporting winGRASS is a must.<br>
<br>
maybe let's spend some money to fix some crucial OS-depending issues...<br>
<br>
<br>
<br>
<br>
-----<br>
best regards<br>
Helmut<br>
--<br>
View this message in context: <a href="http://osgeo-org.1560.x6.nabble.com/future-of-GRASS-for-Windows-was-Re-GRASS-SVN-r60679-grass-trunk-lib-python-script-tp5149214p5149221.html" target="_blank">http://osgeo-org.1560.x6.nabble.com/future-of-GRASS-for-Windows-was-Re-GRASS-SVN-r60679-grass-trunk-lib-python-script-tp5149214p5149221.html</a><br>
Sent from the Grass - Dev mailing list archive at Nabble.com.<br>
<div class="HOEnZb"><div class="h5">_______________________________________________<br>
grass-dev mailing list<br>
<a href="mailto:grass-dev@lists.osgeo.org">grass-dev@lists.osgeo.org</a><br>
<a href="http://lists.osgeo.org/mailman/listinfo/grass-dev" target="_blank">http://lists.osgeo.org/mailman/listinfo/grass-dev</a><br>
</div></div></blockquote></div><br><br clear="all"><div><br></div>-- <br><div>Doug Newcomb</div><div>USFWS</div><div>Raleigh, NC</div><div>919-856-4520 ext. 14 <a href="mailto:doug_newcomb@fws.gov" target="_blank">doug_newcomb@fws.gov</a></div>
<div>---------------------------------------------------------------------------------------------------------</div><div>The opinions I express are my own and are not representative of the official policy of the U.S.Fish and Wildlife Service or Dept. of the Interior. Life is too short for undocumented, proprietary data formats.</div>
</div>