<html><body><p>Hello GRASS PSC,</p><p><br></p><p>I’d love to send a message to the
community to encourage more involvement in testing GRASS GIS and sharing
ideas for improvements—kind of a pre-summit push to get things moving
before we all meet in Raleigh. The idea is not just to report bugs but
also to openly discuss what features people would love to see in GRASS
GIS.</p><p><br></p><p>Of course, the best scenario is when users not
only suggest new features but also take the initiative to implement
them, but even if someone
can’t code it themselves, just sharing the idea is still valuable. If
it’s something useful for many users, it could make its way into the
GRASS GIS roadmap or even become a student project in the future.</p><p><br></p><p>Before I send this out, I wanted to check with you all—does this sound good? Any suggestions on how to phrase it best?</p><p><br></p><p>To help organize and prioritize GUI development, I’ve started a <strong>GRASS GUI roadmap</strong>, where PSC can collaboratively set priorities for future improvements (based on their experience and expected user feedback). Feel free to contribute here:<span> </span>[1].</p><p><span><br></span></p><p><span>Cheers,</span></p><p><span>Linda<br></span></p><p><span><br></span></p><p><span>[1] https://docs.google.com/document/d/1g3RK6X-u8qIl5UADrzfHN06zOmHBzHe-AHKkG2sLGYA/edit?usp=sharing<br></span></p></body></html>