Conversation
|
Thanks for putting together the 2025 Annual Report — it’s very helpful for getting an overview of the project activities. As a newcomer reviewing this, one thing that might help readers is a short summary or pointer to where new contributors can get involved (e.g., links to contributor docs, newcomer-friendly issues, or entry points into GRASS development) if that fits the scope of the report. Otherwise, this is a great overview of the work done during the year. |
|
Looks good from my perspective |
|
Looks good |
…ghts across sections.
chaedri
left a comment
chaedri
left a comment
There was a problem hiding this comment.
This reads really nicely to me! GRASS has accomplished so much this year.
I think @cwhite911 is going to migrate our FOSS4G-NA workshop to ncsu-geoforall-lab so we may need to update the link after this.
|
Great, I like it a lot! Maybe we could add a short paragraph about the Jupyter Notebook integration to GUI as well? The PR OSGeo/grass#5901 is currently waiting for the final review from @petrasovaa, and I believe that once it’s reviewed and merged, it should make it into 8.5. |
| </a> | ||
|
|
||
| The **GRASS Markdown documentation project** resulted in a complete redesign of our user documentation. The [modernized documentation](https://grass.osgeo.org/grass85/manuals/index.html) integrates access to user and developer web pages, incorporates Python syntax into tool manuals, and features numerous improvements including better indexing and search. Each tool's manual page now shows tabs for Command line, Python (*grass.script*), and Python (*grass.tools*) usage, making it easier for users to find the right syntax for their preferred interface. The work was done by Martin Landa, Markus Neteler, Corey White, Vaclav Petras, Anna Petrasova and others. | ||
|
|
There was a problem hiding this comment.
It is not merged yet, so given that the other things there are already merged, we can leave this for later. It is mentioned in the developer summit:
Participants explored a wide range of ideas—from improving access to GRASS tools...to...integrating Jupyter into the GRASS GUI.
9 participants
Please all read and suggest any missing developments, events, etc. Or better images.
There are couple unfinished details (links to workshops), titles in figures and figure layout. I will try to get to them later.