GRASS-Wiki - User contributions [en]

Talk:GRASS Community Meeting Prague 2023

2023-06-12T05:51:55Z

⚠️Lbartoletti: Add Loïc Bartoletti

__TOC__

== 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.)

== Planning and organizing ==

* Initial planning: Veronica Andreo, Martin Landa, Vaclav Petras, Helmut Kudrnovsky, Anna Petrasova, Huidae Cho, Markus Neteler, Helena Mitasova, Micha Silver, Linda Kladivova
* Funding acquisition: Veronica Andreo, Markus Neteler, Vaclav Petras, Anna Petrasova, Huidae Cho, Luca Delucchi, Venkatesh Raghavan
* Budget: Vaclav Petras, Markus Neteler, Veronica Andreo
* Venue and local organizing: Martin Landa, helpers: Ondrej Pesek, Vaclav Petras
* T-shirts, hoodies, stickers: Vaclav Petras, Anna Petrasova
* Promotion, invitations, and social media: Caitlin Haedrich, Veronica Andreo, Vaclav Petras
* Wiki page: Martin Landa, Markus Neteler, Vaclav Petras, Veronica Andreo
* Virtual meeting organizing: Veronica Andreo
* Photography: Caitlin Haedrich, Maris Nartiss

== Ideas for the meeting agenda ==

Collect ideas here :-)

=== Vero ===

* '''All - think about GRASS GIS mission and vision''': Where do we want to be as a project in 5 years time? What do we want to have? What do we want to be?
* Participate in discussions about GRASS interfaces with QGIS and R (rgrass)
* Discuss sponsoring
* Student grant for (python) documentation?
* Discuss about wiki clean-up/update (Anna was working on a list of pages)
* Website enhancements: complete open PR's, meet Daniel Torres, new support item in main menu
* Discuss State of GRASS presentation for FOSS4G 2023
* i.landsat if time permits
* ...

== Reports ==

=== Caitlin Haedrich ===
* Photos, social media and wiki page
* grass.jupyter:
** [https://github.com/OSGeo/grass/pull/3036 add feature for animating series of rasters]

=== Vaclav Petras ===

* Rename location to project
** [https://github.com/OSGeo/grass/pull/2993 wxGUI: Rename location to project #2993]
** Discussion
* Python API
** [https://github.com/OSGeo/grass/pull/2923 grass.experimental: Add object to access modules as functions #2923]
* CI
** [https://github.com/OSGeo/grass/pull/3002 CI: Switch Travis to Ubuntu 22.04 (jammmy) #3002]
* Reviews and merges:
** [https://github.com/OSGeo/grass/pull/2974 t.rast.algebra/testsuite: split file test_raster_algebra.py #2974]
** [https://github.com/OSGeo/grass/pull/2189 Imagery: add libsvm based imagery classification #2189]
** [https://github.com/OSGeo/grass-addons/pull/606 r.random.walk: Add module to create random walks #606]

=== Anna Petrasova ===
* [https://github.com/OSGeo/grass/pull/2992 Fix bug in querying]
* review, merge and backport of [https://github.com/OSGeo/grass/pull/2994 fix in datacatalog]
* review of [https://github.com/OSGeo/grass/pull/2520 wxGUI: fix show MASK statusbar button widget if mask is created]
* merge of [https://github.com/OSGeo/grass/pull/2667 wxGUI: adding a button for undocking an AuiNotebook tab to wx.Frame (Single-Window GUI)]
* edit [https://github.com/OSGeo/grass/pull/2990 check min required wx version when starting wxgui]
* implement widget dependency for i.signatures as part of [https://github.com/OSGeo/grass/pull/3008 PR 3008]
* found and fixed a bug in digitizer, [https://github.com/OSGeo/grass/pull/3027 PR 3027]
* participate in rgrass and QGIS-GRASS discussions
* write up notes from QGIS meeting
* fix randomly failing test in [https://github.com/OSGeo/grass/pull/3037 PR 3037]
* worked on a Jupyter Notebook for GRASS parallelization (to be finished)

=== Maris Nartiss ===

* i.svm.* cleanup and preparation for a review
* A conceptual proposal for a new start up screen
* Initial version of imagery signature management module i.signatures
* Remove obsolete parts of locale README file
* Extract translatable messages also from C++ files
* Improve parser library documentation

=== Micha Silver ===
Working on a new GRASS addon: r.optram
[https://github.com/micha-silver/grass-addons/tree/grass8/src/raster/r.optram the repo on github]

02/06: Initialize main file ''r.optram.py''

includes these functions:
# ''getImgList()'' - get list of IMG_FILEs in a Sentinel 2 SAFE Directory
# ''cropToAOI()'' - Crop the images to the Area of Interest
# ''prepareSTR()'' - Convert SWIR to the SWIR Transformed Reflectance
# ''prepareVI()'' - Prepare the (user chosen) vegetation index

03/06:
# Split to three modules: '''r.optram.preprocess, r.optram, r.optram.soilmoisture'''
# new function: ''prepareTrapezoid()'' - to get wet-dry regression lines and slope, intercept values

04/06
# ''prepareTrapezoid()'' function completed.
# (Joined video conf with Roger Bivand on R-GRASS integration.)

05/06
Initialize third file/function: ''r.optram.soilmoisture.py''
# ''createSoilMoisture()'' - creates new GRASS raster for a single date
# Add documentation to modules
# (joined video conf with Nyall Dawson)

TODO list:
* Read Sentinel cloud mask and mask out cloud pixels in '''r.optram.preprocess'''
* large study areas or very long time series will create a big numpy table of variables (vegetation index and STR). A possible solution:
# Determine some "reasonable" maximum size for the numpy table, depending on computer resources.
# Extract a subset of pixels from each raster in the time series, such that the total table pixel values will not exceed that maximum
# The size of the subset will be set by ("reasonable" max / number of rasters in time series)
# Allow user to determine "reasonable" max.
* Currently this addon consists of three sub-modules. Consider to consolidate to one.
* Improve HTML documentation

=== Luís de Sousa ===

==== Work on GRASS add-on [https://grass.osgeo.org/grass82/manuals/addons/r.mblend.html r.mblend] ====

* Module is still maintained and fully functional in GRASS 8.2 (now included in the [https://github.com/OSGeo/grass-addons GRASS global add-ons repository])
* However was not longer producing correct results due to new behaviour in '''v.what.rast'''
* Solution identified, using inner buffer to interpolation area ([https://github.com/OSGeo/grass-addons/pull/910 PR #910])
* A small unit test suite was developed ([https://github.com/OSGeo/grass-addons/pull/911 PR #911])

==== Documentation ====

* Expanded instructions on Pre-commit ([https://github.com/OSGeo/grass/pull/3006 PR #3006])
* Mini guidelines on unit tests for add-ons ([https://github.com/OSGeo/grass-addons/pull/916 PR #916])

=== Aaron Saw Min Sern ===

* Fix bug to complete r.univar parallelization. [https://github.com/OSGeo/grass/pull/2683 PR]
* Investigate CMake progress in Windows. There still needs to be source code fixes to be port over to MSVC:
* Variable Length Arrays (VLA) is not supported in MSVC (is optional in C99).
* DLL export directives are required across dynamic library boundaries.
* ...
* Coordinate CMake PR, fix some bugs and make some progress (got a full build on UNIX environment). [https://github.com/OSGeo/grass/pull/3021]
* r.mapcalc removed previous threading artifacts that are ineffective.
* r.mapcalc refactored global variables in preparation for threading work. (PR to come)

=== Martin Landa ===

* Check min required wx version when starting wxgui [https://github.com/OSGeo/grass/pull/2990 PR #2990]
* Graphical modeler: avoid overlapping module parameters [https://github.com/OSGeo/grass/issues/2991 PR #2991]
* Show ModelRelation in white on dark mode [https://github.com/OSGeo/grass/pull/2997 PR #2997]
* Add OSGeo4W workflow to compile Addons [https://github.com/OSGeo/grass-addons/pull/912 PR #912]
* Integrate Grapical Modeler into single window layout [https://github.com/OSGeo/grass/pull/3003 PR #3003]
* Graphical Modeler: fix command parsing in "add tool" dialog [https://github.com/OSGeo/grass/pull/3022 PR #3022]
* Describe required updates for new version for winGRASS [https://github.com/OSGeo/grass/issues/2406#issuecomment-1578303935 #2406]

=== Markus Neteler ===

* backport of "HTML header charset changed from ISO-8859-1 to UTF-8" [https://github.com/OSGeo/grass/pull/2547 PR #2547] to GRASS GIS 8.2.1 (fixing r.forcircular manual encoding bug)
* improve "Update alpine Docker tag to v3.18 [https://github.com/OSGeo/grass/pull/2953 PR #2953]
* backport of Alpine Dockerfile improvements
* discussion about "location/mapset" vs "project/..." terminology
* initial QGIS-GRASS update discussion: update of provider to GRASS GIS 8
* Google Photo album feeds
* Use of [https://github.com/OSGeo/grass/blob/main/doc/development/submitting/submitting.md#use-pre-commit pre-commit] (recommended to all devs!)
* Participate in a two-hour meeting with Nyall Dawson (QGIS) and the GRASS Community about interfacing GRASS from QGIS
* GRASS GIS docker images: moved from "mundialis organization" to https://hub.docker.com/r/osgeo/grass-gis (together with Carmen)
** Once the CI completes the images will show up there. Update of grass-web page is in the works.
* Update of release procedure documents (together with Vaclav)
* GRASS GIS manual pages: re-styling and conversion of all pages to markdown:
** convert to markdown with pandoc (draft script see https://app.gitter.im/#/room/#grassgis_sprint:gitter.im discussion)
** using mkdocs (https://www.mkdocs.org/): it provides menus and a search window
** check: automatic formatting for mkdocs: https://github.com/KyleKing/mdformat-mkdocs

[[Image:Grass manual readthedocs.png|First attempt to convert the manual to Markdown/mkdocs|500px]]

* Discuss about a 4th edition of "Open Source GIS: A GRASS GIS Approach"
* GRASS GIS addons overview generator for entire GitHub (and more?) based on tag "[https://github.com/topics/grass-gis-addons grass-gis-addons]"
* User message translation: Easy [https://docs.weblate.org/en/latest/user/translating.html#machine-translation machine translation] of messages in [https://weblate.osgeo.org/translate/grass-gis OSGeo-Weblate] with DeepL API
** my tests with DeepL show that the quality is very good; average translation time of a user message shrinks to 15 seconds {{done}}
** note: one needs to login to Weblate to see the "Automatic suggestion" button (using the OSGeo-ID)

=== Helmut Kudrnovsky ===

* discuss (win)GRASS-R issues [https://github.com/rsbivand/rgrass/issues/57 initGrass Error] and [https://github.com/OSGeo/grass/issues/2998 feature requests]

* Review and initial tests of PR [https://github.com/OSGeo/grass/pull/2684 compilation with cmake] on Windows

* Participated in a two-hour meeting with Roger, Floris, Vaclav, Anna, Micha, ..... about rgrass development

=== Ondřej Pešek ===

* gmodeler: add export to an actinia script: [https://github.com/OSGeo/grass/pull/3005 PR #3005]
* fix GRASS GIS broken for Python 3.12: [https://github.com/OSGeo/grass/pull/3009 PR #3009], [https://github.com/OSGeo/grass/pull/3010 PR #3010], [https://github.com/OSGeo/grass/pull/3011 PR #3011], [https://github.com/OSGeo/grass/pull/3018 PR #3018]
* fix GRASS GIS addons broken for Python 3.12: [https://github.com/OSGeo/grass-addons/pull/917 PR #917], [https://github.com/OSGeo/grass-addons/pull/918 PR #918], [https://github.com/OSGeo/grass-addons/pull/919 PR #919]
* work on docs: [https://github.com/OSGeo/grass/pull/3043 PR #3043]

=== Floris Vanderhaeghe ===

* Explore reading straight from the GRASS database into R (https://github.com/rsbivand/rgrass/issues/75)
* Help Markus in improving the documentation of the GDAL-GRASS drivers (https://github.com/OSGeo/gdal-grass)
* Help arranging a meeting with Nyall Dawson for the QGIS GRASS interface
* Participate in a two-hour meeting with Roger Bivand, Vero Andreo, Vaclav, Anna, Helmut, Micha, ..... about rgrass development
* Draft and finalize the meeting minutes of the rgrass meeting
* Participate in a two-hour meeting with Nyall Dawson (QGIS) and the GRASS Community about interfacing GRASS from QGIS

=== Vero Andreo ===

* Participated in the discussion about renaming locations to projects
* Call with Paulo on diverse topics, r.niche.similarity PR revision and merge
* Participated in a two-hour meeting with Roger, Floris, Vaclav, Anna, Helmut, Micha, ..... about rgrass development
* Worked on GRASS Website:
** Apply fixes and merge the [https://github.com/OSGeo/grass-website/pull/362 DOI] and [https://github.com/OSGeo/grass-website/pull/364 first draft of sponsoring tiers] PRs
** Beautify tables and content of sponsoring page [https://github.com/OSGeo/grass-website/pull/368 #368]
** New menu and submenus (some reordered), please comment [https://github.com/OSGeo/grass-website/pull/369 #369]
** Created a news item about rgrass7 retirement with text snippet contributed by Roger Bivand [https://github.com/OSGeo/grass-website/pull/370 #370]
* Other minor revisions

=== Carmen Tawalika ===

* Move official GRASS GIS Dockerimage from mundialis/grass-py3-pdal to osgeo/grass-gis
** PR for CI in [https://github.com/OSGeo/grass/pull/3001 #3001]
** Update website in [https://github.com/OSGeo/grass-website/pull/371 #371]
** Update reference in actinia-docker repository in [https://github.com/actinia-org/actinia-docker/pull/41 #41]
* Update alpine version in Dockerimage to v3.18
** Local testing for [https://github.com/OSGeo/grass/pull/2953 #2953]
** Update of various images for actinia [https://github.com/actinia-org/actinia-docker/pull/38 #38], [https://github.com/actinia-org/actinia-docker/pull/39 #39] and [https://github.com/actinia-org/actinia-core/pull/442 #442]
* Enhance actinia version info in [https://github.com/actinia-org/actinia-core/pull/443 #443], [https://github.com/actinia-org/actinia-core/pull/444 #444] and [https://github.com/actinia-org/actinia-docker/pull/40 #40]
* Fix tests for actinia-parallel-plugin

=== Loïc Bartoletti ===

* Participate in a two-hour meeting with Nyall Dawson (QGIS) and the GRASS Community about interfacing GRASS from QGIS
* Rebased Markus PR and continuing migration to [https://github.com/OSGeo/grass/pull/3021 CMake]
* Fix a [https://github.com/qgis/QGIS/pull/53345 Crash on QGIS] loading a raster generated with [https://github.com/OSGeo/grass/issues/1017 r.null]
* Fix a memory leak in [https://github.com/OSGeo/grass/pull/3004 lib/bitmap]
* Remove compatibility to GDAL < 2.2 [https://github.com/OSGeo/grass/pull/2995 #2995]
* Tests and reviews for [https://github.com/OSGeo/grass/issues/1034 #1034], [https://github.com/OSGeo/grass/issues/1889 #1889], [https://github.com/OSGeo/grass/pull/2930 #2930]
* Working on Cppcheck and [https://sonarcloud.io/summary/new_code?id=lbartoletti_grass&branch=sonarcloud SonarCloud WIP] for GRASS build
* Update URL to GRASS manual pages in QGIS [https://github.com/qgis/QGIS/pull/53372 #53372] and [https://github.com/qgis/QGIS/pull/53376 #53376]
=== Discussion with Nyall (QGIS) ===

* How to improve the integration
** save some of the existing code
** update "Processing" integration
** ...
* GRASS GIS Addon support in QGIS, see
** https://github.com/qgis/QGIS/pull/53048
** https://github.com/qgis/QGIS/pull/53049

== What to do differently the next time ==

* Use food delivery also for couple of evenings to allow for longer coding. (asked for by several participants)
* Pay for more parallel CI jobs. (the queue was very long and too long for the release procedure)

GRASS Community Meeting Prague 2023

2023-05-12T06:41:01Z

⚠️Lbartoletti: Add myself lbartoletti

{{toc|right}}
The GRASS GIS team is organizing the ''GRASS GIS Community Meeting with contributors, power users and developers'' from '''June 2 to June 6, 2023''' to celebrate GRASS GIS '''40th birthday''' (by contributing to GRASS GIS of course).

<gallery mode="slideshow">
Image:grass-sprint-prague.jpg|Prague 2013
Image:Grass_sprint2018_bonn_fotowall.jpg|Bonn 2018
</gallery>

== Purpose ==

GRASS GIS Community Meeting is a great occasion for folks to support the development by actively contributing to the source code, documentation (manuals, wiki, tutorials), translations, website 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 desiring to '''celebrate with us the 40th GRASS GIS birthday!!'''

In this meeting, we will work on GRASS GIS and integrations with related OSGeo projects. We will revise connection to QGIS to make it easier to maintain, and we will work on migration of the build to CMake to improve Windows builds including PDAL support. Furthermore, we will start moving documentation to Markdown to make it easier to contribute to and we will add images and examples for tools and workflows which still miss them. Finally, we will automate and document maintenance processes to reduce the burden on maintainers and thus improve the project sustainability.

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. 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 at that time given their skills and time available.

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

== Sponsors ==

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 see our

::: '''[https://opencollective.com/osgeo/projects/grass/contribute/grass-community-meeting-prague-2023-55074 OpenCollective GRASS Community Meeting Prague 2023 Tier]'''

Any surplus at the end of the event will used for future activities of the GRASS GIS project such as the successful [[Student Grants|student mini 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. Please see below for the detailed agenda. The developers and contributors are donating their valuable time, so it would be great if in-kind 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.

=== Thanks to our sponsors ===

We are grateful for the support which we have received to organize this GRASS Community Meeting:

[[File:Osgeo logo.png|none|left|alt=Light and dark green logo of OSGeo saying Your Open Source Compass|Open Source Geospatial Foundation]]
* OSGeo: 7303 USD (approved budget contribution, [https://www.loomio.com/p/2m75BZkL/motion-to-approve-7303-to-support-grass-gis-community-meeting motion])

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

Individuals:
* MarWe 50 USD
* Nick Brady 50 USD
* Johannes Brauner 30 USD
* Joaquin Perez Valera 5 USD
* Anonymous sponsors 2750 USD

In-kind contributions:

* Faculty of Civil Engineering Czech Technical University in Prague (FCE CTU) - space and personnel time (planning, preparation)
* North Carolina State University - personnel time (planning, preparation)
* mundialis GmbH & Co. KG - personnel time (planning, preparation)
* CONICET - personnel time (planning, preparation)

== Timing ==

'''When''': June 2-6, 2023

Of course you are invited to join or leave the meeting whenever you want.

== Venue ==

[[Image:logo_cvut.jpg|130px|left]]
Department of Geomatics 
[https://www.fsv.cvut.cz/?lang=en Faculty of Civil Engineering] 
[https://www.cvut.cz/en Czech Technical University in Prague], {{wikipedia|Czech Republic}} 
Thákurova 7/2077, Prague 
Room B868 
[https://en.mapy.cz/s/debazefuse Map] 

Prague has an international [http://www.prg.aero/en/ airport] and is also reachable by train, bus or car.

== Accommodation and Costs ==

Participants should plan for the following costs:

* The participation is free of charge
* Travel to Prague, variable depending on where you come from, reimbursements depending on the financial contributions provided by the community
* Accommodation and meals (with the donated sponsorship money we will try to cover some expenses of the participants)
'''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]).

Please let us know your time of arrival and departure, so we can book accommodations and organize the logistics.

Financial support: (partial) travel grants can be payed upon request thanks to our sponsors!

== Agenda - What we plan to do ==

'''Note:''' The program is generally open for your ideas. Please write an email to the [http://lists.osgeo.org/mailman/listinfo/grass-dev GRASS developer list] to discuss your contribution.

During the meeting we will work on GRASS GIS on these tasks (please add more!):

* We will update and revise the [https://github.com/qgis/QGIS/tree/master/python/plugins/grassprovider GRASS GIS Integration with QGIS] to simplify maintenance.
* Furthermore, we will migrate the compilation technology to CMake to significantly improve the Windows builds including PDAL support and become binary compatible with OSGeo4W.
* The extensive GRASS documentation will be converted from HTML to Markdown to facilitate future collaboration.
* Pictures, examples and workflows will be added to the documentation where they are still missing.
* Software maintenance processes are automated and documented to reduce the burden on maintainers and thus improve the sustainability of the project.

This means that there are tasks from both the programming and documentation areas to appeal to a wide range of interested parties.

Further details about the action items you '''find [[Talk:GRASS Community Meeting Prague 2023|here]]''' and below. Topics cover non-technical, semi-technical, and technical issues.

=== Timeline ===

(agenda is under development, but also flexible)

==== Thursday, 1 June ====

* Arrival

==== Friday, 2 June ====

* 10:00 meeting starts in the room B-868
* Review the plan for the next days
* API for use in Python and in other projects (e.g., QGIS)
* Parallelizations

==== Saturday, 3 June ====

* Reducing cost of distribution on Windows
* Group photo 1

==== Sunday, 4 June ====

* Compilation CMake (Windows, Linux)
* Connections in general, rgrass, qgisprocess
* Group photo 2

==== Monday, 5 June ====

* Connections in general, QGIS, rgrass, qgisprocess
* Parallelizations
* grass.jupyter

==== Tuesday, 6 June ====

* Connections in general, QGIS
* Parallelizations
* grass.jupyter

==== Wednesday, 7 June ====

* Departure

== Participation ==

We are planning for an attendance of 20 people (i.e., coding places) but of course you are welcome to join us and bring new ideas with you: we'll make more places available. Please add your name here or contact [[User:Landa|Martin Landa]] <tt><landa.martin 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:Landa|Martin Landa]]
| Czech Republic
| June 1
| June 7
| Python: create_location ([https://github.com/OSGeo/grass/issues/1987 #1987]), Graphical Modeler improvements and single window layout integration
|
|-
|2
| Micha Silver
| Israel
| June 2
| June 6
| Addon to derive soil moisture from Sentinel 2
|
|-
|3
|[https://www.osgeo.org/member/kudrnovsky/ Helmut Kudrnovsky]
| Austria
| June 2 (18:37) by train
| June 4 (18:24) by train
| support CMake transition
|
|-
|4
|[[User:Neteler|Markus Neteler]]
| Germany
| June 2 (17:17)
| June 6 (12:43)
| translations, manual pages, ..., see [[Talk:GRASS_Community_Meeting_Prague_2023#Markus_Neteler|my list in "Discussion" page]]
|
|-
|5
|[[User:pesekon2|Ondřej Pešek]]
| Czech Republic
| June 2 (17:17)
| June 6 (12:43)
| Python 3.12-connected issues, gmodeler
|
|-
|6
| [[User:helena|Helena Mitasova]]
| United States
| June 2
| June 6
|
|
|-
|7
| [[User:wenzeslaus|Vaclav Petras]]
| United States
| June 1
| June 7
| init and other Python API topics, support CMake transition, revise connection with QGIS and other tools, funding
|
|-
|8
| [[User:Annakrat|Anna Petrasova]]
| United States
| June 1
| June 7
| parallelization documentation, grass.jupyter, R and QGIS integration
|
|-
|9
| [[User:Ctwhite|Corey White]]
| United States
| June 2 (10:55)
| June 7
| Connections with other tools, OpenPlains, JSON outputs
|
|-
|10
| [[User:MarisN|Maris Nartiss]]
| Latvia
| June 2
| June 6
|
|-
|11
| [[User:Aaronsms|Aaron Saw Min Sern]]
| Singapore
| June 1
| June 7
| Support CMake transition, r.mapcalc parallelization
|
|-
|12
| [[User:Ldesousa|Luís de Sousa]]
| The Netherlands
| June 1 (20:00)
| June 5 (20:45)
| Update r.mblend add-on; test CMake transition.
|
|-
|13
| Caitlin Haedrich
| United States
| June 1
| June 7
| grass.jupyter
|
|-
|14
| Linda Kladivová
| Czech Republic
| June 2
| June 6
| Single-Window layout issues and improvements
|
|-
|15
| Carmen Tawalika
| Germany
| June 2 (17:17)
| June 6 (12:43)
| Happy to assist with general topics like documentation + automation, in doubt something related to actinia
|
|-
|16
| Floris Vanderhaeghe
| Belgium
| June 3 (train 19:17)
| June 6 (train 8:25)
| Helping in interfacing GRASS from R (rgrass & qgisprocess packages)
|
|-
|}

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

=== Via chat or hangout ===

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

TBD: Google Meet / 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
|[[User:Baharmon|Brendan Harmon]]
| United States
| Update integration with QGIS
|
|
|-
|2
|[[User:veroandreo|Veronica Andreo]]
| Argentina
| Mission and vision, interfaces with QGIS and R, sponsoring, ... [https://grasswiki.osgeo.org/wiki/Talk:GRASS_Community_Meeting_Prague_2023#Vero see discussion tab]
| available from 8:00 AM ART (UTC-3) onward
|
|-
|3
|[[User:Nobeeakon|Daniel T]]
| Mexico
|
| some availability through the days :/
|
|-
|4
|[[User:LBartoletti|Loïc Bartoletti]]
| France
| QGIS Integration, support CMake transition
|
|-
|}

==== Timing of hangout meetings ====

Vero: available from 8:00 AM ART (UTC-3) onward

=== Collaborative document scratching ===

TBD

== 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 subversion and the compiler tools, and come with a working GRASS development environment if possible.

== Broadcast & Video ==

During the event :)

== Photos ==

Also during the event :)

== FAQ ==

* '''How was it last time?'''
** Very nice, see [[GRASS_GIS at OSGeo Virtual Community Sprint 2020]]!
* ''Is the GRASS Community 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.
** On demand we can do some presentations of current working GRASS implementation and new upcoming features to spread the idea of Open Source GIS software.
* ''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:Landa|Martin Landa]] <tt><landa.martin at gmail.com></tt>

== Report and press release ==

TBD: After the event :-)

We'll esp. craft a report for our sponsors.

[[Category: Workshops]]
[[Category: Code Sprint]]
[[Category: 2023]]