A pre-summit push sounds good. Having clear ideas about what to work on and the status of things helps productivity during the event.
I would definitely like to review the wording, esp. from the summit perspective. We (the organizing committee) are also finishing an official, general announcement with registration - we are a little late with that. It would be good to time your call soon after that. On Wed, 5 Feb 2025 at 11:06, Linda Karlovská via grass-psc < [email protected]> wrote: > Hello GRASS PSC, > > > 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. > > > 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. > > > Before I send this out, I wanted to check with you all—does this sound > good? Any suggestions on how to phrase it best? > > > To help organize and prioritize GUI development, I’ve started a *GRASS > GUI roadmap*, where PSC can collaboratively set priorities for future > improvements (based on their experience and expected user feedback). Feel > free to contribute here: [1]. > > > Cheers, > > Linda > > > [1] > https://docs.google.com/document/d/1g3RK6X-u8qIl5UADrzfHN06zOmHBzHe-AHKkG2sLGYA/edit?usp=sharing > _______________________________________________ > grass-psc mailing list > [email protected] > https://lists.osgeo.org/mailman/listinfo/grass-psc >
_______________________________________________ grass-psc mailing list [email protected] https://lists.osgeo.org/mailman/listinfo/grass-psc
