GRASS-Wiki - User contributions [en]

Talk:GRASS Developer Summit Raleigh 2025

2025-05-15T15:36:26Z

Lads: /* Guests and remote participants */

{{toc|right}}

Quick links: [[GRASS Developer Summit Raleigh 2025|Meeting page]] | [[#Participant_reports|Reports]] | [[GRASS_Developer_Summit_Raleigh_2025#Sponsors|Sponsors]]

== Organizing Team ==

* Initial planning: Vaclav Petras, Anna Petrasova, Veronica Andreo, Corey White, Lois Utt, Sarah White, Doug Newcomb, Huidae Cho, Veronica Andreo ([[GRASS_Developer_Summit_Raleigh_2025#Organizing_Committee|Organizing Committee]])
* Budget: Vaclav Petras, Lois Utt, Anna Petrasova
* Raising support: Helena Mitasova, Vaclav Petras, Anna Petrasova, Michael Barton, Giuseppe Amatulli ([[NSF POSE Project 2023-2025 Timeline|NSF POSE project]] proposal authors)
* Travel: Lois Utt
* Venue: Vaclav Petras, Lois Utt
* Meals: Lois Utt, Sarah White, Vaclav Petras, Corey White, Anna Petrasova
* Agenda: Vaclav Petras, Huidae Cho, Anna Petrasova
* Wiki page: Vaclav Petras, Anna Petrasova
* Swag: Sarah White, Vaclav Petras, Anna Petrasova, Corey White
* Promotion, invitations, and social media: Vaclav Petras, Sarah White, Corey White, John Vogler
* Lightning talks organization: Vaclav Petras, Zachary Arcaro, John Vogler
* Photography: Caitlin Haedrich

== Detailed Schedule ==

=== Day 1, Monday, May 19 ===

Location: Talley Student Union, 2610 Cates Ave ([https://www.google.com/maps/place/Talley+Student+Union/data=!4m2!3m1!1s0x0:0x38989377c96adef0?sa=X&ved=1t:2428&ictx=111 map])

Room: 5101-Executive Board Room

Highlighted topic: ''Contributing to GRASS. Getting started. Is it easy to contribute?''

{| class="wikitable"
! Time !! Slot !!
|-
| 8:00-9:00 || Breakfast || Catered breakfast on site. Meet people, and plan your personal agenda for the day.
|-
| 9:00-10:00 || Morning opening sessions || What to expect from the event, contributing to GRASS using Git and GitHub, making your first contribution.
|-
| 10:00-11:00 || Focus time || Time to work on your laptop, whiteboard solutions with a group, or anything in between.
|-
| 11:00-11:20 || Self-organized feedback session || Your topic here (10-minute presentation and 10-minute discussion)
|-
| 11:20-11:40 || Self-organized feedback sessions || Your topic here
|-
| 11:40-12:00 || Self-organized feedback sessions || Your topic here
|-
| 12:00-13:00 || Lunch || Catered food on site.
|-
| 13:00-17:00 || Focus time || Time to work on your laptop, whiteboard solutions with a group, or anything in between.
|-
| 18:00 || Dinner || We will walk to [https://www.trophybrewing.com/brewing-pizza Trophy Brewing & Pizza] ([https://maps.app.goo.gl/ggnZ7EvXbWqDUmvP9 directions], 30 min walk from Talley)
|}

=== Day 2, Tuesday, May 20 ===

Location: Talley Student Union, 2610 Cates Ave ([https://www.google.com/maps/place/Talley+Student+Union/data=!4m2!3m1!1s0x0:0x38989377c96adef0?sa=X&ved=1t:2428&ictx=111 map])

Room: 5101-Executive Board Room

Highlighted topic: ''Interfacing with R and QGIS (gathering user feedback, testing, discussing with developers, developing action items)''

{| class="wikitable"
! Time !! Slot !!
|-
| 8:00-9:00 || Breakfast || Breakfast on site. Start the day, meet people, and plan your personal agenda for the day.
|-
| 9:00-10:00 || Morning opening sessions || Introduction to writing GRASS tools, program for the day.
|-
| 10:00-11:00 || Focus time || Time to work on your laptop, whiteboard solutions with a group, or anything in between.
|-
| 11:00-11:20 || Self-organized feedback session || Your topic here (10-minute presentation and 10-minute discussion)
|-
| 11:20-11:40 || Self-organized feedback sessions || Your topic here
|-
| 11:40-12:00 || Self-organized feedback sessions || Your topic here
|-
| 12:00-13:00 || Lunch || [https://maps.app.goo.gl/womSkce9DrE8CTnR8 Case dining hall]
|-
| 13:00-17:00 || Focus time || Time to work on your laptop, whiteboard solutions with a group, or anything in between.
|-
| 18:00 || Dinner || [https://maps.app.goo.gl/CQiWoCAQNt1ymZkb7 Served in Jordan Hall at the Center for Geospatial Analytics], evaluate the day's accomplishments, plan and prioritize for the next few days.
|}

=== Day 3, Wednesday, May 21 ===

Location: Talley Student Union, 2610 Cates Ave ([https://www.google.com/maps/place/Talley+Student+Union/data=!4m2!3m1!1s0x0:0x38989377c96adef0?sa=X&ved=1t:2428&ictx=111 map])

Room: 5101-Executive Board Room

Highlighted topic: ''Non-coding contributions, natural language translation, and internationalization.''

{| class="wikitable"
! Time !! Slot !!
|-
| 8:00-9:00 || Breakfast || [https://maps.app.goo.gl/eZ8VK8Mx6TjMt9NP8 Case dining hall]
|-
| 9:00-10:00 || Morning opening sessions || Introduction to non-coding contributions, deep dive into new documentation, natural language translation and internationalization (procedures, glossaries, code customization, translation).
|-
| 10:00-11:00 || Focus time || Time to work on your laptop, whiteboard solutions with a group, or anything in between.
|-
| 11:00-11:20 || Self-organized feedback session || Your topic here (10-minute presentation and 10-minute discussion)
|-
| 11:20-11:40 || Self-organized feedback sessions || Your topic here
|-
| 11:40-12:00 || Self-organized feedback sessions || GSoC call
|-
| 12:00-13:00 || Lunch || Served on site. Eat, drink, and continue the discussion from the feedback sessions.
|-
| 13:00-17:00 || Focus time || Time to work on your laptop, whiteboard solutions with a group, or anything in between.
|-
| 18:00 || Dinner || [https://maps.app.goo.gl/1E39eySMVaxYJUUS8 Picnic at Pullen Park, shelter #3. In case of bad weather, dinner at the Center for Geospatial Analytics.
|}

=== Day 4, Thursday, May 22 ===

Location: Center for Geospatial Analytics, Jordan Hall, 2800 Faucette Drive ([https://www.google.com/maps/search/Jordan+Hall/@35.7816832,-78.6772765,18z/data=!3m1!4b1?entry=ttu&g_ep=EgoyMDI1MDQyMC4wIKXMDSoJLDEwMjExNDUzSAFQAw%3D%3D map])

Room: 5103 (straight from the two elevators, at the end of the hallway)

Highlighted topic: ''Project vision and computational engine use case.''

{| class="wikitable"
! Time !! Slot !!
|-
| 8:00-9:00 || Breakfast || On site. Start the day, meet people, and plan your personal agenda for the day.
|-
| 9:00-10:00 || Morning opening sessions || Project vision and the computational engine use case (missing features, documentation, user groups).
|-
| 10:00-11:00 || Focus time || Time to work on your laptop, whiteboard solutions with a group, or anything in between.
|-
| 11:00-11:20 || Self-organized feedback session || Your topic here (10-minute presentation and 10-minute discussion)
|-
| 11:20-11:40 || Self-organized feedback sessions || Your topic here
|-
| 11:40-12:00 || Self-organized feedback sessions || Your topic here
|-
| 12:00-13:00 || Lunch || On site. Eat, drink, and continue the discussion from the feedback sessions.
|-
| 13:00-16:00 || Focus time || Time to work on your laptop, whiteboard solutions with a group, or anything in between.
|-
| 16:00-17:00 || Lightning talks || Fast-paced talks, showcasing applications of GRASS, room 5111.
|-
| 18:00 || Reception || Connect with researchers, government professionals, and industry collaborators, rooms 5111 and 5119.
|}

=== Day 5, Friday, May 23 ===

Location: James B. Hunt Jr. Library, 1070 Partners Way - Centennial Campus ([https://www.google.com/maps/place/James+B.+Hunt+Jr.+Library/@35.7693736,-78.679167,17z/data=!3m1!5s0x89acf5759f5a31df:0xc547454a0151c440!4m10!1m2!2m1!1shunt+library!3m6!1s0x89acf5759f591f41:0xbe0266269ce37f59!8m2!3d35.7693215!4d-78.6764409!15sCgxodW50IGxpYnJhcnlaDiIMaHVudCBsaWJyYXJ5kgESdW5pdmVyc2l0eV9saWJyYXJ54AEA!16s%2Fm%2F0r4wjf_?entry=ttu&g_ep=EgoyMDI1MDQyMC4wIKXMDSoJLDEwMjExNDUzSAFQAw%3D%3D map])

Room: Faculty Research Commons - 5100 ([https://www.lib.ncsu.edu/hunt/map floor plan])

Highlighted topic: ''GRASS project's future course.''

{| class="wikitable"
! Time !! Slot !!
|-
| 8:00-9:00 || Breakfast || On site. Start the day, meet people, and plan your personal agenda for the day.
|-
| 9:00-10:00 || Morning opening sessions || GRASS project's future course.
|-
| 10:00-11:00 || Focus time || Time to work on your laptop, whiteboard solutions with a group, or anything in between.
|-
| 10:00-11:00 || PSC meeting || Project Steering Committee meets (public).
|-
| 11:00-11:20 || Self-organized feedback session || Your topic here (10-minute presentation and 10-minute discussion)
|-
| 11:20-11:40 || Self-organized feedback sessions || Your topic here
|-
| 11:40-12:00 || Self-organized feedback sessions || Your topic here
|-
| 12:00-13:00 || Lunch || Walk to [https://maps.app.goo.gl/kHVHY62QxTd6wHKd9 On the Oval Culinary Creatins]. Eat, drink, and continue the discussion from the feedback sessions.
|-
| 13:00-17:00 || Focus time || Time to work on your laptop, whiteboard solutions with a group, or anything in between.
|-
| 18:00 || Dinner || Dinner on your own. Corey White will organize trip to downtown. Bus 41 from Hunt library to hotel and then walk.
|}

=== Day 6, Saturday, May 24 ===

Location: James B. Hunt Jr. Library, 1070 Partners Way - Centennial Campus ([https://www.google.com/maps/place/James+B.+Hunt+Jr.+Library/@35.7693736,-78.679167,17z/data=!3m1!5s0x89acf5759f5a31df:0xc547454a0151c440!4m10!1m2!2m1!1shunt+library!3m6!1s0x89acf5759f591f41:0xbe0266269ce37f59!8m2!3d35.7693215!4d-78.6764409!15sCgxodW50IGxpYnJhcnlaDiIMaHVudCBsaWJyYXJ5kgESdW5pdmVyc2l0eV9saWJyYXJ54AEA!16s%2Fm%2F0r4wjf_?entry=ttu&g_ep=EgoyMDI1MDQyMC4wIKXMDSoJLDEwMjExNDUzSAFQAw%3D%3D map])

Room: Faculty Research Commons - 5100 ([https://www.lib.ncsu.edu/hunt/map floor plan])

Highlighted topics: ''NSF POSE project evaluation.''

{| class="wikitable"
! Time !! Slot !!
|-
| 8:00-9:00 || Breakfast || TBA. Start the day, meet people, and plan your personal agenda for the day.
|-
| 9:00-10:00 || Morning opening sessions || NSF POSE project evaluation, contributor community feedback.
|-
| 10:00-11:00 || Focus time || Time to work on your laptop, whiteboard solutions with a group, or anything in between.
|-
| 11:00-11:20 || Self-organized feedback session || Your topic here (10-minute presentation and 10-minute discussion)
|-
| 11:20-11:40 || Self-organized feedback sessions || Your topic here
|-
| 11:40-12:00 || Self-organized feedback sessions || Your topic here
|-
| 12:00-13:00 || Lunch || TBA. Eat, drink, and continue the discussion from the feedback sessions.
|-
| 13:00-17:00 || Focus time || Time to work on your laptop, whiteboard solutions with a group, or anything in between.
|-
| 18:00 || Dinner || TBA.
|}

== Daily tasks for participants ==

* List all the things you are working on in the Participant reports section below. Update the list each day. Include things you work on with other people.
* If you want to discuss something with the whole group, add yourself to a Self-organized feedback sessions slot in the schedule above or tell Vaclav (Vashek) Petras.
* For people with triage access and above: 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.)

== Participant reports ==

Per-person reports from the meeting.

=== Giuseppe Amatulli | Yale University ===

* Testing r.watershed and r.stream.* for handling large datasets

=== Veronica Andreo | CONICET - Instituto Gulich ===

* Complete review of temporal tutorials to push them, GRASS and tutorials websites, GRASS project stuff, understand how new docs work, understand new contribution workflows, interface with R.

=== Abdullah Azzam | New Mexico State University ===

* I plan to develop a module that computes runoff volume using the SCS Curve Number method. I will explore techniques to make it fast, efficient, and reliable, creating a valuable tool for water resources professionals, students, and researchers.

=== Michael Barton | Arizona State University ===

* POSE related activities

=== Laura Belica | NC State University ===

* tutorial development

=== Shonil Sateesh Bhide | NC State University ===

* CI optimization

=== Huidae Cho | New Mexico State University ===

* CMake, conda, CI, Mentoring

=== Edouard Choinière ===

* Quick ideas, way too much for a week: Helping others (may take a reasonable part of the time), managing CI, setting up localization template updating workflow, backporting tool? Pytest/coverage improvements? Discuss and design other projects, to work on during the year. Open to change on other priorities once there, anything that is useful. Maybe make a little progress on high dpi GUI, especially on Windows.

=== Laurent Courty ===

* An xarray backend for GRASS STRDS. Fixing related issues

=== Robert S. Dzur | Bohannan Huston, Inc. ===

* r.in.pdal

=== David W. Farris | East Carolina University ===

* A tool to calculate gravity terrain corrections

=== Neel Ghoshal | NC State University ===

=== Caitlin Haedrich | NC State University ===

* Jupyter API, event photographs

=== Brendan Harmon | Louisiana State University ===

* Plugin development (r.earthworks) & tutorials

=== Linda Karlovska | Czech Technical University in Prague ===

* I plan to work on GUI enhancements, particularly the Jupyter-style interactive page for enhanced scripting and visualization.

=== Martin Landa | Czech Technical University in Prague ===

* Graphical modeler, Python API, Windows builds

=== Nicklas Larsson | Hungarian National Museum ===

* CMake build system; perhaps Conda recipe

=== Chung-Yuan Liang ===

* parallelize some modules, improve testing

=== Andres Lucero | Bohannan Huston Inc ===

* r.in.pdal

=== Alen Mangafić | Geodetic Institute of Slovenia ===

* Add-on which offers basic hyperspectral data support in GRASS.

=== Helena Mitasova | NC State University ===

* standardized data set and related tutorials

=== Michael Mulqueen | MassGIS ===

* depth to water, hydro from lidar, etc

=== Māris Nartišs ===

* Publish modules in progress.

=== Ondřej Pešek | Czech Technical University in Prague ===

* Many things to fix/improve in g.gui.gmodeler, finally finish an addon for CNNs in GRASS

=== Vaclav (Vashek) Petras | NC State University ===

* [https://github.com/wenzeslaus?tab=overview&from=2025-05-19&to=2025-05-24 GitHub activity]
* computational engine, APIs, funding, summit organization

=== Anna Petrasova | NC State University ===

* [https://github.com/petrasovaa?tab=overview&from=2025-05-19&to=2025-05-24 GitHub activity]
* mentoring, documentation

=== Gregory Power | Town of Cary ===

* Documentation

=== Pratikshya Regmi | NC State University ===

* I plan to show the I am working on integrating LLM and GRASS.

=== Riya | Indian Institute of Technology, Roorkee ===

* I am currently thinking of developing an AI Agent for the grass jupyter library which will help the users with mathematical calculations done in GIS.

=== Krishna Prasad Sheshadri ===

*

=== Adam Smith | Missouri Botanical Garden ===

* fasterRaster (fielding bug reports, adding features)

=== Michelle (Mimi) Stephens ===

* Coding and visualization

=== Corey White | NC State University ===

* JSON, mentoring

=== Jayneel Shah | NC State University ===

* improve the test coverage of imagery modules.

== Guests and remote participants ==

=== Luís de Sousa | University of Lisbon ===

* Review outstanding PRs
* Prepare GRASS sessions for the OpenGeoHub Summer School

Talk:GRASS Community Meeting Prague 2024

2024-06-20T10:55:14Z

Lads: /* Luís de Sousa */

{{toc|right}}

Quick links: [[GRASS Community Meeting Prague 2024|Meeting page]] | [[#Reports|Reports]] | [[GRASS_Community_Meeting_Prague_2024#Sponsors|Sponsors]]

== Organizing Team ==

* Initial planning: Vaclav Petras, Veronica Andreo, Markus Neteler, Anna Petrasova, Martin Landa, Helmut Kudrnovsky, Helena Mitasova
* Budget: Vaclav Petras, Anna Petrasova, Markus Neteler, Veronica Andreo, Helena Mitasova
* Raising support: Vaclav Petras, Veronica Andreo, Markus Neteler, Helmut Kudrnovsky, Anna Petrasova
* Reimbursements: Vaclav Petras
* Venue: Vaclav Petras
* Meals: Caitlin Haedrich, Alen Mangafić, Martin Landa, Anna Petrasova, Vaclav Petras, Ondrej Pesek, Veronica Andreo
* Agenda: Veronica Andreo, Anna Petrasova
* Wiki page: Vaclav Petras, Veronica Andreo, Martin Landa
* Virtual participant support: Veronica Andreo
* T-shirts, hoodies, stickers: Vaclav Petras, Veronica Andreo
* Promotion, invitations, and social media: Caitlin Haedrich, Veronica Andreo, Vaclav Petras
* Photography: Caitlin Haedrich, Helmut Kudrnovsky

== 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.
* Link the [https://github.com/orgs/OSGeo/projects/1/ GRASS Community Meeting Prague 2023] project on GitHub to each PR or issue you are working on or plan to be working on.
* 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.)

=== Floris Vanderhaeghe ===

* Make maintenance pull requests [https://github.com/rsbivand/rgrass/pull/90 PR #90] and [https://github.com/rsbivand/rgrass/pull/91 PR #91] to support future contributors of the [https://github.com/rsbivand/rgrass R package rgrass].
* Test the standalone GDAL-GRASS driver in R and create issues [https://github.com/OSGeo/gdal-grass/issues/46 #46], [https://github.com/OSGeo/gdal-grass/issues/47 #47], [https://github.com/OSGeo/gdal-grass/issues/48 #48] and [https://github.com/OSGeo/gdal-grass/issues/49 #49] in its code repository, with help of Markus Neteler.
* Implement the GDAL-GRASS driver in the <code>read_VECT()</code> function of [https://github.com/rsbivand/rgrass R package rgrass], as well as some associated enhancements. See [https://github.com/rsbivand/rgrass/pull/93 PR #93].
* Make an [https://github.com/rsbivand/rgrass/issues/92 issue], with the help of Helmut Kudrnovsky and Veronica Andreo, about launching R in the OSGeo4W shell independently of GRASS GIS.
* Help sorting out a few issues in the [https://github.com/rsbivand/rgrass repository of R package rgrass].
* Point at the PROJJSON specification in support of GRASS GIS issue [https://github.com/OSGeo/grass/issues/3020 #3020].
* Participate in the GRASS GIS roadmap discussion on Saturday.
* Participate in the discussion on interfacing GRASS GIS from QGIS. See [https://github.com/OSGeo/grass/discussions/3898 meeting minutes].

=== Markus Neteler ===

* cleanup labels in GitHub repo
* replace --tmp-location with --tmp-project (pull requests [https://github.com/OSGeo/grass/pull/3825 PR #3825], [https://github.com/OSGeo/grass/pull/3822 PR #3822])
* docker: remove "grass-session" pip approach, replace to new build-in Python API (pull request [https://github.com/OSGeo/grass/pull/3819 PR #3819])
* Participated in the PSC meeting to define elections date and other elections related issues. See [[PSC_Meeting_2024-06-14]].
* Discussion about our Dockerfiles
* Simplified examples for working with GRASS 8.4+ in Python (update [https://gis.stackexchange.com/a/457875/687 Stackexchange posts])
* Participated of the roadmap discussion session
* cleanup of many pull request titles to be recognized by https://github.com/OSGeo/grass/blob/main/utils/release.yml
* Complete OpenSSF Best Practices badge questionnaire to 100%: https://www.bestpractices.dev/en/projects/2470
* backport plenty of pull requests to GRASS GIS 8.4 release branch
* lib/gis: modernize getl2() https://github.com/OSGeo/grass/pull/3850
* social media outreach: suggest use of Publer.io to easier feed our channels (discuss with Vero and Caitlin)
* work on 8.4.0RC1, together with Vaclav, see https://github.com/OSGeo/grass/releases
* Participation in QGIS-GRASS session with Nyall Dawson
* Worked with Vero on the highlights for the 8.4.0RC1 release notes.
* Updated hugo version on the website, see also [https://github.com/OSGeo/grass-website/pull/438 PR]

=== Veronica Andreo ===

* Discuss tutorial topics with Alen
* Reviewed and tested contributions by the Google Summer of Code student working on EODAG integration.
* Reviewed other PRs: temporal framework, tutorial on GRASS usage within Jupyter on Windows, t.stac, among others.
* Participated in the PSC meeting to define elections date and other elections related issues. See [[PSC_Meeting_2024-06-14]].
* Compiled the raw list of contributors since Dec 2020, to create the list of voters, as discussed in PSC meeting.
* Set up a swag shop in RedBubble and added designs with color and white logos. Yet not published as payment details need to be configured with OSGeo treasurer.
* Participated of the roadmap discussion session - Roadmap will be published in the website.
* Participated of the documentation discussion session.
* Participated of the call with Nyall Dawson about improving GRASS-QGIS integration.
* Worked with Markus on the highlights for the RC1 release notes.
* Assisted Caitlin with social media posting, review posts and setting up Publer and Buffer services suggested by Markus to streamline posting in various channels.
* Discussed and tested gdal-grass driver implementation by Floris.
* Went through grass-website issues, closed some, pinged in others and changed hugo version in the website [https://github.com/OSGeo/grass-website/pull/438 PR].
* Reviewed PR and tested the upcoming t.stac tool.

=== Alen Mangafić ===
* Discuss tutorial with Veronica and Vaclav.
* Setting up the environment for the tutorial with Ondřej and Corey, resulting in a process to build a Docker container with the main branch and it's kernel connection to Jupyter Lab.
* Writing a Jupyter Lab framework which works. Helped by Vaclav with locating the "GISENV" location bug.
* Data preparation: correction the point clouds to match correct Global Encoding value of a LAS 1.4 file with PDRF 6 - 10 is 17 (16 + 1); CRS definition.
* Testing and drafting the workflow in GUI.
* Found a and reported a bug about how r.in.pdal handles the number of returns ([https://github.com/OSGeo/grass/issues/3827 #3827]).
* Built a micromamba python environment for grass scripting with point cloud visualization with help of Edouard.
* Writing the tutorial.

=== Corey White ===

* Discussed and reviewed PRs for Google Summer of Code json and jupyter notebook projects.
* Helped setting up Docker environment for GRASS GIS and Jupyter Lab.
* Working on t.stac.* addon. (PR https://github.com/OSGeo/grass-addons/pull/802)
* Opened PR for new point pattern analysis tool v.paa (https://github.com/OSGeo/grass/pull/3826)

=== Luís de Sousa ===

* Debugging [https://github.com/OSGeo/grass/issues/2187 issue #2187] ([https://github.com/OSGeo/grass/pull/3869 PR #3869])
* Unit tests for [https://github.com/OSGeo/grass/tree/main/vector/v.out.ogr v.out.ogr] ([https://github.com/OSGeo/grass/pull/3848 PR #3848])
* Unit tests for [https://github.com/OSGeo/grass/tree/main/raster/r.out.gdal r.out.gdal] ([https://github.com/OSGeo/grass/pull/3903 PR #3903])
* Updates to add-ons documentation ([https://github.com/OSGeo/grass-addons/pull/1105 PR #1105])
* Review to Unit Test documentation ([https://github.com/OSGeo/grass/issues/3887 issue #3887])
* Discussion on parallel computation, sparked by [https://www.linkedin.com/feed/update/urn:li:activity:7208372306924994560?commentUrn=urn%3Ali%3Acomment%3A%28activity%3A7208372306924994560%2C7208521495923306496%29&dashCommentUrn=urn%3Ali%3Afsd_comment%3A%287208521495923306496%2Curn%3Ali%3Aactivity%3A7208372306924994560%29 Tom Hengl's remarks]:
** several approaches exist (documented in the [https://github.com/ncsu-geoforall-lab/opengeohub-2023 OpenGeoHub 2023 workshop]) but not all accessible to non-programmers;
** most modules obvious to be parallelised have [https://grass.osgeo.org/grass83/manuals/keywords.html#parallel already been so];
** patching of results is an issue (high overhead), although in the [https://grass.osgeo.org/grass83/manuals/libpython/pygrass.modules.grid.html GridModule] class a virtual raster could be an option.

=== Anna Petrasova ===
* Participated in the PSC meeting to define elections date and other elections related issues. See [[PSC_Meeting_2024-06-14]].
* Discussed and reviewed PR for Google Summer of Code jupyter notebook projects.
* Reviewing v.surf.rst PR (Cross-validation OpenMP support, PR #3590)
* Tasked Caitlin to show layer controller in grass.jupyter.InteractiveMap by default, defined implementation, reviewed her PR (#3880)
* Solving conflict and reviewing PR #2481
* Testing and reviewing r.texture PR #3857, running benchmarks on laptop and desktop.
* Participated in QGIS discussion, put together meeting minutes: https://github.com/OSGeo/grass/discussions/3898
* Participated in the roadmap discussion session.
* Participated in the documentation discussion session.
* Restructured CONTRIBUTING.md by moving out Github workflow into separate file
* Led GSoC students presentations.
* Participated in discussion about parallelization with Luis and Vashek, Caitlin and others

=== Chung-Yuan Liang ===
* Refactored r.texture and updated tests (PR [https://github.com/OSGeo/grass/pull/3785 #3785], [https://github.com/OSGeo/grass/pull/3786 #3786]).
* Parallelized r.texture and provided benchmarks.
* Revised v.surf.rst PR (Cross-validation OpenMP support, PR [https://github.com/OSGeo/grass/pull/3590 #3590]).
* Enabled Python benchmark module to plot speedup and efficiency (PR [https://github.com/OSGeo/grass/pull/3835 #3835]).
* Parallelized r.horizon and provided benchmarks. (PR [https://github.com/OSGeo/grass/pull/3890 #3890])
* Discussed details of parallelizing modules with Vashek and Anna.

=== Caitlin Haedrich ===
* Discussed GRASS, Jupyter and Windows with Heli
* Wrote tutorial for using OSGeo4W to set up Jupyter Lab in Notebooks - [https://github.com/ncsu-geoforall-lab/tutorials/pull/3 PR]
* Set up Publer account for social media management, compared with Buffer
* Took pictures and posted 2x daily to social media
* Added Layer Control by default to grass.jupyter.InteractiveMap() - [https://github.com/OSGeo/grass/pull/3880 PR]
* Reviewed all GRASS GIS online profiled and compiled list that need updating (report in progress)

=== Edouard Choinière ===
* Discussion with Vaclav Petras on current state of python packaging, build, and testing framework and coverage, Windows porting improvements, and future plans. Planning for the week. Lead to PRs addressing Windows blockers: [https://github.com/OSGeo/grass/pull/3850 #3850] and [https://github.com/OSGeo/grass/pull/3853 #3853], which I tested on my fork combined with my changes highlighting the bugs.
* Reviewing of PRs, managing CI during the sprint (restarting transient failures, finding inefficiencies, queueing jobs before and after active periods).
* Maintaining code quality CI and pre-commit. Example: Flake8 fails with Python 3.12 in pre-commit, as it is way outdated, harming contributions of the sprint's participants. Bumping to a new version has other failures and dependent changes needed. Related PRs include: [https://github.com/OSGeo/grass/pull/3808 #3808], [https://github.com/OSGeo/grass/pull/3831 #3831], [https://github.com/OSGeo/grass/pull/3833 #3833], [https://github.com/OSGeo/grass/pull/3840 #3840], [https://github.com/OSGeo/grass/pull/3814 #3814], [https://github.com/OSGeo/grass/pull/3799 #3799], [https://github.com/OSGeo/grass/pull/3834 #3834], [https://github.com/OSGeo/grass/pull/3815 #3815], [https://github.com/OSGeo/grass/pull/3820 #3820], [https://github.com/OSGeo/grass/pull/3818, #3818], [https://github.com/OSGeo/grass/pull/3813 #3813], [https://github.com/OSGeo/grass/pull/3855 #3855], [https://github.com/OSGeo/grass/pull/3817 #3817], [https://github.com/OSGeo/grass/pull/3812 #3812], [https://github.com/OSGeo/grass/pull/3859 #3859], [https://github.com/OSGeo/grass/pull/3860 #3860], [https://github.com/OSGeo/grass/pull/3861 #3861], [https://github.com/OSGeo/grass/pull/3841 #3841]
* Help Markus debugging Dockerfile builds. Reviewed docker-related PRs, improved docker builds, upgrade base images. (PRs: [https://github.com/OSGeo/grass/pull/3802 #3802], [https://github.com/OSGeo/grass/pull/3807 #3807], [https://github.com/OSGeo/grass/pull/3810 #3810], [https://github.com/OSGeo/grass/pull/3828 #3828], [https://github.com/OSGeo/grass/pull/3819 #3819], [https://github.com/OSGeo/grass/pull/3830 #3830], [https://github.com/OSGeo/grass/pull/3797 #3797], [https://github.com/OSGeo/grass/pull/3787 #3787], [https://github.com/OSGeo/grass/pull/3773 #3773], [https://github.com/OSGeo/grass/pull/3822 #3822], [https://github.com/OSGeo/grass/pull/3728 #3728])
* Helped multiple times Alen Mangafić with usage and building custom Docker images with different versions of PDAL.
* Designing and drafting the integration of docker build caching to improve build times whilst keeping risk of using cached old dependencies. [https://github.com/OSGeo/grass/pull/3821 #3821]
* With Vaclav Petras: reviewing backportable PRs, and designing the requirements and it's implementation of a automated backport solution with GitHub actions. Prioritized to work on the implementation after the sprint, as other features affecting productivity during the sprint should be worked on. Edit: implementation started on [https://github.com/echoix/grass/tree/backport-automation a branch of my fork]
* With Vaclav Petras: Discussing release notes generation improvements, deciding on new labels and classification, adjusting and improving titles regexes. Designed a process to validate PR that PR titles are classified correctly automatically, to greatly simplify future releases. This lead to Vaclav creating the validation function in [https://github.com/OSGeo/grass/pull/3824 PR #3824]. Implementation of validation workflow on PR creation and title changes will follow. PRs related to these decisions also include: [https://github.com/OSGeo/grass/pull/3823 #3823], [https://github.com/OSGeo/grass/pull/3829 #3829]
* Clarifying our supported languages standard support with Vaclav Petras and when changes should be made, leading to reduction of C/C++ CI usage in [https://github.com/OSGeo/grass/pull/3846 #3846]. Postponed checking of newer C++23 until Ubuntu 24.04 builds with newest GCC toolchain are included in CI.
* Helping Alen Mangafić with a local build to run alongside jupyter and conda environment.
* Reviewing Chung-Yuan Liang's PR, then assisting him multiple times with git operations, argparse, and unittest-related problems when programming. Sample of resulting PRs: [https://github.com/OSGeo/grass/pull/3835 #3835]
* Review and ajust repository's configuration to prevent some noticed problems, including pull request title/commit details (with Markus) and ruleset permissions related to branch creation (with Vaclav).
* PR title validation workflow implemented: [https://github.com/OSGeo/grass/pull/3877 #3877]
* Debug and investigate pytest timeout failures of [https://github.com/OSGeo/grass/pull/3879 #3879] that that same PR was supposed to prevent. The most probable explanation requires changing the multiprocessing startup method from fork to spawn, that also requires the code to be pickle-able. Alternative solution to avoid this requires changes of blocked and unmerged PRs that I worked to unblock. Unblocking these is also required to run pytest on macOS and Windows, and for a future python 3.14 on Linux too.
* Finish debugging porting Travis CI to Ubuntu 22.04 (Jammy) to unblock other PRs. Needed to fix some errors from -Wdeprecated-non-prototype to make Travis pass with the new -Werror flag. PR: [https://github.com/OSGeo/grass/pull/3002 #3002]
* Windows test failures due to external web content used for g.extension tests not being available for 8.5 on winGRASS yet. [https://github.com/OSGeo/grass/issues/3893 #3893]

=== Vaclav Petras ===

* PR reviews (a lot)
* Work on RC1 (release notes, automatic generators)
* Venue organizing and hosting
* Review of media posts

Talk:GRASS Community Meeting Prague 2024

2024-06-19T15:17:43Z

Lads: /* Luís de Sousa */

{{toc|right}}

Quick links: [[GRASS Community Meeting Prague 2024|Meeting page]] | [[#Reports|Reports]] | [[GRASS_Community_Meeting_Prague_2024#Sponsors|Sponsors]]

== Organizing Team ==

* Initial planning: Vaclav Petras, Veronica Andreo, Markus Neteler, Anna Petrasova, Martin Landa, Helmut Kudrnovsky, Helena Mitasova
* Budget: Vaclav Petras, Anna Petrasova, Markus Neteler, Veronica Andreo, Helena Mitasova
* Raising support: Vaclav Petras, Veronica Andreo, Markus Neteler, Helmut Kudrnovsky, Anna Petrasova
* Reimbursements: Vaclav Petras
* Venue: Vaclav Petras
* Meals: Caitlin Haedrich, Alen Mangafić, Martin Landa, Anna Petrasova, Vaclav Petras, Ondrej Pesek, Veronica Andreo
* Agenda: Veronica Andreo, Anna Petrasova
* Wiki page: Vaclav Petras, Veronica Andreo, Martin Landa
* Virtual participant support: Veronica Andreo
* T-shirts, hoodies, stickers: Vaclav Petras, Veronica Andreo
* Promotion, invitations, and social media: Caitlin Haedrich, Veronica Andreo, Vaclav Petras
* Photography: Caitlin Haedrich, Helmut Kudrnovsky

== 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.
* Link the [https://github.com/orgs/OSGeo/projects/1/ GRASS Community Meeting Prague 2023] project on GitHub to each PR or issue you are working on or plan to be working on.
* 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.)

=== Floris Vanderhaeghe ===

* Make maintenance pull requests [https://github.com/rsbivand/rgrass/pull/90 PR #90] and [https://github.com/rsbivand/rgrass/pull/91 PR #91] to support future contributors of the [https://github.com/rsbivand/rgrass R package rgrass].
* Test the standalone GDAL-GRASS driver in R and create issues [https://github.com/OSGeo/gdal-grass/issues/46 #46], [https://github.com/OSGeo/gdal-grass/issues/47 #47], [https://github.com/OSGeo/gdal-grass/issues/48 #48] and [https://github.com/OSGeo/gdal-grass/issues/49 #49] in its code repository, with help of Markus Neteler.
* Implement the GDAL-GRASS driver in the <code>read_VECT()</code> function of [https://github.com/rsbivand/rgrass R package rgrass], as well as some associated enhancements. See [https://github.com/rsbivand/rgrass/pull/93 PR #93].
* Make an [https://github.com/rsbivand/rgrass/issues/92 issue], with the help of Helmut Kudrnovsky and Veronica Andreo, about launching R in the OSGeo4W shell independently of GRASS GIS.
* Help sorting out a few issues in the [https://github.com/rsbivand/rgrass repository of R package rgrass].
* Point at the PROJJSON specification in support of GRASS GIS issue [https://github.com/OSGeo/grass/issues/3020 #3020].
* Participate in the GRASS GIS roadmap discussion on Saturday.
* Participate in the discussion on interfacing GRASS GIS from QGIS. See [https://github.com/OSGeo/grass/discussions/3898 meeting minutes].

=== Markus Neteler ===

* cleanup labels in GitHub repo
* replace --tmp-location with --tmp-project (pull requests [https://github.com/OSGeo/grass/pull/3825 PR #3825], [https://github.com/OSGeo/grass/pull/3822 PR #3822])
* docker: remove "grass-session" pip approach, replace to new build-in Python API (pull request [https://github.com/OSGeo/grass/pull/3819 PR #3819])
* Participated in the PSC meeting to define elections date and other elections related issues. See [[PSC_Meeting_2024-06-14]].
* Discussion about our Dockerfiles
* Simplified examples for working with GRASS 8.4+ in Python (update [https://gis.stackexchange.com/a/457875/687 Stackexchange posts])
* Participated of the roadmap discussion session
* cleanup of many pull request titles to be recognized by https://github.com/OSGeo/grass/blob/main/utils/release.yml
* Complete OpenSSF Best Practices badge questionnaire to 100%: https://www.bestpractices.dev/en/projects/2470
* backport plenty of pull requests to GRASS GIS 8.4 release branch
* lib/gis: modernize getl2() https://github.com/OSGeo/grass/pull/3850
* social media outreach: suggest use of Publer.io to easier feed our channels (discuss with Vero and Caitlin)
* work on 8.4.0RC1, together with Vaclav, see https://github.com/OSGeo/grass/releases
* Participation in QGIS-GRASS session with Nyall Dawson
* Worked with Vero on the highlights for the 8.4.0RC1 release notes.
* Updated hugo version on the website, see also [https://github.com/OSGeo/grass-website/pull/438 PR]

=== Veronica Andreo ===

* Discuss tutorial topics with Alen
* Reviewed and tested contributions by the Google Summer of Code student working on EODAG integration.
* Reviewed other PRs: temporal framework, tutorial on GRASS usage within Jupyter on Windows, t.stac, among others.
* Participated in the PSC meeting to define elections date and other elections related issues. See [[PSC_Meeting_2024-06-14]].
* Compiled the raw list of contributors since Dec 2020, to create the list of voters, as discussed in PSC meeting.
* Set up a swag shop in RedBubble and added designs with color and white logos. Yet not published as payment details need to be configured with OSGeo treasurer.
* Participated of the roadmap discussion session - Roadmap will be published in the website.
* Participated of the documentation discussion session.
* Participated of the call with Nyall Dawson about improving GRASS-QGIS integration.
* Worked with Markus on the highlights for the RC1 release notes.
* Assisted Caitlin with social media posting, review posts and setting up Publer and Buffer services suggested by Markus to streamline posting in various channels.
* Discussed and tested gdal-grass driver implementation by Floris.
* Went through grass-website issues, closed some, pinged in others and changed hugo version in the website [https://github.com/OSGeo/grass-website/pull/438 PR].
* Reviewed PR and tested the upcoming t.stac tool.

=== Alen Mangafić ===
* Discuss tutorial with Veronica and Vaclav.
* Setting up the environment for the tutorial with Ondřej and Corey, resulting in a process to build a Docker container with the main branch and it's kernel connection to Jupyter Lab.
* Writing a Jupyter Lab framework which works. Helped by Vaclav with locating the "GISENV" location bug.
* Data preparation: correction the point clouds to match correct Global Encoding value of a LAS 1.4 file with PDRF 6 - 10 is 17 (16 + 1); CRS definition.
* Testing and drafting the workflow in GUI.
* Found a and reported a bug about how r.in.pdal handles the number of returns ([https://github.com/OSGeo/grass/issues/3827 #3827]).
* Built a micromamba python environment for grass scripting with point cloud visualization with help of Edouard.
* Writing the tutorial.

=== Corey White ===

* Discussed and reviewed PRs for Google Summer of Code json and jupyter notebook projects.
* Helped setting up Docker environment for GRASS GIS and Jupyter Lab.
* Working on t.stac.* addon. (PR https://github.com/OSGeo/grass-addons/pull/802)
* Opened PR for new point pattern analysis tool v.paa (https://github.com/OSGeo/grass/pull/3826)

=== Luís de Sousa ===

* Debugging [https://github.com/OSGeo/grass/issues/2187 issue #2187] ([https://github.com/OSGeo/grass/pull/3869 PR #3869])
* Unit tests for [https://github.com/OSGeo/grass/tree/main/vector/v.out.ogr v.out.ogr] ([https://github.com/OSGeo/grass/pull/3848 PR #3848])
* Unit tests for [https://github.com/OSGeo/grass/tree/main/raster/r.out.gdal r.out.gdal] ([https://github.com/OSGeo/grass/pull/3903 PR #3903])
* Updates to add-ons documentation ([https://github.com/OSGeo/grass-addons/pull/1105 PR #1105])
* Review to Unit Test documentation ([https://github.com/OSGeo/grass/issues/3887 issue #3887])
* Discussion on parallel computation, sparked by [https://www.linkedin.com/feed/update/urn:li:activity:7208372306924994560?commentUrn=urn%3Ali%3Acomment%3A%28activity%3A7208372306924994560%2C7208521495923306496%29&dashCommentUrn=urn%3Ali%3Afsd_comment%3A%287208521495923306496%2Curn%3Ali%3Aactivity%3A7208372306924994560%29 Tom Hengl's remarks]:
** several approaches exist (documented in the [https://github.com/ncsu-geoforall-lab/opengeohub-2023 OpenGeoHub 2023 workshop]) but not all accessible to non-programmers;
** most modules obvious to be parallelised have [https://grass.osgeo.org/grass83/manuals/keywords.html#parallel already been so];
** patching of results is an issue (high overhead), although in the GridModule a virtual raster could be an option.

=== Anna Petrasova ===
* Participated in the PSC meeting to define elections date and other elections related issues. See [[PSC_Meeting_2024-06-14]].
* Discussed and reviewed PR for Google Summer of Code jupyter notebook projects.
* Reviewing v.surf.rst PR (Cross-validation OpenMP support, PR #3590)
* Tasked Caitlin to show layer controller in grass.jupyter.InteractiveMap by default, defined implementation, reviewed her PR (#3880)
* Solving conflict and reviewing PR #2481
* Testing and reviewing r.texture PR #3857, running benchmarks on laptop and desktop.
* Participated in QGIS discussion, put together meeting minutes: https://github.com/OSGeo/grass/discussions/3898
* Participated in the roadmap discussion session.
* Participated in the documentation discussion session.
* Restructured CONTRIBUTING.md by moving out Github workflow into separate file
* Led GSoC students presentations.
* Participated in discussion about parallelization with Luis and Vashek, Caitlin and others

=== Chung-Yuan Liang ===
* Refactored r.texture and updated tests (PR [https://github.com/OSGeo/grass/pull/3785 #3785], [https://github.com/OSGeo/grass/pull/3786 #3786]).
* Parallelized r.texture and provided benchmarks.
* Revised v.surf.rst PR (Cross-validation OpenMP support, PR [https://github.com/OSGeo/grass/pull/3590 #3590]).
* Enabled Python benchmark module to plot speedup and efficiency (PR [https://github.com/OSGeo/grass/pull/3835 #3835]).
* Parallelized r.horizon and provided benchmarks. (PR [https://github.com/OSGeo/grass/pull/3890 #3890])
* Discussed details of parallelizing modules with Vashek and Anna.

=== Caitlin Haedrich ===
* Discussed GRASS, Jupyter and Windows with Heli
* Wrote tutorial for using OSGeo4W to set up Jupyter Lab in Notebooks - [https://github.com/ncsu-geoforall-lab/tutorials/pull/3 PR]
* Set up Publer account for social media management, compared with Buffer
* Took pictures and posted 2x daily to social media
* Added Layer Control by default to grass.jupyter.InteractiveMap() - [https://github.com/OSGeo/grass/pull/3880 PR]
* Reviewed all GRASS GIS online profiled and compiled list that need updating (report in progress)

=== Edouard Choinière ===
* Discussion with Vaclav Petras on current state of python packaging, build, and testing framework and coverage, Windows porting improvements, and future plans. Planning for the week. Lead to PRs addressing Windows blockers: [https://github.com/OSGeo/grass/pull/3850 #3850] and [https://github.com/OSGeo/grass/pull/3853 #3853], which I tested on my fork combined with my changes highlighting the bugs.
* Reviewing of PRs, managing CI during the sprint (restarting transient failures, finding inefficiencies, queueing jobs before and after active periods).
* Maintaining code quality CI and pre-commit. Example: Flake8 fails with Python 3.12 in pre-commit, as it is way outdated, harming contributions of the sprint's participants. Bumping to a new version has other failures and dependent changes needed. Related PRs include: [https://github.com/OSGeo/grass/pull/3808 #3808], [https://github.com/OSGeo/grass/pull/3831 #3831], [https://github.com/OSGeo/grass/pull/3833 #3833], [https://github.com/OSGeo/grass/pull/3840 #3840], [https://github.com/OSGeo/grass/pull/3814 #3814], [https://github.com/OSGeo/grass/pull/3799 #3799], [https://github.com/OSGeo/grass/pull/3834 #3834], [https://github.com/OSGeo/grass/pull/3815 #3815], [https://github.com/OSGeo/grass/pull/3820 #3820], [https://github.com/OSGeo/grass/pull/3818, #3818], [https://github.com/OSGeo/grass/pull/3813 #3813], [https://github.com/OSGeo/grass/pull/3855 #3855], [https://github.com/OSGeo/grass/pull/3817 #3817], [https://github.com/OSGeo/grass/pull/3812 #3812], [https://github.com/OSGeo/grass/pull/3859 #3859], [https://github.com/OSGeo/grass/pull/3860 #3860], [https://github.com/OSGeo/grass/pull/3861 #3861], [https://github.com/OSGeo/grass/pull/3841 #3841]
* Help Markus debugging Dockerfile builds. Reviewed docker-related PRs, improved docker builds, upgrade base images. (PRs: [https://github.com/OSGeo/grass/pull/3802 #3802], [https://github.com/OSGeo/grass/pull/3807 #3807], [https://github.com/OSGeo/grass/pull/3810 #3810], [https://github.com/OSGeo/grass/pull/3828 #3828], [https://github.com/OSGeo/grass/pull/3819 #3819], [https://github.com/OSGeo/grass/pull/3830 #3830], [https://github.com/OSGeo/grass/pull/3797 #3797], [https://github.com/OSGeo/grass/pull/3787 #3787], [https://github.com/OSGeo/grass/pull/3773 #3773], [https://github.com/OSGeo/grass/pull/3822 #3822], [https://github.com/OSGeo/grass/pull/3728 #3728])
* Helped multiple times Alen Mangafić with usage and building custom Docker images with different versions of PDAL.
* Designing and drafting the integration of docker build caching to improve build times whilst keeping risk of using cached old dependencies. [https://github.com/OSGeo/grass/pull/3821 #3821]
* With Vaclav Petras: reviewing backportable PRs, and designing the requirements and it's implementation of a automated backport solution with GitHub actions. Prioritized to work on the implementation after the sprint, as other features affecting productivity during the sprint should be worked on. Edit: implementation started on [https://github.com/echoix/grass/tree/backport-automation a branch of my fork]
* With Vaclav Petras: Discussing release notes generation improvements, deciding on new labels and classification, adjusting and improving titles regexes. Designed a process to validate PR that PR titles are classified correctly automatically, to greatly simplify future releases. This lead to Vaclav creating the validation function in [https://github.com/OSGeo/grass/pull/3824 PR #3824]. Implementation of validation workflow on PR creation and title changes will follow. PRs related to these decisions also include: [https://github.com/OSGeo/grass/pull/3823 #3823], [https://github.com/OSGeo/grass/pull/3829 #3829]
* Clarifying our supported languages standard support with Vaclav Petras and when changes should be made, leading to reduction of C/C++ CI usage in [https://github.com/OSGeo/grass/pull/3846 #3846]. Postponed checking of newer C++23 until Ubuntu 24.04 builds with newest GCC toolchain are included in CI.
* Helping Alen Mangafić with a local build to run alongside jupyter and conda environment.
* Reviewing Chung-Yuan Liang's PR, then assisting him multiple times with git operations, argparse, and unittest-related problems when programming. Sample of resulting PRs: [https://github.com/OSGeo/grass/pull/3835 #3835]
* Review and ajust repository's configuration to prevent some noticed problems, including pull request title/commit details (with Markus) and ruleset permissions related to branch creation (with Vaclav).
* PR title validation workflow implemented: [https://github.com/OSGeo/grass/pull/3877 #3877]
* Debug and investigate pytest timeout failures of [https://github.com/OSGeo/grass/pull/3879 #3879] that that same PR was supposed to prevent. The most probable explanation requires changing the multiprocessing startup method from fork to spawn, that also requires the code to be pickle-able. Alternative solution to avoid this requires changes of blocked and unmerged PRs that I worked to unblock. Unblocking these is also required to run pytest on macOS and Windows, and for a future python 3.14 on Linux too.
* Finish debugging porting Travis CI to Ubuntu 22.04 (Jammy) to unblock other PRs. Needed to fix some errors from -Wdeprecated-non-prototype to make Travis pass with the new -Werror flag. PR: [https://github.com/OSGeo/grass/pull/3002 #3002]
* Windows test failures due to external web content used for g.extension tests not being available for 8.5 on winGRASS yet. [https://github.com/OSGeo/grass/issues/3893 #3893]

=== Vaclav Petras ===

* PR reviews (a lot)
* Work on RC1 (release notes, automatic generators)
* Venue organizing and hosting
* Review of media posts

Talk:GRASS Community Meeting Prague 2024

2024-06-19T09:40:17Z

Lads: /* Luís de Sousa */

{{toc|right}}

Quick links: [[GRASS Community Meeting Prague 2024|Meeting page]] | [[#Reports|Reports]] | [[GRASS_Community_Meeting_Prague_2024#Sponsor_us!|Sponsors]]

== Organizing Team ==

* Initial planning: Vaclav Petras, Veronica Andreo, Markus Neteler, Anna Petrasova, Martin Landa, Helmut Kudrnovsky, Helena Mitasova
* Budget: Vaclav Petras, Anna Petrasova, Markus Neteler, Veronica Andreo, Helena Mitasova
* Raising support: Vaclav Petras, Veronica Andreo, Markus Neteler, Helmut Kudrnovsky, Anna Petrasova
* Reimbursements: Vaclav Petras
* Venue: Vaclav Petras
* Food coordination: Anna Petrasova, Martin Landa, Caitlin Haedrich, Vaclav Petras, Ondrej Pesek, Veronica Andreo
* Agenda: Veronica Andreo, Anna Petrasova
* Wiki page: Vaclav Petras, Veronica Andreo, Martin Landa
* Virtual participant support: Veronica Andreo
* T-shirts, hoodies, stickers: Vaclav Petras, Veronica Andreo
* Promotion, invitations, and social media: Caitlin Haedrich, Veronica Andreo, Vaclav Petras
* Photography: Caitlin Haedrich, Helmut Kudrnovsky

== 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.
* Link the [https://github.com/orgs/OSGeo/projects/1/ GRASS Community Meeting Prague 2023] project on GitHub to each PR or issue you are working on or plan to be working on.
* 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.)

=== Floris Vanderhaeghe ===

* Make maintenance pull requests [https://github.com/rsbivand/rgrass/pull/90 PR #90] and [https://github.com/rsbivand/rgrass/pull/91 PR #91] to support future contributors of the [https://github.com/rsbivand/rgrass R package rgrass].
* Test the standalone GDAL-GRASS driver in R and create issues [https://github.com/OSGeo/gdal-grass/issues/46 #46], [https://github.com/OSGeo/gdal-grass/issues/47 #47] and [https://github.com/OSGeo/gdal-grass/issues/48 #48] in its code repository.
* Implement the GDAL-GRASS driver in the <code>read_RAST()</code> and <code>read_VECT()</code> functions of [https://github.com/rsbivand/rgrass R package rgrass], as well as some associated enhancements. See [https://github.com/rsbivand/rgrass/pull/93 PR #93].
* Make an [https://github.com/rsbivand/rgrass/issues/92 issue], with the help of Helmut Kudrnovsky and Veronica Andreo, about launching R in the OSGeo4W shell independently of GRASS GIS.
* Help sorting out a few issues in the [https://github.com/rsbivand/rgrass repository of R package rgrass].
* Point at the PROJJSON specification in support of GRASS GIS issue [https://github.com/OSGeo/grass/issues/3020 #3020].
* Participate in the GRASS GIS roadmap discussion on Saturday.

=== Markus Neteler ===

* cleanup labels in GitHub repo
* replace --tmp-location with --tmp-project (pull requests [https://github.com/OSGeo/grass/pull/3825 PR #3825], [https://github.com/OSGeo/grass/pull/3822 PR #3822])
* docker: remove "grass-session" pip approach, replace to new build-in Python API (pull request [https://github.com/OSGeo/grass/pull/3819 PR #3819])
* Participated in the PSC meeting to define elections date and other elections related issues. See [[PSC_Meeting_2024-06-14]].
* Discussion about our Dockerfiles
* Simplified examples for working with GRASS 8.4+ in Python (update [https://gis.stackexchange.com/a/457875/687 Stackexchange posts])
* Participated of the roadmap discussion session
* cleanup of many pull request titles to be recognized by https://github.com/OSGeo/grass/blob/main/utils/release.yml
* Complete OpenSSF Best Practices badge questionnaire to 100%: https://www.bestpractices.dev/en/projects/2470
* backport plenty of pull requests to GRASS GIS 8.4 release branch
* lib/gis: modernize getl2() https://github.com/OSGeo/grass/pull/3850
* social media outreach: suggest use of Publer.io to easier feed our channels (discuss with Vero and Caitlin)
* work on 8.4.0RC1, together with Vaclav, see https://github.com/OSGeo/grass/releases
* Participation in QGIS-GRASS session with Nyall Dawson
* Worked with Vero on the highlights for the 8.4.0RC1 release notes.
* Updated hugo version on the website, see also [https://github.com/OSGeo/grass-website/pull/438 PR]

=== Veronica Andreo ===

* Discuss tutorial topics with Alen
* Reviewed and tested contributions by the Google Summer of Code student working on EODAG integration.
* Reviewed other PRs: temporal framework, tutorial on GRASS usage within Jupyter on Windows, t.stac, among others.
* Participated in the PSC meeting to define elections date and other elections related issues. See [[PSC_Meeting_2024-06-14]].
* Compiled the raw list of contributors since Dec 2020, to create the list of voters, as discussed in PSC meeting.
* Set up a swag shop in RedBubble and added designs with color and white logos. Yet not published as payment details need to be configured with OSGeo treasurer.
* Participated of the roadmap discussion session - Roadmap will be published in the website.
* Participated of the documentation discussion session.
* Participated of the call with Nyall Dawson about improving GRASS-QGIS integration.
* Worked with Markus on the highlights for the RC1 release notes.
* Assisted Caitlin with social media posting, review posts and setting up Publer and Buffer services suggested by Markus to streamline posting in various channels.
* Discussed and tested gdal-grass driver implementation by Floris.
* Tested upcoming t.stac tool.
* Went through grass-website issues, closed some, pinged in others and changed hugo version in the website [https://github.com/OSGeo/grass-website/pull/438 PR].

=== Alen Mangafić ===
* Discuss tutorial with Veronica and Vaclav.
* Setting up the environment for the tutorial with Ondřej and Corey, resulting in a process to build a Docker container with the main branch and it's kernel connection to Jupyter Lab.
* Writing a Jupyter Lab framework which works. Helped by Vaclav with locating the "GISENV" location bug.
* Data preparation: correction the point clouds to match correct Global Encoding value of a LAS 1.4 file with PDRF 6 - 10 is 17 (16 + 1); CRS definition.
* Testing and drafting the workflow in GUI.
* Found a and reported a bug about how r.in.pdal handles the number of returns ([https://github.com/OSGeo/grass/issues/3827 #3827]).
* Built a micromamba python environment for grass scripting with point cloud visualization with help of Edouard.
* Writing the tutorial.

=== Corey White ===

* Discussed and reviewed PRs for Google Summer of Code json and jupyter notebook projects.
* Helped setting up Docker environment for GRASS GIS and Jupyter Lab.
* Working on t.stac.* addon. (PR https://github.com/OSGeo/grass-addons/pull/802)
* Opened PR for new point pattern analysis tool v.paa (https://github.com/OSGeo/grass/pull/3826)

=== Luís de Sousa ===

* Debugging [https://github.com/OSGeo/grass/issues/2187 issue #2187] ([https://github.com/OSGeo/grass/pull/3869 PR #3869])
* Unit tests for [https://github.com/OSGeo/grass/tree/main/vector/v.out.ogr v.out.ogr] ([https://github.com/OSGeo/grass/pull/3848 PR #3848])
* Updates to add-ons documentation ([https://github.com/OSGeo/grass-addons/pull/1105 PR #1105])
* Review to Unit Test documentation ([https://github.com/OSGeo/grass/issues/3887 issue #3887])
* Discussion on parallel computation:
** several approaches exist (documented in the [https://github.com/ncsu-geoforall-lab/opengeohub-2023 OpenGeoHub 2023 workshop]) but not all accessible to non-programmers;
** most modules obvious to be parallelised have [https://grass.osgeo.org/grass83/manuals/keywords.html#parallel already been so];
** patching of results is an issue (high overhead), although in the GridModule a virtual raster could be an option.

=== Anna Petrasova ===
* Participated in the PSC meeting to define elections date and other elections related issues. See [[PSC_Meeting_2024-06-14]].
* Discussed and reviewed PR for Google Summer of Code jupyter notebook projects.
* Reviewing v.surf.rst PR (Cross-validation OpenMP support, PR #3590)
* Tasked Caitlin to show layer controller in grass.jupyter.InteractiveMap by default, defined implementation, reviewed her PR (#3880)
* Solving conflict and reviewing PR #2481
* Testing and reviewing r.texture PR #3857, running benchmarks on laptop and desktop.
* Participated in QGIS discussion, put together meeting minutes.
* Participated in the roadmap discussion session.
* Participated in the documentation discussion session.
* Restructured CONTRIBUTING.md by moving out Github workflow into separate file
* Led GSoC students presentations.

=== Chung-Yuan Liang ===
* Refactored r.texture and updated tests (PR #3785, #3786).
* Parallelized r.texture and provided benchmarks.
* Revised v.surf.rst PR (Cross-validation OpenMP support, PR #3590).
* Enabled Python benchmark module to plot speedup or efficiency.

=== Caitlin Haedrich ===
* Discussed GRASS, Jupyter and Windows with Heli
* Wrote tutorial for using OSGeo4W to set up Jupyter Lab in Notebooks ([PR](https://github.com/ncsu-geoforall-lab/tutorials/pull/3))
* Set up Publer account for social media management, compared with Buffer
* Took pictures and posted 2x daily to social media
* Added Layer Control by default to grass.jupyter.InteractiveMap() ([PR](https://github.com/OSGeo/grass/pull/3880))
* Reviewed all GRASS GIS online profiled and compiled list that need updating (report in progress)

=== Edouard Choinière ===
* Discussion with Vaclav Petras on current state of python packaging, build, and testing framework and coverage, Windows porting improvements, and future plans. Planning for the week. Lead to PRs addressing Windows blockers: [https://github.com/OSGeo/grass/pull/3850 #3850] and [https://github.com/OSGeo/grass/pull/3853 #3853], which I tested on my fork combined with my changes highlighting the bugs.
* Reviewing of PRs, managing CI during the sprint (restarting transient failures, finding inefficiencies, queueing jobs before and after active periods).
* Maintaining code quality CI and pre-commit. Example: Flake8 fails with Python 3.12 in pre-commit, as it is way outdated, harming contributions of the sprint's participants. Bumping to a new version has other failures and dependent changes needed. Related PRs include: [https://github.com/OSGeo/grass/pull/3808 #3808], [https://github.com/OSGeo/grass/pull/3831 #3831], [https://github.com/OSGeo/grass/pull/3833 #3833], [https://github.com/OSGeo/grass/pull/3840 #3840], [https://github.com/OSGeo/grass/pull/3814 #3814], [https://github.com/OSGeo/grass/pull/3799 #3799], [https://github.com/OSGeo/grass/pull/3834 #3834], [https://github.com/OSGeo/grass/pull/3815 #3815], [https://github.com/OSGeo/grass/pull/3820 #3820], [https://github.com/OSGeo/grass/pull/3818, #3818], [https://github.com/OSGeo/grass/pull/3813 #3813], [https://github.com/OSGeo/grass/pull/3855 #3855], [https://github.com/OSGeo/grass/pull/3817 #3817], [https://github.com/OSGeo/grass/pull/3812 #3812], [https://github.com/OSGeo/grass/pull/3859 #3859], [https://github.com/OSGeo/grass/pull/3860 #3860], [https://github.com/OSGeo/grass/pull/3861 #3861], [https://github.com/OSGeo/grass/pull/3841 #3841]
* Help Markus debugging Dockerfile builds. Reviewed docker-related PRs, improved docker builds, upgrade base images. (PRs: [https://github.com/OSGeo/grass/pull/3802 #3802], [https://github.com/OSGeo/grass/pull/3807 #3807], [https://github.com/OSGeo/grass/pull/3810 #3810], [https://github.com/OSGeo/grass/pull/3828 #3828], [https://github.com/OSGeo/grass/pull/3819 #3819], [https://github.com/OSGeo/grass/pull/3830 #3830], [https://github.com/OSGeo/grass/pull/3797 #3797], [https://github.com/OSGeo/grass/pull/3787 #3787], [https://github.com/OSGeo/grass/pull/3773 #3773], [https://github.com/OSGeo/grass/pull/3822 #3822], [https://github.com/OSGeo/grass/pull/3728 #3728])
* Helped multiple times Alen Mangafić with usage and building custom Docker images with different versions of PDAL.
* Designing and drafting the integration of docker build caching to improve build times whilst keeping risk of using cached old dependencies. [https://github.com/OSGeo/grass/pull/3821 #3821]
* With Vaclav Petras: reviewing backportable PRs, and designing the requirements and it's implementation of a automated backport solution with GitHub actions. Prioritized to work on the implementation after the sprint, as other features affecting productivity during the sprint should be worked on.
* With Vaclav Petras: Discussing release notes generation improvements, deciding on new labels and classification, adjusting and improving titles regexes. Designed a process to validate PR that PR titles are classified correctly automatically, to greatly simplify future releases. This lead to Vaclav creating the validation function in [https://github.com/OSGeo/grass/pull/3824 PR #3824]. Implementation of validation workflow on PR creation and title changes will follow. PRs related to these decisions also include: [https://github.com/OSGeo/grass/pull/3823 #3823], [https://github.com/OSGeo/grass/pull/3829 #3829]
* Clarifying our supported languages standard support with Vaclav Petras and when changes should be made, leading to reduction of C/C++ CI usage in [https://github.com/OSGeo/grass/pull/3846 #3846]. Postponed checking of newer C++23 until Ubuntu 24.04 builds with newest GCC toolchain are included in CI.
* Helping Alen Mangafić with a local build to run alongside jupyter and conda environment.
* Reviewing Chung-Yuan Liang's PR, then assisting him multiple times with git operations, argparse, and unittest-related problems when programming. Sample of resulting PRs: [https://github.com/OSGeo/grass/pull/3835 #3835]
* Review and ajust repository's configuration to prevent some noticed problems, including pull request title/commit details (with Markus) and ruleset permissions related to branch creation (with Vaclav).

=== Vaclav Petras ===

* PR reviews (a lot)
* Work on RC1 (release notes, automatic generators)
* Venue organizing and hosting
* Review of media posts

Talk:GRASS Community Meeting Prague 2024

2024-06-18T14:59:37Z

Lads: /* Luís de Sousa */

{{toc|right}}

Quick links: [[GRASS Community Meeting Prague 2024|Meeting page]] | [[#Reports|Reports]] | [[GRASS_Community_Meeting_Prague_2024#Sponsor_us!|Sponsors]]

== Organizing Team ==

* Initial planning: Vaclav Petras, Veronica Andreo, Markus Neteler, Anna Petrasova, Martin Landa, Helmut Kudrnovsky, Helena Mitasova
* Budget: Vaclav Petras, Anna Petrasova, Markus Neteler, Veronica Andreo, Helena Mitasova
* Raising support: Vaclav Petras, Veronica Andreo, Markus Neteler, Helmut Kudrnovsky, Anna Petrasova
* Reimbursements: Vaclav Petras
* Venue: Vaclav Petras
* Food coordination: Anna Petrasova, Martin Landa, Caitlin Haedrich, Vaclav Petras, Ondrej Pesek, Veronica Andreo
* Agenda: Veronica Andreo, Anna Petrasova
* Wiki page: Vaclav Petras, Veronica Andreo, Martin Landa
* Virtual participant support: Veronica Andreo
* T-shirts, hoodies, stickers: Vaclav Petras, Veronica Andreo
* Promotion, invitations, and social media: Caitlin Haedrich, Veronica Andreo, Vaclav Petras
* Photography: Caitlin Haedrich, Helmut Kudrnovsky

== 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.
* Link the [https://github.com/orgs/OSGeo/projects/1/ GRASS Community Meeting Prague 2023] project on GitHub to each PR or issue you are working on or plan to be working on.
* 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.)

=== Floris Vanderhaeghe ===

* Make maintenance pull requests [https://github.com/rsbivand/rgrass/pull/90 PR #90] and [https://github.com/rsbivand/rgrass/pull/91 PR #91] to support future contributors of the [https://github.com/rsbivand/rgrass R package rgrass].
* Test the standalone GDAL-GRASS driver in R and create issues [https://github.com/OSGeo/gdal-grass/issues/46 #46], [https://github.com/OSGeo/gdal-grass/issues/47 #47] and [https://github.com/OSGeo/gdal-grass/issues/48 #48] in its code repository.
* Implement the GDAL-GRASS driver in the <code>read_RAST()</code> and <code>read_VECT()</code> functions of [https://github.com/rsbivand/rgrass R package rgrass], as well as some associated enhancements. See [https://github.com/rsbivand/rgrass/pull/93 PR #93].
* Make an [https://github.com/rsbivand/rgrass/issues/92 issue], with the help of Helmut Kudrnovsky and Veronica Andreo, about launching R in the OSGeo4W shell independently of GRASS GIS.
* Help sorting out a few issues in the [https://github.com/rsbivand/rgrass repository of R package rgrass].
* Point at the PROJJSON specification in support of GRASS GIS issue [https://github.com/OSGeo/grass/issues/3020 #3020].
* Participate in the GRASS GIS roadmap discussion on Saturday.

=== Markus Neteler ===

* cleanup labels in GitHub repo
* replace --tmp-location with --tmp-project (pull requests [https://github.com/OSGeo/grass/pull/3825 PR #3825], [https://github.com/OSGeo/grass/pull/3822 PR #3822])
* docker: remove "grass-session" pip approach, replace to new build-in Python API (pull request [https://github.com/OSGeo/grass/pull/3819 PR #3819])
* Participated in the PSC meeting to define elections date and other elections related issues. See [[PSC_Meeting_2024-06-14]].
* Discussion about our Dockerfiles
* Simplified examples for working with GRASS 8.4+ in Python (update [https://gis.stackexchange.com/a/457875/687 Stackexchange posts])
* Participated of the roadmap discussion session
* cleanup of many pull request titles to be recognized by https://github.com/OSGeo/grass/blob/main/utils/release.yml
* Complete OpenSSF Best Practices badge questionnaire to 100%: https://www.bestpractices.dev/en/projects/2470
* backport plenty of pull requests to GRASS GIS 8.4 release branch
* lib/gis: modernize getl2() https://github.com/OSGeo/grass/pull/3850
* social media outreach: suggest use of Publer.io to easier feed our channels (discuss with Vero and Caitlin)
* work on 8.4.0RC1, together with Vaclav, see https://github.com/OSGeo/grass/releases
* Participation in QGIS-GRASS session with Nyall Dawson
* Worked with Vero on the highlights for the 8.4.0RC1 release notes.

=== Veronica Andreo ===

* Discuss tutorial topics with Alen
* Reviewed and tested contributions by the Google Summer of Code student working on EODAG integration.
* Reviewed other PRs: temporal framework, tutorial on GRASS usage within Jupyter on Windows, t.stac, among others.
* Participated in the PSC meeting to define elections date and other elections related issues. See [[PSC_Meeting_2024-06-14]].
* Compiled the raw list of contributors since Dec 2020, to create the list of voters, as discussed in PSC meeting.
* Set up a swag shop in RedBubble and added designs with color and white logos. Yet not published as payment details need to be configured with OSGeo treasurer.
* Participated of the roadmap discussion session - Roadmap will be published in the website.
* Participated of the documentation discussion session.
* Participated of the call with Nyall Dawson about improving GRASS-QGIS integration.
* Worked with Markus on the highlights for the RC1 release notes.
* Assisted Caitlin with social media posting and setting up Publer and Buffer services suggested by Markus to streamline posting in various channels.
* Discussed and tested gdal-grass driver implementation by Floris.

=== Alen Mangafić ===
* Discuss tutorial with Veronica and Vaclav.
* Setting up the environment for the tutorial with Ondřej and Corey, resulting in a process to build a Docker container with the main branch and it's kernel connection to Jupyter Lab.
* Writing a Jupyter Lab framework which works. Helped by Vaclav with locating the "GISENV" location bug.
* Data preparation: correction the point clouds to match correct Global Encoding value of a LAS 1.4 file with PDRF 6 - 10 is 17 (16 + 1); CRS definition.
* Testing and drafting the workflow in GUI.
* Found a and reported a bug about how r.in.pdal handles the number of returns ([https://github.com/OSGeo/grass/issues/3827 #3827]).
* Built a micromamba python environment for grass scripting with point cloud visualization with help of Edouard.
* Writing the tutorial.

=== Corey White ===

* Discussed and reviewed PRs for Google Summer of Code json and jupyter notebook projects.
* Helped setting up Docker environment for GRASS GIS and Jupyter Lab.
* Working on t.stac.* addon. (PR https://github.com/OSGeo/grass-addons/pull/802)
* Opened PR for new point pattern analysis tool v.paa (https://github.com/OSGeo/grass/pull/3826)

=== Luís de Sousa ===

* Debugging [https://github.com/OSGeo/grass/issues/2187 issue #2187] ([https://github.com/OSGeo/grass/pull/3869 PR #3869])
* Unit tests for [https://github.com/OSGeo/grass/tree/main/vector/v.out.ogr v.out.ogr] ([https://github.com/OSGeo/grass/pull/3848 PR #3848])
* Updates to add-ons documentation ([https://github.com/OSGeo/grass-addons/pull/1105 PR #1105])
* Review to Unit Test documentation ([https://github.com/OSGeo/grass/issues/3887 issue #3887])

=== Anna Petrasova ===
* Participated in the PSC meeting to define elections date and other elections related issues. See [[PSC_Meeting_2024-06-14]].
* Discussed and reviewed PR for Google Summer of Code jupyter notebook projects.
* Reviewing v.surf.rst PR (Cross-validation OpenMP support, PR #3590)
* Tasked Caitlin to show layer controller in grass.jupyter.InteractiveMap by default, defined implementation
* Solving conflict and reviewing PR #2481
* Testing r.texture PR #3857
* Participated in QGIS discussion, put together meeting minutes.
* Participated in the roadmap discussion session.
* Participated in the documentation discussion session.
* Restructured CONTRIBUTING.md by moving out Github workflow into separate file

=== Chung-Yuan Liang ===
* Refactored r.texture and updated tests (PR #3785, #3786).
* Parallelized r.texture and provided benchmarks.
* Revised v.surf.rst PR (Cross-validation OpenMP support, PR #3590).
* Enabled Python benchmark module to plot speedup or efficiency.

=== Caitlin Haedrich ===
* Discussed GRASS, Jupyter and Windows with Heli
* Wrote tutorial for using OSGeo4W to set up Jupyter Lab in Notebooks ([PR](https://github.com/ncsu-geoforall-lab/tutorials/pull/3))
* Set up Publer account for social media management, compared with Buffer
* Took pictures and posted 2x daily to social media
* Added Layer Control by default to grass.jupyter.InteractiveMap() ([PR](https://github.com/OSGeo/grass/pull/3880))
* Reviewed all GRASS GIS online profiled and compiled list that need updating (report in progress)

=== Edouard Choinière ===
* Discussion with Vaclav Petras on current state of python packaging, build, and testing framework and coverage, Windows porting improvements, and future plans. Planning for the week. Lead to PRs addressing Windows blockers: [https://github.com/OSGeo/grass/pull/3850 #3850] and [https://github.com/OSGeo/grass/pull/3853 #3853], which I tested on my fork combined with my changes highlighting the bugs.
* Reviewing of PRs, managing CI during the sprint (restarting transient failures, finding inefficiencies, queueing jobs before and after active periods).
* Maintaining code quality CI and pre-commit. Example: Flake8 fails with Python 3.12 in pre-commit, as it is way outdated, harming contributions of the sprint's participants. Bumping to a new version has other failures and dependent changes needed. Related PRs include: [https://github.com/OSGeo/grass/pull/3808 #3808], [https://github.com/OSGeo/grass/pull/3831 #3831], [https://github.com/OSGeo/grass/pull/3833 #3833], [https://github.com/OSGeo/grass/pull/3840 #3840], [https://github.com/OSGeo/grass/pull/3814 #3814], [https://github.com/OSGeo/grass/pull/3799 #3799], [https://github.com/OSGeo/grass/pull/3834 #3834], [https://github.com/OSGeo/grass/pull/3815 #3815], [https://github.com/OSGeo/grass/pull/3820 #3820], [https://github.com/OSGeo/grass/pull/3818, #3818], [https://github.com/OSGeo/grass/pull/3813 #3813], [https://github.com/OSGeo/grass/pull/3855 #3855], [https://github.com/OSGeo/grass/pull/3817 #3817], [https://github.com/OSGeo/grass/pull/3812 #3812], [https://github.com/OSGeo/grass/pull/3859 #3859], [https://github.com/OSGeo/grass/pull/3860 #3860], [https://github.com/OSGeo/grass/pull/3861 #3861], [https://github.com/OSGeo/grass/pull/3841 #3841]
* Help Markus debugging Dockerfile builds. Reviewed docker-related PRs, improved docker builds, upgrade base images. (PRs: [https://github.com/OSGeo/grass/pull/3802 #3802], [https://github.com/OSGeo/grass/pull/3807 #3807], [https://github.com/OSGeo/grass/pull/3810 #3810], [https://github.com/OSGeo/grass/pull/3828 #3828], [https://github.com/OSGeo/grass/pull/3819 #3819], [https://github.com/OSGeo/grass/pull/3830 #3830], [https://github.com/OSGeo/grass/pull/3797 #3797], [https://github.com/OSGeo/grass/pull/3787 #3787], [https://github.com/OSGeo/grass/pull/3773 #3773], [https://github.com/OSGeo/grass/pull/3822 #3822], [https://github.com/OSGeo/grass/pull/3728 #3728])
* Helped multiple times Alen Mangafić with usage and building custom Docker images with different versions of PDAL.
* Designing and drafting the integration of docker build caching to improve build times whilst keeping risk of using cached old dependencies. [https://github.com/OSGeo/grass/pull/3821 #3821]
* With Vaclav Petras: reviewing backportable PRs, and designing the requirements and it's implementation of a automated backport solution with GitHub actions. Prioritized to work on the implementation after the sprint, as other features affecting productivity during the sprint should be worked on.
* With Vaclav Petras: Discussing release notes generation improvements, deciding on new labels and classification, adjusting and improving titles regexes. Designed a process to validate PR that PR titles are classified correctly automatically, to greatly simplify future releases. This lead to Vaclav creating the validation function in [https://github.com/OSGeo/grass/pull/3824 PR #3824]. Implementation of validation workflow on PR creation and title changes will follow. PRs related to these decisions also include: [https://github.com/OSGeo/grass/pull/3823 #3823], [https://github.com/OSGeo/grass/pull/3829 #3829]
* Clarifying our supported languages standard support with Vaclav Petras and when changes should be made, leading to reduction of C/C++ CI usage in [https://github.com/OSGeo/grass/pull/3846 #3846]. Postponed checking of newer C++23 until Ubuntu 24.04 builds with newest GCC toolchain are included in CI.
* Helping Alen Mangafić with a local build to run alongside jupyter and conda environment.
* Reviewing Chung-Yuan Liang's PR, then assisting him multiple times with git operations, argparse, and unittest-related problems when programming. Sample of resulting PRs: [https://github.com/OSGeo/grass/pull/3835 #3835]
* Review and ajust repository's configuration to prevent some noticed problems, including pull request title/commit details (with Markus) and ruleset permissions related to branch creation (with Vaclav).

=== Vaclav Petras ===

Talk:GRASS Community Meeting Prague 2024

2024-06-17T13:55:14Z

Lads: /* Luís de Sousa */

{{toc|right}}

Quick links: [[GRASS Community Meeting Prague 2024|Meeting page]] | [[#Reports|Reports]] | [[GRASS_Community_Meeting_Prague_2024#Sponsor_us!|Sponsors]]

== Organizing Team ==

* Initial planning: Vaclav Petras, Veronica Andreo, Markus Neteler, Anna Petrasova, Martin Landa, Helmut Kudrnovsky, Helena Mitasova
* Budget: Vaclav Petras, Anna Petrasova, Markus Neteler, Veronica Andreo, Helena Mitasova
* Raising support: Vaclav Petras, Veronica Andreo, Markus Neteler, Helmut Kudrnovsky, Anna Petrasova
* Reimbursements: Vaclav Petras
* Venue: Vaclav Petras
* Food coordination: Anna Petrasova, Martin Landa, Caitlin Haedrich, Vaclav Petras, Ondrej Pesek, Veronica Andreo
* Agenda: Veronica Andreo, Anna Petrasova
* Wiki page: Vaclav Petras, Veronica Andreo, Martin Landa
* Virtual participant support: Veronica Andreo
* T-shirts, hoodies, stickers: Vaclav Petras, Veronica Andreo
* Promotion, invitations, and social media: Caitlin Haedrich, Veronica Andreo, Vaclav Petras
* Photography: Caitlin Haedrich, Helmut Kudrnovsky

== 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.
* Link the [https://github.com/orgs/OSGeo/projects/1/ GRASS Community Meeting Prague 2023] project on GitHub to each PR or issue you are working on or plan to be working on.
* 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.)

=== Floris Vanderhaeghe ===

* Make maintenance pull requests [https://github.com/rsbivand/rgrass/pull/90 PR #90] and [https://github.com/rsbivand/rgrass/pull/91 PR #91] to support future contributors of the [https://github.com/rsbivand/rgrass R package rgrass].
* Test the standalone GDAL-GRASS driver in R and create issues [https://github.com/OSGeo/gdal-grass/issues/46 #46], [https://github.com/OSGeo/gdal-grass/issues/47 #47] and [https://github.com/OSGeo/gdal-grass/issues/48 #48] in its code repository.
* Implement the GDAL-GRASS driver in the <code>read_RAST()</code> and <code>read_VECT()</code> functions of [https://github.com/rsbivand/rgrass R package rgrass], as well as some associated enhancements. See [https://github.com/rsbivand/rgrass/pull/93 PR #93].
* Make an [https://github.com/rsbivand/rgrass/issues/92 issue], with the help of Helmut Kudrnovsky and Veronica Andreo, about launching R in the OSGeo4W shell independently of GRASS GIS.
* Help sorting out a few issues in the [https://github.com/rsbivand/rgrass repository of R package rgrass].
* Point at the PROJJSON specification in support of GRASS GIS issue [https://github.com/OSGeo/grass/issues/3020 #3020].
* Participate in the GRASS GIS roadmap discussion on Saturday.

=== Markus Neteler ===

* cleanup labels in GitHub repo
* replace --tmp-location with --tmp-project (pull requests [https://github.com/OSGeo/grass/pull/3825 PR #3825], [https://github.com/OSGeo/grass/pull/3822 PR #3822])
* docker: remove "grass-session" pip approach, replace to new build-in Python API (pull request [https://github.com/OSGeo/grass/pull/3819 PR #3819])
* Participated in the PSC meeting to define elections date and other elections related issues. See [[PSC_Meeting_2024-06-14]].
* Discussion about our Dockerfiles
* Simplified examples for working with GRASS 8.4+ in Python (update [https://gis.stackexchange.com/a/457875/687 Stackexchange posts])
* Participated of the roadmap discussion session
* cleanup of many pull request titles to be recognized by https://github.com/OSGeo/grass/blob/main/utils/release.yml
* Complete OpenSSF Best Practices badge questionnaire to 100%: https://www.bestpractices.dev/en/projects/2470
* backport plenty of pull requests to GRASS GIS 8.4 release branch
* lib/gis: modernize getl2() https://github.com/OSGeo/grass/pull/3850
* social media outreach: suggest use of Publer.io to easier feed our channels (discuss with Vero and Caitlin)

=== Veronica Andreo ===

* Discuss tutorial topics with Alen
* Reviewed PRs: i.eodag, a couple related to the temporal framework, tutorial on GRASS usage within Jupyter on Windows, among others.
* Participated in the PSC meeting to define elections date and other elections related issues. See [[PSC_Meeting_2024-06-14]].
* Compiled the raw list of contributors since Dec 2020, to create the list of voters, as discussed in PSC meeting.
* Set up a swag shop in RedBubble and added designs with color and white logos. Yet not published as payment details need to be configured with OSGeo treasurer.
* Participated of the roadmap discussion session - Roadmap will be published in the website.
* Participated of the documentation discussion session.

=== Alen Mangafić ===
* Discuss tutorial with Veronica and Vaclav.
* Setting up the environment for the tutorial with Ondřej and Corey, resulting in a process to build a Docker container with the main branch and it's kernel connection to Jupyter Lab.
* Writing a Jupyter Lab framework which works. Helped by Vaclav with locating the "GISENV" location bug.
* Data preparation: correction the point clouds to match correct Global Encoding value of a LAS 1.4 file with PDRF 6 - 10 is 17 (16 + 1); CRS definition.
* Testing and drafting the workflow in GUI.
* Found a and reported a bug about how r.in.pdal handles the number of returns ([https://github.com/OSGeo/grass/issues/3827 #3827]).

=== Corey White ===

* Discussed and reviewed PRs for Google Summer of Code json and jupyter notebook projects.
* Helped setting up Docker environment for GRASS GIS and Jupyter Lab.
* Working on t.stac.* addon. (PR https://github.com/OSGeo/grass-addons/pull/802)
* Opened PR for new point pattern analysis tool v.paa (https://github.com/OSGeo/grass/pull/3826)

=== Luís de Sousa ===

* Debugging [https://github.com/OSGeo/grass/issues/2187 issue #2187] ([https://github.com/OSGeo/grass/pull/3869 PR #3869])
* Unit tests for [https://github.com/OSGeo/grass/tree/main/vector/v.out.ogr v.out.ogr] ([https://github.com/OSGeo/grass/pull/3848 PR #3848])
* Updates to add-ons documentation ([https://github.com/OSGeo/grass-addons/pull/1105 PR #1105])

=== Anna Petrasova ===
* Participated in the PSC meeting to define elections date and other elections related issues. See [[PSC_Meeting_2024-06-14]].
* Discussed and reviewed PR for Google Summer of Code jupyter notebook projects.
* Reviewing v.surf.rst PR (Cross-validation OpenMP support, PR #3590)
* Tasked Caitlin to show layer controller in grass.jupyter.InteractiveMap by default, defined implementation
* Solving conflict and reviewing PR #2481

=== Chung-Yuan Liang ===
* Refactored r.texture and updated tests (PR #3785, #3786).
* Parallelized r.texture and provided benchmarks.
* Revised v.surf.rst PR (Cross-validation OpenMP support, PR #3590).
* Enabled Python benchmark module to plot speedup or efficiency.

=== Caitlin Haedrich ===
* Discussed GRASS, Jupyter and Windows with Heli
* Wrote tutorial for using OSGeo4W to set up Jupyter Lab in Notebooks ([PR](https://github.com/ncsu-geoforall-lab/tutorials/pull/3))
* Set up Publer account for social media management
* Took pictures and posted 2x daily to social media
* Reviewed all GRASS GIS online profiled and compiled list that need updating (report in progress)

=== Edouard Choinière ===
* Discussion with Vaclav Petras on current state of python packaging, build, and testing framework and coverage, Windows porting improvements, and future plans. Planning for the week. Lead to PRs addressing Windows blockers: [https://github.com/OSGeo/grass/pull/3850 #3850] and [https://github.com/OSGeo/grass/pull/3853 #3853], which I tested on my fork combined with my changes highlighting the bugs.
* Reviewing of PRs, managing CI during the sprint (restarting transient failures, finding inefficiencies, queueing jobs before and after active periods).
* Maintaining code quality CI and pre-commit. Example: Flake8 fails with Python 3.12 in pre-commit, as it is way outdated, harming contributions of the sprint's participants. Bumping to a new version has other failures and dependent changes needed. Related PRs include: [https://github.com/OSGeo/grass/pull/3808 #3808], [https://github.com/OSGeo/grass/pull/3831 #3831], [https://github.com/OSGeo/grass/pull/3833 #3833], [https://github.com/OSGeo/grass/pull/3840 #3840], [https://github.com/OSGeo/grass/pull/3814 #3814], [https://github.com/OSGeo/grass/pull/3799 #3799], [https://github.com/OSGeo/grass/pull/3834 #3834], [https://github.com/OSGeo/grass/pull/3815 #3815], [https://github.com/OSGeo/grass/pull/3820 #3820], [https://github.com/OSGeo/grass/pull/3818, #3818], [https://github.com/OSGeo/grass/pull/3813 #3813], [https://github.com/OSGeo/grass/pull/3855 #3855], [https://github.com/OSGeo/grass/pull/3817 #3817], [https://github.com/OSGeo/grass/pull/3812 #3812], [https://github.com/OSGeo/grass/pull/3859 #3859], [https://github.com/OSGeo/grass/pull/3860 #3860], [https://github.com/OSGeo/grass/pull/3861 #3861], [https://github.com/OSGeo/grass/pull/3841 #3841]
* Help Markus debugging Dockerfile builds. Reviewed docker-related PRs, improved docker builds, upgrade base images. (PRs: [https://github.com/OSGeo/grass/pull/3802 #3802], [https://github.com/OSGeo/grass/pull/3807 #3807], [https://github.com/OSGeo/grass/pull/3810 #3810], [https://github.com/OSGeo/grass/pull/3828 #3828], [https://github.com/OSGeo/grass/pull/3819 #3819], [https://github.com/OSGeo/grass/pull/3830 #3830], [https://github.com/OSGeo/grass/pull/3797 #3797], [https://github.com/OSGeo/grass/pull/3787 #3787], [https://github.com/OSGeo/grass/pull/3773 #3773], [https://github.com/OSGeo/grass/pull/3822 #3822], [https://github.com/OSGeo/grass/pull/3728 #3728])
* Helped multiple times Alen Mangafić with usage and building custom Docker images with different versions of PDAL.
* Designing and drafting the integration of docker build caching to improve build times whilst keeping risk of using cached old dependencies. [https://github.com/OSGeo/grass/pull/3821 #3821]
* With Vaclav Petras: reviewing backportable PRs, and designing the requirements and it's implementation of a automated backport solution with GitHub actions. Prioritized to work on the implementation after the sprint, as other features affecting productivity during the sprint should be worked on.
* With Vaclav Petras: Discussing release notes generation improvements, deciding on new labels and classification, adjusting and improving titles regexes. Designed a process to validate PR that PR titles are classified correctly automatically, to greatly simplify future releases. This lead to Vaclav creating the validation function in [https://github.com/OSGeo/grass/pull/3824 PR #3824]. Implementation of validation workflow on PR creation and title changes will follow. PRs related to these decisions also include: [https://github.com/OSGeo/grass/pull/3823 #3823], [https://github.com/OSGeo/grass/pull/3829 #3829]
* Clarifying our supported languages standard support with Vaclav Petras and when changes should be made, leading to reduction of C/C++ CI usage in [https://github.com/OSGeo/grass/pull/3846 #3846]. Postponed checking of newer C++23 until Ubuntu 24.04 builds with newest GCC toolchain are included in CI.
* Helping Alen Mangafić with a local build to run alongside jupyter and conda environment.
* Reviewing Chung-Yuan Liang's PR, then assisting him multiple times with git operations, argparse, and unittest-related problems when programming. Sample of resulting PRs: [https://github.com/OSGeo/grass/pull/3835 #3835]
* Review and ajust repository's configuration to prevent some noticed problems, including pull request title/commit details (with Markus) and ruleset permissions related to branch creation (with Vaclav).

=== Vaclav Petras ===

Talk:GRASS Community Meeting Prague 2024

2024-06-17T13:35:55Z

Lads: /* Luís de Sousa */

{{toc|right}}

Quick links: [[GRASS Community Meeting Prague 2024|Meeting page]] | [[#Reports|Reports]] | [[GRASS_Community_Meeting_Prague_2024#Sponsor_us!|Sponsors]]

== Organizing Team ==

* Initial planning: Vaclav Petras, Veronica Andreo, Markus Neteler, Anna Petrasova, Martin Landa, Helmut Kudrnovsky, Helena Mitasova
* Budget: Vaclav Petras, Anna Petrasova, Markus Neteler, Veronica Andreo, Helena Mitasova
* Raising support: Vaclav Petras, Veronica Andreo, Markus Neteler, Helmut Kudrnovsky, Anna Petrasova
* Reimbursements: Vaclav Petras
* Venue: Vaclav Petras
* Food coordination: Anna Petrasova, Martin Landa, Caitlin Haedrich, Vaclav Petras, Ondrej Pesek, Veronica Andreo
* Agenda: Veronica Andreo, Anna Petrasova
* Wiki page: Vaclav Petras, Veronica Andreo, Martin Landa
* Virtual participant support: Veronica Andreo
* T-shirts, hoodies, stickers: Vaclav Petras, Veronica Andreo
* Promotion, invitations, and social media: Caitlin Haedrich, Veronica Andreo, Vaclav Petras
* Photography: Caitlin Haedrich, Helmut Kudrnovsky

== 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.
* Link the [https://github.com/orgs/OSGeo/projects/1/ GRASS Community Meeting Prague 2023] project on GitHub to each PR or issue you are working on or plan to be working on.
* 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.)

=== Floris Vanderhaeghe ===

* Make maintenance pull requests [https://github.com/rsbivand/rgrass/pull/90 PR #90] and [https://github.com/rsbivand/rgrass/pull/91 PR #91] to support future contributors of the [https://github.com/rsbivand/rgrass R package rgrass].
* Test the standalone GDAL-GRASS driver in R and create issues [https://github.com/OSGeo/gdal-grass/issues/46 #46], [https://github.com/OSGeo/gdal-grass/issues/47 #47] and [https://github.com/OSGeo/gdal-grass/issues/48 #48] in its code repository.
* Implement the GDAL-GRASS driver in the <code>read_RAST()</code> and <code>read_VECT()</code> functions of [https://github.com/rsbivand/rgrass R package rgrass], as well as some associated enhancements. See [https://github.com/rsbivand/rgrass/pull/93 PR #93].
* Make an [https://github.com/rsbivand/rgrass/issues/92 issue], with the help of Helmut Kudrnovsky and Veronica Andreo, about launching R in the OSGeo4W shell independently of GRASS GIS.
* Help sorting out a few issues in the [https://github.com/rsbivand/rgrass repository of R package rgrass].
* Point at the PROJJSON specification in support of GRASS GIS issue [https://github.com/OSGeo/grass/issues/3020 #3020].
* Participate in the GRASS GIS roadmap discussion on Saturday.

=== Markus Neteler ===

* cleanup labels in GitHub repo
* replace --tmp-location with --tmp-project (pull requests [https://github.com/OSGeo/grass/pull/3825 PR #3825], [https://github.com/OSGeo/grass/pull/3822 PR #3822])
* docker: remove "grass-session" pip approach, replace to new build-in Python API (pull request [https://github.com/OSGeo/grass/pull/3819 PR #3819])
* Participated in the PSC meeting to define elections date and other elections related issues. See [[PSC_Meeting_2024-06-14]].
* Discussion about our Dockerfiles
* Simplified examples for working with GRASS 8.4+ in Python (update [https://gis.stackexchange.com/a/457875/687 Stackexchange posts])
* Participated of the roadmap discussion session
* cleanup of many pull request titles to be recognized by https://github.com/OSGeo/grass/blob/main/utils/release.yml
* Complete OpenSSF Best Practices badge questionnaire to 100%: https://www.bestpractices.dev/en/projects/2470
* backport plenty of pull requests to GRASS GIS 8.4 release branch
* lib/gis: modernize getl2() https://github.com/OSGeo/grass/pull/3850
* social media outreach: suggest use of Publer.io to easier feed our channels (discuss with Vero and Caitlin)

=== Veronica Andreo ===

* Discuss tutorial topics with Alen
* Reviewed PRs: i.eodag, a couple related to the temporal framework, tutorial on GRASS usage within Jupyter on Windows, among others.
* Participated in the PSC meeting to define elections date and other elections related issues. See [[PSC_Meeting_2024-06-14]].
* Compiled the raw list of contributors since Dec 2020, to create the list of voters, as discussed in PSC meeting.
* Set up a swag shop in RedBubble and added designs with color and white logos. Yet not published as payment details need to be configured with OSGeo treasurer.
* Participated of the roadmap discussion session - Roadmap will be published in the website.
* Participated of the documentation discussion session.

=== Alen Mangafić ===
* Discuss tutorial with Veronica and Vaclav.
* Setting up the environment for the tutorial with Ondřej and Corey, resulting in a process to build a Docker container with the main branch and it's kernel connection to Jupyter Lab.
* Writing a Jupyter Lab framework which works. Helped by Vaclav with locating the "GISENV" location bug.
* Data preparation: correction the point clouds to match correct Global Encoding value of a LAS 1.4 file with PDRF 6 - 10 is 17 (16 + 1); CRS definition.
* Testing and drafting the workflow in GUI.
* Found a and reported a bug about how r.in.pdal handles the number of returns ([https://github.com/OSGeo/grass/issues/3827 #3827]).

=== Corey White ===

* Discussed and reviewed PRs for Google Summer of Code json and jupyter notebook projects.
* Helped setting up Docker environment for GRASS GIS and Jupyter Lab.
* Working on t.stac.* addon. (PR https://github.com/OSGeo/grass-addons/pull/802)
* Opened PR for new point pattern analysis tool v.paa (https://github.com/OSGeo/grass/pull/3826)

=== Luís de Sousa ===

* Debugging [https://github.com/OSGeo/grass/issues/2187 issue #2187]
* Unit tests for [https://github.com/OSGeo/grass/tree/main/vector/v.out.ogr v.out.ogr] ([https://github.com/OSGeo/grass/pull/3848 PR #3848])
* Updates to add-ons documentation ([https://github.com/OSGeo/grass-addons/pull/1105 PR #1105])

=== Anna Petrasova ===
* Participated in the PSC meeting to define elections date and other elections related issues. See [[PSC_Meeting_2024-06-14]].
* Discussed and reviewed PR for Google Summer of Code jupyter notebook projects.
* Reviewing v.surf.rst PR (Cross-validation OpenMP support, PR #3590)
* Tasked Caitlin to show layer controller in grass.jupyter.InteractiveMap by default, defined implementation
* Solving conflict and reviewing PR #2481

=== Chung-Yuan Liang ===
* Refactored r.texture and updated tests (PR #3785, #3786).
* Parallelized r.texture and provided benchmarks.
* Revised v.surf.rst PR (Cross-validation OpenMP support, PR #3590).
* Enabled Python benchmark module to plot speedup or efficiency.

=== Caitlin Haedrich ===
* Discussed GRASS, Jupyter and Windows with Heli
* Wrote tutorial for using OSGeo4W to set up Jupyter Lab in Notebooks ([PR](https://github.com/ncsu-geoforall-lab/tutorials/pull/3))
* Set up Publer account for social media management
* Took pictures and posted 2x daily to social media
* Reviewed all GRASS GIS online profiled and compiled list that need updating (report in progress)

=== Edouard Choinière ===
* Discussion with Vaclav Petras on current state of python packaging, build, and testing framework and coverage, Windows porting improvements, and future plans. Planning for the week. Lead to PRs addressing Windows blockers: [https://github.com/OSGeo/grass/pull/3850 #3850] and [https://github.com/OSGeo/grass/pull/3853 #3853], which I tested on my fork combined with my changes highlighting the bugs.
* Reviewing of PRs, managing CI during the sprint (restarting transient failures, finding inefficiencies, queueing jobs before and after active periods).
* Maintaining code quality CI and pre-commit. Example: Flake8 fails with Python 3.12 in pre-commit, as it is way outdated, harming contributions of the sprint's participants. Bumping to a new version has other failures and dependent changes needed. Related PRs include: [https://github.com/OSGeo/grass/pull/3808 #3808], [https://github.com/OSGeo/grass/pull/3831 #3831], [https://github.com/OSGeo/grass/pull/3833 #3833], [https://github.com/OSGeo/grass/pull/3840 #3840], [https://github.com/OSGeo/grass/pull/3814 #3814], [https://github.com/OSGeo/grass/pull/3799 #3799], [https://github.com/OSGeo/grass/pull/3834 #3834], [https://github.com/OSGeo/grass/pull/3815 #3815], [https://github.com/OSGeo/grass/pull/3820 #3820], [https://github.com/OSGeo/grass/pull/3818, #3818], [https://github.com/OSGeo/grass/pull/3813 #3813], [https://github.com/OSGeo/grass/pull/3855 #3855], [https://github.com/OSGeo/grass/pull/3817 #3817], [https://github.com/OSGeo/grass/pull/3812 #3812], [https://github.com/OSGeo/grass/pull/3859 #3859], [https://github.com/OSGeo/grass/pull/3860 #3860], [https://github.com/OSGeo/grass/pull/3861 #3861], [https://github.com/OSGeo/grass/pull/3841 #3841]
* Help Markus debugging Dockerfile builds. Reviewed docker-related PRs, improved docker builds, upgrade base images. (PRs: [https://github.com/OSGeo/grass/pull/3802 #3802], [https://github.com/OSGeo/grass/pull/3807 #3807], [https://github.com/OSGeo/grass/pull/3810 #3810], [https://github.com/OSGeo/grass/pull/3828 #3828], [https://github.com/OSGeo/grass/pull/3819 #3819], [https://github.com/OSGeo/grass/pull/3830 #3830], [https://github.com/OSGeo/grass/pull/3797 #3797], [https://github.com/OSGeo/grass/pull/3787 #3787], [https://github.com/OSGeo/grass/pull/3773 #3773], [https://github.com/OSGeo/grass/pull/3822 #3822], [https://github.com/OSGeo/grass/pull/3728 #3728])
* Helped multiple times Alen Mangafić with usage and building custom Docker images with different versions of PDAL.
* Designing and drafting the integration of docker build caching to improve build times whilst keeping risk of using cached old dependencies. [https://github.com/OSGeo/grass/pull/3821 #3821]
* With Vaclav Petras: reviewing backportable PRs, and designing the requirements and it's implementation of a automated backport solution with GitHub actions. Prioritized to work on the implementation after the sprint, as other features affecting productivity during the sprint should be worked on.
* With Vaclav Petras: Discussing release notes generation improvements, deciding on new labels and classification, adjusting and improving titles regexes. Designed a process to validate PR that PR titles are classified correctly automatically, to greatly simplify future releases. This lead to Vaclav creating the validation function in [https://github.com/OSGeo/grass/pull/3824 PR #3824]. Implementation of validation workflow on PR creation and title changes will follow. PRs related to these decisions also include: [https://github.com/OSGeo/grass/pull/3823 #3823], [https://github.com/OSGeo/grass/pull/3829 #3829]
* Clarifying our supported languages standard support with Vaclav Petras and when changes should be made, leading to reduction of C/C++ CI usage in [https://github.com/OSGeo/grass/pull/3846 #3846]. Postponed checking of newer C++23 until Ubuntu 24.04 builds with newest GCC toolchain are included in CI.
* Helping Alen Mangafić with a local build to run alongside jupyter and conda environment.
* Reviewing Chung-Yuan Liang's PR, then assisting him multiple times with git operations, argparse, and unittest-related problems when programming. Sample of resulting PRs: [https://github.com/OSGeo/grass/pull/3835 #3835]
* Review and ajust repository's configuration to prevent some noticed problems, including pull request title/commit details (with Markus) and ruleset permissions related to branch creation (with Vaclav).

=== Vaclav Petras ===

Talk:GRASS Community Meeting Prague 2024

2024-06-16T16:58:19Z

Lads: /* Luís de Sousa */

Talk:GRASS Community Meeting Prague 2024

2024-06-16T11:11:00Z

Lads: /* Luís de Sousa */

Talk:GRASS Community Meeting Prague 2024

2024-06-15T10:26:00Z

Lads: /* Reports */

GRASS Community Meeting Prague 2024

2024-05-27T10:50:22Z

Lads: /* Tuesday, June 18 */

{{toc|right}}
The ''GRASS GIS Community Meeting'' for contributors and developers will be happening from '''June 14 to June 19, 2024''' in Prague, Czechia.

[[File:Prague-Community-Meeting-2023-crop.jpg|500px|frameless|center]]

== Sponsor us! ==

We welcome financial contributions to support the meeting and we are looking for sponsors to cover costs such as meals or to help reducing travel and accommodation expenses for GRASS developers who volunteer their time. If you are interested in sponsoring the GRASS Community Meeting, please go to:

::: '''[https://opencollective.com/osgeo/projects/grass/contribute OpenCollective]'''

Any surplus at the end of the event will be used for future activities of the GRASS GIS project such as the [[Student Grants|Student Grant program]].

This GRASS Community Meeting is a great occasion for you to support the development of GRASS. With your contribution you'll enable more developers to meet. Community meetings are important opportunities for developers to discuss, fix bugs, plan the direction for the project and work on new features. The developers and other contributors or their employers are donating their valuable time, so it would be great if funding can be made available from within the community to cover out-of-pocket expenses. All of the work that takes place at the community meeting will be directly contributed back into the GRASS project to the benefit of everyone who uses it. Note that while we have our general plan, we can't accept any earmarked donations, i.e., we can't make any promises for a specific work to be done, please contact specific developers or support commercial providers for that.

We are grateful to the following sponsors for their support and commitment!

* U.S. National Science Foundation, award 2303651. (Travel for 5 participants and their time, event venue.)

[[File:NSF Official logo.png|none|left|200px|alt=Logo of US NSF|U.S. National Science Foundation]]

* [https://www.osgeo.org/ OSGeo]: 5500 USD (approved budget contribution, [https://www.loomio.com/p/W9Qz5cf1/motion-to-approve-5-500-for-the-grass-community-meeting-2024-budget motion])

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

* [https://www.fossgis.de/ FOSSGIS e.V.]: 3500 EUR (approved budget contribution, [https://www.fossgis.de/wiki/F%C3%B6rderantr%C3%A4ge/GRASS_GIS_Community_Meeting_2024 request])

[[File:FOSSGIS_eV_logo.png|none|left|400px|alt=Logo of FOSSGIS e.V.|FOSSGIS e.V.]]

* In-kind contributions will be acknowledged here.
* Personal time and/or financial contributions will be acknowledged here.

== Purpose ==

The ''GRASS GIS 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 GIS project and the interfaces to QGIS, GDAL, PostGIS, R, OGC Services and others.

In this meeting, building on momentum from the 40th birthday meeting, we will continue the revisions of the maintenance processes and infrastructure - a process which highly benefits from the current maintainers being in one place (and time zone). Topics which require highly synchronous collaboration will be included such as Markdown documentation and CMake build transitions. Other contributors are expected to enhance existing tools and their documentation. A [https://grass.osgeo.org/news/2023_08_13_grass_community_meeting_prague_june_2023_report/ press release] gives an overview of last year's event.

We do require participants to work on GRASS GIS 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.

For the detailed agenda and individual's plans, see below.

== Agenda ==
These are some of the identified project priorities:
* Develop the project roadmap to better communicate project vision and priorities.
* Discuss the GRASS GIS integration with QGIS with its maintainers to identify next steps.
* Test the CMake and conda packaging implementations.
* Finalize the HTML to Markdown documentation conversion.
* GSoC students will showcase their projects and seek feedback. We also search for fostering their engagement with community members participating in the meeting and others that want to join online.
* Test and review onboarding documentation for developers, maintainers and other contributors.
* Develop use cases and tutorials on the use and integration of STAC related modules into data processing workflows.
* Get feedback on ongoing GRASS website UX improvements and add missing content.
* Address issues discussed last year about GRASS-R integration: https://github.com/rsbivand/rgrass/discussions/78
* Discuss mailing list (mailman) vs [https://discourse.osgeo.org/ discourse] (forum)
* Simplify [[Working with GRASS without starting it explicitly#Python:_GRASS_GIS_8_with_existing_location|working with GRASS 8.4+ in Python wiki page]]

=== Thursday, June 13 ===

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

=== Friday, June 14 ===

* Welcome.
* Refine shared goals.

=== Saturday, June 15 ===

* morning: GRASS in Windows
* 2 pm: Project roadmap discussion

=== Sunday, June 16 ===

* 2 pm: Documentation discussion
** html - md conversion status
** Programming manuals
** Guidelines: contribution, submission, translation, etc.
** Tutorials: feedback on topics, where to include them, etc.

=== Monday, June 17 ===

* Morning: Status of GRASS-QGIS integration
* Afternoon: GSoC students presentations

=== Tuesday, June 18 ===

* 10am: GeoSPARQL in GRASS
** SPARQLing Unicorn modularisation
** on-line with Timo Homburg

* 2pm: Website redesign discussion
** UX feedback
** Content

=== Wednesday, June 19 ===

=== Thursday, June 20 ===

Day of departure.

== Participation ==

Please add your name here or contact [[User:wenzeslaus|Vaclav Petras]] <tt><wenzeslaus at gmail com></tt>:

=== In person ===

{|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:wenzeslaus|Vaclav Petras]]
| United States
| June 13
| June 20
| review PR, reduce PR queue, Python API topics (also for QGIS and R), funding
|
|-
|2
| [[User:Annakrat|Anna Petrasova]]
| United States
| June 13
| June 20
| grass.jupyter, R and QGIS integration
|
|-
|3
| [[User:Ctwhite|Corey White]]
| United States
| June 13
| June 20
| STAC, JSON outputs, connections with other tools (OpenPlains)
|-
|4
| [[User:Chaedri|Caitlin Haedrich]]
| United States
| June 13
| June 20
| grass.jupyter, GRASS on Windows
|
|-
|5
| [[User:Veroandreo | Vero Andreo]]
| United States
| June 13
| June 20
| STAC, tutorials, website, documentation, contributing guidelines
|
|-
|6
| [[User:florisvdh | Floris Vanderhaeghe]]
| Belgium
| June 13
| June 18 (morning)
| Interfacing GRASS from R (parts of the [https://github.com/rsbivand/rgrass/discussions/78 todo-list])
|
|-
|7
| [[User:martinl | Martin Landa]]
| Czech Republic
| June 14
| June 19
| GUI, Modeler, Markdown, ...
|
|-
|8
| [[User:hellik | Helmut Kudrnovsky]]
| Austria
| June 14
| June 16
| ...
|
|-
|9
| [[User:neteler | Markus Neteler]]
| Germany
| June 13
| June 19
| Infrastructure, Markdown, mailman vs discourse...
|
|-
|10
| [[User:lads | Luís de Sousa]]
| Portugal
| June 14
| June 20
| r.mblend, [https://github.com/OSGeo/grass/issues/2187 issue 2187], GeoSPARQL plug-in, DGGS free thinking, ...
| Arrival on Friday evening.
|-
|11
| Edouard Choinière
| Canada
| June 13
| June 20
| CI, checks, code quality
|
|-
|12
| [[User:pesekon2 | Ondřej Pešek]]
| Czech Republic
| June 13
| June 20
| Modeler, refactoring, ...
| Not joining on June 15
|-
|13
| [[User:Mazingaro | Alen Mangafić]]
| Slovenia
| June 13
| June 20
| LiDAR tuorial, hyperspectral discussion
|
|-
|14
| Ivan Minčík
| Slovakia
| June 17
| June 19
| packaging
|
|}

If you are arriving or departing on the days of the event, please specify the time, too.

=== Online ===

Join our [https://app.gitter.im/#/room/#grassgis_community:gitter.im Gitter chatroom]

Gitter has a video (and backup will be Zoom).

Participating virtually:

{|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'''
!'''Topics'''
!'''Times, synchronous or fully asynchronous'''
!'''Notes'''
|-
|1
| Be The First
| Your Country
| Your Topic
| When you will be available (timezone, days, times)
|
|-
|}

== Venue ==

[[File:Ncsu logo.jpg|240px|frameless|left]]
[https://prague.ncsu.edu/about/ NC State European Center in Prague] 
Malé náměstí 144/1 
Praha 1 – 110 00 
Prague, Czech Republic 

[https://en.mapy.cz/s/fohulovaha Map] 

Prague, the capital of Czechia (Czech Republic) has an international [http://www.prg.aero/en/ airport]. It's location in the middle of central Europe makes it easily reachable by train, bus or car. The city itself has great public transportation.

== Accommodation and Costs ==

''Participation is free of charge''. However, participants should plan for the following costs:

* Travel
* Lodging
* Food and drink (some may be covered)

'''Please note''': The currency in Czech Republic is {{wikipedia|Czech crown}} (CZK, koruna, Kč). 100 Czech crowns are about 4 Euros (see [https://www.cnb.cz/cs/financni-trhy/devizovy-trh/kurzy-devizoveho-trhu/kurzy-devizoveho-trhu/ current rates]).

== Individual Preparation ==

* Bring your own computer
* Bring {{wikipedia|AC adapter|power connector adapter}} if needed (Czech Republic: 230V, 50Hz, {{wikipedia|File:Euro-Flachstecker_2.jpg|Type C Europlugs}} are common and also {{wikipedia|File:French_plug_and_socket.jpg|Type E}})
* 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 ==

* ''How was it last time?''
** Splendid! See [[GRASS Community Meeting Prague 2023]]!
* ''Is the meeting just a coding event?''
** It is mainly a coding and documentation event. It is a working session for people who are already participants in the GRASS project and/or are committed to improving the GRASS project. Committed newcomers are welcome!
* ''Is the GRASS Community Meeting for developers only?''
** No, anybody can help, with testing, checking out bugs and fixes, documentation and more.
* ''Where can I get help and more information about the community meeting?''
** Contact [[User:wenzeslaus|Vaclav Petras]] <tt><wenzeslaus at gmail com></tt>.

GRASS Community Meeting Prague 2024

2024-05-14T10:06:00Z

Lads: /* In person */

{{toc|right}}
The ''GRASS GIS Community Meeting'' for contributors and developers will be happening from '''June 14 to June 19, 2024''' in Prague, Czechia.

[[File:Prague-Community-Meeting-2023-crop.jpg|500px|frameless|center]]

== Sponsor us! ==

We welcome financial contributions to support the meeting and we are looking for sponsors to cover costs such as meals or to help reducing travel and accommodation expenses for GRASS developers who volunteer their time. If you are interested in sponsoring the GRASS Community Meeting, please go to:

::: '''[https://opencollective.com/osgeo/projects/grass/contribute OpenCollective]'''

Any surplus at the end of the event will be used for future activities of the GRASS GIS project such as the [[Student Grants|Student Grant program]].

This GRASS Community Meeting is a great occasion for you to support the development of GRASS. With your contribution you'll enable more developers to meet. Community meetings are important opportunities for developers to discuss, fix bugs, plan the direction for the project and work on new features. The developers and other contributors or their employers are donating their valuable time, so it would be great if funding can be made available from within the community to cover out-of-pocket expenses. All of the work that takes place at the community meeting will be directly contributed back into the GRASS project to the benefit of everyone who uses it. Note that while we have our general plan, we can't accept any earmarked donations, i.e., we can't make any promises for a specific work to be done, please contact specific developers or support commercial providers for that.

We are grateful to the following sponsors for their support and commitment!

* U.S. National Science Foundation, award 2303651. (Travel for 5 participants and their time, event venue.)

[[File:NSF Official logo.png|none|left|200px|alt=Logo of US NSF|U.S. National Science Foundation]]

* In-kind contributions will be acknowledged here.
* Personal time and/or financial contributions will be acknowledged here.

== Purpose ==

The ''GRASS GIS 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 GIS project and the interfaces to QGIS, GDAL, PostGIS, R, OGC Services and others.

In this meeting, building on momentum from the 40th birthday meeting, we will continue the revisions of the maintenance processes and infrastructure - a process which highly benefits from the current maintainers being in one place (and time zone). Topics which require highly synchronous collaboration will be included such as Markdown documentation and CMake build transitions. Other contributors are expected to enhance existing tools and their documentation. A [https://grass.osgeo.org/news/2023_08_13_grass_community_meeting_prague_june_2023_report/ press release] gives an overview of last year's event.

We do require participants to work on GRASS GIS 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.

For the detailed agenda and individual's plans, see below.

== Agenda ==
These are some of the identified project priorities:
* Develop the project roadmap to better communicate project vision and priorities.
* Discuss the GRASS GIS integration with QGIS with its maintainers to identify next steps.
* Test the CMake and conda packaging implementations.
* Finalize the HTML to Markdown documentation conversion.
* GSoC students will showcase their projects and seek feedback. We also search for fostering their engagement with community members participating in the meeting and others that want to join online.
* Test and review onboarding documentation for developers, maintainers and other contributors.
* Develop use cases and tutorials on the use and integration of STAC related modules into data processing workflows.
* Get feedback on ongoing GRASS website UX improvements and add missing content.
* Address issues discussed last year about GRASS-R integration: https://github.com/rsbivand/rgrass/discussions/78
* Discuss mailing list (mailman) vs [https://discourse.osgeo.org/ discourse] (forum)

=== Thursday, June 13 ===

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

=== Friday, June 14 ===

* Welcome.
* Refine shared goals.

=== Saturday, June 15 ===

* morning: GRASS in Windows
* 2 pm: Project roadmap discussion

=== Sunday, June 16 ===

* 2 pm: Documentation discussion
** html - md conversion status
** Programming manuals
** Guidelines: contribution, submission, translation, etc.
** Tutorials: feedback on topics, where to include them, etc.

=== Monday, June 17 ===

* Morning: Status of GRASS-QGIS integration
* Afternoon: GSoC students presentations

=== Tuesday, June 18 ===

* 2pm: Website redesign discussion
** UX feedback
** Content

=== Wednesday, June 19 ===

=== Thursday, June 20 ===

Day of departure.

== Participation ==

We are planning for an attendance of 15 people at the same time but you are welcome to sign up regardless of capacity: We will find a space for you. Please add your name here or contact [[User:wenzeslaus|Vaclav Petras]] <tt><wenzeslaus at gmail com></tt>:

=== In person ===

{|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:wenzeslaus|Vaclav Petras]]
| United States
| June 13
| June 20
| review PR, reduce PR queue, Python API topics (also for QGIS and R), funding
|
|-
|2
| [[User:Annakrat|Anna Petrasova]]
| United States
| June 13
| June 20
| grass.jupyter, R and QGIS integration
|
|-
|3
| [[User:Ctwhite|Corey White]]
| United States
| June 13
| June 20
| STAC, JSON outputs, connections with other tools (OpenPlains)
|-
|4
| [[User:Chaedri|Caitlin Haedrich]]
| United States
| June 13
| June 20
| grass.jupyter
|
|-
|5
| [[User:Veroandreo | Vero Andreo]]
| United States
| June 13
| June 20
| STAC, tutorials, website, documentation, contributing guidelines
|
|-
|6
| [[User:florisvdh | Floris Vanderhaeghe]]
| Belgium
| June 13
| June 18 (morning)
| Interfacing GRASS from R (parts of the [https://github.com/rsbivand/rgrass/discussions/78 todo-list])
|
|-
|7
| [[User:martinl | Martin Landa]]
| Czech Republic
| June 14
| June 19
| GUI, Modeler, Markdown, ...
|
|-
|8
| [[User:hellik | Helmut Kudrnovsky]]
| Austria
| June 14
| June 16
| ...
|
|-
|9
| [[User:neteler | Markus Neteler]]
| Germany
| June 14
| June 20
| Infrastructure, Markdown, mailman vs discourse...
|
|-
|10
| [[User:lads | Luís de Sousa]]
| Portugal
| June 14
| June 20
| r.mblend, [https://github.com/OSGeo/grass/issues/2187 issue 2187], GeoSPARQL plug-in, DGGS free thinking, ...
| Arrival on Friday evening.
|-
|11
| Edouard Choinière
| Canada
| June 13
| June 20
| CI, checks, code quality
|
|-
|12
| [[User:pesekon2 | Ondřej Pešek]]
| Czech Republic
| June 13
| June 20
| Modeler, refactoring, ...
| Not joining on June 15
|-
|13
| [[User:Mazingaro | Alen Mangafić]]
| Slovenia
| June 13
| June 20
| Documenting strange optimization techniques, addon contribution, translation.
| Joining for the first time, so I'll be lost in the beginning. Topics under construction.
|}

If you are arriving or departing on the days of the event, please specify the time, too.

=== Online ===

Join our [https://app.gitter.im/#/room/#grassgis_community:gitter.im Gitter chatroom]

Gitter has a video (and backup will be Zoom).

Participating virtually:

{|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'''
!'''Topics'''
!'''Times, synchronous or fully asynchronous'''
!'''Notes'''
|-
|1
| Be The First
| Your Country
| Your Topic
| When you will be available (timezone, days, times)
|
|-
|}

== Venue ==

[[File:Ncsu logo.jpg|240px|frameless|left]]
[https://prague.ncsu.edu/about/ NC State European Center in Prague] 
Malé náměstí 144/1 
Praha 1 – 110 00 
Prague, Czech Republic 

[https://en.mapy.cz/s/fohulovaha Map] 

Prague, the capital of Czechia (Czech Republic) has an international [http://www.prg.aero/en/ airport]. It's location in the middle of central Europe makes it easily reachable by train, bus or car. The city itself has great public transportation.

== Accommodation and Costs ==

''Participation is free of charge''. However, participants should plan for the following costs:

* Travel
* Lodging
* Food and drink (some may be covered)

'''Please note''': The currency in Czech Republic is {{wikipedia|Czech crown}} (CZK, koruna, Kč). 100 Czech crowns are about 4 Euros (see [https://www.cnb.cz/cs/financni-trhy/devizovy-trh/kurzy-devizoveho-trhu/kurzy-devizoveho-trhu/ current rates]).

== Individual Preparation ==

* Bring your own computer
* Bring {{wikipedia|AC adapter|power connector adapter}} if needed (Czech Republic: 230V, 50Hz, {{wikipedia|File:Euro-Flachstecker_2.jpg|Type C Europlugs}} are common and also {{wikipedia|File:French_plug_and_socket.jpg|Type E}})
* 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 ==

* ''How was it last time?''
** Splendid! See [[GRASS Community Meeting Prague 2023]]!
* ''Is the meeting just a coding event?''
** It is mainly a coding and documentation event. It is a working session for people who are already participants in the GRASS project and/or are committed to improving the GRASS project. Committed newcomers are welcome!
* ''Is the GRASS Community Meeting for developers only?''
** No, anybody can help, with testing, checking out bugs and fixes, documentation and more.
* ''Where can I get help and more information about the community meeting?''
** Contact [[User:wenzeslaus|Vaclav Petras]] <tt><wenzeslaus at gmail com></tt>.

GRASS Community Meeting Prague 2024

2024-05-08T15:08:19Z

Lads: /* In person */

{{toc|right}}
The ''GRASS GIS Community Meeting'' for contributors and developers will be happening from '''June 14 to June 19, 2024''' in Prague, Czechia.

[[File:Prague-Community-Meeting-2023-crop.jpg|500px|frameless|center]]

== Sponsor us! ==

We welcome financial contributions to support the meeting and we are looking for sponsors to cover costs such as meals or to help reducing travel and accommodation expenses for GRASS developers who volunteer their time. If you are interested in sponsoring the GRASS Community Meeting, please go to:

::: '''[https://opencollective.com/osgeo/projects/grass/contribute OpenCollective]'''

Any surplus at the end of the event will be used for future activities of the GRASS GIS project such as the [[Student Grants|Student Grant program]].

This GRASS Community Meeting is a great occasion for you to support the development of GRASS. With your contribution you'll enable more developers to meet. Community meetings are important opportunities for developers to discuss, fix bugs, plan the direction for the project and work on new features. The developers and other contributors or their employers are donating their valuable time, so it would be great if funding can be made available from within the community to cover out-of-pocket expenses. All of the work that takes place at the community meeting will be directly contributed back into the GRASS project to the benefit of everyone who uses it. Note that while we have our general plan, we can't accept any earmarked donations, i.e., we can't make any promises for a specific work to be done, please contact specific developers or support commercial providers for that.

We are grateful to the following sponsors for their support and commitment!

* U.S. National Science Foundation, award 2303651. (Travel for 5 participants and their time, event venue.)

[[File:NSF Official logo.png|none|left|200px|alt=Logo of US NSF|U.S. National Science Foundation]]

* In-kind contributions will be acknowledged here.
* Personal time and/or financial contributions will be acknowledged here.

== Purpose ==

The ''GRASS GIS 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 GIS project and the interfaces to QGIS, GDAL, PostGIS, R, OGC Services and others.

In this meeting, building on momentum from the 40th birthday meeting, we will continue the revisions of the maintenance processes and infrastructure - a process which highly benefits from the current maintainers being in one place (and time zone). Topics which require highly synchronous collaboration will be included such as Markdown documentation and CMake build transitions. Other contributors are expected to enhance existing tools and their documentation. A [https://grass.osgeo.org/news/2023_08_13_grass_community_meeting_prague_june_2023_report/ press release] gives an overview of last year's event.

We do require participants to work on GRASS GIS 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.

For the detailed agenda and individual's plans, see below.

== Agenda ==
These are some of the identified project priorities:
* Develop the project roadmap to better communicate project vision and priorities.
* Discuss the GRASS GIS integration with QGIS with its maintainers to identify next steps.
* Test the CMake and conda packaging implementations.
* Finalize the HTML to Markdown documentation conversion.
* GSoC students will showcase their projects and seek feedback. We also search for fostering their engagement with community members participating in the meeting and others that want to join online.
* Test and review onboarding documentation for developers, maintainers and other contributors.
* Develop use cases and tutorials on the use and integration of STAC related modules into data processing workflows.
* Get feedback on ongoing GRASS website UX improvements and add missing content.
* Address issues discussed last year about GRASS-R integration: https://github.com/rsbivand/rgrass/discussions/78
* Discuss mailing list (mailman) vs [https://discourse.osgeo.org/ discourse] (forum)

=== Thursday, June 13 ===

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

=== Friday, June 14 ===

* Welcome.
* Refine shared goals.

=== Saturday, June 15 ===

* morning: GRASS in Windows
* 2 pm: Project roadmap discussion

=== Sunday, June 16 ===

* 2 pm: Documentation discussion
** html - md conversion status
** Programming manuals
** Guidelines: contribution, submission, translation, etc.
** Tutorials: feedback on topics, where to include them, etc.

=== Monday, June 17 ===

* Morning: Status of GRASS-QGIS integration
* Afternoon: GSoC students presentations

=== Tuesday, June 18 ===

* 2pm: Website redesign discussion
** UX feedback
** Content

=== Wednesday, June 19 ===

=== Thursday, June 20 ===

Day of departure.

== Participation ==

We are planning for an attendance of 15 people at the same time but you are welcome to sign up regardless of capacity: We will find a space for you. Please add your name here or contact [[User:wenzeslaus|Vaclav Petras]] <tt><wenzeslaus at gmail com></tt>:

=== In person ===

{|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:wenzeslaus|Vaclav Petras]]
| United States
| June 13
| June 20
| review PR, reduce PR queue, Python API topics (also for QGIS and R), funding
|
|-
|2
| [[User:Annakrat|Anna Petrasova]]
| United States
| June 13
| June 20
| grass.jupyter, R and QGIS integration
|
|-
|3
| [[User:Ctwhite|Corey White]]
| United States
| June 13
| June 20
| STAC, JSON outputs, connections with other tools (OpenPlains)
|-
|4
| [[User:Chaedri|Caitlin Haedrich]]
| United States
| June 13
| June 20
| grass.jupyter
|
|-
|5
| [[User:Veroandreo | Vero Andreo]]
| United States
| June 13
| June 20
| STAC, tutorials, website, documentation, contributing guidelines
|
|-
|6
| [[User:florisvdh | Floris Vanderhaeghe]]
| Belgium
| June 13
| June 18 (morning)
| Interfacing GRASS from R (parts of the [https://github.com/rsbivand/rgrass/discussions/78 todo-list])
|
|-
|7
| [[User:martinl | Martin Landa]]
| Czech Republic
| June 14
| June 19
| GUI, Modeler, Markdown, ...
|
|-
|8
| [[User:hellik | Helmut Kudrnovsky]]
| Austria
| June 14
| June 16
| ...
|
|-
|9
| [[User:neteler | Markus Neteler]]
| Germany
| June 14
| June 20
| Infrastructure, Markdown, mailman vs discourse...
|
|-
|10
| [[User:lads | Luís de Sousa]]
| Portugal
| June 14
| June 20
| r.mblend, GeoSPARQL plug-in, DGGS free thinking, ...
| Arrival on Friday evening.
|-
|11
| Edouard Choinière
| Canada
| June 13
| June 20
| CI, checks, code quality
|
|-
|12
| [[User:pesekon2 | Ondřej Pešek]]
| Czech Republic
| June 13
| June 20
| Modeler, refactoring, ...
| Not joining on June 15
|-
|}

If you are arriving or departing on the days of the event, please specify the time, too.

=== Online ===

Join our [https://app.gitter.im/#/room/#grassgis_community:gitter.im Gitter chatroom]

Gitter has a video (and backup will be Zoom).

Participating virtually:

{|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'''
!'''Topics'''
!'''Times, synchronous or fully asynchronous'''
!'''Notes'''
|-
|1
| Be The First
| Your Country
| Your Topic
| When you will be available (timezone, days, times)
|
|-
|}

== Venue ==

[[File:Ncsu logo.jpg|240px|frameless|left]]
[https://prague.ncsu.edu/about/ NC State European Center in Prague] 
Malé náměstí 144/1 
Praha 1 – 110 00 
Prague, Czech Republic 

[https://en.mapy.cz/s/fohulovaha Map] 

Prague, the capital of Czechia (Czech Republic) has an international [http://www.prg.aero/en/ airport]. It's location in the middle of central Europe makes it easily reachable by train, bus or car. The city itself has great public transportation.

== Accommodation and Costs ==

''Participation is free of charge''. However, participants should plan for the following costs:

* Travel
* Lodging
* Food and drink (some may be covered)

'''Please note''': The currency in Czech Republic is {{wikipedia|Czech crown}} (CZK, koruna, Kč). 100 Czech crowns are about 4 Euros (see [https://www.cnb.cz/cs/financni-trhy/devizovy-trh/kurzy-devizoveho-trhu/kurzy-devizoveho-trhu/ current rates]).

== Individual Preparation ==

* Bring your own computer
* Bring {{wikipedia|AC adapter|power connector adapter}} if needed (Czech Republic: 230V, 50Hz, {{wikipedia|File:Euro-Flachstecker_2.jpg|Type C Europlugs}} are common and also {{wikipedia|File:French_plug_and_socket.jpg|Type E}})
* 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 ==

* ''How was it last time?''
** Splendid! See [[GRASS Community Meeting Prague 2023]]!
* ''Is the meeting just a coding event?''
** It is mainly a coding and documentation event. It is a working session for people who are already participants in the GRASS project and/or are committed to improving the GRASS project. Committed newcomers are welcome!
* ''Is the GRASS Community Meeting for developers only?''
** No, anybody can help, with testing, checking out bugs and fixes, documentation and more.
* ''Where can I get help and more information about the community meeting?''
** Contact [[User:wenzeslaus|Vaclav Petras]] <tt><wenzeslaus at gmail com></tt>.

GRASS Community Meeting Prague 2024

2024-04-10T14:09:36Z

Lads: /* In person */

{{toc|right}}
The ''GRASS GIS Community Meeting'' for contributors and developers will be happening from '''June 14 to June 19, 2024''' in Prague, Czechia.

[[File:Prague-Community-Meeting-2023-crop.jpg|500px|frameless|center]]

== Sponsor us! ==

We welcome financial contributions to support the meeting and we are looking for sponsors to cover costs such as meals or to help reducing travel and accommodation expenses for GRASS developers who volunteer their time. If you are interested in sponsoring the GRASS Community Meeting, please go to:

::: '''[https://opencollective.com/osgeo/projects/grass/contribute OpenCollective]'''

Any surplus at the end of the event will be used for future activities of the GRASS GIS project such as the [[Student Grants|Student Grant program]].

This GRASS Community Meeting is a great occasion for you to support the development of GRASS. With your contribution you'll enable more developers to meet. Community meetings are important opportunities for developers to discuss, fix bugs, plan the direction for the project and work on new features. The developers and other contributors or their employers are donating their valuable time, so it would be great if funding can be made available from within the community to cover out-of-pocket expenses. All of the work that takes place at the community meeting will be directly contributed back into the GRASS project to the benefit of everyone who uses it. Note that while we have our general plan, we can't accept any earmarked donations, i.e., we can't make any promises for a specific work to be done, please contact specific developers or support commercial providers for that.

We are grateful to the following sponsors for their support and commitment!

* U.S. National Science Foundation, award 2303651. (Travel for 5 participants and their time, event venue.)

[[File:NSF Official logo.png|none|left|200px|alt=Logo of US NSF|U.S. National Science Foundation]]

* In-kind contributions will be acknowledged here.
* Personal time and/or financial contributions will be acknowledged here.

== Purpose ==

The ''GRASS GIS 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 GIS project and the interfaces to QGIS, GDAL, PostGIS, R, OGC Services and others.

In this meeting, building on momentum from the 40th birthday meeting, we will continue the revisions of the maintenance processes and infrastructure - a process which highly benefits from the current maintainers being in one place (and time zone). Topics which require highly synchronous collaboration will be included such as Markdown documentation and CMake build transitions. Other contributors are expected to enhance existing tools and their documentation. A [https://grass.osgeo.org/news/2023_08_13_grass_community_meeting_prague_june_2023_report/ press release] gives an overview of last year's event.

We do require participants to work on GRASS GIS 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.

For the detailed agenda and individual's plans, see below.

== Agenda ==
These are some of the identified project priorities:
* Develop the project roadmap to better communicate project vision and priorities.
* Discuss the GRASS GIS integration with QGIS with its maintainers to identify next steps.
* Test the CMake and conda packaging implementations.
* Finalize the HTML to Markdown documentation conversion.
* GSoC students will showcase their projects and seek feedback. We also search for fostering their engagement with community members participating in the meeting and others that want to join online.
* Test and review onboarding documentation for developers, maintainers and other contributors.
* Develop use cases and tutorials on the use and integration of STAC related modules into data processing workflows.
* Get feedback on ongoing GRASS website UX improvements and add missing content.
* Address issues discussed last year about GRASS-R integration: https://github.com/rsbivand/rgrass/discussions/78
* Discuss mailing list (mailman) vs [https://discourse.osgeo.org/ discourse] (forum)

=== Thursday, June 13 ===

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

=== Friday, June 14 ===

* Welcome.
* Refine shared goals.

=== Saturday, June 15 ===

=== Sunday, June 16 ===

=== Monday, June 17 ===

=== Tuesday, June 18 ===

=== Wednesday, June 19 ===

=== Thursday, June 20 ===

Day of departure.

== Participation ==

We are planning for an attendance of 15 people at the same time but you are welcome to sign up regardless of capacity: We will find a space for you. Please add your name here or contact [[User:wenzeslaus|Vaclav Petras]] <tt><wenzeslaus at gmail com></tt>:

=== In person ===

{|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:wenzeslaus|Vaclav Petras]]
| United States
| June 13
| June 20
| review PR, reduce PR queue, Python API topics (also for QGIS and R), funding
|
|-
|2
| [[User:Annakrat|Anna Petrasova]]
| United States
| June 13
| June 20
| grass.jupyter, R and QGIS integration
|
|-
|3
| [[User:Ctwhite|Corey White]]
| United States
| June 13
| June 20
| STAC, JSON outputs, connections with other tools (OpenPlains)
|-
|4
| [[User:Chaedri|Caitlin Haedrich]]
| United States
| June 13
| June 20
| grass.jupyter
|
|-
|5
| [[User:Veroandreo | Vero Andreo]]
| United States
| June 13
| June 20
| STAC, tutorials, website, documentation, contributing guidelines
|
|-
|6
| [[User:florisvdh | Floris Vanderhaeghe]]
| Belgium
| June 13
| June 18 (morning)
| Interfacing GRASS from R (parts of the [https://github.com/rsbivand/rgrass/discussions/78 todo-list])
|
|-
|7
| [[User:martinl | Martin Landa]]
| Czech Republic
| June 14
| June 19
| GUI, Modeler, Markdown, ...
|
|-
|8
| [[User:hellik | Helmut Kudrnovsky]]
| Austria
| June 14
| June 16
| ...
|
|-
|9
| [[User:neteler | Markus Neteler]]
| Germany
| June 14
| June 20
| Infrastructure, Markdown, mailman vs discourse...
|
|-
|10
| [[User:lads | Luís de Sousa]]
| Portugal
| June 14
| June 18
| r.mblend, GeoSPARQL plug-in, DGGS free thinking, ...
| Travelling yet to be arranged, dates are tentative.
|-
|}

If you are arriving or departing on the days of the event, please specify the time, too.

=== Online ===

Join our [https://app.gitter.im/#/room/#grassgis_community:gitter.im Gitter chatroom]

Gitter has a video (and backup will be Zoom).

Participating virtually:

{|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'''
!'''Topics'''
!'''Times, synchronous or fully asynchronous'''
!'''Notes'''
|-
|1
| Be The First
| Your Country
| Your Topic
| When you will be available (timezone, days, times)
|
|-
|}

== Venue ==

[[File:Ncsu logo.jpg|240px|frameless|left]]
[https://prague.ncsu.edu/about/ NC State European Center in Prague] 
Malé náměstí 144/1 
Praha 1 – 110 00 
Prague, Czech Republic 

[https://en.mapy.cz/s/fohulovaha Map] 

Prague, the capital of Czechia (Czech Republic) has an international [http://www.prg.aero/en/ airport]. It's location in the middle of central Europe makes it easily reachable by train, bus or car. The city itself has great public transportation.

== Accommodation and Costs ==

''Participation is free of charge''. However, participants should plan for the following costs:

* Travel
* Lodging
* Food and drink (some may be covered)

'''Please note''': The currency in Czech Republic is {{wikipedia|Czech crown}} (CZK, koruna, Kč). 100 Czech crowns are about 4 Euros (see [https://www.cnb.cz/cs/financni-trhy/devizovy-trh/kurzy-devizoveho-trhu/kurzy-devizoveho-trhu/ current rates]).

== Individual Preparation ==

* Bring your own computer
* Bring {{wikipedia|AC adapter|power connector adapter}} if needed (Czech Republic: 230V, 50Hz, {{wikipedia|File:Euro-Flachstecker_2.jpg|Type C Europlugs}} are common and also {{wikipedia|File:French_plug_and_socket.jpg|Type E}})
* 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 ==

* ''How was it last time?''
** Splendid! See [[GRASS Community Meeting Prague 2023]]!
* ''Is the meeting just a coding event?''
** It is mainly a coding and documentation event. It is a working session for people who are already participants in the GRASS project and/or are committed to improving the GRASS project. Committed newcomers are welcome!
* ''Is the GRASS Community Meeting for developers only?''
** No, anybody can help, with testing, checking out bugs and fixes, documentation and more.
* ''Where can I get help and more information about the community meeting?''
** Contact [[User:wenzeslaus|Vaclav Petras]] <tt><wenzeslaus at gmail com></tt>.