GRASS-Wiki - User contributions [en]

PSC Meeting 2026-08-14

2026-09-03T19:52:32Z

Neteler: minor updates

Postponed to August 21 so that more PSC members can join.

== Participants ==
* Helli
* Anna
* Vashek
* Nicklas
* Linda
* Vero
* Huidae
* Markus
* Paulo

== Agenda ==

The topics proposed are:

* Review action points from previous meetings
** Nicklas and Edouard's access to the grass.osgeo.org server?
** Status of translation, grass-gui and grass-stats lists
* Community Meeting San Michele 2026:
** Aftermath, budget, reimbursements
** Remaining budget from FOSSGIS e.V. will be available for Student Grants (requires NUMfocus invoice to FOSSGIS e.V.)
** Overall experience: what worked, what to improve for next time
** Alen's proposal for 2027 Community Meeting
* PSC Elections
** Define date
** Who's up for re-election
** CRO
** Refine voters list, re-assess criteria according to latest AI contributions?
* GSoC students progress
* Windows build server status:
** Standalone installer
** Addons
* Wiki state (Mediawiki)
** MN implemented harder fail2ban rules to keep botnets out, seems to work
** Regina (SAC) proposed to use cloudflare if this isn't sufficient
** MN want to get a responsive theme implemented (also on wiki.osgeo.org needed)
* Releases
** FSH status
* Website updates
* NumFOCUS: any updates on transparency, OpenCollective/Redbubble fiscal host status, transition
* NumFOCUS mini grant: Linda plans to apply with a topic focused on improving the user experience around computational regions (discussion already in https://github.com/OSGeo/grass/issues/7614)
* Upcoming events
** FOSS4G 2026
** FOSS4G NA?
* RFC
** New planned RFC to make C11's optional feature 'atomic support' required for 8.6
* GitHub - limiting the number of open PRs

== Minutes ==

Since most of us had limited time on this occasion, topics were discussed in order of importance, not exactly following the proposed agenda.

'''1. PSC Elections'''

* Five seats are up for renewal: VP, AP, VA, MN, HC. See current member list: https://grasswiki.osgeo.org/wiki/PSC#Members
* MN announced he will step down after 25 years of service to the project.
* The PSC noted the importance of improving gender balance among candidates.
* Potential candidates were discussed.
* The election procedure will follow the 2024 process: https://grasswiki.osgeo.org/wiki/PSC_Election_2024#The_process
* [Action] Vero to coordinate election dates directly with Hernán, who agreed to be CRO again.
* [Action] Vero will run the scripts again to get a final voter list.

'''2. GSoC 2026'''

* Temporal framework project: successful.
* Parallelization project: r.param.scale done, r.geomorphons done, r.proj not yet (complex, not ready to merge in the near term, suggestion to ping Markus Metz once the code is cleaner).

'''3. Community Meeting 2027'''

* Alen proposed to organize and host the 2027 community meeting.
* [Action] Ask Alen to send a form with proposed dates and logistics to understand how many would be able to attend.

'''4. Reimbursements - Community Meeting 2026'''

* FOSSGIS e.V.: ongoing talks; the FOSSGIS treasurer recently quit, but the situation will be managed. There are approximately 700 EUR remaining (relative to our 4,500 EUR request) that FOSSGIS will still pay to us via a NumFOCUS invoice, to be used for student grants. A form is needed from NumFOCUS.
* [Action] Once the NumFOCUS form is available, MN will follow up with FOSSGIS e.V. => done, waiting for the response of FOSSGIS e.V.
* OSGeo money: Edouard and Vero to follow up on reimbursements.
* [Action] VP will coordinate this with Mike (OSGeo treasurer).

'''5. NumFOCUS'''

* NumFOCUS is now the fiscal host of our shop on Redbubble.com (merch)
* Transparency on the current balance and financial activity remains unclear.
* [Action] VP will clarify with NumFOCUS how much money we have and how to get a transparent view of it.

'''6. Website and infrastructure'''

* Website: Corey has been doing extensive work on style and build tooling.
* Server access (grass.osgeo.org): Corey already has access.
* [Action] MN will coordinate with Regina (OSGeo SAC) to set up a dedicated Matomo instance for GRASS within OSGeo infrastructure, replacing the current external solution.
* Nicklas will revisit server access: he is not interested in access just for macOS binaries, but would be willing to act as a backup person for the GRASS infrastructure.
* Wiki mobile responsiveness: MN is looking thru OSGeo-SAC into a theme solution for MediaWiki.
* [Action] MN will create a SAC ticket
* Wiki bot attacks: Regina offered to put the wiki behind a Cloudflare container, but this is significant work and not a high priority at this point. MN has implemented an auto-restart mechanism for the Apache/DB server as a mitigation. Meanwhile over 250k IP-addresses have been banned with MN's fail2ban script on the server.
* Windows builds: VP will speak with Edouard to assess the current status. At present, only the OSGeo4W installer is available; some progress was made during the Community Meeting thanks to Antonio.

'''7. Release 8.6'''

* Several distribution-related issues need to be resolved before 8.6 can ship:
** Conda: the Windows package is no longer compiling; C addons cannot be installed when running GRASS from a conda environment.
** Markdown in manuals: Is that ready?
*** MN mentioned that mundialis addons are now built without HTML files, generating them from Markdown in the Makefile (see [https://github.com/mundialis/r.dop.import/blob/515c3a36fb2490baf797f7d35c6b689f84031a9d/Makefile example]).
** CMake: do we make the switch for this release?
* FHS: currently not working; something is missing. Nicklas will investigate in the coming weeks; it may not be ready for 8.6.

'''8. Events'''

* Corey will attend FOSS4G North America.
* Alen and Luca will attend FOSS4G Hiroshima
* Markus will deliver a remote keynote at FOSS4G Hiroshima (together with Venkatesh Raghavan).

'''9. Other'''

* GitHub PR limit: the maximum number of open PRs for new users was set to 5.
* NumFOCUS small development grants: Linda will apply with a project focused on handling regions in the GUI.

[[Category:PSC]]

Geoprocessing Engine Working Group

2026-09-03T17:54:35Z

Neteler: GRASS/actinia is part of the new Horizon Europe project "GeoAI toolbox for Epidemic Intelligence"

Geoprocessing engine working group is established to coordinate the development of GRASS as a geoprocessing engine to facilitate GRASS adoption by researchers and industry.

== Scope ==
* coordinate development of GRASS as a geoprocessing engine
* coordinate development of Python API
* coordinate software distribution
* source code quality assurance, testing, CI

== Activity ==

While the group itself is currently not active as a group, things are happening, for example
* Vaclav Petras's collaboration with Natrx, Inc. to create new Python API to tools (grass.tools)
* GRASS/actinia being part of the new Horizon Europe project "GeoAI toolbox for Epidemic Intelligence" ([https://doi.org/10.3030/101287260 DOI]) with mundialis/Markus Neteler/Markus Metz as consortium partners

== Members ==
Let us know who you are and what are your interests and topics you want to discuss and develop as part of this group.

; [https://wiki.osgeo.org/wiki/User:Wenzeslaus Vaclav (Vashek) Petras] (working group coordinator)
: Researcher and software developer at North Carolina State University
: Interested in ...

; Markus Neteler
:
:

; Loïc Bartoletti
:
:

; [https://hcho.isnew.info/ Huidae Cho]
: Water resources engineer and senior GIS developer
: Interested in Open Source Hydrology, especially, GRASS GIS applications and algorithm development

; Helmut Kudrnovsky
:
:

; Massimo Di Stefano
:

;Yann Chemin
:

; Stefan Blumentrath
:

To be added to this working group, please contact the group coordinator.

== Communication Channels ==
* [https://lists.osgeo.org/mailman/listinfo/grass-dev grass-dev] mailing list
* [https://github.com/OSGeo/grass OSGeo/grass GitHub issues and pull requests] and [https://github.com/orgs/OSGeo/projects/4 GitHub project]

[[Category:Community]]
[[Category:Working_Groups]]

GRASS in the wild

2026-08-23T12:53:16Z

Neteler: GRASS DOI added, cleanup

Huge lists of GRASS GIS related articles:
* Zotero.org:
** GRASS DOI: https://doi.org/10.5281/zenodo.5176030
** GIS group, tag "GRASS GIS": https://www.zotero.org/groups/gis/items/tag/GRASS%20GIS
* Google Scholar:
** [https://scholar.google.com/citations?user=gJ0ZB0cAAAAJ structured GRASS citations]
** You may also search for [https://scholar.google.com/scholar?q=GRASS+GIS GRASS GIS articles in Google Scholar] (activate Bibtex output in "Scholar settings")
*CiteULike, tag "GRASS": https://www.citeulike.org/tag/grass

[[Category:Citations]]
[[Category:Documentation]]
[[Category:FAQ]]

GRASS historical documents

2026-08-23T12:40:28Z

Neteler: +GRASS historical documents (source: https://discourse.osgeo.org/t/grass-dev-grass-historical-documents/85477/2)

== GRASS historical documents ==

(Missing: Manuals of GRASS 1.0 and 2.0 - please submit to us!)

1983
* Goran, W.D., Dvorak, W.E., Van Warren, L. and Webster, R.D., 1983, Fort Hood Geographic Information System: Pilot System Development and User Instructions, Technical Report N-154, USA Construction Engineering Research Laboratory, Champaign, IL: https://grass.osgeo.org/files/fhgis83rep.pdf

1987

* Sources of Digital Spatial Data for Geographic Information Systems (1987): https://archive.org/details/DTIC_ADA189788

1989
* GRASS 3.0 Programmer's Manual (1989): https://archive.org/details/DTIC_ADA252461
* GRASS/GIS (Geographic Resources Analysis Support System/Geographic Information System) Implementation Guide (1989): https://archive.org/details/DTIC_ADA214623/
* Proceedings of the Geographical Resource Analysis Support System (GRASS) User Group Meeting Held in Champaign, Illinois, 1988 (1989): https://archive.org/details/DTIC_ADA213823
* Methodology for Performing Return-On-Investment (ROI) Studies for Implementation of GRASS on Military Installations (1989): https://archive.org/details/DTIC_ADA222064
* GRASS Hardware Configurations Guide (1989): https://archive.org/details/DTIC_ADA220954
* Guidelines for Running GRASS Benchmarks (1989): https://archive.org/details/DTIC_ADA221332
* Testing Guidelines for GRASS Ports and Drivers (1989): https://archive.org/details/DTIC_ADA221176
* Options for Acquiring Elevation Data (1989): https://archive.org/details/DTIC_ADA220934

1990:
* Cartographic Issues in the Development of a Digital GRASS Database (1990): https://archive.org/details/DTIC_ADA227582

1991:
* A Comparison of Manual and Automated Methods for Delimiting Watersheds for Use with GRASS/GIS Software (1991): https://archive.org/details/DTIC_ADA242633

1992:
* Geographic Resources Analysis Support System (GRASS) Version 4.0 User's Reference Manual (1992): https://archive.org/details/DTIC_ADA255218
* GRASS 4.0 Map Digitizing User's Manual: v.digit (1992): https://archive.org/details/DTIC_ADA256859
* GRASS-Intergraph Data Conversion Guide (1992): https://archive.org/details/DTIC_ADA251458
* Predicting Database Requirements for Geographic Information Systems in the Year 2000: Long-Term Design Issues for GRASS (1992): https://archive.org/details/DTIC_ADA256862
* Flood Damage Analysis Within the Readiness Management System (1992): https://archive.org/details/DTIC_ADA273274

1993:
* Sound Exposure Level Prediction for Impulse Sound Sources Above Variable Terrain (1993): https://archive.org/details/DTIC_ADA267535
* Estimating dry grass residues using landscape integration analysis (1993): https://archive.org/details/NASA_NTRS_Archive_19950017447

1994:
* Using Neural Networks to Correlate Satellite Imagery and Ground-Truth Data (1994): https://archive.org/details/DTIC_ADA285486
* A Multiscale Random Field Model for Bayesian Image Segmentation (1994): https://archive.org/details/DTIC_ADA283875

1996:
* Implementation of a Distributed Hydrologic Model within Geographic Resources Analysis Support System (GRASS) (1996): https://archive.org/details/DTIC_ADA348892

1998:
* GRASS to ARC/INFO Data Conversion (1998): https://archive.org/details/DTIC_ADA353594

Documents just tangential to GRASS, but perhaps interesting:
* Digital Mapping: Fact or Fiction. (1986): https://archive.org/details/DTIC_ADA167571
* Geographic Information Systems: A Primer (1990): https://archive.org/details/DTIC_ADA231465

=== See also ===

* [[GRASS Citation Repository]]
* PDF files: https://grass.osgeo.org/files/

[[Category: Documentation]]
[[Category: History]]

GRASS Documents

2026-08-23T12:28:35Z

Neteler: /* Development */

== Usage ==

=====[[Faq|Frequently asked questions and answers (FAQ)]]=====

==== [http://grass.osgeo.org/documentation/manuals/ GRASS Manual pages] ====

==== GRASS tutorials ====

===== General =====
* [http://grass.osgeo.org/documentation/tutorials/ GRASS Tutorials]
* [[Wiki Tutorials]]: a nice collection
* [http://grass.osgeo.org/gdp/index.php GRASS Documentation project] huge amount of information for many versions of GRASS spanning the last 15 years; relevant content needs to be moved into this Wiki [''please help!'']
* [[GRASS_Education_%28Free_GIS_education%29#Teaching_Materials | Teaching materials]] (courses, training videos, presentations, etc.) contributed by the community.
* [[GRASS 6 Tutorial]]
* [http://www.ing.unitn.it/~grass/docs/tutorial_642/ GRASS 6.4.2 tutorial] by Ciolli, Tattoni, Vitti, Zottele, and Zatelli.
* [http://www.grassbook.org/ GRASS GIS Book] with educational data set download
* A list of [[Tips and Tricks|tips and tricks]] for the use of GRASS

===== Basics =====
* Help with [[data formats]]
* Help with [[Vector Database Management|vector database management]]
* An overview of working with GRASS [[Vectordata | vector data]] (topological)
* [[SQL]] support in GRASS GIS
* [[Spatial SQL]] support in GRASS GIS
* [[Help with 3D]]

===== Specific subjects =====
* [[Terrain Analysis with Geomorphons]]
* Geostatistics: [[How to interpolate point value using kriging method with R and GRASS 6|how to interpolate point value using kriging method with R and GRASS]].
* Help with [[Image_processing|Imagery and satellite]] data
* Help with [[LIDAR|LIDAR and swath bathymetry]] data
* Help with [[Time series]]
* Help with [[Color tables]]
* Help with creating [[Movies|Movies and animations]]
* Help with [[vector network analysis]]
* Help with [[GPS]] applications
* [[Trace vector contours from a scanned map]]
* [[Digitizing Area Features]]
* [[Interpolation|Resampling methods and interpolation in GRASS]]
* Help with [[GRASS raster semantics]]
* [[Cartography|Hints and links]] for the use of the cartographic tools in GRASS
* Help with the [[module command line parser]]
* Help with [[RST Spline Surfaces]]
* [[Lidar_Analysis_of_Vegetation_Structure]]

===== Scripting & interfacing other systems =====
* [[GRASS and ABM]]
* [[GRASS and C++]]
* [[GRASS and GMT]]
* [[GRASS and Java]]
* [[GRASS and Octave]]
* [[GRASS and Paraview]]
* [[GRASS and PHP]]
* [[GRASS and Python]]
* [[GRASS and SAGA]]
* [[GRASS and Sextante]]
* [[GRASS and Shell]]
* [[GRASS and VTK]]
* [[GRASS and bat-files in windows console]]
* [[QGIS GRASS Cookbook]]

===== Help with modules =====
* [[r.sun]] - Solar irradiation model
* [[ps.map]] - Cartographic plot builder
* [[r.stream.*]] - r.stream tutorial

== General ==

=== GRASS Citation Repository ===
You are encouraged to cite GRASS when using the software in your work. [[GRASS Citation Repository|On this page]] you find suggestions how to cite GRASS.

=== Installation ===
* [[Installation Guide]] for binary packages
* [[Compile and Install]] from GRASS GIS source code repository (the latest and greatest...)
* [[Compile and install GRASS and QGIS with GDAL/OGR Plugin]] (e.g., to enable QGIS to read GRASS data directly)
* [[GRASS AddOns]] (User contributions)
* [[Raspberry Pi|GRASS on the Raspberry Pi]] $25 low powered/embedded mini-PC

=== Development ===
* Programming: see document list at [[Development]].
* [[GRASS Translation Glossary]]
* [[GRASS Module Porting List]] (check here if you don't find a certain command in GRASS 6)
* [[Development#Linking GRASS to external languages|Linking GRASS to external languages]]

=== GRASS historical documents ===
* [[GRASS historical documents]]

[[Category: Documentation]]
[[Category: Tutorial]]

Promotional material

2026-08-23T12:27:25Z

Neteler: + GRASS historical documents

Collection of material to promote the GRASS project

==== Technical background, history ====

* Official Web site: https://grass.osgeo.org
* [[Description of the project]] (100-150 words)
* Listing the [[core features]]
* [[Technical Data sheet]]
* [[GRASS GIS Performance]]
* [[Software requirements specification]]
* Portable software: Linux, MacOSX, MS-Windows, Sun, Android, ...

GRASS GIS History:
* {{website|about/history|Project history}}: Started 1982, GRASS 1.0 published 1984
* [https://wiki.osgeo.org/wiki/Open_Source_GIS_History Open Source GIS History]
* [[GRASS historical documents]]

Web site history:
* [https://grass.osgeo.org/about/history/web-evolution/ GRASS Web site evolution] from plain HTML to HTML/PHP with RSS integrated to hugo maintained in git)

==== Presentation slides ====

* Many presentations are available at [https://www.slideshare.net/search/slideshow?searchfrom=header&q=grass+gis&ud=any&ft=all&lang=**&sort= Slideshare]

==== Social media outreach ====

* https://trac.osgeo.org/grass/wiki/PSC/Marketing
* [[Contact Databases]]
* {{website|about/community|Community}}
* Social media
** https://www.facebook.com/groups/GRASS
** https://twitter.com/GRASSGIS

==== Screenshots ====

* Graphics, {{website|learn/gallery/|screenshots}} or images that represent the GRASS GIS project (see also [[Screenshot suggestions]])
* [[Screenshot_suggestions|Wiki screenshot bullpen]] ''(please add URLs and indicate license)''
* Presentations: [https://www.slideshare.net/markusN/25-years-of-grass-gis-3005600 25 Years of GRASS GIS] and [https://www.slideshare.net/markusN/grass-gis-640 The upcoming GRASS GIS 6.4.0 release] (news 9/2010 - it is available :-)
* [[GRASS Propaganda]] (desktop and presentation background images)

==== Artwork ====

* [[GRASS Art Gallery]]

* {{website|about/brand/|GRASS GIS logos}}
* [https://trac.osgeo.org/osgeo/browser/marketing/logo OSGeo marketing logos etc.]

==== GRASS T-shirts ====

The community_sprints logos are available for download [https://github.com/OSGeo/grass-promo/tree/master/events/community_sprints here].

==== GRASS Flyers ====

This flyer gives a short introduction in GRASS GIS:
* [https://github.com/OSGeo/grass-promo/tree/master/grassflyer/flyer_2016 Flyer in various languages]

==== General and specific GRASS GIS Poster ====
The current poster was designed for the German FOSSGIS Conference and then translated into English, Italian, Polish and Czech. It might be useful at other conferences and fairs, as well. The grass-addons repository contains the poster in PDF- and ODP (OpenOffice Impress)-Format. Translations are best stored again in the svn.

* [https://github.com/OSGeo/grass-promo/tree/master/grassposter Selection of GRASS GIS posters]

==== Videos ====

* [https://www.youtube.com/results?search_query=grass+gis GRASS GIS videos on YouTube]
* [http://doi.org/10.5446/12963 '''GRASS video (1987)'''] narrated by William Shatner (Captain Kirk of Star Trek) - in public domain
* [[GRASS development visualization]]
** GRASS GIS 6.4 source code evolution: {{YouTube|MR4_5GSID2A|desc=GRASS GIS 6.4 development visualization from 1999 to 2013 (with soundtrack)}}
** GRASS GIS 6 source code evolution: {{YouTube|suyDqmGXoWk|desc=GRASS GIS 6.4 development visualization from 1999 to 2011 with Gource}}
* [https://www.youtube.com/watch?v=_ZOQSn5tyqQ GFOSS.it video] (in Italian with English subtitles)
* [https://www.youtube.com/watch?v=BhqzZAEh_wQ&feature=channel_page Various GFOSS videos: GRASS and QGIS]
* [https://wiki.osgeo.org/wiki/FOSS_for_GIS_video_tutorials_and_screencasts FOSS for GIS video tutorials and screencasts] (OSGeo)
* [https://www.uni-koblenz-landau.de/landau/fb7/umweltwissenschaften/landscape-ecology/Teaching/geostat GEOSTAT2011 GRASS GIS video tutorials]

How to create an own screencast? See [[Movies#Q:_How_to_create_a_screencast_.28for_video_tutorials_etc.29.3F|here]]

=== OSGeo Foundation material ===

* [https://www.osgeo.org/about/branding-material/ OSGeo related promotion material] including GRASS (PDFs, Powerpoint-, OpenOffice- & Scribus templates) and mailing list statistics
* OSGeo Marketing repository: https://github.com/OSGeo/osgeo/tree/master/marketing/ (Brochures, exhibition packs, etc).
* OSGeo GRASS Brochures:
** [https://github.com/OSGeo/osgeo/tree/master/marketing/print/one-page-info Brochures in various languages]
* [https://wiki.osgeo.org/wiki/FOSS_for_GIS_video_tutorials_and_screencasts FOSS for GIS video tutorials and screencasts]

=== Events logo ===
* [https://github.com/OSGeo/grass-promo/tree/master/events/community_sprints/ Community Sprint XXXX]: see subfolders

=== Communication & Support ===
* 11 [https://lists.osgeo.org/mailman/listinfo English mailing lists] (user, devel, Quality Assessment, ...), and 9 [https://grass.osgeo.org/about/community/ localized mailing lists]
* [irc://irc.libera.chat/grass IRC], see also [[IRC]]
* [https://www.osgeo.org/search_profile?SET=1&MUL_TECH%5B%5D=00015 Companies supporting GRASS]
* Press releases: [[Contact Databases]]

=== Project statistics ===

* [[GRASS mailing list community evolution]]
* [https://wiki.osgeo.org/wiki/VisibilityStats OSGeo Visibility Statistics] incl. GRASS GIS
* [https://wiki.osgeo.org/wiki/Project_Stats OSGeo Project Statistics] incl. GRASS GIS
* https://www.openhub.net/p/grass_gis/widgets:

<div style="margin:0; margin-top:10px; border:1px solid #dfdfdf; padding:0em 1em 1em 1em; background-color:#f8f8ff;">
Project Metrics provided by [https://www.openhub.net/p/grass_gis Ohloh].

{{#widget:Ohloh Project|id=3666|type=partner_badge}}
</div>

=== LiveDVD of OSGeo.org ===

* https://live.osgeo.org
**

=== See also ===

[[:Category:Promotion]] (GRASS Promotion Team)

[[Category: Community]]
[[Category: Promotion]]
[[Category: Branding]]

PSC Meeting 2026-08-14

2026-08-21T15:55:04Z

Neteler: +Wiki state (Mediawiki)

PSC Meeting 2026-08-14

2026-08-21T15:36:10Z

Neteler: /* Agenda */

2026-07-16T08:04:35Z

Neteler: Update Sponsors to numFOCUS

{{toc|right}}

Quick links: [[GRASS Community Meeting San Michele 2026|Meeting page]] | [[#Reports|Reports]] | [[GRASS_Community_Meeting_Prague_2024#Sponsors|Sponsors]]

== Organizing Team ==

* Initial planning: Luca Delucchi, Vaclav Petras, Veronica Andreo, Markus Neteler, Anna Petrasova
* Budget: Luca Delucchi, Vaclav Petras, Markus Neteler, Veronica Andreo
* Raising support: Vaclav Petras, Markus Neteler, Veronica Andreo
* Reimbursements:
* Venue: Luca Delucchi
* Meals: Luca Delucchi
* Agenda: Veronica Andreo, Anna Petrasova
* Wiki page: Anna Petrasova, Luca Delucchi, Vaclav Petras
* Virtual participant support:
* Promotion, invitations, and social media: Vaclav Petras, Veronica Andreo
* Photography: Veronica Andreo

== Tasks for participants ==

* Create section for you in the Reports section.
* List all the things you are working on in the section. Update the list each day. Include things you work on with other people.
* If you are or will be working on an issue or on a PR which is not originally submitted by you, assign yourself to the issue or PR. (You can unassign yourself later if you change your mind.)

== Reports ==

Per-person reports from the meeting (one <code>=== Name ===</code> section per participant.)

=== Markus Neteler ===

==== Jul 12 ====
* work on generating an auto-generated GRASS addons index covering all addons found with GitHub topic "[https://github.com/topics/grass-gis-addons grass-gis-addons]"
** part 1: add missing markdown manual files to all addons missing them (addons found on GitHub outside of "grass-addons": currently 71)
** part 2: developing of a script doing the git clone/compilation/manual page generation steps [https://github.com/OSGeo/grass-addons/pull/1782 PR#1782]
*** yet unsubmitted

==== Jul 13 ====
* cleanup of some old stale tickets
* work on SBOM implementation [https://github.com/OSGeo/grass/issues/7215 issue 7215]

==== Jul 14 ====
* work on SBOM implementation [https://github.com/OSGeo/grass/issues/7215 issue 7215]
** Discussed sbom formatting (SPDX vs CycloneDX) and changes that need to made for compliance.
** Draft [https://github.com/OSGeo/grass/pull/7698 PR#7698] (CycloneDX SBOM)
* work on SPDX header cleanup [https://github.com/OSGeo/grass/issues/4190 issue 4190]
** Draft [https://github.com/OSGeo/grass/pull/7716 PR#7716]

==== Jul 15 ====
* continuation of work on SPDX header cleanup, learned a lot about agents
* re-gained ssh access (thanks, strk and Regina!)
** to grass.osgeo.org - fixes for new website deployment method
** to grasswiki.osgeo.org - check for captcha removal

==== Jul 16 ====
* Update [[Sponsors]] to numFOCUS

=== Veronica Andreo ===

* Review grass-tutorials PRs [https://github.com/OSGeo/grass-tutorials/pull/116 #116], [https://github.com/OSGeo/grass-tutorials/pull/130 130], [https://github.com/OSGeo/grass-tutorials/pull/133 #133],[https://github.com/OSGeo/grass-tutorials/pull/135 #135], [https://github.com/OSGeo/grass-tutorials/pull/136 #136].
* Review grass-website PRs [https://github.com/OSGeo/grass-website/pull/169 169], [https://github.com/OSGeo/grass-website/pull/611 611], [https://github.com/OSGeo/grass-website/pull/613 613], [https://github.com/OSGeo/grass-website/pull/645 645].
* PRs and issues clean-up in tutorials and website.
* Fix conda submenu [https://github.com/OSGeo/grass-website/pull/643 643].
* Participated of the discussion on STDS integration into GUI with Anna and Stefan.
* Assisted Luca with local organization issues.
* Compiled list of voters for upcoming PSC elections in line with PSC criteria defined on [[PSC_Meeting_2024-06-14]].
** Went through grass, grass-addons, grass-promo, grass-website, grass-tutorials, rgrass and got contributors with at least one merged PR during the current and previous PSC mandates, i.e., as far as 2016.
** Check attendants to community meetings in the same period.
** Check contributions to QGIS related to GRASS in the same period.
** Processed all lists and compiled a file with unique names and emails.
* Pictures and social media posting.
* Managed to compile GRASS-dev in WSL.
* Tested [https://github.com/OSGeo/grass/pull/7707 grass#7077].
* Tested and reviewed [https://github.com/OSGeo/grass-addons/pull/641 grass-addons#641], [https://github.com/OSGeo/grass-addons/pull/1005 grass-addons#1005], [https://github.com/OSGeo/grass-addons/pull/1010 grass-addons#1010].

=== Corey White ===
'''12-07-2026'''

GRASS Website migration to Bootstrap 5 and sass-dart
* Addressing [https://github.com/OSGeo/grass-website/issues/600 Issue #600]
Current state
# [https://github.com/OSGeo/grass-website/pull/599 PR#599 (grass-website)] - Approved (pending PR#635 and PR#1783)
# [https://github.com/OSGeo/grass-website/pull/552 PR#552 (grass-website)] (devcontainer) - Closed (superseded by #599)
# PR B (grass-website)(bootstrap5-migration) - Pushed to fork, not opened. I'll open after #599 merges
# PR C (grass-website) (brand-tokens-single-source) - Pushed to fork, not opened. I'll open after PR B merges
# [https://github.com/OSGeo/grass-website/pull/635 PR#635 (grass-website)] - Build production site in CI and publish it as a release artifact
# [https://github.com/OSGeo/grass-addons/pull/1783 PR#1783 (grass-addons)] - Updates deploy website CRON job from the CI-built release artifact

'''13-07-2026'''
# [https://github.com/OSGeo/grass/pull/3826 PR#3826 (grass) v.ppa] - Split code into smaller lib functions, fix issues with original implementation, and updated tests.
# [https://github.com/OSGeo/grass/pull/7298 Reviewed PR#7298] - grass.script: add create_mapset function
# Got t.stac tutorial reviewed by Vero
# [https://github.com/OSGeo/grass-website/pull/635 PR#635 (grass-website)] - '''(Merged)''' Build production site in CI and publish it as a release artifact
# [https://github.com/OSGeo/grass-website/pull/637 PR#637 (grass-website)] - '''(Merged)''' Fix production build: inline Renovate-managed toolchain versions
# [https://github.com/OSGeo/grass-website/pull/639 PR#637 grass-website)] - '''(Merged)''' Add Renovate's helper preset to pin GitHub Actions to the full length SHA

'''14-07-2026'''
# [https://github.com/OSGeo/grass-website/pull/643 PR#643 (grass-website)] - '''(Reviewed/Merged)''' Menu entries: Use uppercase for Conda submenu
# [https://github.com/OSGeo/grass-addons/pull/1783 PR#1783 (grass-addons)] - '''(Approved)''' Updates deploy website CRON job from the CI-built release artifact
# [https://github.com/OSGeo/grass-website/pull/644 PR#644 (grass-website)] - '''(Approved)''' Migrate markup to Bootstrap 5 and drop jQuery
# [https://github.com/OSGeo/grass-website/pull/645 PR#645 (grass-website)] - '''(In-Review)''' Single-source brand tokens; remove orphaned style.css (issue #600)
# [https://github.com/OSGeo/grass-website/pull/646 PR#645 (grass-website)] - '''(In-Review)''' Split production artifact workflow into build and deploy jobs
# [https://github.com/OSGeo/grass-addons/pull/1641 PR#1641 (grass-addons)] - '''(Merged)''' t.stac: fixed issue with download and import asset potentially overwhelming network.
# [https://github.com/OSGeo/grass/pull/3826 PR#3826 (grass) v.ppa] - '''(In-Review)''' Split code into smaller lib functions, fix issues with original implementation, updated tests, and images to docs
# Discussed sbom formatting (SPDX vs CycloneDX) and changes that need to made for compliance.

'''15-07-2026'''
# [https://github.com/OSGeo/grass-addons/pull/1788 PR#1788 (grass-addons)] - '''(Draft)''' Create new r.soils.rosetta addon.
# [https://github.com/OSGeo/grass-addons/pull/1336 PR#1336 (grass-addons)] - '''(Closed)''' Update python script shebang line to python3
# [https://github.com/OSGeo/grass/pull/7298 PR#7298 (grass)] - '''(Reviewed/Approved)''' grass.script: add create_mapset function
# [https://github.com/OpenPlainsInc/grass-obsidian (grass-obsidian)] - '''(Published)''' Opened up the OpenPlains grass-obsidian plugin that allows you to review your grass project from your obsidian notes.
# [https://github.com/OSGeo/grass-website/pull/646 PR#645 (grass-website)] - '''(Merged)''' Split production artifact workflow into build and deploy jobs
# [https://github.com/OSGeo/grass-website/pull/599 PR#599 (grass-website)] - '''(Merged)''' Hugo dart scss
# [https://github.com/OSGeo/grass-website/pull/644 PR#644 (grass-website)] - '''(Merged)''' Migrate markup to Bootstrap 5 and drop jQuery
# [https://github.com/OSGeo/grass-website/pull/645 PR#645 (grass-website)] - '''(Merged)''' Single-source brand tokens; remove orphaned style.css (issue #600)
# [https://github.com/OSGeo/grass-addons/pull/1783 PR#1783 (grass-addons)] - '''(Merged)''' Updates deploy website CRON job from the CI-built release artifact
# [https://github.com/OSGeo/grass-website/issues/636 Issue#636 (grass-website] - '''(Closed)''' Add zizmor to the checks run
# [https://github.com/OSGeo/grass/pull/7703 PR#7703 (grass)] - '''(Open)''' python: Use argument lists instead of shell=True for subprocess
# [https://github.com/OSGeo/grass/pull/7713 PR#7713 (grass)] - '''(Open)''' checks: Mark justified partial-path subprocess calls as nosec B607
# [https://github.com/OSGeo/grass/pull/7698 PR#7698 (grass)] - '''(Reviewed)'''CI: add CycloneDX SBOM generation for releases
# [https://github.com/OSGeo/grass-website/pull/583 PR#583 (grass-website)] '''(Closed)''' Update brand download dropdowns to Bootstrap 5 namespaced attributes

'''15-07-2026'''
# [https://github.com/OSGeo/grass-website/issues/600 (grass-website)] '''(Closed)''' Migrating to Bootstrap v5 from v3

=== Anna Petrasova ===
==== Jul 12 ====
* Review of [https://github.com/OSGeo/grass/pull/7659 #7659], [https://github.com/OSGeo/grass/pull/7599 #7599]
* Finish v.geometry tool: [https://github.com/OSGeo/grass/pull/7329 #7329]
* Working on markdown to man page conversion to remove old html pages:
** [https://github.com/OSGeo/grass/pull/7540 #7540] - merged
** [https://github.com/OSGeo/grass/pull/7674 #7674]
* Review website [https://github.com/OSGeo/grass-website/pull/599 #599]

==== Jul 13 ====

* Discussion with Vero and Stefan on GSoC project implementation
* Fixed bug in temporal library: [https://github.com/OSGeo/grass/pull/7681 #7681]
* t.info tests [https://github.com/OSGeo/grass/pull/7682 #7682]
* Review Jupyter GUI integration [https://github.com/OSGeo/grass/pull/5901 #5901]
* Discussion between me, Linda, Alen and Vashek about data catalog and regions

==== Jul 14 ====

* Fixing v.class causing flaky test [https://github.com/OSGeo/grass/pull/7692 #7692]
* Call with Saket and Stefan about the GSoC project
* Review [https://github.com/OSGeo/grass/pull/7608 #7608], [https://github.com/OSGeo/grass/pull/5901 #5901]
* Adding new icons for #7608.
* Cmake fixes [https://github.com/OSGeo/grass/pull/7720 #7720]

==== July 15 ====
* temporal fixes [https://github.com/OSGeo/grass/pull/7717 #7717]
* over 10 PRs reviewed
* fix temporal with 3.14 [https://github.com/OSGeo/grass/pull/7724 #7724]

==== July 16 ====

=== Edouard Choinière ===
==== 2026-07-11 ====
* Discussion with Corey White on trying to build docs with Zensical, and dropping Sphinx for [https://zensical.org/docs/setup/extensions/mkdocstrings/ mkdocstrings]
* Discussion with Vaclav Petras on Windows builds and Fable:
** The nsis installer had a change to do (as debugged last year by me in [https://github.com/OSGeo/grass/issues/5663 #5663]), but we don't know how to do it well. We suggested to let Anthropic's Fable try to do it before it stopped being included in the Claude subscription.
** For us to try out the fixed nsis installer script, Fable should be able to create the installer in CI. It is being tried in [https://github.com/echoix/grass/pull/664 echoix#664]/[https://github.com/wenzeslaus/grass/pull/12 wenzeslaus#12]
** Also suggested to use Fable to attempt to solve issues in a pending Sphinx PR that we were stuck for too long, (Stcuk PR: [https://github.com/OSGeo/grass/pull/7526 #7526], result: [https://github.com/wenzeslaus/grass/pull/11 wenzeslaus#11])
==== 2026-07-12 ====
* Got PRs merged: [https://github.com/OSGeo/grass/pull/7660 #7660], [https://github.com/OSGeo/grass/pull/7659 #7659],
* Created follow-up PR for sscanf: [https://github.com/OSGeo/grass/pull/7673 #7673]
* Discussed with Stefan Blumentrath:
** temporal init, choice of his PR or another contributor
** Discussed AI findings on various files accumulated in the last weeks: most are valid and should be filed.
* Reviewed PRs: [https://github.com/OSGeo/grass-addons/pull/641 grass-addons#641], [https://github.com/OSGeo/grass/pull/7635 #7635], [https://github.com/OSGeo/grass/pull/7671 #7671], [https://github.com/OSGeo/grass/pull/7669 #7669]
* Video call on FHS
* First review of Fable windows installer in CI on [https://github.com/echoix/grass/pull/664 echoix#664]

==== 2026-07-13 ====
* Reviewed PRs: [https://github.com/OSGeo/grass/pull/7663 #7663], [https://github.com/OSGeo/grass-website/pull/635 grass-website#635], [https://github.com/OSGeo/grass/pull/7337 #7337], [https://github.com/OSGeo/grass/pull/7672 #7672], [https://github.com/OSGeo/grass/pull/7684 #7684], [https://github.com/OSGeo/grass/pull/7687 #7687]
* Worked on the last sscanf CodeQL alert, for [https://github.com/OSGeo/grass/pull/7673 #7673]
* Tested out windows standalone installer built in CI [https://github.com/echoix/grass/pull/664 echoix#664]. Almost works, as it installs, but it doesn't start because of a path error. Wrote some notes about windows compilation in CI in relation to addons in Vashek's google doc.
* Wrote notes on the windows build script having two versions, where OSGeo4W uses a different one than the one we use in CI for our tests, and they diverged
* Submitted PR of AI findings for tests of g.md2man [https://github.com/OSGeo/grass/pull/7679 #7679]
* Configured CI required checks to not wait for successful checks during the code sprint, with the new rights given to me. Discussed with Vashek on what approach we'd want for the 4 ubuntu job configurations.
** Commented on an issue closed today [https://github.com/OSGeo/grass/issues/1313 #1313] about cppcheck: cppcheck could be useful to cover a bit more configuration combinations, but as discussed, only being to compile would only get us so far without testing.
* Discussion with Vashek on AI policy and approach to use with AI, low-quality contributors; Approach on renovate updates; Wishes on release cadence
* Multiple reviews and pair brainstorming on grass-website with Corey White, including [https://github.com/OSGeo/grass-website/pull/635 grass-website#635], [https://github.com/OSGeo/grass-website/pull/637 grass-website#637], [https://github.com/OSGeo/grass-website/pull/639 grass-website#639], [https://github.com/OSGeo/grass-website/pull/634 grass-website#634], [https://github.com/OSGeo/grass-website/pull/640 grass-website#640]
* Worked on CMake formatting, moving forward the PR a contributor opened for Gersemi, PR [https://github.com/OSGeo/grass/pull/7663 #7663], discussed weird finding with Vashek, lead to issue [https://github.com/OSGeo/grass/issues/7686 #7686]. To be continued the next day.
* Opened PR [https://github.com/OSGeo/grass/pull/7685 #7685] (merged), [https://github.com/OSGeo/grass/pull/7683 #7683] (needs more work/investigation), [https://github.com/OSGeo/grass/pull/7680 #7680] (merged)
* Opened issue to add zizmor to grass-website tools used to check, either local or CI [https://github.com/OSGeo/grass-website/issues/636 grass-website#636]

==== 2026-07-14 ====
* (Early night) Merge PR that updates minimum Python version to 3.11, needed to change the required checks in order to do so. [https://github.com/OSGeo/grass/pull/7684 #7684].
** In the morning, update PRs which were most probably ready, and needed the check passing, like [https://github.com/OSGeo/grass/pull/7329 #7329], [https://github.com/OSGeo/grass/pull/7635 #7635], [https://github.com/OSGeo/grass/pull/7687 #7687]
* Review and/or merge [https://github.com/OSGeo/grass-website/pull/642 grass-website#642], [https://github.com/OSGeo/grass/pull/7674 #7674], [https://github.com/OSGeo/grass/pull/7689 #7689], [https://github.com/OSGeo/grass/pull/7688 #7688], [https://github.com/OSGeo/grass/pull/7690 #7690], [https://github.com/OSGeo/grass/pull/7699 #7699], [https://github.com/OSGeo/grass/pull/7697 #7697], [https://github.com/OSGeo/grass/pull/7713 #7713], [https://github.com/OSGeo/grass/pull/7702 #7702], [https://github.com/OSGeo/grass/pull/7678 #7678], [https://github.com/OSGeo/grass-addons/pull/1786 grass-addons#1786]
* Long review and analysis of [https://github.com/OSGeo/grass-website/pull/646 grass-website#646], coming from a discussion earlier on that using a single workflow to build, but split the deploy part in order to run separately.
* Work on CMake formatting tool: Finally ended up replacing [https://github.com/OSGeo/grass/pull/7663 #7663] with [https://github.com/OSGeo/grass/pull/7696 #7696]. Will close issue [https://github.com/OSGeo/grass/issues/7346 #7346] and [https://github.com/OSGeo/grass/issues/7686 #7686]. Opened issues with the tool's repo [https://github.com/BlankSpruce/gersemi/issues/123], [https://github.com/BlankSpruce/gersemi/issues/124], and [https://github.com/BlankSpruce/gersemi/issues/122] (the previous day).
* Help Stefan Blumentrath's son get started with finding simple ruff rules to fix.
* Work with Antonio Galea on making windows standalone installer + addons work without the old server. The installer now works. [https://github.com/echoix/grass/pull/664 echoix#664]
* Reviewing PR by navigating types in dynamic gui code [https://github.com/OSGeo/grass/pull/7693 #7693]
* More precise discussion with team on what renovate grouping strategy to use.
* Discussion with Vashek on python version support policy.
* Created PR [https://github.com/OSGeo/grass/pull/7718 #7718] (merged)

==== 2026-07-15 ====
* Merged [https://github.com/OSGeo/grass/pull/7699 #7699]
* Review issue [https://github.com/OSGeo/grass/issues/7646 #7646]
* Created PR [https://github.com/OSGeo/grass/pull/7722 #7722] (merged), [https://github.com/OSGeo/grass/pull/7723 #7723]
* Review PR [https://github.com/OSGeo/grass/pull/7687 #7687], [https://github.com/OSGeo/grass-website/pull/646 grass-website#646], [https://github.com/OSGeo/grass-addons/pull/1769 grass-addons#1769], [https://github.com/OSGeo/grass-addons/pull/1785 grass-addons#1785], [https://github.com/OSGeo/grass/pull/7676 #7676], [https://github.com/OSGeo/grass-website/pull/645 grass-website#645], [https://github.com/OSGeo/grass/pull/5656 #5656], [https://github.com/OSGeo/grass-addons/pull/1791 grass-addons#1791]
* Try to get [https://github.com/OSGeo/grass/pull/7635 #7635] merged (update after other PR fixed test).
* Finished editing [https://github.com/OSGeo/grass/pull/7693 #7693]
* Worked again on CMake formatting, creating stubs for unrecognized functions [https://github.com/OSGeo/grass/pull/7696 #7696]
* Create draft rulesets for the grass-website repo.
* Debugged [https://github.com/OSGeo/grass/pull/7683 #7683] for codecov to work on macOS runners configured to build grass
* Discussion with Anna on the viability of MkDocs, alternatives, and how the attempt on using Zensical turned out. Zensical is missing at least tag listing pages.

==== 2026-07-16 ====
* Applied the fixes for [https://github.com/OSGeo/grass/pull/7683 #7683] to work.

=== Vaclav Petras ===

==== 2026-07-12 ====

* Reviews and discussion on FHS (video call, [https://github.com/OSGeo/grass/pull/5630 5630], [https://github.com/wenzeslaus/grass/pull/10 my fork PR 10])
* Test reviews: [https://github.com/OSGeo/grass/pull/7675 #7675]
* Windows distribution reviews: [https://github.com/OSGeo/grass/issues/5663 #5663]
* Sphinx reviews: [https://github.com/OSGeo/grass/pull/7526 #7526]
* RegionManager discussion ([https://github.com/OSGeo/grass/pull/7599 7599])
* Parson allocation review: [https://github.com/OSGeo/grass/pull/7208 7208]

==== 2026-07-13 ====

* Reduce Sphinx warnings

==== 2026-07-14 ====

* Update RFC for updating Python versions which also sets up precedence for RFC amendments.
* Review v.class undefined behavior PR
* Reduce Sphinx warnings
* Port old in-package grass.pygrass unit tests to pytest

=== Stefan Blumentrath ===
==== 2026-07-12 ====
Opened PRs: [https://github.com/OSGeo/grass/pull/7672 #7672]

Reviewed: [https://github.com/OSGeo/grass/pull/7670 #7670], [https://github.com/OSGeo/grass/pull/7671 #7671]

Closed PRs: [https://github.com/OSGeo/grass/pull/7644 #7644]

==== 2026-07-13 ====

Discussed options for handling STDS in the GUI

Opened PRs: [https://github.com/OSGeo/grass/pull/7678 #7678]

Reviewed PRs: [https://github.com/OSGeo/grass/pull/7670 #7670]

Merged PRs: [https://github.com/OSGeo/grass/pull/7672 #7672]

Closed PRs: [https://github.com/OSGeo/grass/pull/7671 #7671]

==== 2026-07-14 ====

Opened PRs: [https://github.com/OSGeo/grass/pull/7707 #7707]

Reviewed PRs: [https://github.com/OSGeo/grass/pull/7670 #7670]

==== 2026-07-15 ====

Reviewed PRs: [https://github.com/OSGeo/grass/pull/7682 #7682], [https://github.com/OSGeo/grass/pull/7714 #7714], [https://github.com/OSGeo/grass/pull/7670 #7670]

Closed PRs: [https://github.com/OSGeo/grass/pull/7707 #7707]

=== Luca Delucchi ===

* All the local organizing (Thank you, Luca!)

==== Website ====

* [https://github.com/OSGeo/grass-website/pull/169 Community map]

==== Addons ====
* [https://github.com/OSGeo/grass-addons/pull/1010/ t.rast.aggregate.seasons] new addon
* [https://github.com/OSGeo/grass-addons/pull/1005 t.rast.climatologies] new addon
* [https://github.com/OSGeo/grass-addons/pull/641 t.rast.vi] new addon
* [https://github.com/OSGeo/grass-addons/pull/1695 r.learn.predict] fix map history

=== Antonio Galea ===

==== Jul 14 ====
* support with the development of the (broken) winGRASS server replacement with a GitHub actions based Windows installer in CI on [https://github.com/echoix/grass/pull/664 echoix#664]

=== Tomaž Žagar ===
==== 2026-07-14 ====

* i.hyper addon: enhancement/bugfix when importing EnMAP example data: https://github.com/mazingaro/grass-addons/issues/12
* i,hyper addon: fixed radiance import: https://github.com/mazingaro/grass-addons/issues/16
* started to work on: https://github.com/mazingaro/grass-addons/issues/6

==== 2026-07-15 ====
* Continued to work on: https://github.com/mazingaro/grass-addons/issues/6
** first implemented it as Python addon - then switched to C addon as proposed for "better" integration (compilation when installing addon with g.extension) with https://github.com/YannChemin/libsixsv
** included https://github.com/YannChemin/i.hyper.atcorr to https://github.com/mazingaro/grass-addons/tree/i.hyper/src/imagery/i.hyper/i.hyper.atcorr
** added i.hyper.history handling to https://github.com/mazingaro/grass-addons/commit/97957ebf7723a2866a13926ded57d104a546036a
** testing and wondering

=== Matjaž Krebs ===
==== 2026-07-13 ====
* i.hyper addon: Started working on new importer module for emit data
==== 2026-07-14 ====
* i.hyper addon: working on importer module for emit data. Implementing and troubleshooting.
* i.hyper addon: working on i.hyper.export bug for exporting 3D raster cube from WGS 4326

=== Alen Mangafić ===
==== 2026-07-14 ====

* i.hyper addon: improved EnMAP import handling and related bugfixes: https://github.com/mazingaro/grass-addons/commit/0a30d9505, https://github.com/mazingaro/grass-addons/commit/36bf3e686
* i.hyper addon: improved metadata copying/validation and fixed i.hyper.preproc import behavior: https://github.com/mazingaro/grass-addons/commit/d4313f162, https://github.com/mazingaro/grass-addons/commit/a52012289, https://github.com/mazingaro/grass-addons/commit/ce6cdd25d, https://github.com/mazingaro/grass-addons/commit/6d994e853
* i.hyper addon: implemented spectral resampling and merged it into i.hyper: https://github.com/mazingaro/grass-addons/commit/38a8e073b, https://github.com/mazingaro/grass-addons/commit/c992bc90f
* helped Matjaž Krebs to survive the day
==== 2026-07-15 ====

* SPDX License AI monkey business TBA

Talk:GRASS Community Meeting San Michele 2026

2026-07-15T21:53:33Z

Neteler: /* Jul 15 */ re-gained ssh access

Talk:GRASS Community Meeting San Michele 2026

2026-07-15T08:57:38Z

Neteler: /* Jul 14 */

Talk:GRASS Community Meeting San Michele 2026

2026-07-15T06:14:40Z

Neteler: /* Antonio Galea */

Talk:GRASS Community Meeting San Michele 2026

2026-07-15T06:13:01Z

Neteler: +Antonio Galea

Talk:GRASS Community Meeting San Michele 2026

2026-07-14T17:20:11Z

Neteler: Draft SPDX header PR

Talk:GRASS Community Meeting San Michele 2026

2026-07-14T14:18:45Z

Neteler: /* Jul 14 */

Talk:GRASS Community Meeting San Michele 2026

2026-07-14T13:57:34Z

Neteler: MN SBOM

Talk:GRASS Community Meeting San Michele 2026

2026-07-14T13:10:43Z

Neteler: /* Reports */

Talk:GRASS Community Meeting San Michele 2026

2026-07-14T13:04:37Z

Neteler: /* Markus Neteler */

Talk:GRASS Community Meeting San Michele 2026

2026-07-12T21:41:28Z

Neteler: /* Reports */

Talk:GRASS Community Meeting San Michele 2026

2026-07-12T20:32:03Z

Neteler: /* Markus Neteler */

Talk:GRASS Community Meeting San Michele 2026

2026-07-12T17:15:55Z

Neteler: MN: auto-generated GRASS addons index

GRASS GSoC 2026 Parallelizing r.proj and Raster Processing Modules in GRASS

2026-07-12T08:11:46Z

Neteler: (added usage of ''{{cmd|xxx}}''

{| class="wikitable"
| '''Student Name''' || Kaushik Raja
|-
| '''Organization''' || [https://numfocus.org/ NumFOCUS]
|-
| '''Mentor Name''' || Huidae Cho, Anna Petrasova, Vaclav Petras
|-
| '''GitHub Fork''' || [https://github.com/krcoder123/grass View Repo]
|-
| '''LinkedIn Profile''' || [https://www.linkedin.com/in/kaushikrraja/ View LinkedIn]
|}
== Abstract ==
{{cmd|r.proj}} is one of the most commonly used modules in GRASS. It reprojects raster maps between coordinate systems. It has always been single threaded, so on modern multi core hardware most CPU cores sit idle and large reprojections take longer than they need to.

This project parallelizes r.proj and {{cmd|r.param.scale}} using OpenMP, with {{cmd|r.geomorphon}} planned as a third module. The two main obstacles are memory and the PROJ library. A naive parallel version holds the entire input map in RAM, which does not scale to large maps, and PROJ transformation objects cannot be shared between threads. The approach here processes the output map in horizontal bands sized to stay under a user controlled memory cap. For strongly tilted projections where even a single row of output needs more input than the cap allows, each band is further split into smaller column sections until every piece fits. Reading the input and computing the reprojection both run in parallel, with each thread using its own file descriptor and its own PROJ context, while the output is still written in row order so the result is exactly identical to the serial module.

r.param.scale, a terrain analysis module, was parallelized with the same memory bounded idea. Its sequential sliding window was replaced with a two level band and chunk design that honors the memory option. During that work a long standing data race was found in the GRASS math library and fixed. Together these changes give future GRASS contributors a reusable pattern for parallelizing raster modules under a memory constraint.
== Project Scope ==
# Parallelize r.proj with a memory bounded band design and a user controlled memory option
# Split bands into column sections for tilted projections that do not fit the memory cap at full width
# Give each thread its own PROJ context through new gproj library functions
# Parallelize input reading with per thread file descriptors
# Parallelize r.param.scale with a band and chunk design that honors the memory option
# Find and fix the data race in G_ludcmp in the GRASS math library
# Verify every parallel version produces output exactly identical to the serial version
# Benchmark all modules across thread counts
# Parallelize r.geomorphon as a third module
# Document all parallelized modules
== Timeline ==
{| class="wikitable"
!Period !! Timeline !! Tasks !! Status
|-
| Community Bonding Period
| May 1 - May 25
|
# Thread safety audit of gprojects library calls
# Study readcell.c internals
# Set up benchmarking infrastructure
# Source audit of remaining modules
# Finalize dev environment
# Confirm benchmarks are reproducible
# Agree on implementation details with mentors
| Done
|-
| rowspan="8" | Official Coding Period
| May 25 - June 8
|
# Build r.proj proof of concept with RAM buffer and per thread PROJ contexts (PR #7185)
# Benchmark RAM buffer approach against tile cache approach
# Add user controlled memory option
# Build first r.param.scale parallel draft (PR #7236)
# Rule out a suspected Mac OpenMP bug, traced to benchmark setup
| Done
|-
| June 9 - June 22
|
# Redesign r.param.scale from a single strip into a two level band and chunk structure that honors the memory option, modeled on r.neighbors (PR #7440)
# Give each thread its own input access so threads no longer share one reader
# Measure 4.6x speedup at 8 threads, up from 2.7x before the redesign, with output identical to the serial module
# Trace a scaling dip to thread load imbalance using per thread timing, correlation of 0.99 between imbalance and slow runs, ruling out a CPU frequency explanation
# Find a data race in G_ludcmp in the GRASS math library affecting every parallel caller, prove it with ThreadSanitizer and a controlled toggle experiment, report it (issue #7539)
# Fix the race and verify with ThreadSanitizer showing 14 race reports before and 0 after, repeated test runs going from 10 failures in 100 to 0 in 20, and a 40 configuration bit identical output comparison
# Check every caller of the fixed function at runtime to confirm safety for dependent modules
# Debug CI failures across platforms including CMake PROJ linkage and unguarded OpenMP timer calls, resolve a git branch divergence, unskip and pass the pytest suites on Python 3.10 and 3.13, pass all 26 checks, mark PR #7440 ready for review
| Done
|-
| June 23 - July 6
|
# Design and build the band based r.proj (PR #7627)
# Size each band by projecting its edges back to the input to find the rows it needs
# Cut peak memory from 763 MB to 130 MB with identical output
# Measure 2.9x total and 5.2x compute speedup at 8 threads on a 105 million cell map
# Answer two rounds of mentor review
| Done
|-
| style="background:#ffdead;" | July 7 - July 11
|
# Submit midterm evaluation
# Fix two CI failures, a missing PROJ dependency in the CMake build and OpenMP timer calls breaking the no OpenMP build
# Parallelize input reading with per thread file descriptors, 1.9x faster reads, about 3.0x total
# Move per thread PROJ context handling into the gproj library as new API functions at maintainer request
# Measure which projections need column splitting with a standalone footprint tool
# Split bands into column sections so tilted reprojections that failed under the memory cap now complete, verified identical on three projections
# Cut the section sizing search from 54 seconds to 2.6 seconds
# Benchmark everything and present results to mentors
| Done
|-
| July 20 - August 3
|
# Speed up the section sizing search further by reusing neighboring band results
# Test whether pole covering sections complete when given more memory
# Build the tile cache fallback for pole covering sections
# Address code review feedback on PR #7627
| In progress
|-
| August 4 - August 11
|
# Parallelize bilinear, bicubic and lanczos interpolation in the band design
# r.geomorphon parallelization
|
|-
| August 12 - August 18
|
# Pre-commit fixes, manual pages, final PR polish
# Blog post for OSGeo Planet
|
|-
| Final Week
| August 19 - August 26
|
# Submit final evaluation
|
|}
== Reports ==
=== Community Bonding Period ===
=== Coding Period ===
== Log of Pull Requests ==
* [https://github.com/OSGeo/grass/pull/7440 PR #7440] - r.param.scale parallelization and G_ludcmp race fix, ready for review
* [https://github.com/OSGeo/grass/pull/7627 PR #7627] - r.proj parallelization with memory bounded bands, in review
* [https://github.com/OSGeo/grass/issues/7539 Issue #7539] - G_ludcmp data race report
* [https://github.com/OSGeo/grass/pull/7185 PR #7185] - r.proj proof of concept, superseded by #7627
* [https://github.com/OSGeo/grass/pull/7236 PR #7236] - r.param.scale proof of concept, superseded by #7440

GRASS Community Meeting San Michele 2026

2026-07-10T15:46:05Z

Neteler: be less mysterious

[[File:Sanmichele.png|frameless|center|1000px|San Michele all'Adige]]

{{toc|right}}

The ''GRASS Community Meeting'' for contributors and developers will be happening from '''July 11 - 19, 2026''' in [https://www.openstreetmap.org/relation/46990#map=12/46.1349/11.1947 San Michele all'Adige, Trentino, Italy].

== Sponsors ==

Sponsors make the event possible. Learn more about [https://grass.osgeo.org/contribute/sponsoring/ Sponsoring].

* [https://www.osgeo.org/ OSGeo]: 2500 USD (see [https://wiki.osgeo.org/w/index.php?title=GRASS_Community_Meeting_2026:_Budget budget]]).

[[File:Osgeo logo.png|none|left|alt=Light and dark green logo of OSGeo saying Your Open Source Compass|Open Source Geospatial Foundation]]

== Purpose ==
The ''GRASS Community Meeting'' is a great occasion for folks to support the development by actively contributing to the project in different ways. These include source code updates, documentation (manuals, wiki, tutorials), translations, website improvements or likewise. The community meeting is also a get-together where supporters, contributors, power users and developers make decisions and tackle larger problems related to the project, discuss and collaboratively resolve bugs, plan the direction for the project and work on new features. We welcome people committed to improving the GRASS project and the interfaces to QGIS, GDAL, PostGIS, R, OGC Services and others.

The focus is on GRASS maintenance, and interaction with other projects. Many maintenance tasks, infrastructure changes, and planning of large changes especially benefits from maintainers being in one place and time zone. While the specific topics highly depend on the participants, we will prioritize topics which require highly synchronous collaboration, such as the CMake build system transition and API transitions. The [https://grass.osgeo.org/news/2025_05_27_grass_dev_summit_report/ 2025 event report] gives an overview of what was achieved last year.

We do require participants to work on GRASS or connections to other projects. However, we leave them the freedom to work on what they think is the best contribution to the project given their skills and time available.

== Agenda ==

Agenda is being refined.

=== Saturday, July 11 ===

Day of arrival. Contact organizers (Luca, see FAQ below) if you are interested in individualized program or helping with organization.

=== Sunday, July 12 ===

* Hybrid meeting about 8.6.0 with Filesystem Hierarchy Standard and Jupyter in GUI updates

=== Monday, July 13 ===

* Filesystem Hierarchy Standard ([https://en.wikipedia.org/wiki/Filesystem_Hierarchy_Standard FHS])
* Updating the GRASS Roadmap
* New '''Windows build server''' needed for addon provisioning and to get rid of "windows-2022 build and tests" (<code>ERROR: Cannot open URL <http://wingrass.fsv.cvut.cz/grass85/addons/grass-8.5.1dev/r.stream.distance.zip>: HTTP Error 404: Not Found</code>)

=== Tuesday, July 14 ===

* [[GSoC]] (may be moved to different day)
* GeoAI

=== Wednesday, July 15 ===

* Python API review
* Plan [[PSC]] elections

=== Thursday, July 16 ===

* Reducing PR backlog

=== Friday, July 17 ===

* Address issues for the upcoming [https://github.com/OSGeo/grass/milestone/29 8.6.0 release]

=== Saturday, July 18 ===

* Website review: fix the serious bootstrap mixup and broken sitemap bugs

=== Sunday, July 19 ===

Day of departure.

== Participation ==

Please add your name here:

{|class="wikitable sortable" border="2" cellspacing="0" cellpadding="4" rules="all" style="margin:1em 1em 1em 0; border:solid 1px #AAAAAA; border-collapse:collapse; background-color:#edf9c7; font-size:95%; empty-cells:show;"
!width=50px|'''Number'''
!width=130px|'''Participant '''
!width=100px|'''Country'''
!width=100px|'''Arrival'''
!width=100px|'''Departure'''
!'''Topics'''
!'''Notes'''
|-
|1
| [[User:Lucadelu|Luca Delucchi]]
| Italy
|
|
|
|
|-
|2
| [[User:wenzeslaus|Vaclav Petras]]
| United States
| 11.07.
| 19.07.
| grass.tools, pytest, subcommands, reviews
|
|-
|3
| [[User:Annakrat|Anna Petrasova]]
| United States
| 11.07.
| 19.07.
| GSoC, reviews, PR backlog, tutorials
|
|-
|4
| [[User:Neteler|Markus Neteler]]
| Germany
| 06.07.
| 18.07.
| documentation, website, state of GRASS support in QGIS 3.x/4.x, knowledge-transfer
|
|-
|5
| [[User:Sbl|Stefan Blumentrath]]
| Norway
| 11.07. (presumably)
| 18.07. (presumably)
| Handling Copernicus data with GRASS / actinia
|
|-
|6
| [[User:Hellik|Helmut Kudrnovsky]]
| Austria
|
|
|
|
|-
|7
| [[User:Veroandreo|Verónica Andreo]]
| Argentina
| 11.07.
| 19.07.
|
|
|-
|8
| [[User:Ctwhite|Corey White]]
| United States
| 11.07.
| 19.07.
| grass.jupyter, documentation, website, reviews, tutorials
|
|-
|9
| [[User:Echoix|Edouard Choinière]]
| Canada
| 11.07. (presumably)
| 19.07. (presumably)
| Reviews, CI, pytest, Windows GUI, i18n, undecided
|
|-
|10
| [[User:Mazingaro|Alen Mangafić]]
| Slovenia
| 13.07.
| 17.07.
| i.hyper: [https://grass.osgeo.org/grass-stable/manuals/addons/i.hyper.html Road Map] fulfilling; State of GRASS @FOSS4G 2026
|
|-
|11
| Tomaž Žagar
| Slovenia
| 13.07.
| 17.07.
| i.hyper: [https://grass.osgeo.org/grass-stable/manuals/addons/i.hyper.html Road Map] fulfilling
|
|-
|12
| Matjaž Krebs
| Slovenia
| 13.07.
| 17.07.
| i.hyper: [https://grass.osgeo.org/grass-stable/manuals/addons/i.hyper.html Road Map] fulfilling
|
|-
|}

Registration is free; participants cover their own travel and lodging (see below), often with employer support — thank you. Ideally we'd reimburse everyone, and every [https://numfocus.org/donate-to-grass donation] or [https://grass.osgeo.org/contribute/sponsoring/ employer sponsorship] of the project helps us get closer.

== Venue ==
The meeting will be hosted at [https://fmach.it/ Fondazione Edmund Mach] (FEM) in San Michele all'Adige, Trentino, Italy — about 15 km north of Trento. FEM is a research and education center with on-site facilities that allow participants to work, sleep, and eat in the same location.

[https://maps.app.goo.gl/5YEuEts6qXvky7HD9 Map]

=== Getting there ===

San Michele all'Adige is reachable by train on the Trento–Bolzano line (Trento or Mezzocorona station), with frequent connections from Trento (~15 minutes) and Verona (~1 hour). The nearest airports are Verona (VRN), Venice Marco Polo (VCE) and Treviso (TSF), Milan Bergamo (BGY), Malpensa (MXP), and Linate (LIN), Bologna (BLQ), and Innsbruck (INN) in Austria. Trento is also the host city of FOSS4G Italy 2026 (July 9–11), making it convenient to combine both events.

From Trento main train station you need to move to Ferrovia Trento-Malè (FTM) train station (few minutes by walk, https://www.openstreetmap.org/#map=17/46.072739/11.120814) and there take a train to Grumo/San Michele all'Adige. Train timetable is [https://www.trentinotrasporti.it/images/allegati/ferrovia/ftm/FTM%20est2026%20-%20ANDATA.pdf here], the opposite way is [https://www.trentinotrasporti.it/images/allegati/ferrovia/ftm/FTM%20est2026%20-%20RITORNO.pdf this one]

Another possibility is to arrive with the main train (Ferrovie dello Stato) in Mezzocorona and here you can walk to San Michele (around 20 minutes by walk) or take the small train Trento-Malè from Mezzocorona Ferrovia station (in front of main train station https://www.openstreetmap.org/#map=18/46.206633/11.128024) and stop in Grumo/San Michele (you need to look for the [https://www.trentinotrasporti.it/images/allegati/ferrovia/ftm/FTM%20est2026%20-%20RITORNO.pdf way back schedule])

== Accommodation and Costs ==

''Registration is free''. However, participants should plan for the following costs:

* Travel
* Lodging

Participants can stay on-site at the FEM convitto (dormitory), keeping the community together for the full duration of the meeting:

* €35 per person per night
* Double and triple rooms (triples include a small kitchen)
* A mandatory on-site supervisor is required at €200 per night (flat fee, shared across the group)
* Family members are welcome to stay in the dormitory as well
* [https://cif.fmach.it/content/download/2701/78358/file/brochure_convitto.pdf Brochure]
* For '''lodging booking''' options: see [https://grasscommunitymeeting2026.eventbrite.it/ Eventbrite]

For anyone preferring alternative lodging, hotels and B&Bs are available in San Michele and nearby Trento.

Lunches on weekdays can be taken at the FEM canteen (mensa), located on the same campus. Details and pricing are being finalized.

== Individual Preparation ==

* Bring your own computer
* Bring {{wikipedia|AC power plugs and sockets|power adapter}} if needed (Italy: 230V, 50Hz, {{wikipedia|Europlug|Type C}}, {{wikipedia|Schuko|Type F}}, and {{wikipedia|AC power plugs and sockets: L|Type L}} sockets are common)
* Install git and the compiler tools, and come with a working GRASS development environment if possible. See [https://github.com/OSGeo/grass/blob/main/CONTRIBUTING.md here] for details.

== FAQ ==

* ''Is this a conference?''
** Talks or presentations may be included, but the purpose is to work together on the project. Among conference formats, the closest comparison would be a participatory workshop.
* ''Is this a hackathon?''
** While there is plenty of intensive coding, the meeting is not competitive. We meet to collaborate.
* ''Is the GRASS Community Meeting for developers only?''
** No, the meeting is open to all users, supporters, contributors, power users, and developers ''who want to make a meaningful contribution to the project''.
* ''What skills do I need?''
** Coding skills are not required. Contributions to documentation, tutorials, translations, website, and testing are all valuable. Practical help during the meeting, such as coordinating meals, photography, or reporting, is a real contribution too.
* ''Can I attend remotely?''
** The meeting is in-person, but everyone is welcome to use the same week for focused work on the project from wherever they are.
* ''What language is used during the meeting?''
** English is the working language, but you may hear several other languages spoken at the event.
* ''How was it last time?''
** Splendid! See [[GRASS Developer Summit Raleigh 2025]]!
* ''Where can I get help and more information about the community meeting?''
** Contact local organizer [[User:Lucadelu|Luca Delucchi]] (<tt><lucadeluge at gmail com></tt>) or [[User:wenzeslaus|Vaclav Petras]] (<tt><wenzeslaus at gmail com></tt>) for budget questions.
* ''What if I can't spend time on this?''
** Can you spend money instead? [https://numfocus.org/donate-to-grass Donate to GRASS through NumFOCUS] to help keep the project going.

[[Category: Workshops]]
[[Category: Code Sprint]]
[[Category: 2026]]

GRASS Community Meeting San Michele 2026

2026-07-10T15:36:58Z

Neteler: New Windows build server needed

[[File:Sanmichele.png|frameless|center|1000px|San Michele all'Adige]]

{{toc|right}}

The ''GRASS Community Meeting'' for contributors and developers will be happening from '''July 11 - 19, 2026''' in [https://www.openstreetmap.org/relation/46990#map=12/46.1349/11.1947 San Michele all'Adige, Trentino, Italy].

== Sponsors ==

Sponsors make the event possible. Learn more about [https://grass.osgeo.org/contribute/sponsoring/ Sponsoring].

* [https://www.osgeo.org/ OSGeo]: 2500 USD (see [https://wiki.osgeo.org/w/index.php?title=GRASS_Community_Meeting_2026:_Budget budget]]).

[[File:Osgeo logo.png|none|left|alt=Light and dark green logo of OSGeo saying Your Open Source Compass|Open Source Geospatial Foundation]]

== Purpose ==
The ''GRASS Community Meeting'' is a great occasion for folks to support the development by actively contributing to the project in different ways. These include source code updates, documentation (manuals, wiki, tutorials), translations, website improvements or likewise. The community meeting is also a get-together where supporters, contributors, power users and developers make decisions and tackle larger problems related to the project, discuss and collaboratively resolve bugs, plan the direction for the project and work on new features. We welcome people committed to improving the GRASS project and the interfaces to QGIS, GDAL, PostGIS, R, OGC Services and others.

The focus is on GRASS maintenance, and interaction with other projects. Many maintenance tasks, infrastructure changes, and planning of large changes especially benefits from maintainers being in one place and time zone. While the specific topics highly depend on the participants, we will prioritize topics which require highly synchronous collaboration, such as the CMake build system transition and API transitions. The [https://grass.osgeo.org/news/2025_05_27_grass_dev_summit_report/ 2025 event report] gives an overview of what was achieved last year.

We do require participants to work on GRASS or connections to other projects. However, we leave them the freedom to work on what they think is the best contribution to the project given their skills and time available.

== Agenda ==

Agenda is being refined.

=== Saturday, July 11 ===

Day of arrival. Contact organizers if you are interested in individualized program or helping with organization.

=== Sunday, July 12 ===

* Hybrid meeting about 8.6.0 with FHS and Jupyter in GUI updates

=== Monday, July 13 ===

* FHS
* Updating the GRASS Roadmap
* New '''Windows build server''' needed for addon provisioning and to get rid of "windows-2022 build and tests" (<code>ERROR: Cannot open URL <http://wingrass.fsv.cvut.cz/grass85/addons/grass-8.5.1dev/r.stream.distance.zip>: HTTP Error 404: Not Found</code>)

=== Tuesday, July 14 ===

* GSoC (may be moved to different day)
* GeoAI

=== Wednesday, July 15 ===

* Python API review
* Plan PSC elections

=== Thursday, July 16 ===

* Reducing PR backlog

=== Friday, July 17 ===

* Address issues for 8.6.0 release

=== Saturday, July 18 ===

* Website review

=== Sunday, July 19 ===

Day of departure.

== Participation ==

Please add your name here:

{|class="wikitable sortable" border="2" cellspacing="0" cellpadding="4" rules="all" style="margin:1em 1em 1em 0; border:solid 1px #AAAAAA; border-collapse:collapse; background-color:#edf9c7; font-size:95%; empty-cells:show;"
!width=50px|'''Number'''
!width=130px|'''Participant '''
!width=100px|'''Country'''
!width=100px|'''Arrival'''
!width=100px|'''Departure'''
!'''Topics'''
!'''Notes'''
|-
|1
| [[User:Lucadelu|Luca Delucchi]]
| Italy
|
|
|
|
|-
|2
| [[User:wenzeslaus|Vaclav Petras]]
| United States
| 11.07.
| 19.07.
| grass.tools, pytest, subcommands, reviews
|
|-
|3
| [[User:Annakrat|Anna Petrasova]]
| United States
| 11.07.
| 19.07.
| GSoC, reviews, PR backlog, tutorials
|
|-
|4
| [[User:Neteler|Markus Neteler]]
| Germany
| 06.07.
| 18.07.
| documentation, website, state of GRASS support in QGIS 3.x/4.x, knowledge-transfer
|
|-
|5
| [[User:Sbl|Stefan Blumentrath]]
| Norway
| 11.07. (presumably)
| 18.07. (presumably)
| Handling Copernicus data with GRASS / actinia
|
|-
|6
| [[User:Hellik|Helmut Kudrnovsky]]
| Austria
|
|
|
|
|-
|7
| [[User:Veroandreo|Verónica Andreo]]
| Argentina
| 11.07.
| 19.07.
|
|
|-
|8
| [[User:Ctwhite|Corey White]]
| United States
| 11.07.
| 19.07.
| grass.jupyter, documentation, website, reviews, tutorials
|
|-
|9
| [[User:Echoix|Edouard Choinière]]
| Canada
| 11.07. (presumably)
| 19.07. (presumably)
| Reviews, CI, pytest, Windows GUI, i18n, undecided
|
|-
|10
| [[User:Mazingaro|Alen Mangafić]]
| Slovenia
| 13.07.
| 17.07.
| i.hyper: [https://grass.osgeo.org/grass-stable/manuals/addons/i.hyper.html Road Map] fulfilling; State of GRASS @FOSS4G 2026
|
|-
|11
| Tomaž Žagar
| Slovenia
| 13.07.
| 17.07.
| i.hyper: [https://grass.osgeo.org/grass-stable/manuals/addons/i.hyper.html Road Map] fulfilling
|
|-
|12
| Matjaž Krebs
| Slovenia
| 13.07.
| 17.07.
| i.hyper: [https://grass.osgeo.org/grass-stable/manuals/addons/i.hyper.html Road Map] fulfilling
|
|-
|}

Registration is free; participants cover their own travel and lodging (see below), often with employer support — thank you. Ideally we'd reimburse everyone, and every [https://numfocus.org/donate-to-grass donation] or [https://grass.osgeo.org/contribute/sponsoring/ employer sponsorship] of the project helps us get closer.

== Venue ==
The meeting will be hosted at [https://fmach.it/ Fondazione Edmund Mach] (FEM) in San Michele all'Adige, Trentino, Italy — about 15 km north of Trento. FEM is a research and education center with on-site facilities that allow participants to work, sleep, and eat in the same location.

[https://maps.app.goo.gl/5YEuEts6qXvky7HD9 Map]

=== Getting there ===

San Michele all'Adige is reachable by train on the Trento–Bolzano line (Trento or Mezzocorona station), with frequent connections from Trento (~15 minutes) and Verona (~1 hour). The nearest airports are Verona (VRN), Venice Marco Polo (VCE) and Treviso (TSF), Milan Bergamo (BGY), Malpensa (MXP), and Linate (LIN), Bologna (BLQ), and Innsbruck (INN) in Austria. Trento is also the host city of FOSS4G Italy 2026 (July 9–11), making it convenient to combine both events.

From Trento main train station you need to move to Ferrovia Trento-Malè (FTM) train station (few minutes by walk, https://www.openstreetmap.org/#map=17/46.072739/11.120814) and there take a train to Grumo/San Michele all'Adige. Train timetable is [https://www.trentinotrasporti.it/images/allegati/ferrovia/ftm/FTM%20est2026%20-%20ANDATA.pdf here], the opposite way is [https://www.trentinotrasporti.it/images/allegati/ferrovia/ftm/FTM%20est2026%20-%20RITORNO.pdf this one]

Another possibility is to arrive with the main train (Ferrovie dello Stato) in Mezzocorona and here you can walk to San Michele (around 20 minutes by walk) or take the small train Trento-Malè from Mezzocorona Ferrovia station (in front of main train station https://www.openstreetmap.org/#map=18/46.206633/11.128024) and stop in Grumo/San Michele (you need to look for the [https://www.trentinotrasporti.it/images/allegati/ferrovia/ftm/FTM%20est2026%20-%20RITORNO.pdf way back schedule])

== Accommodation and Costs ==

''Registration is free''. However, participants should plan for the following costs:

* Travel
* Lodging

Participants can stay on-site at the FEM convitto (dormitory), keeping the community together for the full duration of the meeting:

* €35 per person per night
* Double and triple rooms (triples include a small kitchen)
* A mandatory on-site supervisor is required at €200 per night (flat fee, shared across the group)
* Family members are welcome to stay in the dormitory as well
* [https://cif.fmach.it/content/download/2701/78358/file/brochure_convitto.pdf Brochure]
* For '''lodging booking''' options: see [https://grasscommunitymeeting2026.eventbrite.it/ Eventbrite]

For anyone preferring alternative lodging, hotels and B&Bs are available in San Michele and nearby Trento.

Lunches on weekdays can be taken at the FEM canteen (mensa), located on the same campus. Details and pricing are being finalized.

== Individual Preparation ==

* Bring your own computer
* Bring {{wikipedia|AC power plugs and sockets|power adapter}} if needed (Italy: 230V, 50Hz, {{wikipedia|Europlug|Type C}}, {{wikipedia|Schuko|Type F}}, and {{wikipedia|AC power plugs and sockets: L|Type L}} sockets are common)
* Install git and the compiler tools, and come with a working GRASS development environment if possible. See [https://github.com/OSGeo/grass/blob/main/CONTRIBUTING.md here] for details.

== FAQ ==

* ''Is this a conference?''
** Talks or presentations may be included, but the purpose is to work together on the project. Among conference formats, the closest comparison would be a participatory workshop.
* ''Is this a hackathon?''
** While there is plenty of intensive coding, the meeting is not competitive. We meet to collaborate.
* ''Is the GRASS Community Meeting for developers only?''
** No, the meeting is open to all users, supporters, contributors, power users, and developers ''who want to make a meaningful contribution to the project''.
* ''What skills do I need?''
** Coding skills are not required. Contributions to documentation, tutorials, translations, website, and testing are all valuable. Practical help during the meeting, such as coordinating meals, photography, or reporting, is a real contribution too.
* ''Can I attend remotely?''
** The meeting is in-person, but everyone is welcome to use the same week for focused work on the project from wherever they are.
* ''What language is used during the meeting?''
** English is the working language, but you may hear several other languages spoken at the event.
* ''How was it last time?''
** Splendid! See [[GRASS Developer Summit Raleigh 2025]]!
* ''Where can I get help and more information about the community meeting?''
** Contact local organizer [[User:Lucadelu|Luca Delucchi]] (<tt><lucadeluge at gmail com></tt>) or [[User:wenzeslaus|Vaclav Petras]] (<tt><wenzeslaus at gmail com></tt>) for budget questions.
* ''What if I can't spend time on this?''
** Can you spend money instead? [https://numfocus.org/donate-to-grass Donate to GRASS through NumFOCUS] to help keep the project going.

[[Category: Workshops]]
[[Category: Code Sprint]]
[[Category: 2026]]

GRASS Community Meeting San Michele 2026

2026-07-09T08:25:22Z

Neteler: + state of GRASS support in QGIS 3.x/4.x

[[File:Sanmichele.png|frameless|center|1000px|San Michele all'Adige]]

{{toc|right}}

The ''GRASS Community Meeting'' for contributors and developers will be happening from '''July 11 - 19, 2026''' in [https://www.openstreetmap.org/relation/46990#map=12/46.1349/11.1947 San Michele all'Adige, Trentino, Italy].

== Sponsors ==

Sponsors make the event possible. Learn more about [https://grass.osgeo.org/contribute/sponsoring/ Sponsoring].

* [https://www.osgeo.org/ OSGeo]: 2500 USD (see [https://wiki.osgeo.org/w/index.php?title=GRASS_Community_Meeting_2026:_Budget budget]]).

[[File:Osgeo logo.png|none|left|alt=Light and dark green logo of OSGeo saying Your Open Source Compass|Open Source Geospatial Foundation]]

== Purpose ==
The ''GRASS Community Meeting'' is a great occasion for folks to support the development by actively contributing to the project in different ways. These include source code updates, documentation (manuals, wiki, tutorials), translations, website improvements or likewise. The community meeting is also a get-together where supporters, contributors, power users and developers make decisions and tackle larger problems related to the project, discuss and collaboratively resolve bugs, plan the direction for the project and work on new features. We welcome people committed to improving the GRASS project and the interfaces to QGIS, GDAL, PostGIS, R, OGC Services and others.

The focus is on GRASS maintenance, and interaction with other projects. Many maintenance tasks, infrastructure changes, and planning of large changes especially benefits from maintainers being in one place and time zone. While the specific topics highly depend on the participants, we will prioritize topics which require highly synchronous collaboration, such as the CMake build system transition and API transitions. The [https://grass.osgeo.org/news/2025_05_27_grass_dev_summit_report/ 2025 event report] gives an overview of what was achieved last year.

We do require participants to work on GRASS or connections to other projects. However, we leave them the freedom to work on what they think is the best contribution to the project given their skills and time available.

== Agenda ==

Agenda is being refined.

=== Saturday, July 11 ===

Day of arrival. Contact organizers if you are interested in individualized program or helping with organization.

=== Sunday, July 12 ===

* Hybrid meeting about 8.6.0 with FHS and Jupyter in GUI updates

=== Monday, July 13 ===

* FHS
* Updating the GRASS Roadmap

=== Tuesday, July 14 ===

* GSoC (may be moved to different day)
* GeoAI

=== Wednesday, July 15 ===

* Python API review
* Plan PSC elections

=== Thursday, July 16 ===

* Reducing PR backlog

=== Friday, July 17 ===

* Address issues for 8.6.0 release

=== Saturday, July 18 ===

* Website review

=== Sunday, July 19 ===

Day of departure.

== Participation ==

Please add your name here:

{|class="wikitable sortable" border="2" cellspacing="0" cellpadding="4" rules="all" style="margin:1em 1em 1em 0; border:solid 1px #AAAAAA; border-collapse:collapse; background-color:#edf9c7; font-size:95%; empty-cells:show;"
!width=50px|'''Number'''
!width=130px|'''Participant '''
!width=100px|'''Country'''
!width=100px|'''Arrival'''
!width=100px|'''Departure'''
!'''Topics'''
!'''Notes'''
|-
|1
| [[User:Lucadelu|Luca Delucchi]]
| Italy
|
|
|
|
|-
|2
| [[User:wenzeslaus|Vaclav Petras]]
| United States
| 11.07.
| 19.07.
| grass.tools, pytest, subcommands, reviews
|
|-
|3
| [[User:Annakrat|Anna Petrasova]]
| United States
| 11.07.
| 19.07.
| GSoC, reviews, PR backlog, tutorials
|
|-
|4
| [[User:Neteler|Markus Neteler]]
| Germany
| 06.07.
| 18.07.
| documentation, website, state of GRASS support in QGIS 3.x/4.x, knowledge-transfer
|
|-
|5
| [[User:Sbl|Stefan Blumentrath]]
| Norway
| 11.07. (presumably)
| 18.07. (presumably)
| Handling Copernicus data with GRASS / actinia
|
|-
|6
| [[User:Hellik|Helmut Kudrnovsky]]
| Austria
|
|
|
|
|-
|7
| [[User:Veroandreo|Verónica Andreo]]
| Argentina
| 11.07.
| 19.07.
|
|
|-
|8
| [[User:Ctwhite|Corey White]]
| United States
| 11.07.
| 19.07.
| grass.jupyter, documentation, website, reviews, tutorials
|
|-
|9
| [[User:Echoix|Edouard Choinière]]
| Canada
| 11.07. (presumably)
| 19.07. (presumably)
| Reviews, CI, pytest, Windows GUI, i18n, undecided
|
|-
|10
| [[User:Mazingaro|Alen Mangafić]]
| Slovenia
| 13.07.
| 17.07.
| i.hyper: [https://grass.osgeo.org/grass-stable/manuals/addons/i.hyper.html Road Map] fulfilling; State of GRASS @FOSS4G 2026
|
|-
|11
| Tomaž Žagar
| Slovenia
| 13.07.
| 17.07.
| i.hyper: [https://grass.osgeo.org/grass-stable/manuals/addons/i.hyper.html Road Map] fulfilling
|
|-
|12
| Matjaž Krebs
| Slovenia
| 13.07.
| 17.07.
| i.hyper: [https://grass.osgeo.org/grass-stable/manuals/addons/i.hyper.html Road Map] fulfilling
|
|-
|}

Registration is free; participants cover their own travel and lodging (see below), often with employer support — thank you. Ideally we'd reimburse everyone, and every [https://numfocus.org/donate-to-grass donation] or [https://grass.osgeo.org/contribute/sponsoring/ employer sponsorship] of the project helps us get closer.

== Venue ==
The meeting will be hosted at [https://fmach.it/ Fondazione Edmund Mach] (FEM) in San Michele all'Adige, Trentino, Italy — about 15 km north of Trento. FEM is a research and education center with on-site facilities that allow participants to work, sleep, and eat in the same location.

[https://maps.app.goo.gl/5YEuEts6qXvky7HD9 Map]

=== Getting there ===

San Michele all'Adige is reachable by train on the Trento–Bolzano line (Trento or Mezzocorona station), with frequent connections from Trento (~15 minutes) and Verona (~1 hour). The nearest airports are Verona (VRN), Venice Marco Polo (VCE) and Treviso (TSF), Milan Bergamo (BGY), Malpensa (MXP), and Linate (LIN), Bologna (BLQ), and Innsbruck (INN) in Austria. Trento is also the host city of FOSS4G Italy 2026 (July 9–11), making it convenient to combine both events.

From Trento main train station you need to move to Ferrovia Trento-Malè (FTM) train station (few minutes by walk, https://www.openstreetmap.org/#map=17/46.072739/11.120814) and there take a train to Grumo/San Michele all'Adige. Train timetable is [https://www.trentinotrasporti.it/images/allegati/ferrovia/ftm/FTM%20est2026%20-%20ANDATA.pdf here], the opposite way is [https://www.trentinotrasporti.it/images/allegati/ferrovia/ftm/FTM%20est2026%20-%20RITORNO.pdf this one]

Another possibility is to arrive with the main train (Ferrovie dello Stato) in Mezzocorona and here you can walk to San Michele (around 20 minutes by walk) or take the small train Trento-Malè from Mezzocorona Ferrovia station (in front of main train station https://www.openstreetmap.org/#map=18/46.206633/11.128024) and stop in Grumo/San Michele (you need to look for the [https://www.trentinotrasporti.it/images/allegati/ferrovia/ftm/FTM%20est2026%20-%20RITORNO.pdf way back schedule])

== Accommodation and Costs ==

''Registration is free''. However, participants should plan for the following costs:

* Travel
* Lodging

Participants can stay on-site at the FEM convitto (dormitory), keeping the community together for the full duration of the meeting:

* €35 per person per night
* Double and triple rooms (triples include a small kitchen)
* A mandatory on-site supervisor is required at €200 per night (flat fee, shared across the group)
* Family members are welcome to stay in the dormitory as well
* [https://cif.fmach.it/content/download/2701/78358/file/brochure_convitto.pdf Brochure]
* For '''lodging booking''' options: see [https://grasscommunitymeeting2026.eventbrite.it/ Eventbrite]

For anyone preferring alternative lodging, hotels and B&Bs are available in San Michele and nearby Trento.

Lunches on weekdays can be taken at the FEM canteen (mensa), located on the same campus. Details and pricing are being finalized.

== Individual Preparation ==

* Bring your own computer
* Bring {{wikipedia|AC power plugs and sockets|power adapter}} if needed (Italy: 230V, 50Hz, {{wikipedia|Europlug|Type C}}, {{wikipedia|Schuko|Type F}}, and {{wikipedia|AC power plugs and sockets: L|Type L}} sockets are common)
* Install git and the compiler tools, and come with a working GRASS development environment if possible. See [https://github.com/OSGeo/grass/blob/main/CONTRIBUTING.md here] for details.

== FAQ ==

* ''Is this a conference?''
** Talks or presentations may be included, but the purpose is to work together on the project. Among conference formats, the closest comparison would be a participatory workshop.
* ''Is this a hackathon?''
** While there is plenty of intensive coding, the meeting is not competitive. We meet to collaborate.
* ''Is the GRASS Community Meeting for developers only?''
** No, the meeting is open to all users, supporters, contributors, power users, and developers ''who want to make a meaningful contribution to the project''.
* ''What skills do I need?''
** Coding skills are not required. Contributions to documentation, tutorials, translations, website, and testing are all valuable. Practical help during the meeting, such as coordinating meals, photography, or reporting, is a real contribution too.
* ''Can I attend remotely?''
** The meeting is in-person, but everyone is welcome to use the same week for focused work on the project from wherever they are.
* ''What language is used during the meeting?''
** English is the working language, but you may hear several other languages spoken at the event.
* ''How was it last time?''
** Splendid! See [[GRASS Developer Summit Raleigh 2025]]!
* ''Where can I get help and more information about the community meeting?''
** Contact local organizer [[User:Lucadelu|Luca Delucchi]] (<tt><lucadeluge at gmail com></tt>) or [[User:wenzeslaus|Vaclav Petras]] (<tt><wenzeslaus at gmail com></tt>) for budget questions.
* ''What if I can't spend time on this?''
** Can you spend money instead? [https://numfocus.org/donate-to-grass Donate to GRASS through NumFOCUS] to help keep the project going.

[[Category: Workshops]]
[[Category: Code Sprint]]
[[Category: 2026]]

GRASS Community Meeting San Michele 2026

2026-07-06T07:09:47Z

Neteler: MN: update departure

[[File:Sanmichele.png|frameless|center|1000px|San Michele all'Adige]]

{{toc|right}}

The ''GRASS Community Meeting'' for contributors and developers will be happening from '''July 11 - 19, 2026''' in [https://www.openstreetmap.org/relation/46990#map=12/46.1349/11.1947 San Michele all'Adige, Trentino, Italy].

== Sponsors ==

Sponsors make the event possible. Learn more about [https://grass.osgeo.org/contribute/sponsoring/ Sponsoring].

* [https://www.osgeo.org/ OSGeo]: 2500 USD (see [https://wiki.osgeo.org/w/index.php?title=GRASS_Community_Meeting_2026:_Budget budget]]).

[[File:Osgeo logo.png|none|left|alt=Light and dark green logo of OSGeo saying Your Open Source Compass|Open Source Geospatial Foundation]]

== Purpose ==
The ''GRASS Community Meeting'' is a great occasion for folks to support the development by actively contributing to the project in different ways. These include source code updates, documentation (manuals, wiki, tutorials), translations, website improvements or likewise. The community meeting is also a get-together where supporters, contributors, power users and developers make decisions and tackle larger problems related to the project, discuss and collaboratively resolve bugs, plan the direction for the project and work on new features. We welcome people committed to improving the GRASS project and the interfaces to QGIS, GDAL, PostGIS, R, OGC Services and others.

The focus is on GRASS maintenance, and interaction with other projects. Many maintenance tasks, infrastructure changes, and planning of large changes especially benefits from maintainers being in one place and time zone. While the specific topics highly depend on the participants, we will prioritize topics which require highly synchronous collaboration, such as the CMake build system transition and API transitions. The [https://grass.osgeo.org/news/2025_05_27_grass_dev_summit_report/ 2025 event report] gives an overview of what was achieved last year.

We do require participants to work on GRASS or connections to other projects. However, we leave them the freedom to work on what they think is the best contribution to the project given their skills and time available.

== Agenda ==

Agenda is being refined.

=== Saturday, July 11 ===

Day of arrival. Contact organizers if you are interested in individualized program or helping with organization.

=== Sunday, July 12 ===

* Hybrid meeting about 8.6.0 with FHS and Jupyter in GUI updates

=== Monday, July 13 ===

* FHS
* Updating the GRASS Roadmap

=== Tuesday, July 14 ===

* GSoC (may be moved to different day)
* GeoAI

=== Wednesday, July 15 ===

* Python API review
* Plan PSC elections

=== Thursday, July 16 ===

* Reducing PR backlog

=== Friday, July 17 ===

* Address issues for 8.6.0 release

=== Saturday, July 18 ===

* Website review

=== Sunday, July 19 ===

Day of departure.

== Participation ==

Please add your name here:

{|class="wikitable sortable" border="2" cellspacing="0" cellpadding="4" rules="all" style="margin:1em 1em 1em 0; border:solid 1px #AAAAAA; border-collapse:collapse; background-color:#edf9c7; font-size:95%; empty-cells:show;"
!width=50px|'''Number'''
!width=130px|'''Participant '''
!width=100px|'''Country'''
!width=100px|'''Arrival'''
!width=100px|'''Departure'''
!'''Topics'''
!'''Notes'''
|-
|1
| [[User:Lucadelu|Luca Delucchi]]
| Italy
|
|
|
|
|-
|2
| [[User:wenzeslaus|Vaclav Petras]]
| United States
| 11.07.
| 19.07.
| grass.tools, pytest, subcommands, reviews
|
|-
|3
| [[User:Annakrat|Anna Petrasova]]
| United States
| 11.07.
| 19.07.
| GSoC, reviews, PR backlog, tutorials
|
|-
|4
| [[User:Neteler|Markus Neteler]]
| Germany
| 06.07.
| 18.07.
| documentation, website, reviews, tutorials, knowledge-transfer
|
|-
|5
| [[User:Sbl|Stefan Blumentrath]]
| Norway
| 11.07. (presumably)
| 18.07. (presumably)
| Handling Copernicus data with GRASS / actinia
|
|-
|6
| [[User:Hellik|Helmut Kudrnovsky]]
| Austria
|
|
|
|
|-
|7
| [[User:Veroandreo|Verónica Andreo]]
| Argentina
| 11.07.
| 19.07.
|
|
|-
|8
| [[User:Ctwhite|Corey White]]
| United States
| 11.07.
| 19.07.
| grass.jupyter, documentation, website, reviews, tutorials
|
|-
|9
| [[User:Echoix|Edouard Choinière]]
| Canada
| 11.07. (presumably)
| 19.07. (presumably)
| Reviews, CI, pytest, Windows GUI, i18n, undecided
|
|-
|10
| [[User:Mazingaro|Alen Mangafić]]
| Slovenia
| 13.07.
| 17.07.
| i.hyper: [https://grass.osgeo.org/grass-stable/manuals/addons/i.hyper.html Road Map] fulfilling; State of GRASS @FOSS4G 2026
|
|-
|11
| Tomaž Žagar
| Slovenia
| 13.07.
| 17.07.
| i.hyper: [https://grass.osgeo.org/grass-stable/manuals/addons/i.hyper.html Road Map] fulfilling
|
|-
|12
| Matjaž Krebs
| Slovenia
| 13.07.
| 17.07.
| i.hyper: [https://grass.osgeo.org/grass-stable/manuals/addons/i.hyper.html Road Map] fulfilling
|
|-
|}

Registration is free; participants cover their own travel and lodging (see below), often with employer support — thank you. Ideally we'd reimburse everyone, and every [https://numfocus.org/donate-to-grass donation] or [https://grass.osgeo.org/contribute/sponsoring/ employer sponsorship] of the project helps us get closer.

== Venue ==
The meeting will be hosted at [https://fmach.it/ Fondazione Edmund Mach] (FEM) in San Michele all'Adige, Trentino, Italy — about 15 km north of Trento. FEM is a research and education center with on-site facilities that allow participants to work, sleep, and eat in the same location.

[https://maps.app.goo.gl/5YEuEts6qXvky7HD9 Map]

=== Getting there ===

San Michele all'Adige is reachable by train on the Trento–Bolzano line (Trento or Mezzocorona station), with frequent connections from Trento (~15 minutes) and Verona (~1 hour). The nearest airports are Verona (VRN), Venice Marco Polo (VCE) and Treviso (TSF), Milan Bergamo (BGY), Malpensa (MXP), and Linate (LIN), Bologna (BLQ), and Innsbruck (INN) in Austria. Trento is also the host city of FOSS4G Italy 2026 (July 9–11), making it convenient to combine both events.

From Trento main train station you need to move to Ferrovia Trento-Malè (FTM) train station (few minutes by walk, https://www.openstreetmap.org/#map=17/46.072739/11.120814) and there take a train to Grumo/San Michele all'Adige. Train timetable is [https://www.trentinotrasporti.it/images/allegati/ferrovia/ftm/FTM%20est2026%20-%20ANDATA.pdf here], the opposite way is [https://www.trentinotrasporti.it/images/allegati/ferrovia/ftm/FTM%20est2026%20-%20RITORNO.pdf this one]

Another possibility is to arrive with the main train (Ferrovie dello Stato) in Mezzocorona and here you can walk to San Michele (around 20 minutes by walk) or take the small train Trento-Malè from Mezzocorona Ferrovia station (in front of main train station https://www.openstreetmap.org/#map=18/46.206633/11.128024) and stop in Grumo/San Michele (you need to look for the [https://www.trentinotrasporti.it/images/allegati/ferrovia/ftm/FTM%20est2026%20-%20RITORNO.pdf way back schedule])

== Accommodation and Costs ==

''Registration is free''. However, participants should plan for the following costs:

* Travel
* Lodging

Participants can stay on-site at the FEM convitto (dormitory), keeping the community together for the full duration of the meeting:

* €35 per person per night
* Double and triple rooms (triples include a small kitchen)
* A mandatory on-site supervisor is required at €200 per night (flat fee, shared across the group)
* Family members are welcome to stay in the dormitory as well
* [https://cif.fmach.it/content/download/2701/78358/file/brochure_convitto.pdf Brochure]
* For '''lodging booking''' options: see [https://grasscommunitymeeting2026.eventbrite.it/ Eventbrite]

For anyone preferring alternative lodging, hotels and B&Bs are available in San Michele and nearby Trento.

Lunches on weekdays can be taken at the FEM canteen (mensa), located on the same campus. Details and pricing are being finalized.

== Individual Preparation ==

* Bring your own computer
* Bring {{wikipedia|AC power plugs and sockets|power adapter}} if needed (Italy: 230V, 50Hz, {{wikipedia|Europlug|Type C}}, {{wikipedia|Schuko|Type F}}, and {{wikipedia|AC power plugs and sockets: L|Type L}} sockets are common)
* Install git and the compiler tools, and come with a working GRASS development environment if possible. See [https://github.com/OSGeo/grass/blob/main/CONTRIBUTING.md here] for details.

== FAQ ==

* ''Is this a conference?''
** Talks or presentations may be included, but the purpose is to work together on the project. Among conference formats, the closest comparison would be a participatory workshop.
* ''Is this a hackathon?''
** While there is plenty of intensive coding, the meeting is not competitive. We meet to collaborate.
* ''Is the GRASS Community Meeting for developers only?''
** No, the meeting is open to all users, supporters, contributors, power users, and developers ''who want to make a meaningful contribution to the project''.
* ''What skills do I need?''
** Coding skills are not required. Contributions to documentation, tutorials, translations, website, and testing are all valuable. Practical help during the meeting, such as coordinating meals, photography, or reporting, is a real contribution too.
* ''Can I attend remotely?''
** The meeting is in-person, but everyone is welcome to use the same week for focused work on the project from wherever they are.
* ''What language is used during the meeting?''
** English is the working language, but you may hear several other languages spoken at the event.
* ''How was it last time?''
** Splendid! See [[GRASS Developer Summit Raleigh 2025]]!
* ''Where can I get help and more information about the community meeting?''
** Contact local organizer [[User:Lucadelu|Luca Delucchi]] (<tt><lucadeluge at gmail com></tt>) or [[User:wenzeslaus|Vaclav Petras]] (<tt><wenzeslaus at gmail com></tt>) for budget questions.
* ''What if I can't spend time on this?''
** Can you spend money instead? [https://numfocus.org/donate-to-grass Donate to GRASS through NumFOCUS] to help keep the project going.

[[Category: Workshops]]
[[Category: Code Sprint]]
[[Category: 2026]]

Bug tracking

2026-06-23T21:44:41Z

Neteler: /* GitHub issues (2020 - present time) */ + Migrating GRASS code repository from SVN to git

== Introduction ==

=== GitHub issues (2020 - present time) ===

Jan 23, 2020, we switched from trac to GitHub also for the bug tracking (now called "issues").

:'''https://github.com/OSGeo/grass/issues'''

See
* announcement: https://grass.osgeo.org/news/2020_01_23_grass_gis_issues_now_on_github/
* notes: https://neteler.org/blog/remarks-on-svn-trac-to-github-migration/
* Migrating GRASS code repository from SVN to git: https://trac.osgeo.org/grass/wiki/GitMigration

=== trac (2007 - 2020) ===

Since 9 Dec 2007 we use '''Trac'''. [http://trac.edgewall.org Trac] is an open source, web-based project management and bug-tracking tool, inspired by CVSTrac. It is developed and maintained by Edgewall Software.

:'''http://trac.osgeo.org/grass'''

Historical note: The GForge and RT can be used to examine the previously resolved issues, and those that were still in progress as the new system was released. It would be good to move all the tickets from the former trackers to the new one, but nodody has volunteered yet. If you are the one, please contact the admin to arrange it.

=== GForge (2007 - 2008) ===

Used: Jan 2007 - Dec 2008

The former tracker was [http://gforge.org GForge] (a feature-rich system for collaborating on a software project). Under the [http://wald.intevation.org/ GForge setup by Intevation company], there is a [http://wald.intevation.org/tracker/?group_id=21 set of trackers for the GRASS project].

==== Participate ====

The trackers are available for public view, but in order to be able to post (including creating a new report), and to use all the features of the trackers, you need to [http://wald.intevation.org/account/register.php setup an account at GForge] and [http://wald.intevation.org/project/request.php?group_id=21 join the GRASS project at GForge].

==== GForge: How it works ====

''(note: historic section)''

All trackers' new submissions are automatically forwarded to the [http://grass.itc.it/community/support.php#devellists GRASS development mailing list]. The followup traffic is stored in the tracker, and forwarded only to parties discussing the ticket. However, any project member can "monitor" a ticket, or a whole tracker, in order to receive all the related traffic (see [http://gforge.org/docman/index.php?group_id=1&selected_doc_group_id=5&language_id=1 GForge manuals]).

Maintainers:
;general admin and cleaner
:[[User:msieczka|Maciej Sieczka]]
;backup admin
:[http://wald.intevation.org/users/bernhard Bernhard Reiter]
;code patches
:Jachym Cepicky
;website patches
:Scott Mitchell
;doc patches
:[[User:Landa|Martin Landa]]

There are 3 project member roles: ''admin'', ''developer'' and ''user''.

; ''admin'': Manages requests to join the project and maintains the GRASS project's setup at GForge.

; ''developer'': Can do most of the things that admin can. Only that he doesn't have his duties and he can't remove the whole GRASS project. But he still can add/modify/delete trackers as well as delete tickets for good. It was neccessary to provide that much power to ''developers'' so that they could move tickets between the trackers. ''Developers'' - please use your power wisely and let the admin know before doing something more intrusive you are not sure about :).

; ''user'': Can open new tickets in the trackers, reply to other tickets and ''monitor'', participate in surveys (''admin'' and ''developer'' can too, of course).

===== Buggy GForge bugtracker? =====

When you spot something wrong or a possible enhacement in the setup of GRASS trackers at GForge, please drop admin a line. If it's a bug or a missing feature in the GForge software itself, please report it to [http://wald.intevation.org/projects/siteadmin wald.intevation.org GForge site maintainers], preferably using [http://wald.intevation.org/tracker/?atid=162&group_id=1&func=browse their bugtracker]. If unsure whether the issue is in the GRASS trackers setup, or in the GForge itself, contact admin first, or ask on [http://grass.itc.it/devel/index.php#list GRASS dev ML].

Current top issues with GForge from the point of view of GRASS team, which hamper info flow and productivity:

* [http://wald.intevation.org/tracker/index.php?func=detail&aid=300&group_id=1&atid=162 can't CC an email from GForge]
* <strike>[http://wald.intevation.org/tracker/index.php?func=detail&aid=360&group_id=1&atid=162 whole discussion included in the email notification = noise]</strike> ''fixed by Sascha Wilde on 18.07.2007''
* [http://wald.intevation.org/tracker/index.php?func=detail&aid=85&group_id=1&atid=162 mail reply doesn't work]
* <strike>[http://wald.intevation.org/tracker/index.php?func=detail&aid=286&group_id=1&atid=162 email notifications sent from GForge to GRASS dev ML should also have it's address to reply to]</strike> ''fixed by Sascha Wilde on 30.07.2007''

===== GForge: beyond the trackers =====

GForge provides many functionalities. Currently we use only the trackers, as all the other functionalities are implemented in the current GRASS infrastructure (besides surveys; maybe there will be some use for them - let's keep them in mind :) ). However, it is worth rembering that GForge can provide things like discussion forums, mailing lists, ftp space, SVN server and some more.

''NOTE, 2007.04.07: according to [http://www.nabble.com/d.menu%2C-d.ask-tf3385241.html#a9832649 discussion on GRASS dev ML], [[SVN hosting|migration to SVN]] is planned soon.''

=== Request Tracker RT (2000 - 2006) ===

Used: Dec 2000 - Dec 2006

There is also the even older [https://web.archive.org/web/20070630161517/http://intevation.de/rt/webrt?q_status=open&q_queue=grass GRASS Request Tracker] - RT.

=== Bug tracking in early days (1982 - 1999) ===

The entire bug tracking was done manually, through emails (with focus on the mailing lists).

== See also ==

* GRASS GIS [[Migration from CVS to SVN]]
* GRASS GIS 7 [[SVN hosting]]
* OSGeo: [https://wiki.osgeo.org/wiki/Project_Infrastructure_Migration_2007 Project Infrastructure Migration 2007]
* [http://gforge.org/docman/index.php?group_id=1&selected_doc_group_id=5&language_id=1 GForge manuals]
* [http://grass.itc.it/bugtracking/index.php bugtracking page] on the GRASS website

[[Category: Development]]
[[Category: Community]]

Bug tracking

2026-06-23T21:43:28Z

Neteler: linked notes on SVN-trac to GitHub migration

== Introduction ==

=== GitHub issues (2020 - present time) ===

Jan 23, 2020, we switched from trac to GitHub also for the bug tracking (now called "issues").

:'''https://github.com/OSGeo/grass/issues'''

See
* announcement: https://grass.osgeo.org/news/2020_01_23_grass_gis_issues_now_on_github/
* notes: https://neteler.org/blog/remarks-on-svn-trac-to-github-migration/

=== trac (2007 - 2020) ===

Since 9 Dec 2007 we use '''Trac'''. [http://trac.edgewall.org Trac] is an open source, web-based project management and bug-tracking tool, inspired by CVSTrac. It is developed and maintained by Edgewall Software.

:'''http://trac.osgeo.org/grass'''

Historical note: The GForge and RT can be used to examine the previously resolved issues, and those that were still in progress as the new system was released. It would be good to move all the tickets from the former trackers to the new one, but nodody has volunteered yet. If you are the one, please contact the admin to arrange it.

=== GForge (2007 - 2008) ===

Used: Jan 2007 - Dec 2008

The former tracker was [http://gforge.org GForge] (a feature-rich system for collaborating on a software project). Under the [http://wald.intevation.org/ GForge setup by Intevation company], there is a [http://wald.intevation.org/tracker/?group_id=21 set of trackers for the GRASS project].

==== Participate ====

The trackers are available for public view, but in order to be able to post (including creating a new report), and to use all the features of the trackers, you need to [http://wald.intevation.org/account/register.php setup an account at GForge] and [http://wald.intevation.org/project/request.php?group_id=21 join the GRASS project at GForge].

==== GForge: How it works ====

''(note: historic section)''

All trackers' new submissions are automatically forwarded to the [http://grass.itc.it/community/support.php#devellists GRASS development mailing list]. The followup traffic is stored in the tracker, and forwarded only to parties discussing the ticket. However, any project member can "monitor" a ticket, or a whole tracker, in order to receive all the related traffic (see [http://gforge.org/docman/index.php?group_id=1&selected_doc_group_id=5&language_id=1 GForge manuals]).

Maintainers:
;general admin and cleaner
:[[User:msieczka|Maciej Sieczka]]
;backup admin
:[http://wald.intevation.org/users/bernhard Bernhard Reiter]
;code patches
:Jachym Cepicky
;website patches
:Scott Mitchell
;doc patches
:[[User:Landa|Martin Landa]]

There are 3 project member roles: ''admin'', ''developer'' and ''user''.

; ''admin'': Manages requests to join the project and maintains the GRASS project's setup at GForge.

; ''developer'': Can do most of the things that admin can. Only that he doesn't have his duties and he can't remove the whole GRASS project. But he still can add/modify/delete trackers as well as delete tickets for good. It was neccessary to provide that much power to ''developers'' so that they could move tickets between the trackers. ''Developers'' - please use your power wisely and let the admin know before doing something more intrusive you are not sure about :).

; ''user'': Can open new tickets in the trackers, reply to other tickets and ''monitor'', participate in surveys (''admin'' and ''developer'' can too, of course).

===== Buggy GForge bugtracker? =====

When you spot something wrong or a possible enhacement in the setup of GRASS trackers at GForge, please drop admin a line. If it's a bug or a missing feature in the GForge software itself, please report it to [http://wald.intevation.org/projects/siteadmin wald.intevation.org GForge site maintainers], preferably using [http://wald.intevation.org/tracker/?atid=162&group_id=1&func=browse their bugtracker]. If unsure whether the issue is in the GRASS trackers setup, or in the GForge itself, contact admin first, or ask on [http://grass.itc.it/devel/index.php#list GRASS dev ML].

Current top issues with GForge from the point of view of GRASS team, which hamper info flow and productivity:

* [http://wald.intevation.org/tracker/index.php?func=detail&aid=300&group_id=1&atid=162 can't CC an email from GForge]
* <strike>[http://wald.intevation.org/tracker/index.php?func=detail&aid=360&group_id=1&atid=162 whole discussion included in the email notification = noise]</strike> ''fixed by Sascha Wilde on 18.07.2007''
* [http://wald.intevation.org/tracker/index.php?func=detail&aid=85&group_id=1&atid=162 mail reply doesn't work]
* <strike>[http://wald.intevation.org/tracker/index.php?func=detail&aid=286&group_id=1&atid=162 email notifications sent from GForge to GRASS dev ML should also have it's address to reply to]</strike> ''fixed by Sascha Wilde on 30.07.2007''

===== GForge: beyond the trackers =====

GForge provides many functionalities. Currently we use only the trackers, as all the other functionalities are implemented in the current GRASS infrastructure (besides surveys; maybe there will be some use for them - let's keep them in mind :) ). However, it is worth rembering that GForge can provide things like discussion forums, mailing lists, ftp space, SVN server and some more.

''NOTE, 2007.04.07: according to [http://www.nabble.com/d.menu%2C-d.ask-tf3385241.html#a9832649 discussion on GRASS dev ML], [[SVN hosting|migration to SVN]] is planned soon.''

=== Request Tracker RT (2000 - 2006) ===

Used: Dec 2000 - Dec 2006

There is also the even older [https://web.archive.org/web/20070630161517/http://intevation.de/rt/webrt?q_status=open&q_queue=grass GRASS Request Tracker] - RT.

=== Bug tracking in early days (1982 - 1999) ===

The entire bug tracking was done manually, through emails (with focus on the mailing lists).

== See also ==

* GRASS GIS [[Migration from CVS to SVN]]
* GRASS GIS 7 [[SVN hosting]]
* OSGeo: [https://wiki.osgeo.org/wiki/Project_Infrastructure_Migration_2007 Project Infrastructure Migration 2007]
* [http://gforge.org/docman/index.php?group_id=1&selected_doc_group_id=5&language_id=1 GForge manuals]
* [http://grass.itc.it/bugtracking/index.php bugtracking page] on the GRASS website

[[Category: Development]]
[[Category: Community]]

Bug tracking

2026-06-23T21:40:54Z

Neteler: fix URL of https://grass.osgeo.org/news/2020_01_23_grass_gis_issues_now_on_github/

== Introduction ==

=== GitHub issues (2020 - present time) ===

Jan 23, 2020, we switched from trac to GitHub also for the bug tracking (now called "issues").

:'''https://github.com/OSGeo/grass/issues'''

See announcement: https://grass.osgeo.org/news/2020_01_23_grass_gis_issues_now_on_github/

=== trac (2007 - 2020) ===

Since 9 Dec 2007 we use '''Trac'''. [http://trac.edgewall.org Trac] is an open source, web-based project management and bug-tracking tool, inspired by CVSTrac. It is developed and maintained by Edgewall Software.

:'''http://trac.osgeo.org/grass'''

Historical note: The GForge and RT can be used to examine the previously resolved issues, and those that were still in progress as the new system was released. It would be good to move all the tickets from the former trackers to the new one, but nodody has volunteered yet. If you are the one, please contact the admin to arrange it.

=== GForge (2007 - 2008) ===

Used: Jan 2007 - Dec 2008

The former tracker was [http://gforge.org GForge] (a feature-rich system for collaborating on a software project). Under the [http://wald.intevation.org/ GForge setup by Intevation company], there is a [http://wald.intevation.org/tracker/?group_id=21 set of trackers for the GRASS project].

==== Participate ====

The trackers are available for public view, but in order to be able to post (including creating a new report), and to use all the features of the trackers, you need to [http://wald.intevation.org/account/register.php setup an account at GForge] and [http://wald.intevation.org/project/request.php?group_id=21 join the GRASS project at GForge].

==== GForge: How it works ====

''(note: historic section)''

All trackers' new submissions are automatically forwarded to the [http://grass.itc.it/community/support.php#devellists GRASS development mailing list]. The followup traffic is stored in the tracker, and forwarded only to parties discussing the ticket. However, any project member can "monitor" a ticket, or a whole tracker, in order to receive all the related traffic (see [http://gforge.org/docman/index.php?group_id=1&selected_doc_group_id=5&language_id=1 GForge manuals]).

Maintainers:
;general admin and cleaner
:[[User:msieczka|Maciej Sieczka]]
;backup admin
:[http://wald.intevation.org/users/bernhard Bernhard Reiter]
;code patches
:Jachym Cepicky
;website patches
:Scott Mitchell
;doc patches
:[[User:Landa|Martin Landa]]

There are 3 project member roles: ''admin'', ''developer'' and ''user''.

; ''admin'': Manages requests to join the project and maintains the GRASS project's setup at GForge.

; ''developer'': Can do most of the things that admin can. Only that he doesn't have his duties and he can't remove the whole GRASS project. But he still can add/modify/delete trackers as well as delete tickets for good. It was neccessary to provide that much power to ''developers'' so that they could move tickets between the trackers. ''Developers'' - please use your power wisely and let the admin know before doing something more intrusive you are not sure about :).

; ''user'': Can open new tickets in the trackers, reply to other tickets and ''monitor'', participate in surveys (''admin'' and ''developer'' can too, of course).

===== Buggy GForge bugtracker? =====

When you spot something wrong or a possible enhacement in the setup of GRASS trackers at GForge, please drop admin a line. If it's a bug or a missing feature in the GForge software itself, please report it to [http://wald.intevation.org/projects/siteadmin wald.intevation.org GForge site maintainers], preferably using [http://wald.intevation.org/tracker/?atid=162&group_id=1&func=browse their bugtracker]. If unsure whether the issue is in the GRASS trackers setup, or in the GForge itself, contact admin first, or ask on [http://grass.itc.it/devel/index.php#list GRASS dev ML].

Current top issues with GForge from the point of view of GRASS team, which hamper info flow and productivity:

* [http://wald.intevation.org/tracker/index.php?func=detail&aid=300&group_id=1&atid=162 can't CC an email from GForge]
* <strike>[http://wald.intevation.org/tracker/index.php?func=detail&aid=360&group_id=1&atid=162 whole discussion included in the email notification = noise]</strike> ''fixed by Sascha Wilde on 18.07.2007''
* [http://wald.intevation.org/tracker/index.php?func=detail&aid=85&group_id=1&atid=162 mail reply doesn't work]
* <strike>[http://wald.intevation.org/tracker/index.php?func=detail&aid=286&group_id=1&atid=162 email notifications sent from GForge to GRASS dev ML should also have it's address to reply to]</strike> ''fixed by Sascha Wilde on 30.07.2007''

===== GForge: beyond the trackers =====

GForge provides many functionalities. Currently we use only the trackers, as all the other functionalities are implemented in the current GRASS infrastructure (besides surveys; maybe there will be some use for them - let's keep them in mind :) ). However, it is worth rembering that GForge can provide things like discussion forums, mailing lists, ftp space, SVN server and some more.

''NOTE, 2007.04.07: according to [http://www.nabble.com/d.menu%2C-d.ask-tf3385241.html#a9832649 discussion on GRASS dev ML], [[SVN hosting|migration to SVN]] is planned soon.''

=== Request Tracker RT (2000 - 2006) ===

Used: Dec 2000 - Dec 2006

There is also the even older [https://web.archive.org/web/20070630161517/http://intevation.de/rt/webrt?q_status=open&q_queue=grass GRASS Request Tracker] - RT.

=== Bug tracking in early days (1982 - 1999) ===

The entire bug tracking was done manually, through emails (with focus on the mailing lists).

== See also ==

* GRASS GIS [[Migration from CVS to SVN]]
* GRASS GIS 7 [[SVN hosting]]
* OSGeo: [https://wiki.osgeo.org/wiki/Project_Infrastructure_Migration_2007 Project Infrastructure Migration 2007]
* [http://gforge.org/docman/index.php?group_id=1&selected_doc_group_id=5&language_id=1 GForge manuals]
* [http://grass.itc.it/bugtracking/index.php bugtracking page] on the GRASS website

[[Category: Development]]
[[Category: Community]]

GRASS Community Meeting San Michele 2026

2026-06-19T13:46:05Z

Neteler: For lodging booking options: see https://grasscommunitymeeting2026.eventbrite.it/

[[File:Sanmichele.png|frameless|center|1000px|San Michele all'Adige]]

{{toc|right}}

The ''GRASS Community Meeting'' for contributors and developers will be happening from '''July 11 - 19, 2026''' in [https://www.openstreetmap.org/relation/46990#map=12/46.1349/11.1947 San Michele all'Adige, Trentino, Italy].

== Sponsors ==

Sponsors make the event possible. Learn more about [https://grass.osgeo.org/contribute/sponsoring/ Sponsoring].

* [https://www.osgeo.org/ OSGeo]: 2500 USD (see [https://wiki.osgeo.org/w/index.php?title=GRASS_Community_Meeting_2026:_Budget budget]]).

[[File:Osgeo logo.png|none|left|alt=Light and dark green logo of OSGeo saying Your Open Source Compass|Open Source Geospatial Foundation]]

== Purpose ==
The ''GRASS Community Meeting'' is a great occasion for folks to support the development by actively contributing to the project in different ways. These include source code updates, documentation (manuals, wiki, tutorials), translations, website improvements or likewise. The community meeting is also a get-together where supporters, contributors, power users and developers make decisions and tackle larger problems related to the project, discuss and collaboratively resolve bugs, plan the direction for the project and work on new features. We welcome people committed to improving the GRASS project and the interfaces to QGIS, GDAL, PostGIS, R, OGC Services and others.

The focus is on GRASS maintenance, and interaction with other projects. Many maintenance tasks, infrastructure changes, and planning of large changes especially benefits from maintainers being in one place and time zone. While the specific topics highly depend on the participants, we will prioritize topics which require highly synchronous collaboration, such as the CMake build system transition and API transitions. The [https://grass.osgeo.org/news/2025_05_27_grass_dev_summit_report/ 2025 event report] gives an overview of what was achieved last year.

We do require participants to work on GRASS or connections to other projects. However, we leave them the freedom to work on what they think is the best contribution to the project given their skills and time available.

== Agenda ==

Agenda is being refined.

=== Saturday, July 11 ===

Day of arrival. Contact organizers if you are interested in individualized program or helping with organization.

=== Sunday, July 12 ===

* Hybrid meeting about 8.6.0 with FHS and Jupyter in GUI updates

=== Monday, July 13 ===

* FHS
* Updating the GRASS Roadmap

=== Tuesday, July 14 ===

* GSoC (may be moved to different day)
* GeoAI

=== Wednesday, July 15 ===

* Python API review
* Plan PSC elections

=== Thursday, July 16 ===

* Reducing PR backlog

=== Friday, July 17 ===

* Address issues for 8.6.0 release

=== Saturday, July 18 ===

* Website review

=== Sunday, July 19 ===

Day of departure.

== Participation ==

Please add your name here:

{|class="wikitable sortable" border="2" cellspacing="0" cellpadding="4" rules="all" style="margin:1em 1em 1em 0; border:solid 1px #AAAAAA; border-collapse:collapse; background-color:#edf9c7; font-size:95%; empty-cells:show;"
!width=50px|'''Number'''
!width=130px|'''Participant '''
!width=100px|'''Country'''
!width=100px|'''Arrival'''
!width=100px|'''Departure'''
!'''Topics'''
!'''Notes'''
|-
|1
| [[User:Lucadelu|Luca Delucchi]]
| Italy
|
|
|
|
|-
|2
| [[User:wenzeslaus|Vaclav Petras]]
| United States
| 11.07.
| 19.07.
| grass.tools, pytest, subcommands, reviews
|
|-
|3
| [[User:Annakrat|Anna Petrasova]]
| United States
| 11.07.
| 19.07.
| GSoC, reviews, PR backlog, tutorials
|
|-
|4
| [[User:Neteler|Markus Neteler]]
| Germany
| 06.07.
| 19.07. (?)
| documentation, website, reviews, tutorials, knowledge-transfer
|
|-
|5
| [[User:Sbl|Stefan Blumentrath]]
| Norway
| 11.07. (presumably)
| 18.07. (presumably)
| Handling Copernicus data with GRASS / actinia
|
|-
|6
| [[User:Hellik|Helmut Kudrnovsky]]
| Austria
|
|
|
|
|-
|7
| [[User:Veroandreo|Verónica Andreo]]
| Argentina
| 11.07.
| 19.07.
|
|
|-
|8
| [[User:Ctwhite|Corey White]]
| United States
| 11.07.
| 19.07.
| grass.jupyter, documentation, website, reviews, tutorials
|
|-
|9
| [[User:Echoix|Edouard Choinière]]
| Canada
| 11.07. (presumably)
| 19.07. (presumably)
| Reviews, CI, pytest, Windows GUI, i18n, undecided
|
|-
|10
| [[User:Mazingaro|Alen Mangafić]]
| Slovenia
| 13.07.
| 17.07.
| i.hyper: [https://grass.osgeo.org/grass-stable/manuals/addons/i.hyper.html Road Map] fulfilling; State of GRASS @FOSS4G 2026
|
|-
|11
| Tomaž Žagar
| Slovenia
| 13.07.
| 17.07.
| i.hyper: [https://grass.osgeo.org/grass-stable/manuals/addons/i.hyper.html Road Map] fulfilling
|
|-
|12
| Matjaž Krebs
| Slovenia
| 13.07.
| 17.07.
| i.hyper: [https://grass.osgeo.org/grass-stable/manuals/addons/i.hyper.html Road Map] fulfilling
|
|-
|}

Registration is free; participants cover their own travel and lodging (see below), often with employer support — thank you. Ideally we'd reimburse everyone, and every [https://numfocus.org/donate-to-grass donation] or [https://grass.osgeo.org/contribute/sponsoring/ employer sponsorship] of the project helps us get closer.

== Venue ==
The meeting will be hosted at [https://fmach.it/ Fondazione Edmund Mach] (FEM) in San Michele all'Adige, Trentino, Italy — about 15 km north of Trento. FEM is a research and education center with on-site facilities that allow participants to work, sleep, and eat in the same location.

[https://maps.app.goo.gl/5YEuEts6qXvky7HD9 Map]

=== Getting there ===

San Michele all'Adige is reachable by train on the Trento–Bolzano line (San Michele all'Adige–Mezzocorona station), with frequent connections from Trento (~15 minutes) and Verona (~1 hour). The nearest airports are Verona (VRN), Venice Marco Polo (VCE) and Treviso (TSF), Milan Bergamo (BGY), Malpensa (MXP), and Linate (LIN), Bologna (BLQ), and Innsbruck (INN) in Austria. Trento is also the host city of FOSS4G Italy 2026 (July 9–11), making it convenient to combine both events.

== Accommodation and Costs ==

''Registration is free''. However, participants should plan for the following costs:

* Travel
* Lodging

Participants can stay on-site at the FEM convitto (dormitory), keeping the community together for the full duration of the meeting:

* €35 per person per night
* Double and triple rooms (triples include a small kitchen)
* A mandatory on-site supervisor is required at €200 per night (flat fee, shared across the group)
* Family members are welcome to stay in the dormitory as well
* [https://cif.fmach.it/content/download/2701/78358/file/brochure_convitto.pdf Brochure]
* For '''lodging booking''' options: see [https://grasscommunitymeeting2026.eventbrite.it/ Eventbrite]

For anyone preferring alternative lodging, hotels and B&Bs are available in San Michele and nearby Trento.

Lunches on weekdays can be taken at the FEM canteen (mensa), located on the same campus. Details and pricing are being finalized.

== Individual Preparation ==

* Bring your own computer
* Bring {{wikipedia|AC power plugs and sockets|power adapter}} if needed (Italy: 230V, 50Hz, {{wikipedia|Europlug|Type C}}, {{wikipedia|Schuko|Type F}}, and {{wikipedia|AC power plugs and sockets: L|Type L}} sockets are common)
* Install git and the compiler tools, and come with a working GRASS development environment if possible. See [https://github.com/OSGeo/grass/blob/main/CONTRIBUTING.md here] for details.

== FAQ ==

* ''Is this a conference?''
** Talks or presentations may be included, but the purpose is to work together on the project. Among conference formats, the closest comparison would be a participatory workshop.
* ''Is this a hackathon?''
** While there is plenty of intensive coding, the meeting is not competitive. We meet to collaborate.
* ''Is the GRASS Community Meeting for developers only?''
** No, the meeting is open to all users, supporters, contributors, power users, and developers ''who want to make a meaningful contribution to the project''.
* ''What skills do I need?''
** Coding skills are not required. Contributions to documentation, tutorials, translations, website, and testing are all valuable. Practical help during the meeting, such as coordinating meals, photography, or reporting, is a real contribution too.
* ''Can I attend remotely?''
** The meeting is in-person, but everyone is welcome to use the same week for focused work on the project from wherever they are.
* ''What language is used during the meeting?''
** English is the working language, but you may hear several other languages spoken at the event.
* ''How was it last time?''
** Splendid! See [[GRASS Developer Summit Raleigh 2025]]!
* ''Where can I get help and more information about the community meeting?''
** Contact local organizer [[User:Lucadelu|Luca Delucchi]] (<tt><lucadeluge at gmail com></tt>) or [[User:wenzeslaus|Vaclav Petras]] (<tt><wenzeslaus at gmail com></tt>) for budget questions.
* ''What if I can't spend time on this?''
** Can you spend money instead? [https://numfocus.org/donate-to-grass Donate to GRASS through NumFOCUS] to help keep the project going.

[[Category: Workshops]]
[[Category: Code Sprint]]
[[Category: 2026]]

GRASS Community Meeting San Michele 2026

2026-06-08T14:53:54Z

Neteler: update arrival + activities (Markus)

[[File:Sanmichele.png|frameless|center|1000px|San Michele all'Adige]]

{{toc|right}}

The ''GRASS Community Meeting'' for contributors and developers will be happening from '''July 11 - 19, 2026''' in [https://www.openstreetmap.org/relation/46990#map=12/46.1349/11.1947 San Michele all'Adige, Trentino, Italy].

== Sponsors ==

Sponsors make the event possible. Learn more about [https://grass.osgeo.org/contribute/sponsoring/ Sponsoring].

* [https://www.osgeo.org/ OSGeo]: 2500 USD (see [https://wiki.osgeo.org/w/index.php?title=GRASS_Community_Meeting_2026:_Budget budget]]).

[[File:Osgeo logo.png|none|left|alt=Light and dark green logo of OSGeo saying Your Open Source Compass|Open Source Geospatial Foundation]]

== Purpose ==
The ''GRASS Community Meeting'' is a great occasion for folks to support the development by actively contributing to the project in different ways. These include source code updates, documentation (manuals, wiki, tutorials), translations, website improvements or likewise. The community meeting is also a get-together where supporters, contributors, power users and developers make decisions and tackle larger problems related to the project, discuss and collaboratively resolve bugs, plan the direction for the project and work on new features. We welcome people committed to improving the GRASS project and the interfaces to QGIS, GDAL, PostGIS, R, OGC Services and others.

The focus is on GRASS maintenance, and interaction with other projects. Many maintenance tasks, infrastructure changes, and planning of large changes especially benefits from maintainers being in one place and time zone. While the specific topics highly depend on the participants, we will prioritize topics which require highly synchronous collaboration, such as the CMake build system transition and API transitions. The [https://grass.osgeo.org/news/2025_05_27_grass_dev_summit_report/ 2025 event report] gives an overview of what was achieved last year.

We do require participants to work on GRASS or connections to other projects. However, we leave them the freedom to work on what they think is the best contribution to the project given their skills and time available.

== Agenda ==

Agenda is being refined.

=== Saturday, July 11 ===

Day of arrival. Contact organizers if you are interested in individualized program or helping with organization.

=== Sunday, July 12 ===

* Hybrid meeting about 8.6.0 with FHS and Jupyter in GUI updates

=== Monday, July 13 ===

* FHS
* Updating the GRASS Roadmap

=== Tuesday, July 14 ===

* GSoC (may be moved to different day)
* GeoAI

=== Wednesday, July 15 ===

* Python API review
* Plan PSC elections

=== Thursday, July 16 ===

* Reducing PR backlog

=== Friday, July 17 ===

* Address issues for 8.6.0 release

=== Saturday, July 18 ===

* Website review

=== Sunday, July 19 ===

Day of departure.

== Participation ==

Please add your name here:

{|class="wikitable sortable" border="2" cellspacing="0" cellpadding="4" rules="all" style="margin:1em 1em 1em 0; border:solid 1px #AAAAAA; border-collapse:collapse; background-color:#edf9c7; font-size:95%; empty-cells:show;"
!width=50px|'''Number'''
!width=130px|'''Participant '''
!width=100px|'''Country'''
!width=100px|'''Arrival'''
!width=100px|'''Departure'''
!'''Topics'''
!'''Notes'''
|-
|1
| [[User:Lucadelu|Luca Delucchi]]
| Italy
|
|
|
|
|-
|2
| [[User:wenzeslaus|Vaclav Petras]]
| United States
| 11.07.
| 19.07.
| grass.tools, pytest, subcommands, reviews
|
|-
|3
| [[User:Annakrat|Anna Petrasova]]
| United States
| 11.07.
| 19.07.
| GSoC, reviews, PR backlog, tutorials
|
|-
|4
| [[User:Neteler|Markus Neteler]]
| Germany
| 06.07.
| 19.07. (?)
| documentation, website, reviews, tutorials, knowledge-transfer
|
|-
|5
| [[User:Sbl|Stefan Blumentrath]]
| Norway
| 11.07. (presumably)
| 18.07. (presumably)
| Handling Copernicus data with GRASS / actinia
|
|-
|6
| [[User:Hellik|Helmut Kudrnovsky]]
| Austria
|
|
|
|
|-
|7
| [[User:Veroandreo|Verónica Andreo]]
| Argentina
| 11.07.
| 19.07.
|
|
|-
|8
| [[User:Ctwhite|Corey White]]
| United States
| 11.07.
| 19.07.
| grass.jupyter, documentation, website, reviews, tutorials
|
|-
|9
| [[User:Echoix|Edouard Choinière]]
| Canada
| 11.07. (presumably)
| 19.07. (presumably)
| Reviews, CI, pytest, Windows GUI, i18n, undecided
|
|-
|10
| [[User:Mazingaro|Alen Mangafić]]
| Slovenia
| 13.07.
| 17.07.
| i.hyper: [https://grass.osgeo.org/grass-stable/manuals/addons/i.hyper.html Road Map] fullfilling; State of GRASS @FOSS4G 2026
|
|-
|11
| Tomaž Žagar
| Slovenia
| 13.07.
| 17.07.
| i.hyper: [https://grass.osgeo.org/grass-stable/manuals/addons/i.hyper.html Road Map] fullfilling
|
|-
|12
| Matjaž Krebs
| Slovenia
| 13.07.
| 17.07.
| i.hyper: [https://grass.osgeo.org/grass-stable/manuals/addons/i.hyper.html Road Map] fullfilling
|
|-
|}

Registration is free; participants cover their own travel and lodging, often with employer support — thank you. Ideally we'd reimburse everyone, and every [https://numfocus.org/donate-to-grass donation] or [https://grass.osgeo.org/contribute/sponsoring/ employer sponsorship] of the project helps us get closer.

== Venue ==
The meeting will be hosted at [https://fmach.it/ Fondazione Edmund Mach] (FEM) in San Michele all'Adige, Trentino, Italy — about 15 km north of Trento. FEM is a research and education center with on-site facilities that allow participants to work, sleep, and eat in the same location.

[https://maps.app.goo.gl/5YEuEts6qXvky7HD9 Map]

=== Getting there ===

San Michele all'Adige is reachable by train on the Trento–Bolzano line (San Michele all'Adige–Mezzocorona station), with frequent connections from Trento (~15 minutes) and Verona (~1 hour). The nearest airports are Verona (VRN), Venice Marco Polo (VCE) and Treviso (TSF), Milan Bergamo (BGY), Malpensa (MXP), and Linate (LIN), Bologna (BLQ), and Innsbruck (INN) in Austria. Trento is also the host city of FOSS4G Italy 2026 (July 9–11), making it convenient to combine both events.

== Accommodation and Costs ==

''Registration is free''. However, participants should plan for the following costs:

* Travel
* Lodging

Participants can stay on-site at the FEM convitto (dormitory), keeping the community together for the full duration of the meeting:

* €35 per person per night
* Double and triple rooms (triples include a small kitchen)
* A mandatory on-site supervisor is required at €200 per night (flat fee, shared across the group)
* Family members are welcome to stay in the dormitory as well
* [https://cif.fmach.it/content/download/2701/78358/file/brochure_convitto.pdf Brochure]
* Details to be communicated soon.

For anyone preferring alternative lodging, hotels and B&Bs are available in San Michele and nearby Trento.

Lunches on weekdays can be taken at the FEM canteen (mensa), located on the same campus. Details and pricing are being finalized.

== Individual Preparation ==

* Bring your own computer
* Bring {{wikipedia|AC power plugs and sockets|power adapter}} if needed (Italy: 230V, 50Hz, {{wikipedia|Europlug|Type C}}, {{wikipedia|Schuko|Type F}}, and {{wikipedia|AC power plugs and sockets: L|Type L}} sockets are common)
* Install git and the compiler tools, and come with a working GRASS development environment if possible. See [https://github.com/OSGeo/grass/blob/main/CONTRIBUTING.md here] for details.

== FAQ ==

* ''Is this a conference?''
** Talks or presentations may be included, but the purpose is to work together on the project. Among conference formats, the closest comparison would be a participatory workshop.
* ''Is this a hackathon?''
** While there is plenty of intensive coding, the meeting is not competitive. We meet to collaborate.
* ''Is the GRASS Community Meeting for developers only?''
** No, the meeting is open to all users, supporters, contributors, power users, and developers ''who want to make a meaningful contribution to the project''.
* ''What skills do I need?''
** Coding skills are not required. Contributions to documentation, tutorials, translations, website, and testing are all valuable. Practical help during the meeting, such as coordinating meals, photography, or reporting, is a real contribution too.
* ''Can I attend remotely?''
** The meeting is in-person, but everyone is welcome to use the same week for focused work on the project from wherever they are.
* ''What language is used during the meeting?''
** English is the working language, but you may hear several other languages spoken at the event.
* ''How was it last time?''
** Splendid! See [[GRASS Developer Summit Raleigh 2025]]!
* ''Where can I get help and more information about the community meeting?''
** Contact local organizer [[User:Lucadelu|Luca Delucchi]] (<tt><lucadeluge at gmail com></tt>) or [[User:wenzeslaus|Vaclav Petras]] (<tt><wenzeslaus at gmail com></tt>) for budget questions.
* ''What if I can't spend time on this?''
** Can you spend money instead? [https://numfocus.org/donate-to-grass Donate to GRASS through NumFOCUS] to help keep the project going.

[[Category: Workshops]]
[[Category: Code Sprint]]
[[Category: 2026]]

PSC Meeting 2026-05-08

2026-05-11T15:57:42Z

Neteler: Some URLs added

== Participants ==

* Helli
* Anna
* Vashek
* Nicklas
* Paulo
* Linda
* Vero
* Huidae

== Agenda ==

The topics proposed are:

* Review action points from previous meetings:
** Community Meeting (see below)
** Was Corey added to the list of GRASS people with access to the OSGeo server?
** Status of translation, grass-gui and grass-stats mailman lists?

* [[GRASS Community Meeting San Michele 2026]]
** Wiki created, [https://grass.osgeo.org/news/2026%2004%2022%20grass%20community%20meeting%20san%20michele%202026/ event announced], [https://grass.osgeo.org/ main page carousel updated]
** Agenda
** Rooms, food, housing
** FOSSGIS e.V. request: support needed to complete and submit the request

* Releases
** [https://github.com/OSGeo/grass/releases/tag/8.5.0RC1 8.5 RC1]
*** did anyone test it?
** How are we for 8.5.0?
** [https://github.com/OSGeo/grass/discussions/7328 GitHub Discussion: What to cut from our release procedure to simplify it? #7328]

* GSoC
** Support the mentees in maximizing a good use of AI to allow mentors spend time on higher level code reviews and open-source mentoring ''by purchasing a professional subscription for the mentees''?

* Funding/Sponsoring
** New sponsoring tiers at https://grass.osgeo.org/contribute/sponsoring/
** Updates from NumFocus?

* RFC
** New planned RFC to make C11's optional feature 'atomic support' required for 8.6

== Minutes ==

'''1. OSGeo server access'''

* A ticket was opened a month ago to request OSGeo server access for Corey: https://trac.osgeo.org/osgeo/ticket/3561
** No response has been received so far from OSGeo SAC.
** [Action] Use the same ticket or create new ones to get Nicklas and Edouard access to the server.

'''2. GRASS Community Meeting - San Michele'''

* We drafted the agenda for the event, as it will support the [https://www.fossgis.de/wiki/F%C3%B6rderantr%C3%A4ge/GRASS_GIS_Community_Meeting_2026 sponsoring request to FOSSGIS e.V.]
* [Action] Vero will meet with MarkusN to help prepare the FOSSGIS request.
* We discussed criteria for (partial) reimbursement of participants, esp. in terms of commits to the main grass repo.
* [Action] Treasurer will propose who to reimburse and how much.
* [Action] All: Let's invite contributors personally, too.

'''3. Release'''

* [https://grass.osgeo.org/news/2026_05_08_grass_8_5_0_released/ 8.5.0 is out]!
* We discussed the release procedure based on the [https://github.com/OSGeo/grass/discussions/7328 #7328], in particular, whether Release Candidates are needed, given that they are rarely tested. Bas is a notable exception, consistently providing feedback on RCs.
* The goal is to get 8.6 out approximately 6 months after 8.5, as several things are almost ready and did not make it into 8.5.
* We went through the release announcement and the list of changes on GitHub and did minor edits during the meeting.
* [Action] Update versions and dates in the roadmap.
* [Action] Update Download/Windows layout since there is no standalone installer.
* [Action] Remove all "GIS" from the Download menu.

'''4. GSoC'''

* First time under [https://numfocus.org/programs/google-summer-code NumFocus].
* GRASS was allocated 3 students. Their projects and mentors are as follows:
** '''Pytest''' — Mentors: Vashek and Corey
** '''Integrating STDS into Data Catalog''' — Mentors: Anna and Stefan (Vero and Linda are interested in following this topic)
** '''Parallelise r.proj''' — Mentor: Huidae
* The first two projects will include adding JSON output to the tools they address.
* NumFOCUS acts as the fiscal intermediary but is not heavily involved in day-to-day matters.
* Proposal to use GRASS budget to pay for AI tools for GSoC students — to be discussed further.

'''5. Funding/Sponsoring'''

* We went through the new sponsoring page.
* New tiers were suggested by NumFOCUS.
* [Action] Ping Robert Dzur to check whether they want to sponsor the meeting in San Michele.

[[Category:PSC]]

PSC Meeting 2026-05-08

2026-05-10T23:27:17Z

Neteler: /* Minutes */

== Participants ==

* Helli
* Anna
* Vashek
* Nicklas
* Paulo
* Linda
* Vero
* Huidae

== Agenda ==

The topics proposed are:

* Review action points from previous meetings:
** Community Meeting (see below)
** Was Corey added to the list of GRASS people with access to the OSGeo server?
** Status of translation, grass-gui and grass-stats mailman lists?

* [[GRASS Community Meeting San Michele 2026]]
** Wiki created, [https://grass.osgeo.org/news/2026%2004%2022%20grass%20community%20meeting%20san%20michele%202026/ event announced], [https://grass.osgeo.org/ main page carousel updated]
** Agenda
** Rooms, food, housing
** FOSSGIS e.V. request: support needed to complete and submit the request

* Releases
** [https://github.com/OSGeo/grass/releases/tag/8.5.0RC1 8.5 RC1]
*** did anyone test it?
** How are we for 8.5.0?
** [https://github.com/OSGeo/grass/discussions/7328 GitHub Discussion: What to cut from our release procedure to simplify it? #7328]

* GSoC
** Support the mentees in maximizing a good use of AI to allow mentors spend time on higher level code reviews and open-source mentoring ''by purchasing a professional subscription for the mentees''?

* Funding/Sponsoring
** New sponsoring tiers at https://grass.osgeo.org/contribute/sponsoring/
** Updates from NumFocus?

* RFC
** New planned RFC to make C11's optional feature 'atomic support' required for 8.6

== Minutes ==

'''1. OSGeo server access'''

* A ticket was opened a month ago to request OSGeo server access for Corey: https://trac.osgeo.org/osgeo/ticket/3561
* No response has been received so far from OSGeo SAC.
* [Action] Use the same ticket or create new ones to get Nicklas and Edouard access to the server.

'''2. GRASS Community Meeting - San Michele'''

* We drafted the agenda for the event, as it will support the sponsoring request to FOSSGIS e.V.
* [Action] Vero will meet with MarkusN to help prepare the FOSSGIS request.
* We discussed criteria for (partial) reimbursement of participants, esp. in terms of commits to the main grass repo.
* [Action] Treasurer will propose who to reimburse and how much.
* [Action] All: Let's invite contributors personally, too.

'''3. Release'''

* [https://grass.osgeo.org/news/2026_05_08_grass_8_5_0_released/ 8.5.0 is out]!
* We discussed the release procedure based on the [https://github.com/OSGeo/grass/discussions/7328 #7328], in particular, whether Release Candidates are needed, given that they are rarely tested. Bas is a notable exception, consistently providing feedback on RCs.
* The goal is to get 8.6 out approximately 6 months after 8.5, as several things are almost ready and did not make it into 8.5.
* We went through the release announcement and the list of changes on GitHub and did minor edits during the meeting.
* [Action] Update versions and dates in the roadmap.
* [Action] Update Download/Windows layout since there is no standalone installer.
* [Action] Remove all "GIS" from the Download menu.

'''4. GSoC'''

* First time under NumFocus.
* GRASS was allocated 3 students. Their projects and mentors are as follows:
** '''Pytest''' — Mentors: Vashek and Corey
** '''Integrating STDS into Data Catalog''' — Mentors: Anna and Stefan (Vero and Linda are interested in following this topic)
** '''Parallelise r.proj''' — Mentor: Huidae
* The first two projects will include adding JSON output to the tools they address.
* NumFOCUS acts as the fiscal intermediary but is not heavily involved in day-to-day matters.
* Proposal to use GRASS budget to pay for AI tools for GSoC students — to be discussed further.

'''5. Funding/Sponsoring'''

* We went through the new sponsoring page.
* New tiers were suggested by NumFOCUS.
* [Action] Ping Robert Dzur to check whether they want to sponsor the meeting in San Michele.

[[Category:PSC]]

PSC Meeting 2026-05-08

2026-05-02T13:19:43Z

Neteler: /* Agenda */

== Participants ==

* TBD

== Agenda ==

The topics proposed are:

* Review action points from previous meetings:
** Community Meeting (see below)
** Was Corey added to the list of GRASS people with access to the OSGeo server?
** Status of translation, grass-gui and grass-stats mailman lists?

* [[GRASS Community Meeting San Michele 2026]]
** Wiki created, event announced
** Agenda
** Rooms, food, housing
** FOSSGIS e.V. request: support needed to complete and submit the request

* Releases
** [https://github.com/OSGeo/grass/releases/tag/8.5.0RC1 8.5 RC1]
*** did anyone test it?
** How are we for 8.5.0?

* GSoC

* Funding/Sponsoring
** New sponsoring tiers at https://grass.osgeo.org/contribute/sponsoring/
** Updates from NumFocus?

* ...
* add your topic here

== Minutes ==

[[Category:PSC]]