<html xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:Helvetica;
panose-1:0 0 0 0 0 0 0 0 0 0;}
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:"Lucida Grande";
panose-1:2 11 6 0 4 5 2 2 2 4;}
@font-face
{font-family:"Lucida Sans";
panose-1:2 11 6 2 3 5 4 2 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style>
</head>
<body lang="EN-US" link="blue" vlink="purple" style="word-wrap:break-word">
<div class="WordSection1">
<p class="MsoNormal">I am honored to be nominated to continue on the PSC. <o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">By way of background, I have been a GRASS user and contributor for nearly two decades. When I first managed to compile GRASS on my Mac, I wrote a polite email to Markus Neteler asking about the possibility of a GUI. He wrote back a polite
email explaining that this new open source project relied on volunteers to do such development. While uncertain about my ability to contribute the project, I tried anyway--learning and benefiting much. I have had a number of roles in the GRASS community and
indeed ended us designing and coding several generations of GUI's, including the one now used. This work is now carried on by others younger and more talented than I am. Importantly, all of my contributions would not have been possible without the collaboration
of other volunteers in this community. While I still do a little development work, my main contribution is to maintain the Mac binaries. <o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">I use GRASS for socio-ecological research and dynamic modeling, and teach geospatial technologies with GRASS (in the USA, Germany, and Spain). Being a member of the international GRASS community has made me an ardent and vocal advocate
of FOSS and open science. Promoting open scientific computation is key to the mission of the scientific network I lead, CoMSES.NET. I regularly point to GRASS as an exemplar open source software project, a bottom up, self-organized network of users and developers
around the world who together create some of the most powerful and highest quality geospatial software available. <o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">I will continue to participate in the GRASS developer and user communities, advocating for GRASS and FOSS, whether or not I am on the PSC. If selected, I am happy to continue to provide input, a historical perspective, and support the PSC
as a researcher/educator/developer and as a Mac user of GRASS. My goals for GRASS center around making it more accessible so that more people can use it and contribute to the project. I am very happy to see the continued growth of the developer and user communities,
especially the new generation of developers who are continuing the GRASS tradition of high-quality, cutting-edge software. I certainly support ongoing work to make the GUI more flexible and more usable, critically important for enabling a wide diversity of
people to apply this sophisticated and powerful software. Along these lines, I would encourage incipient development efforts to provide a browser-based version of GRASS, available online as software-as-a-service. Also, in order to support transparent, scientific
workflows, one suggestion I have is for an option that would automatically record the commands behind a series of GUI actions in a file that could be saved and shared. All the functionality to do this is already in place in GRASS. Finally, while preparing
this statement, I went looking for an expression of the GRASS mission, and found that one is not available beyond "Bringing advanced geospatial technologies to the world". This is indeed laudable. But given the long and successful history, and worldwide use
of GRASS, it would be of value for the PSC, with approval of voting community members, to articulate a more comprehensive GRASS mission statement to communicate the vision of this community to a global audience. <o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Michael Barton<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal"><span style="font-size:9.0pt;font-family:Helvetica;color:black">______________________________</span><span style="font-size:10.0pt;font-family:"Lucida Grande",sans-serif;color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:9.0pt;font-family:"Lucida Sans",sans-serif;color:#5E5E5E">C. Michael Barton <br>
Network for Computational Modeling in Social & Ecological Sciences<br>
School of Complex Adaptive Systems<br>
School of Human Evolution & Social Change<br>
Arizona State University<br>
USA<br>
<br>
<br>
</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
</body>
</html>