GRASS-Wiki - User contributions [en]

AVIRIS

2023-12-21T22:01:58Z

⚠️Wenzeslaus: Replace source tag with syntaxhighlight according to the automatically linked category https://grasswiki.osgeo.org/wiki/Category:Pages_using_deprecated_source_tags

== AVIRIS Hyperspectral Sensor ==
[[File:aviris_text2.png]]
=== Introduction ===
'''AVIRIS''' is an acronym for the Airborne Visible InfraRed Imaging Spectrometer ([https://aviris.jpl.nasa.gov/ AVIRIS Main page]).

Its optical sensor creates calibrated images of the upwelling spectral radiance in 224 contiguous spectral channels/bands with wavelengths from 400 to 2500 nanometers (nm).

=== Airplanes ===
'''AVIRIS''' has been flown on four aircraft platforms:
* NASA's ER-2 jet
* Twin Otter International's turboprop
* Scaled Composites' Proteus
* NASA's WB-57.

Flight details:
* The ER-2 flies at approximately 20km above sea level, at about 730 km/hr.
* The Twin Otter aircraft flies at 4km above ground level at 130km/hr.

=== Data Download ===
Downloading data from '''AVIRIS''' flights is straightforward using the [https://aviris.jpl.nasa.gov/dataportal/ AVIRIS Data Portal].

== Import AVIRIS in GRASS ==
=== Data Downloaded ===

'''AVIRIS''' is downloaded as a .tar.gz file (i.e. ''f180116t01p00r07.tar.gz'') uncompressing as a directory (i.e. ''f180116t01p00r07rdn_e/'') containing with a set files like this:

==== List of files ====
* AVIRIS_OrthoProcessing_Info.txt
* f180116t01p00r07rdn_e_eph
* f180116t01p00r07rdn_e.gain
* f180116t01p00r07rdn_e_lonlat_eph
* ''f180116t01p00r07rdn_e_obs''
* f180116t01p00r07rdn_e_obs.hdr
* ''f180116t01p00r07rdn_e_obs_ort''
* f180116t01p00r07rdn_e_obs_ort.hdr
* ''f180116t01p00r07rdn_e_ort_glt''
* f180116t01p00r07rdn_e_ort_glt.hdr
* ''f180116t01p00r07rdn_e_ort_igm''
* f180116t01p00r07rdn_e_ort_igm.hdr
* f180116t01p00r07rdn_e_ort.plog
* f180116t01p00r07rdn_e.rccf18
* ''f180116t01p00r07rdn_e_sc01_ort_img''
* f180116t01p00r07rdn_e_sc01_ort_img.hdr
* f180116t01p00r07rdn_e.spc

All files twinned with a .hdr file, and in italics in the list above, are ENVI style binary imagery datasets (''BSQ format''). Towards the end of the list, the file matching the pattern ''sc01'' is the largest file, and the one holding the actual hyperspectral data.

==== DN to Radiance Conversion ====

The DN to Radiance correction is done by applying a gain to the stored data in the BSQ file. In this case, the gain file in ''f180116t01p00r07rdn_e.gain''. Extracting the gain values can be done like this in Python:

<syntaxhighlight lang="python">
gain = []
with open(AVIRISDir+"rdn_e/"+AVIRISDir+"rdn_e.gain") as file:
for line in file:
gain.append(line.strip().split()[0])
</syntaxhighlight>

After that, the DN to Radiance correction can be done like this:

<syntaxhighlight lang="python">
# define GRASS-Python environment
os.environ['GISBASE'] = "/usr/local/grass84"
grass_pydir = os.path.join("/usr/local/grass84", "etc", "python")
sys.path.append(grass_pydir)
from grass.script import setup as gsetup
from grass.pygrass.modules.shortcuts import raster as r
from grass.pygrass.modules import Module

rmapcalc = Module('r.mapcalc')
# AVIRIS DN->Rad->Ref
print("Convert DN to Rad")
# Apply Gain from file
for j in range(len(gain)):
exp = str("rad."+str(j+1)+"=dn."+str(j+1)+"*10.0/"+str(gain[j]))
#print(exp)
rmapcalc(expression=exp, overwrite=OVR, quiet=QUIET)
rmapcalc.wait()
</syntaxhighlight>

=== Import in GRASS, gain correction (DN2Rad) & atmospheric correction (Rad2Ref) ===
<syntaxhighlight lang="python">
#!/usr/bin/env python
"""
Process all AVIRIS radiance tar.gz into reflectance.

Download all radiance tar.gz files into rsdatapath
Make sure GRASS GIS and python-gdal are installed
run this code after specifying your directories

# Date: 24th October, 2023
# Public domain, GRASS GIS

# PURPOSE
# This script processes AVIRIS images
# 1 - untar *.tar.gz files
# 2 - Connect files in GRASS GIS Location of your choice
# 3 - DN to Radiance (Apply Gain)
# 4 - Radiance to Surface reflectance (i.atcorr)
"""
# Load necessary libraries
import os
import sys
import time
import struct
from subprocess import PIPE
# from osgeo import ogr
from osgeo import osr
from osgeo import gdal
# define GRASS-Python environment
os.environ['GISBASE'] = "/usr/local/grass84"
grass_pydir = os.path.join("/usr/local/grass84", "etc", "python")
sys.path.append(grass_pydir)
from grass.script import setup as gsetup
from grass.pygrass.modules.shortcuts import raster as r
from grass.pygrass.modules.shortcuts import imagery as i
from grass.pygrass.modules import Module
from grass.script.utils import parse_key_val

# QUIET REPORTS
QUIET = True

# OVERWRITE EXISTING FILES
OVR = True

# Setup the path to the AVIRIS Directories
rsdatapath = "/home/yann/RSDATA/AVIRIS"

# Setup your GRASS GIS working directory
grassdata = "/home/yann/grassdata/"
location = "AVIRIS"
print(location)
mapset = "PERMANENT"

# DEM input for atmospheric correction
inDEM = "/home/yann/RSDATA/SRTM/dem.vrt"

# Visibility distance [Km]
vis = 18

# List of .tar.gz AVIRIS radiance tracks downloaded
AVIRISDirs = ["f180116t01p00r07"] # , "f100517t01p00r11"]

# CONFIGURATION OF 6S
# https://grass.osgeo.org/grass84/manuals/i.atcorr.html

# Atmospheric mode
# none = 0
# tropical = 1
# midlatitude summer = 2
# midlatitude winter = 3
atm_mode = 1
# Aerosol model
# none = 0
# continental = 1
# maritime = 2
# urban = 3
aerosol_mode = 2

# END OF USER CHANGES
# DO NOT CHANGE ANYTHING AFTER THIS LINE !

# Change directory to find the tar.gz files of AVIRIS
os.chdir(rsdatapath)

# Remove previous temporary GRASS Location
p = os.system("rm -Rf "+grassdata+location)

def read_ephemeris_file(file_path):
"""
Read the ephemeris _eph file and extract flight altitude.

Parameters
----------
file_path : STRING
the ephemeris *_eph file.

Returns
-------
data : FLOAT
the average height of sensor during flight.
"""
data = []
# Define the format of a single record in the binary file
record_format = 'd' * 6 # Six double-precision floating-point numbers
with open(file_path, 'rb') as f:
while True:
record = f.read(struct.calcsize(record_format))
if not record:
break # Reached end of file
values = struct.unpack(record_format, record)
data.append(values)
return data

# START PROCESS
# Read Gain from File
gain = []
# Start processing each radiance track bundlefrom DN to Ref
for AVIRISDir in AVIRISDirs:
# Untar all of your AVIRIS images in all your directories
print("Untar AVIRIS files in ", AVIRISDir)
#p = os.system("tar xvf "+AVIRISDir+".tar.gz")
with open(AVIRISDir+"rdn_e/"+AVIRISDir+"rdn_e.gain") as file:
for line in file:
gain.append(line.strip().split()[0])
# Process a North alignment of the original file TODO add datatype=float
kwargs = {'format': 'GTiff', 'geoloc': True, 'options': 'overwrite'}
# gdal.UseExceptions()
#ds = gdal.Warp("del.tif", AVIRISDir + "rdn_e/" + AVIRISDir + "rdn_e_sc01_ort_img", **kwargs)
#del ds
# Create a temporary GRASS Location
p = os.system("grass -c del.tif -e "+grassdata+location)
time.sleep(20)
session = gsetup.init(grassdata, location, mapset)
print("Import in GRASS GIS")
# Import DEM for atmospheric correction
ringdal = Module('r.in.gdal')
# In case the DEM file is not empty
# ringdal(input=AVIRISDir+"rdn_e/"+AVIRISDir+"rdn_e_ort_igm", output="dem",
# overwrite=OVR)
# In case the DEM is available to import from srtm.csi.cgiar.org
#rimport = Module('r.import')
#rimport(input=inDEM, output="dem", extent="region", overwrite=OVR)
# The least effective, make your own flat DEM layer
rmapcalc = Module('r.mapcalc')
rmapcalc(expression="dem=1", overwrite=OVR)
rmapcalc.wait()
# Create a visibility (AOD) map
rmapcalc(expression="vis=18", overwrite=OVR)
rmapcalc.wait()
# Import AVIRIS in GRASS
ringdal(input="del.tif", output="dn", quiet=QUIET)
# Remove nodata from DN maps
rnull = Module('r.null')
for idx in range(224):
rnull(map="dn."+str(idx+1), setnull=[-50, 0], quiet=QUIET)
# Read rotated AVIRIS image
src = gdal.Open("del.tif")
ulx_, xres, xskew, uly_, yskew, yres = src.GetGeoTransform()
lrx_ = ulx_ + (src.RasterXSize * xres)
lry_ = uly_ + (src.RasterYSize * yres)
# Setup the source projection
source = osr.SpatialReference()
source.ImportFromWkt(src.GetProjection())
del src
# The target projection is ll wgs84
target = osr.SpatialReference()
target.ImportFromEPSG(4326)
# Create the transform
transform = osr.CoordinateTransformation(source, target)
# Transform the points
uly, ulx, _ = transform.TransformPoint(ulx_, uly_)
lry, lrx, _ = transform.TransformPoint(lrx_, lry_)
# Import Auxiliary layers, rotate it first
ds = gdal.Warp("del1.tif", AVIRISDir + "rdn_e/" + AVIRISDir +
"rdn_e_obs_ort", **kwargs)
del ds
# Import in GRASS TODO force Float data
ringdal(input="del1.tif", output="obs", flags="e", overwrite=OVR, quiet=QUIET)
# Remove nodata from UTC map
rnull(map="obs.10", setnull=[-9999, 0], quiet=QUIET)
# Extract stats
rinfo = Module('r.info', map="obs.10", flags="s", stdout_=PIPE)
rinfo_out = parse_key_val(rinfo.outputs.stdout)
# Extract mean values from Dict
dectime = rinfo_out["mean"]
print("timestamp ", str(dectime))
print(AVIRISDir)
date = ["20"+AVIRISDir[1:3], AVIRISDir[3:5], AVIRISDir[5:7]]
print(date)
# AVIRIS DN->Rad->Ref
print("Convert DN to Rad")
# Apply Gain from file
for j in range(len(gain)):
exp = str("rad."+str(j+1)+"=dn."+str(j+1)+"*10.0/"+str(gain[j]))
#print(exp)
rmapcalc(expression=exp, overwrite=OVR, quiet=QUIET)
rmapcalc.wait()
# Atmospheric Correction
print("Atmospheric Correction")
# Basic script for i.atcorr for AVIRIS
# Geometrical conditions (AVIRIS = 31)
geom = 31
# Sensor height (satellite is -1000)
eph_data = read_ephemeris_file(AVIRISDir+"rdn_e/"+AVIRISDir+"rdn_e_eph")
# Extract average altitude
add = 0
for j in range(len(eph_data)):
add += eph_data[j][2]
height = add/len(eph_data)
# Define the sensor height as Km and negative (for 6S)
sens_height = -1*height/1000.0
# Here we suppose you have altitude (DEM) and Visibility (VIS) maps ready
# ---------------------------------------------
# Altitude dummy value (in Km should be negative in this param file)
# (overwritten by DEM raster input)
alt = -0.600
# datetime of satellite overpass (month, day, GMT decimal hour)
mdh = str(date[1])+" "+str(date[2])+" "+str("%.3f" % float(dectime))
print(mdh)
# Central Lat/Long
Lon = ulx+(lrx-ulx)/2.0
Lat = lry+(uly-lry)/2.0
print(Lon, Lat)
# satellite band number (AVIRIS [209-432])
satbandno = 209 # Band 1 of AVIRIS is first for atmospheric correction
for idx in range(224):
b = "rad." + str(idx+1)
b_out = b.replace("rad.", "ref.")
# Extract min max radiance stats
rinfo = Module('r.info', map="rad."+str(idx+1), flags="s", stdout_=PIPE)
rinfo_out = parse_key_val(rinfo.outputs.stdout)
# Extract mean values from Dict
minimum = rinfo_out["min"]
maximum = rinfo_out["max"]
if (minimum < 0.0):
minimum = 0.0
param = []
# geometrical conditions=AVIRIS
param.append(str(geom)+"\n")
# month day hh.ddd longitude latitude (hh.ddd is in decimal hours GMT)
param.append(str(mdh)+" "+str("%.2f" % Lon)+" "+str("%.2f" % Lat)+"\n")
# atmospheric mode=tropical
param.append(str(atm_mode)+"\n")
# aerosols model=maritime
param.append(str(aerosol_mode)+"\n")
# visibility [km] (aerosol model concentration), not used (raster input)\n")
param.append(str(vis)+"\n")
# mean target elevation above sea level [km] (here 600m asl), not used (raster input)
param.append(str(alt)+"\n")
# sensor height (here, sensor on board a plane)
param.append(str("%.2f" % round(sens_height,2))+"\n")
# puw (water vapor content between the aircraft and the surface)
param.append("-1.0\n")
# po3 (ozone content between the aircraft and the surface)
param.append("-1.0\n")
# taerp (the aerosol optical thickness at 550nm between the aircraft and the surface)
param.append("-1.0\n")
# i th band of AVIRIS (atcorr internal no)
param.append(str(satbandno))
prm = "param_AVIRIS.txt"
f = open(prm, "w")
f.writelines(param)
f.close()
print(b)
print(b_out)
iatcorr = Module('i.atcorr')
iatcorr(input=b, elevation="dem", visibility="vis", parameters=prm,
output=b_out, range=[minimum, maximum], rescale=[0.0,1.0], quiet=QUIET, overwrite=OVR)
routgdal = Module('r.out.gdal')
routgdal(input=b_out, output=AVIRISDir+"_"+b_out+".tif", overwrite=OVR, quiet=QUIET)
satbandno = satbandno + 1
</syntaxhighlight>

Category:Pages using deprecated source tags

2023-12-21T21:58:52Z

⚠️Wenzeslaus: Explain what the category means and how to fix it

This category is populated automatically. It contains pages where MediaWiki has detected deprecated <code>source</code> tag. These should be replaced by <code>syntaxhighlight</code>.

So, replace:

<nowiki>
<source lang="python">
print("Hello world!")
</source></nowiki>

with:

<nowiki>
<syntaxhighlight lang="python">
print("Hello world!")
</syntaxhighlight></nowiki>

which renders just as great:

<syntaxhighlight lang="python">
print("Hello world!")
</syntaxhighlight>

GRASS GIS Budget 2024

2023-12-15T21:13:42Z

⚠️Wenzeslaus:

== Income ==

{| class="wikitable"
! Item !! USD !! EUR !! Notes
|-
| Request to OSGeo (general budget) || 5,000.00 || 4,585.76 || OSGeo Projects budget
|-
| Expected Donations || 550.00 || 504.43 || Based on average from 2020-2022
|-
| Total income || 5,550.00 || 5,090.20 ||
|}

== Expenses ==

{| class="wikitable"
! Item !! USD !! EUR !! Notes
|-
| Events, Sprints, Travel || || ||
|-
| Sprint || 4,100.00 || 3,760.32 || Community contributions to the sprint through the budget
|-
| PSC rep at AGM + Travel to OSGeo Sprint || 2,200.00 || 2,017.74 || Multiple travels on a continent or one travel to a different continent
|-
| Subtotal || 6,300.00 || 5,778.06 ||
|-
| || || ||
|-
| Student Grants || || ||
|-
| Student grants || 4,000.00 || 3,668.61 || See Student Grants wiki page, 4 grants offered
|-
| Subtotal || 4,000.00 || 3,668.61 ||
|-
| || || ||
|-
| Marketing || || ||
|-
| T-shirts, swag for users, conferences, ... || 400.00 || 366.86 || Community members can request for local or global events
|-
| Stickers and magnets (as above) || 400.00 || 366.86 || Community members can request for local or global events
|-
| Subtotal || 800.00 || 733.72 ||
|-
| || || ||
|-
| Total expenses || 11,100.00 || 10,180.39 ||
|}

== Balance ==

{| class="wikitable"
! Item !! USD !! EUR !! Notes
|-
| Year balance (income - expenses) || -5,550.00 || -5,090.20 || If negative, it needs to be covered by additional fundraising and surplus.
|-
| Balance in Open Collective || 6,149.03 || 5,639.60 || State from December 15, 2023
|-
| EOY balance (year balance + surplus) || 599.03 || 549.40 ||
|}

Edits: Ask the treasurer about editing this page.

GRASS GIS Budget 2024

2023-12-15T20:42:18Z

⚠️Wenzeslaus: Created page with "== Income == {| class="wikitable" ! Item !! USD !! EUR !! Notes |- | Request to OSGeo (general budget) || 5,000.00 || 4,585.76 || OSGeo Projects budget |- | Expected Donations || 550.00 || 504.43 || Based on average from 2020-2022 |- | Total income || 5,550.00 || 5,090.20 || |} == Expenses == {| class="wikitable" ! Item !! USD !! EUR !! Notes |- | Events, Sprints, Travel || || || |- | Sprint || 4,100.00 || 3,760.32 || Community contributions to the sprint through..."

NSF POSE Project 2023-2025 Timeline

2023-12-13T01:35:43Z

⚠️Wenzeslaus:

[[File:NSF_grant_announcement.png|500px|right|none]]

To inform GRASS community about the work done as part of the award [https://www.nsf.gov/awardsearch/showAward?AWD_ID=2303651 2303651] from the U.S. National Science Foundation (NSF) to enhance GRASS ecosystem, the following report summarizes the progress and outcomes in quarterly reports and presents the roadmap for the project.

The two main goals of the project are: 1) to facilitate the adoption of GRASS GIS as a key geoprocessing engine by a growing number of researchers and geospatial practitioners in academia, governments, and industry; and 2) to expand and diversify the developer community, especially through supporting next-generation scientists to gain expertise to maintain and innovate GRASS software.

Principal investigators and senior personnel:

* Helena Mitasova, North Carolina State University (Principal Investigator)
* Vaclav Petras, North Carolina State University (Co-Principal Investigator)
* Anna Petrasova, North Carolina State University (Co-Principal Investigator)
* C Michael Barton, Arizona State University (Co-Principal Investigator)
* Huidae Cho, New Mexico State University (Co-Principal Investigator)
* Giuseppe Amatulli, Yale (Senior Personnel)

Other personnel who is joining for the execution of the grant is listed below when relevant.

== 1st quarter report ==
=== Project Announcements and Communication ===
* Announcement on [https://grass.osgeo.org/news/2023_09_06_nsf_grant_awarded/ GRASS website].
* Info session to explain the POSE Project ([https://lists.osgeo.org/pipermail/grass-user/2023-September/083423.html Announcement on GRASS user mailing list], 2 sessions for different time zones).
* Collected statistics from GitHub, X and others and set up automated collection for GitHub.

=== Conference Presentations ===
* [https://petrasovaa.github.io/FUTURES-CONUS-talk/foss4gNA2023.html#/ Parallelization Tips for Geoprocessing with GRASS GIS] by Anna Petrasova at FOSS4GNA, October 2023.
* [https://wenzeslaus.github.io/grass-gis-talks/foss4gna2023.html#/ GRASS GIS: Not What You Think] by Vaclav Petras at FOSS4GNA, October 2023.
* [https://docs.google.com/presentation/d/1D-Fh1cLSPINyeXdVaxlakrE9IjB8kK5lIw3D12yX1bk Computational Notebooks for Reproducible Geospatial Computation in Research and Education] by Caitlin Haedrich at FOSS4GNA, October 2023.
* [https://github.com/HuidaeCho/grass-gis-talk-foss4g-asia-2023 State of GRASS GIS: 40 Years Strong and Counting] by Huidae Cho at FOSS4G Asia, November 2023.

=== Training and Workshops ===
* [https://github.com/ncsu-geoforall-lab/grass-gis-workshop-foss4gna-2023 Unlock the power of GRASS GIS] by Anna Petrasova and Caitlin Haedrich at FOSS4GNA, October 2023.
* [https://github.com/ncsu-geoforall-lab/develop-tools-with-grass-foss4gna-2023 Develop Geospatial Workflows and Custom Tools with GRASS GIS] by Vaclav Petras and Corey White at FOSS4GNA, October 2023.
* [https://github.com/ncsu-geoforall-lab/grass-workshop-gis-week-2023 Big Data Computing with GRASS GIS] by Anna Petrasova and Vaclav Petras at NC State GIS week, November 2023.
* [https://github.com/ncsu-geoforall-lab/grass-gis-on-hpc-henry2/blob/8564c72e9b8929c9ef4d25ada1ef36b569991221/docs/tutorial.md GIS Week Workshop: High Performance Computing for Geospatial Analysis (GRASS GIS part)] by Vaclav Petras (main lecture lead by Andrew Petersen from NCSU OIT) at NC State GIS week, November 2023.
* [https://spatial-ecology.net/docs/build/html/index.html Geocomputation and Machine Learning for Environmental Applications] training course [https://spatial-ecology.net/course-geocomputation-machine-learning-for-environmental-applications-intermediate-level-2024/ announced]. GRASS GIS part led by Giuseppe Amatulli is free of charge thanks to the support by NSF.

=== Community Sprint Participation ===
Anna Petrasova and Vaclav Petras remotely participated in [https://wiki.osgeo.org/wiki/OSGeo_Community_Sprint_2023 OSGeo 2023 code sprint] doing PR reviews and maintenance of GRASS GIS code, documentation, and website.

=== Mentoring Program ===
* Started a development-oriented mentoring program [https://grass.osgeo.org/news/2023_10_11_mentoring_program_announced/ announced] with details available on a [https://grasswiki.osgeo.org/wiki/Mentoring_Program wiki page].
* Program now has 4 participants (from 12 responses) supported by email and video calls.
* Program already resulted in improvements to GRASS GIS core and addons:
** merged PR: [https://github.com/OSGeo/grass/pull/3206 grass.script: ensure memmap content is flushed before writing to a raster]
** radar addon toolset PR: [https://github.com/OSGeo/grass-addons/pull/949 Add i.saocom and i.sar toolsets]
Mentoring Program is a new effort started and so-far performed only by the POSE team.

=== Student Grants Program ===
Student grants [https://grass.osgeo.org/news/2023_11_09_student_grants_announced/ announced] with topics at a [https://grasswiki.osgeo.org/wiki/GRASS_GIS_Student_Grants wiki page]. Student Grants Program is an existing effort which the POSE team participates in.

=== Working Groups ===

Four [https://grasswiki.osgeo.org/wiki/Working_Groups working groups] created (scope, wiki page, coordinator, and a list of people for each).

=== Citations ===

* GRASS GIS Google Scholar [https://scholar.google.com/citations?user=gJ0ZB0cAAAAJ account] updated with more complete records.
* A [https://forms.gle/cDEvMJu7d6nvxLKn9 form] was created to collect new and missing records.
* Profile link added to GRASS website [https://grass.osgeo.org/contribute/ Contribute] and [https://grass.osgeo.org/about/citation/ Citation] page.

== Roadmap ==
;Mentoring program (fall 2023 - summer 2025)
:Free developer-oriented mentoring program to support researchers and software developers to integrate GRASS GIS into their workflows and contribute to GRASS GIS.

; Streamline contributor onboarding (spring 2024 - fall 2024)
: Includes updating and creating guidelines for code and non-code contributions.

; Streamline user onboarding (spring 2024 - fall 2024)
: Includes modernizing tool documentation, developing tutorials.
: Creating sample datasets for localized tutorials.
: Developing online training materials for big data processing.

; Training sessions (fall 2023 - summer 2025)
: Local training sessions (at universities and conferences) introducing GRASS GIS to students and researchers.
: Training program for big data processing delivered online.

; Engaging industry partners (January - August 2024)
: Identify and engage industry partners to gather feedback and to start industry partnership program.

; Conferences
: Presence (talks, workshops, networking) at FOSS4GNA 2023, FOSS4G Asia 2023, AGU 2023, CSDMD 2024, FOSS4G Europe 2024, FOSS4G 2024, AGU 2024

; Community sprints
: Virtual or in-person participation in OSGeo community sprints, GRASS GIS community sprints

; Software distribution (January 2024 - December 2024)
: Transition to CMake build system
: Develop conda package

;Simplify maintenance of GRASS integrations with QGIS and R (2024-2025)
: Virtual meetings with QGIS and R developers and GRASS GIS developers (spring 2024).
: Identify and implement improvements to the integration.

;Improve code quality, security, and quality assurance
: Code quality (Flake8, Pylint, Cppcheck), first half of 2024.
: Security (CodeQL), second half of 2024.
: Quality assurance (better pytest integration), second half of 2024.

; In-person developer summit (spring/summer 2025)
: Hosted by NC State University, Raleigh, NC, USA.
: Identify additional challenges for adoption of GRASS GIS as geoprocessing engine.
: Long-term planning beyond the POSE project.

== Acknowledgements ==

The funding is provided by the U.S. National Science Foundation, award 2303651.
[[File:NSF Official logo.png|frameless|left]]

[[Category: Community]]
[[Category: Conferences‏‎]]
[[Category: 2023]]
[[Category: 2024]]
[[Category: 2025]]

NSF POSE Project 2023-2025 Timeline

2023-12-11T15:54:21Z

⚠️Wenzeslaus: add list of PIs

[[File:NSF_grant_announcement.png|500px|right|none]]

To inform GRASS community about the work done as part of the award [https://www.nsf.gov/awardsearch/showAward?AWD_ID=2303651 2303651] from the U.S. National Science Foundation (NSF) to enhance GRASS ecosystem, the following report summarizes the progress and outcomes in quarterly reports and presents the roadmap for the project.

The two main goals of the project are: 1) to facilitate the adoption of GRASS GIS as a key geoprocessing engine by a growing number of researchers and geospatial practitioners in academia, governments, and industry; and 2) to expand and diversify the developer community, especially through supporting next-generation scientists to gain expertise to maintain and innovate GRASS software.

Principal investigators and senior personnel:

* Helena Mitasova, North Carolina State University (Principal Investigator)
* Vaclav Petras, North Carolina State University (Co-Principal Investigator)
* Anna Petrasova, North Carolina State University (Co-Principal Investigator)
* C Michael Barton, Arizona State University (Co-Principal Investigator)
* Huidae Cho, New Mexico State University (Co-Principal Investigator)
* Giuseppe Amatulli, Yale, (Senior Personnel)

== 1st quarter report ==
=== Project Announcements and Communication ===
* Announcement on [https://grass.osgeo.org/news/2023_09_06_nsf_grant_awarded/ GRASS website].
* Info session to explain the POSE Project ([https://lists.osgeo.org/pipermail/grass-user/2023-September/083423.html Announcement on GRASS user mailing list], 2 sessions for different time zones).
* Collected statistics from GitHub, X and others and set up automated collection for GitHub.

=== Conference Presentations ===
* [https://petrasovaa.github.io/FUTURES-CONUS-talk/foss4gNA2023.html#/ Parallelization Tips for Geoprocessing with GRASS GIS] by Anna Petrasova at FOSS4GNA, October 2023.
* [https://wenzeslaus.github.io/grass-gis-talks/foss4gna2023.html#/ GRASS GIS: Not What You Think] by Vaclav Petras at FOSS4GNA, October 2023.
* [https://docs.google.com/presentation/d/1D-Fh1cLSPINyeXdVaxlakrE9IjB8kK5lIw3D12yX1bk Computational Notebooks for Reproducible Geospatial Computation in Research and Education] by Caitlin Haedrich at FOSS4GNA, October 2023.
* [https://github.com/HuidaeCho/grass-gis-talk-foss4g-asia-2023 State of GRASS GIS: 40 Years Strong and Counting] by Huidae Cho at FOSS4G Asia, November 2023.

=== Training and Workshops ===
* [https://github.com/ncsu-geoforall-lab/grass-gis-workshop-foss4gna-2023 Unlock the power of GRASS GIS] by Anna Petrasova and Caitlin Haedrich at FOSS4GNA, October 2023.
* [https://github.com/ncsu-geoforall-lab/develop-tools-with-grass-foss4gna-2023 Develop Geospatial Workflows and Custom Tools with GRASS GIS] by Vaclav Petras and Corey White at FOSS4GNA, October 2023.
* [https://github.com/ncsu-geoforall-lab/grass-workshop-gis-week-2023 Big Data Computing with GRASS GIS] by Anna Petrasova and Vaclav Petras at NC State GIS week, November 2023.
* [https://github.com/ncsu-geoforall-lab/grass-gis-on-hpc-henry2/blob/8564c72e9b8929c9ef4d25ada1ef36b569991221/docs/tutorial.md GIS Week Workshop: High Performance Computing for Geospatial Analysis (GRASS GIS part)] by Vaclav Petras (main lecture lead by Andrew Petersen from NCSU OIT) at NC State GIS week, November 2023.
* [https://spatial-ecology.net/docs/build/html/index.html Geocomputation and Machine Learning for Environmental Applications] training course [https://spatial-ecology.net/course-geocomputation-machine-learning-for-environmental-applications-intermediate-level-2024/ announced]. GRASS GIS part led by Giuseppe Amatulli is free of charge thanks to the support by NSF.

=== Community Sprint Participation ===
Anna Petrasova and Vaclav Petras remotely participated in [https://wiki.osgeo.org/wiki/OSGeo_Community_Sprint_2023 OSGeo 2023 code sprint] doing PR reviews and maintenance of GRASS GIS code, documentation, and website.

=== Mentoring Program ===
* Started a development-oriented mentoring program [https://grass.osgeo.org/news/2023_10_11_mentoring_program_announced/ announced] with details available on a [https://grasswiki.osgeo.org/wiki/Mentoring_Program wiki page].
* Program now has 4 participants (from 12 responses) supported by email and video calls.
* Program already resulted in improvements to GRASS GIS core and addons:
** merged PR: [https://github.com/OSGeo/grass/pull/3206 grass.script: ensure memmap content is flushed before writing to a raster]
** radar addon toolset PR: [https://github.com/OSGeo/grass-addons/pull/949 Add i.saocom and i.sar toolsets]
Mentoring Program is a new effort started and so-far performed only by the POSE team.

=== Student Grants Program ===
Student grants [https://grass.osgeo.org/news/2023_11_09_student_grants_announced/ announced] with topics at a [https://grasswiki.osgeo.org/wiki/GRASS_GIS_Student_Grants wiki page]. Student Grants Program is an existing effort which the POSE team participates in.

=== Working Groups ===

Four [https://grasswiki.osgeo.org/wiki/Working_Groups working groups] created (scope, wiki page, coordinator, and a list of people for each).

=== Citations ===

* GRASS GIS Google Scholar [https://scholar.google.com/citations?user=gJ0ZB0cAAAAJ account] updated with more complete records.
* A [https://forms.gle/cDEvMJu7d6nvxLKn9 form] was created to collect new and missing records.
* Profile link added to GRASS website [https://grass.osgeo.org/contribute/ Contribute] and [https://grass.osgeo.org/about/citation/ Citation] page.

== Roadmap ==
;Mentoring program (fall 2023 - summer 2025)
:Free developer-oriented mentoring program to support researchers and software developers to integrate GRASS GIS into their workflows and contribute to GRASS GIS.

; Streamline contributor onboarding (spring 2024 - fall 2024)
: Includes updating and creating guidelines for code and non-code contributions.

; Streamline user onboarding (spring 2024 - fall 2024)
: Includes modernizing tool documentation, developing tutorials.
: Creating sample datasets for localized tutorials.
: Developing online training materials for big data processing.

; Training sessions (fall 2023 - summer 2025)
: Local training sessions (at universities and conferences) introducing GRASS GIS to students and researchers.
: Training program for big data processing delivered online.

; Engaging industry partners (January - August 2024)
: Identify and engage industry partners to gather feedback and to start industry partnership program.

; Conferences
: Presence (talks, workshops, networking) at FOSS4GNA 2023, FOSS4G Asia 2023, AGU 2023, CSDMD 2024, FOSS4G Europe 2024, FOSS4G 2024, AGU 2024

; Community sprints
: Virtual or in-person participation in OSGeo community sprints, GRASS GIS community sprints

; Software distribution (January 2024 - December 2024)
: Transition to CMake build system
: Develop conda package

;Simplify maintenance of GRASS integrations with QGIS and R (2024-2025)
: Virtual meetings with QGIS and R developers and GRASS GIS developers (spring 2024).
: Identify and implement improvements to the integration.

;Improve code quality, security, and quality assurance
: Code quality (Flake8, Pylint, Cppcheck), first half of 2024.
: Security (CodeQL), second half of 2024.
: Quality assurance (better pytest integration), second half of 2024.

; In-person developer summit (spring/summer 2025)
: Hosted by NC State University, Raleigh, NC, USA.
: Identify additional challenges for adoption of GRASS GIS as geoprocessing engine.
: Long-term planning beyond the POSE project.

== Acknowledgements ==

The funding is provided by the U.S. National Science Foundation, award 2303651.
[[File:NSF Official logo.png|frameless|left]]

[[Category: Community]]
[[Category: Conferences‏‎]]
[[Category: 2023]]
[[Category: 2024]]
[[Category: 2025]]

NSF POSE Project 2023-2025 Timeline

2023-12-11T15:44:35Z

⚠️Wenzeslaus: /* 1st quarter report */ Improve categories, add HPC lecture, format text, explain funding for mentoring, student, Geocomputation and ML training course

[[File:NSF_grant_announcement.png|500px|right|none]]

To inform GRASS community about the work done as part of the award [https://www.nsf.gov/awardsearch/showAward?AWD_ID=2303651 2303651] from the U.S. National Science Foundation (NSF) to enhance GRASS ecosystem, the following report summarizes the progress and outcomes in quarterly reports and presents the roadmap for the project.

The two main goals of the project are: 1) to facilitate the adoption of GRASS GIS as a key geoprocessing engine by a growing number of researchers and geospatial practitioners in academia, governments, and industry; and 2) to expand and diversify the developer community, especially through supporting next-generation scientists to gain expertise to maintain and innovate GRASS software.

== 1st quarter report ==
=== Project Announcements and Communication ===
* Announcement on [https://grass.osgeo.org/news/2023_09_06_nsf_grant_awarded/ GRASS website].
* Info session to explain the POSE Project ([https://lists.osgeo.org/pipermail/grass-user/2023-September/083423.html Announcement on GRASS user mailing list], 2 sessions for different time zones).
* Collected statistics from GitHub, X and others and set up automated collection for GitHub.

=== Conference Presentations ===
* [https://petrasovaa.github.io/FUTURES-CONUS-talk/foss4gNA2023.html#/ Parallelization Tips for Geoprocessing with GRASS GIS] by Anna Petrasova at FOSS4GNA, October 2023.
* [https://wenzeslaus.github.io/grass-gis-talks/foss4gna2023.html#/ GRASS GIS: Not What You Think] by Vaclav Petras at FOSS4GNA, October 2023.
* [https://docs.google.com/presentation/d/1D-Fh1cLSPINyeXdVaxlakrE9IjB8kK5lIw3D12yX1bk Computational Notebooks for Reproducible Geospatial Computation in Research and Education] by Caitlin Haedrich at FOSS4GNA, October 2023.
* [https://github.com/HuidaeCho/grass-gis-talk-foss4g-asia-2023 State of GRASS GIS: 40 Years Strong and Counting] by Huidae Cho at FOSS4G Asia, November 2023.

=== Training and Workshops ===
* [https://github.com/ncsu-geoforall-lab/grass-gis-workshop-foss4gna-2023 Unlock the power of GRASS GIS] by Anna Petrasova and Caitlin Haedrich at FOSS4GNA, October 2023.
* [https://github.com/ncsu-geoforall-lab/develop-tools-with-grass-foss4gna-2023 Develop Geospatial Workflows and Custom Tools with GRASS GIS] by Vaclav Petras and Corey White at FOSS4GNA, October 2023.
* [https://github.com/ncsu-geoforall-lab/grass-workshop-gis-week-2023 Big Data Computing with GRASS GIS] by Anna Petrasova and Vaclav Petras at NC State GIS week, November 2023.
* [https://github.com/ncsu-geoforall-lab/grass-gis-on-hpc-henry2/blob/8564c72e9b8929c9ef4d25ada1ef36b569991221/docs/tutorial.md GIS Week Workshop: High Performance Computing for Geospatial Analysis (GRASS GIS part)] by Vaclav Petras (main lecture lead by Andrew Petersen from NCSU OIT) at NC State GIS week, November 2023.
* [https://spatial-ecology.net/docs/build/html/index.html Geocomputation and Machine Learning for Environmental Applications] training course [https://spatial-ecology.net/course-geocomputation-machine-learning-for-environmental-applications-intermediate-level-2024/ announced]. GRASS GIS part led by Giuseppe Amatulli is free of charge thanks to the support by NSF.

=== Community Sprint Participation ===
Anna Petrasova and Vaclav Petras remotely participated in [https://wiki.osgeo.org/wiki/OSGeo_Community_Sprint_2023 OSGeo 2023 code sprint] doing PR reviews and maintenance of GRASS GIS code, documentation, and website.

=== Mentoring Program ===
* Started a development-oriented mentoring program [https://grass.osgeo.org/news/2023_10_11_mentoring_program_announced/ announced] with details available on a [https://grasswiki.osgeo.org/wiki/Mentoring_Program wiki page].
* Program now has 4 participants (from 12 responses) supported by email and video calls.
* Program already resulted in improvements to GRASS GIS core and addons:
** merged PR: [https://github.com/OSGeo/grass/pull/3206 grass.script: ensure memmap content is flushed before writing to a raster]
** radar addon toolset PR: [https://github.com/OSGeo/grass-addons/pull/949 Add i.saocom and i.sar toolsets]
Mentoring Program is a new effort started and so-far performed only by the POSE team.

=== Student Grants Program ===
Student grants [https://grass.osgeo.org/news/2023_11_09_student_grants_announced/ announced] with topics at a [https://grasswiki.osgeo.org/wiki/GRASS_GIS_Student_Grants wiki page]. Student Grants Program is an existing effort which the POSE team participates in.

=== Working Groups ===

Four [https://grasswiki.osgeo.org/wiki/Working_Groups working groups] created (scope, wiki page, coordinator, and a list of people for each).

=== Citations ===

* GRASS GIS Google Scholar [https://scholar.google.com/citations?user=gJ0ZB0cAAAAJ account] updated with more complete records.
* A [https://forms.gle/cDEvMJu7d6nvxLKn9 form] was created to collect new and missing records.
* Profile link added to GRASS website [https://grass.osgeo.org/contribute/ Contribute] and [https://grass.osgeo.org/about/citation/ Citation] page.

== Roadmap ==
;Mentoring program (fall 2023 - summer 2025)
:Free developer-oriented mentoring program to support researchers and software developers to integrate GRASS GIS into their workflows and contribute to GRASS GIS.

; Streamline contributor onboarding (spring 2024 - fall 2024)
: Includes updating and creating guidelines for code and non-code contributions.

; Streamline user onboarding (spring 2024 - fall 2024)
: Includes modernizing tool documentation, developing tutorials.
: Creating sample datasets for localized tutorials.
: Developing online training materials for big data processing.

; Training sessions (fall 2023 - summer 2025)
: Local training sessions (at universities and conferences) introducing GRASS GIS to students and researchers.
: Training program for big data processing delivered online.

; Engaging industry partners (January - August 2024)
: Identify and engage industry partners to gather feedback and to start industry partnership program.

; Conferences
: Presence (talks, workshops, networking) at FOSS4GNA 2023, FOSS4G Asia 2023, AGU 2023, CSDMD 2024, FOSS4G Europe 2024, FOSS4G 2024, AGU 2024

; Community sprints
: Virtual or in-person participation in OSGeo community sprints, GRASS GIS community sprints

; Software distribution (January 2024 - December 2024)
: Transition to CMake build system
: Develop conda package

;Simplify maintenance of GRASS integrations with QGIS and R (2024-2025)
: Virtual meetings with QGIS and R developers and GRASS GIS developers (spring 2024).
: Identify and implement improvements to the integration.

;Improve code quality, security, and quality assurance
: Code quality (Flake8, Pylint, Cppcheck), first half of 2024.
: Security (CodeQL), second half of 2024.
: Quality assurance (better pytest integration), second half of 2024.

; In-person developer summit (spring/summer 2025)
: Hosted by NC State University, Raleigh, NC, USA.
: Identify additional challenges for adoption of GRASS GIS as geoprocessing engine.
: Long-term planning beyond the POSE project.

== Acknowledgements ==

The funding is provided by the U.S. National Science Foundation, award 2303651.
[[File:NSF Official logo.png|frameless|left]]

[[Category: Community]]
[[Category: Conferences‏‎]]
[[Category: 2023]]
[[Category: 2024]]
[[Category: 2025]]

Category:2025

2023-12-11T15:26:47Z

⚠️Wenzeslaus: Created blank page

Category:2024

2023-12-11T15:26:28Z

⚠️Wenzeslaus: Created blank page

NSF POSE Project 2023-2025 Timeline

2023-12-11T15:25:36Z

⚠️Wenzeslaus: /* Roadmap */ Add Acknowledgements and categories

[[File:NSF_grant_announcement.png|500px|right|none]]

To inform GRASS community about the work done as part of the award [https://www.nsf.gov/awardsearch/showAward?AWD_ID=2303651 2303651] from the U.S. National Science Foundation (NSF) to enhance GRASS ecosystem, the following report summarizes the progress and outcomes in quarterly reports and presents the roadmap for the project.

The two main goals of the project are: 1) to facilitate the adoption of GRASS GIS as a key geoprocessing engine by a growing number of researchers and geospatial practitioners in academia, governments, and industry; and 2) to expand and diversify the developer community, especially through supporting next-generation scientists to gain expertise to maintain and innovate GRASS software.

== 1st quarter report ==
=== Project announcement and info session ===
* Announcement on [https://grass.osgeo.org/news/2023_09_06_nsf_grant_awarded/ GRASS website]
* Info session to explain the POSE Project ([https://lists.osgeo.org/pipermail/grass-user/2023-September/083423.html Announcement on GRASS user mailing list])
* Set up collecting statistics from GitHub, X and others

=== GRASS GIS conference presentations ===
* [https://petrasovaa.github.io/FUTURES-CONUS-talk/foss4gNA2023.html#/ Parallelization Tips for Geoprocessing with GRASS GIS] by Anna Petrasova at FOSS4GNA, October 2023.
* [https://wenzeslaus.github.io/grass-gis-talks/foss4gna2023.html#/ GRASS GIS: Not What You Think] by Vaclav Petras at FOSS4GNA, October 2023.
* [https://docs.google.com/presentation/d/1D-Fh1cLSPINyeXdVaxlakrE9IjB8kK5lIw3D12yX1bk Computational Notebooks for Reproducible Geospatial Computation in Research and Education] by Caitlin Haedrich at FOSS4GNA, October 2023.
* [https://github.com/HuidaeCho/grass-gis-talk-foss4g-asia-2023 State of GRASS GIS: 40 Years Strong and Counting] by Huidae Cho at FOSS4G Asia, November 2023.

=== GRASS GIS workshops ===
* [https://github.com/ncsu-geoforall-lab/grass-gis-workshop-foss4gna-2023 Unlock the power of GRASS GIS] by Anna Petrasova and Caitlin Haedrich at FOSS4GNA, October 2023.
* [https://github.com/ncsu-geoforall-lab/develop-tools-with-grass-foss4gna-2023 Develop Geospatial Workflows and Custom Tools with GRASS GIS] by Vaclav Petras and Corey White at FOSS4GNA, October 2023.
* [https://github.com/ncsu-geoforall-lab/grass-workshop-gis-week-2023 Big Data Computing with GRASS GIS] by Anna Petrasova and Vaclav Petras at NC State GIS week, November 2023.

=== OSGeo Community Sprint participation ===
Anna Petrasova and Vaclav Petras remotely participated in
[https://wiki.osgeo.org/wiki/OSGeo_Community_Sprint_2023 OSGeo 2023 code sprint]
doing PR reviews and maintenance of GRASS GIS code, documentation, and website.

=== Mentoring program ===
Development-oriented mentoring program [https://grass.osgeo.org/news/2023_10_11_mentoring_program_announced/ announced]
* [https://grasswiki.osgeo.org/wiki/Mentoring_Program wiki page]
* 4 participants (from 12 responses), supported by email and video calls
Resulted in improvements to GRASS GIS core and addons:
* merged PR: [https://github.com/OSGeo/grass/pull/3206 grass.script: ensure memmap content is flushed before writing to a raster]
* radar addon toolset PR: [https://github.com/OSGeo/grass-addons/pull/949 Add i.saocom and i.sar toolsets]

=== Student grants ===
Student grants [https://grass.osgeo.org/news/2023_11_09_student_grants_announced/ announced] with
topics at a [https://grasswiki.osgeo.org/wiki/GRASS_GIS_Student_Grants wiki page]

=== Working Groups created ===
4 [https://grasswiki.osgeo.org/wiki/Working_Groups working groups] created

=== Google Scholar update ===
GRASS GIS Google Scholar [https://scholar.google.com/citations?user=gJ0ZB0cAAAAJ account] updated with more complete records
* a [https://forms.gle/cDEvMJu7d6nvxLKn9 form] was created to collect missing records
* added to GRASS website [https://grass.osgeo.org/contribute/ Contribute] and [https://grass.osgeo.org/about/citation/ Citation] page

=== GRASS GIS training ===
[https://spatial-ecology.net/docs/build/html/index.html Geocomputation and Machine Learning for Environmental Applications] training course [https://spatial-ecology.net/course-geocomputation-machine-learning-for-environmental-applications-intermediate-level-2024/ announced].
GRASS GIS part free of charge led by Giuseppe Amatulli.

== Roadmap ==
;Mentoring program (fall 2023 - summer 2025)
:Free developer-oriented mentoring program to support researchers and software developers to integrate GRASS GIS into their workflows and contribute to GRASS GIS.

; Streamline contributor onboarding (spring 2024 - fall 2024)
: Includes updating and creating guidelines for code and non-code contributions.

; Streamline user onboarding (spring 2024 - fall 2024)
: Includes modernizing tool documentation, developing tutorials.
: Creating sample datasets for localized tutorials.
: Developing online training materials for big data processing.

; Training sessions (fall 2023 - summer 2025)
: Local training sessions (at universities and conferences) introducing GRASS GIS to students and researchers.
: Training program for big data processing delivered online.

; Engaging industry partners (January - August 2024)
: Identify and engage industry partners to gather feedback and to start industry partnership program.

; Conferences
: Presence (talks, workshops, networking) at FOSS4GNA 2023, FOSS4G Asia 2023, AGU 2023, CSDMD 2024, FOSS4G Europe 2024, FOSS4G 2024, AGU 2024

; Community sprints
: Virtual or in-person participation in OSGeo community sprints, GRASS GIS community sprints

; Software distribution (January 2024 - December 2024)
: Transition to CMake build system
: Develop conda package

;Simplify maintenance of GRASS integrations with QGIS and R (2024-2025)
: Virtual meetings with QGIS and R developers and GRASS GIS developers (spring 2024).
: Identify and implement improvements to the integration.

;Improve code quality, security, and quality assurance
: Code quality (Flake8, Pylint, Cppcheck), first half of 2024.
: Security (CodeQL), second half of 2024.
: Quality assurance (better pytest integration), second half of 2024.

; In-person developer summit (spring/summer 2025)
: Hosted by NC State University, Raleigh, NC, USA.
: Identify additional challenges for adoption of GRASS GIS as geoprocessing engine.
: Long-term planning beyond the POSE project.

== Acknowledgements ==

The funding is provided by the U.S. National Science Foundation, award 2303651.
[[File:NSF Official logo.png|frameless|left]]

[[Category: Community]]
[[Category: Conferences‏‎]]
[[Category: 2023]]
[[Category: 2024]]
[[Category: 2025]]

Student Grants

2023-12-11T15:24:10Z

⚠️Wenzeslaus: Create Mentors section for current mentors, Move Yann Chemin from mentoring program mentors to student grants mentors, add categories for years

{{toc|right}}

[[File:Grassgis logo colorlogo text whitebg.png|300px|right|none]]

GRASS GIS offers a limited number of student grants for projects related to GRASS GIS ([https://grass.osgeo.org/news/2023_11_09_student_grants_announced/ announcement 2023]). These can include actual coding, bug fixing, or documentation and the creation of educational resources.

== Why to apply ==

You will:
* receive mentorship by experienced open-source developers;
* gain programming skills;
* be able to add open-source development into your portfolio;
* get stipend.

== Eligibility ==

To apply for a grant, a student must:
* be eighteen (18) years of age or older upon application;
* be enrolled into a post-secondary academic program, as of the beginning of the grant;
* for the duration of the grant, be eligible to work in the country in which they reside;
* and not be a [https://trac.osgeo.org/grass/wiki/PSC GRASS GIS Project Steering Committee (PSC)] member.

In addition, the student has to:
* demonstrate necessary skills and ability to contribute to GRASS GIS through a [https://github.com/OSGeo/grass/pulls GitHub pull request (PR)].

One person can be awarded one grant at a time, but can apply more than once at different times.

== Stipend ==

* The maximum per grant is 1000 USD. Proposals can be for lower amounts.
* The time to complete the grant should be maximum 3 months, but shorter projects are possible. This depends on the money requested and applicant's availability.
* Start date is flexible.
* For the 2023 deadline, GRASS GIS will offer a total of 4000 USD for stipends.

== Before you apply ==

* Express your interest in applying through the current GRASS community channels (grass-dev@osgeo.org mailing list, GitHub Discussions, or Gitter).
* Identify a topic matching your interest and skills.
* Look for ways to contribute to GRASS that are related to the selected topic (improve documentation, tests, fix bugs, etc.).
* Submit a PR.

== How to apply ==

Students should:
* write their proposals as Google Documents (or similar collaborative online document creation platform) and
* send an email to grass-grants@osgeo.org to notify of their application (with the link to the document).

The email should contain:
* proof of eligibility
** confirm you are 18 year of age or above and that you can work in the country in which you reside for the duration of the grant
** proof of student status (e.g., scanned PDF)
** link to a GRASS GIS PR or PRs (work in progress is okay at this point)

The proposal document should contain:
* applicant's name
* description of the proposed work
* timeline with activities and deliverables
* budget proposal

For timely proposals, applicants will receive feedback from the grants committee and mentors. Changes can be made to the proposal until the deadline.
Proposals can be approved and work started even before the deadline.

For the current call, applications will be accepted until '''December 31, 2023'''.

== Approval process ==

Project proposals are evaluated by the [https://trac.osgeo.org/grass/wiki/PSC GRASS GIS Project Steering Committee] within two weeks after the deadline and a notification will be sent to successful applicants.

== Stipend payment ==

Stipend are paid in two amounts (unless stated otherwise for the specific grant):
* 50% at the beginning of the work phase
* 50% after reception and approval of the final report by the PSC

== Final report ==

The final report should be also written in the [[Student_Grants/2022|GRASS GIS wiki]] under the proposal up to two weeks after the final date planned originally. When finished, the student sends an email to [https://lists.osgeo.org/pipermail/grass-psc/ grass-psc mailing list] to announce the end of the work and share the link to the final report. The final report should include:
* A description of the state of affairs before the work
* A description of the work done

== Topics ==

The GRASS GIS community provides a list of topics highly relevant to the community. Applicants may suggest their own topics.

List of open topics:

* Convert manuals from HTML to markdown, including update of related manual building tools
** convert manual files, e.g. with pandoc
** update man building tools accordingly

* Improve documentation and tests for a set of tools
** includes revising text, add missing/update examples with pictures, notebook how to generate the pictures, add tests (pytest)
** requirements: Python
** $100-200 per tool (proposal should include the total amount requested and budget justification)
** list of suggested tools: r.sim.water, r.reclass, r.resample, r.resamp.filter, r.mask, r.mode, v.surf.idw, v.surf.rst, r.fillnulls, r.surf.*, …

* r.rescale - reimplement as a wrapper to r.recode (see https://github.com/OSGeo/grass/issues/1986), add tests, examples and documentation
** must include tests and documentation
** requirements: Python
** $500

* Parallelize a tool with OpenMP
** possible candidates: r.horizon, r.mapcalc, r.proj, v.surf.idw
** must include tests and benchmarks
** requirements: C, OpenMP experience
** $1000 (one tool)

* Implement ''History manager'' in GRASS GUI
** display history of executed commands and re-execute them
** requirements: Python
** $1000

* Improve d.vect.chart
** fix legend (see https://github.com/OSGeo/grass/issues/3100), update documentation, add tests
** must include documentation, examples, and basic tests
** requirements: basic C and Python
** $500

* Add JSON output to different tools in C
** r.report, r.mapsets, r.what, r.univar, r.info, v.info, r3.info
** must include tests and basic documentation
** requirements: C
** $500 for one tool (proposal should include the total amount requested and budget justification)

See selected topics from past years: [https://trac.osgeo.org/grass/wiki/GSoC/2021/JupyterAndGRASS/MiniGrant2022 Space-Time Dataset Visualization and Improved Interactive Maps for grass.jupyter], [https://trac.osgeo.org/grass/wiki/wxGUIDevelopment/RedesigningStatusbar Redesigning a map display status bar combo box into a new settings dialog]

== Mentors ==

* [https://wiki.osgeo.org/wiki/Anna_Petrasova Anna Petrasova]
* [https://wiki.osgeo.org/wiki/User:Wenzeslaus Vaclav Petras]
* [https://wiki.osgeo.org/wiki/User:Ychemin Yann Chemin]

== Acknowledgements ==

The student stipends are sourced from the financial support the GRASS project receives from sponsors on [https://opencollective.com/grass#section-contributors Open Collective] and [https://www.osgeo.org/ the OSGeo Foundation]. Time of mentors is covered by individual mentors or their employers.

In-kind contributions of personnel time:

* [https://geospatial.ncsu.edu/ North Carolina State University, Center for Geospatial Analytics]
* [https://geomatics.fsv.cvut.cz/en/ Department of Geomatics], Faculty of Civil Engineering, Czech Technical University in Prague

Personal time: Vaclav Petras, Anna Petrasova, Helena Mitasova, Stephan Blumentrath, Martin Landa

[[Category:Community]]
[[Category:Development]]
[[Category:Student Grants]]
[[Category: 2021]]
[[Category: 2022]]
[[Category: 2023]]
[[Category: 2024]]

Mentoring Program

2023-12-11T15:23:06Z

⚠️Wenzeslaus: Move Yann Chemin from mentoring program mentors to student grants mentors, add categories for years

{{toc|right}}

[[File:Grassgis logo colorlogo text whitebg.png|300px|right|none]]

The GRASS GIS project offers a mentoring program to help students, researchers, and software developers integrate GRASS GIS into their projects.

''The mentors hope to grow the GRASS community, so if you are new to GRASS GIS or open-source development in general, this program is for you.''

== Topics ==

The use cases include (but are not limited to):
* developing workflow that uses GRASS GIS e.g., through Python, Bash, R API,
* contributing a research tool for GRASS GIS in Python, C, or C++,
* help with running GRASS GIS on a high-performance cluster,
* integrating GRASS GIS in another software.

== Why to Apply ==

You will:

* receive mentorship by experienced GRASS developers;
* work on a project of your choice;
* use GRASS GIS in the most efficient way for your use case;

Additionally, you may be able to turn a part of your project into a contribution to GRASS GIS. If you do that, you will:

* make your work more accessible;
* preserve your work for future;
* get recognition for open-source contribution.

== Mentoring ==

Mentoring will be provided free of charge by experienced GRASS developers in one-on-one setting allowing for remote and asynchronous communication.

Mentors will work with participants to select the most appropriate and efficient tools and techniques to run and integrate GRASS tools into the participants' workflow and provide advice and feedback during the implementation. Mentors will try to be flexible to accommodate the timing of participants' projects.

== Eligibility ==

The program is open to people from all walks of life regardless of employment or student status. Projects on beginner technical level are welcome. You may be asked to demonstrate your skills for more advanced projects.

The project must use GRASS GIS or contribute to GRASS GIS. Mentors are not able to support other parts of the project, e.g. research aspect or interfacing other software, as part of this program.

The project and applicant eligibility is evaluated by the mentors who may suggest the applicant to modify the proposed topic to make it more suitable for the program or applicant skill set. The final decision on eligibility, admission, and continuation is at the discretion of the mentors.

== How to Apply ==

Fill out [https://forms.gle/Mqri1k9p3uMwr8gG6 the application form] or contact mentors directly (see below).

== Mentors ==

* [https://wiki.osgeo.org/wiki/Anna_Petrasova Anna Petrasova]
* [https://wiki.osgeo.org/wiki/User:Wenzeslaus Vaclav Petras]

== Acknowledgements ==

The funding to cover the time of mentors is provided by the U.S. National Science Foundation, award 2303651.
[[File:NSF Official logo.png|frameless|left]]

[[Category: Community]]
[[Category: 2023]]
[[Category: 2024]]
[[Category: 2025]]

Mentoring Program

2023-10-09T16:50:11Z

⚠️Wenzeslaus: Add NSF logo (NSF's logo can be used by recipients of NSF support for the sole purpose of acknowledging that support. https://www.nsf.gov/policies/logos.jsp)

File:NSF Official logo.png

2023-10-09T16:47:44Z

⚠️Wenzeslaus: NSF Logos and Usage Standards NSF's logo can be used by recipients of NSF support for the sole purpose of acknowledging that support. NSF's logo can be used to link to an NSF website or acknowledge NSF assistance or affiliation. NSF's logo cannot be used in a manner that falsely implies employment by or affiliation with NSF. NSF's logo cannot be used to imply or endorse a product or service. No explicit permission is necessary to use the NSF logo. The NSF logo is the sole visual identifi...

== Summary ==
NSF Logos and Usage Standards

NSF's logo can be used by recipients of NSF support for the sole purpose of acknowledging that support.

NSF's logo can be used to link to an NSF website or acknowledge NSF assistance or affiliation.

NSF's logo cannot be used in a manner that falsely implies employment by or affiliation with NSF. NSF's logo cannot be used to imply or endorse a product or service.

No explicit permission is necessary to use the NSF logo.

The NSF logo is the sole visual identifier of the U.S. National Science Foundation and embodies a set of values that is applied to everything we create and communicate.

Source: https://www.nsf.gov/policies/logos.jsp (2023-10-09)

Mentoring Program

2023-09-26T18:09:30Z

⚠️Wenzeslaus: /* How to Apply */ add mentors as list

{{toc|right}}

[[File:Grassgis logo colorlogo text whitebg.png|300px|right|none]]

The GRASS GIS project offers a mentoring program to help students, researchers, and software developers integrate GRASS GIS into their projects.

''The mentors hope to grow the GRASS community, so if you are new to GRASS GIS or open-source development in general, this program is for you.''

== Why to Apply ==

You will:

* receive mentorship by experienced GRASS developers;
* work on a project of your choice;
* use GRASS GIS in the most efficient way for your use case;

Additionally, you may be able to turn a part of your project into a contribution to GRASS GIS. If you do that, you will:

* make your work more accessible;
* preserve your work for future;
* get recognition for open-source contribution.

== Topics ==

The use cases include (but are not limited to):
* developing workflow that uses GRASS GIS e.g., through Python, Bash, R API,
* contributing a research tool for GRASS GIS in Python, C, or C++,
* help with running GRASS GIS on a high-performance cluster,
* integrating GRASS GIS in another software.

== Mentoring ==

Mentoring will be provided free of charge by experienced GRASS developers in one-on-one setting allowing for remote and asynchronous communication.

Mentors will work with participants to select the most appropriate and efficient tools and techniques to run and integrate GRASS tools into the participants' workflow and provide advice and feedback during the implementation. Mentors will try to be flexible to accommodate the timing of participants' projects.

== Eligibility ==

The program is open to people from all walks of life regardless of employment or student status. Projects on beginner technical level are welcome. You may be asked to demonstrate your skills for more advanced projects.

The project must use GRASS GIS or contribute to GRASS GIS. Mentors are not able to support other parts of the project, e.g. research aspect or interfacing other software, as part of this program.

The project and applicant eligibility is evaluated by the mentors who may suggest the applicant to modify the proposed topic to make it more suitable for the program or applicant skill set. The final decision on eligibility, admission, and continuation is at the discretion of the mentors.

== How to Apply ==

Fill out [https://forms.gle/ttkMok4cfXD5r4pMA the application form].

== Mentors ==

* [https://wiki.osgeo.org/wiki/Anna_Petrasova Anna Petrasova]
* [https://wiki.osgeo.org/wiki/User:Wenzeslaus Vaclav Petras]

== Acknowledgements ==

The funding to cover the time of mentors is provided by the U.S. National Science Foundation, award 2303651.

Student Grants

2023-09-07T18:09:44Z

⚠️Wenzeslaus: Acknowledgements of donations and time

{{toc|right}}

[[File:Grassgis logo colorlogo text whitebg.png|300px|right|none]]

GRASS GIS offers a limited number of student grants for projects related to GRASS GIS. These can include actual coding, bug fixing, or documentation and the creation of educational resources.

== Why to apply ==

You will:
* receive mentorship by experienced open-source developers;
* gain programming skills;
* be able to add open-source development into your portfolio;
* get stipend.

== Eligibility ==

To apply for a grant, a student must:
* be eighteen (18) years of age or older upon application;
* be enrolled into a post-secondary academic program, as of the beginning of the grant;
* for the duration of the grant, be eligible to work in the country in which they reside;
* and not be a [https://trac.osgeo.org/grass/wiki/PSC GRASS GIS Project Steering Committee (PSC)] member.

In addition, the student has to:
* demonstrate necessary skills and ability to contribute to GRASS GIS through a [https://github.com/OSGeo/grass/pulls GitHub pull request (PR)].

One person can be awarded one grant at a time, but can apply more than once at different times.

== Stipend ==

* The maximum per grant is 1000 USD. Proposals can be for lower amounts.
* The time to complete the grant should be maximum 3 months, but shorter projects are possible. This depends on the money requested and applicant's availability.
* Start date is flexible.
* For the 2023 deadline, GRASS GIS will offer a total of 4000 USD for stipends.

== Before you apply ==

* Express your interest in applying through the current GRASS community channels (grass-dev@osgeo.org mailing list, GitHub Discussions, or Gitter).
* Identify a topic matching your interest and skills.
* Look for ways to contribute to GRASS that are related to the selected topic (improve documentation, tests, fix bugs, etc.).
* Submit a PR.

== How to apply ==

Students should:
* write their proposals as Google Documents (or similar collaborative online document creation platform) and
* send an email to grass-grants@osgeo.org to notify of their application (with the link to the document).

The email should contain:
* proof of eligibility
** confirm you are 18 year of age or above and that you can work in the country in which you reside for the duration of the grant
** proof of student status (e.g., scanned PDF)
** link to a GRASS GIS PR or PRs (work in progress is okay at this point)

The proposal document should contain:
* applicant's name
* description of the proposed work
* timeline with activities and deliverables
* budget proposal

For timely proposals, applicants will receive feedback from the grants committee and mentors. Changes can be made to the proposal until the deadline.

For the current call, applications will be accepted until '''October 30, 2023'''.

== Approval process ==

Project proposals are evaluated by the [https://trac.osgeo.org/grass/wiki/PSC GRASS GIS Project Steering Committee] within two weeks after the deadline and a notification will be sent to successful applicants.

== Stipend payment ==

Stipend are paid in two amounts (unless stated otherwise for the specific grant):
* 50% at the beginning of the work phase
* 50% after reception and approval of the final report by the PSC

== Final report ==

The final report should be also written in the [[Student_Grants/2022|GRASS GIS wiki]] under the proposal up to two weeks after the final date planned originally. When finished, the student sends an email to [https://lists.osgeo.org/pipermail/grass-psc/ grass-psc mailing list] to announce the end of the work and share the link to the final report. The final report should include:
* A description of the state of affairs before the work
* A description of the work done

== Topics ==

The GRASS GIS community provides a list of topics highly relevant to the community. Applicants may suggest their own topics.

List of open topics:

* Improve documentation and tests for a set of tools
** includes revising text, add missing/update examples with pictures, notebook how to generate the pictures, add tests (pytest)
** requirements: Python
** $100-200 per tool (proposal should include the total amount requested and budget justification)
** list of suggested tools: r.sim.water, r.reclass, r.resample, r.resamp.filter, r.mask, r.mode, v.surf.idw, v.surf.rst, r.fillnulls, r.surf.*, …

* r.rescale - reimplement as a wrapper to r.recode (see https://github.com/OSGeo/grass/issues/1986), add tests, examples and documentation
** must include tests and documentation
** requirements: Python
** $500

* Parallelize a tool with OpenMP
** possible candidates: r.horizon, r.mapcalc, r.proj, v.surf.idw
** must include tests and benchmarks
** requirements: C, OpenMP experience
** $1000 (one tool)

* Implement ''History manager'' in GRASS GUI
** display history of executed commands and re-execute them
** requirements: Python
** $1000

* Improve d.vect.chart
** fix legend (see https://github.com/OSGeo/grass/issues/3100), update documentation, add tests
** must include documentation, examples, and basic tests
** requirements: basic C and Python
** $500

* Add JSON output to different tools in C
** r.report, r.mapsets, r.what, r.univar, r.info, v.info, r3.info
** must include tests and basic documentation
** requirements: C
** $500 for one tool (proposal should include the total amount requested and budget justification)

See selected topics from past years: [https://trac.osgeo.org/grass/wiki/GSoC/2021/JupyterAndGRASS/MiniGrant2022 Space-Time Dataset Visualization and Improved Interactive Maps for grass.jupyter], [https://trac.osgeo.org/grass/wiki/wxGUIDevelopment/RedesigningStatusbar Redesigning a map display status bar combo box into a new settings dialog]

== Acknowledgements ==

The student stipends are sourced from the financial support the GRASS project receives from sponsors on [https://opencollective.com/grass#section-contributors Open Collective] and [https://www.osgeo.org/ the OSGeo Foundation]. Time of mentors is covered by individual mentors or their employers.

In-kind contributions of personnel time:

* [https://geospatial.ncsu.edu/ North Carolina State University, Center for Geospatial Analytics]

Personal time: Vaclav Petras, Anna Petrasova, Helena Mitasova, Stephan Blumentrath, Martin Landa

[[Category:Community]]
[[Category:Development]]
[[Category:Student Grants]]

Mentoring Program

2023-09-06T20:42:39Z

⚠️Wenzeslaus: Created page with "{{toc|right}} none The GRASS GIS project offers a mentoring program to help students, researchers, and software developers integrate GRASS GIS into their projects. ''The mentors hope to grow the GRASS community, so if you feel distant from the GRASS community or open-source development in general, this program is for you.'' == Why to Apply == You will: * receive mentorship by experienced GRASS developers..."

{{toc|right}}

[[File:Grassgis logo colorlogo text whitebg.png|300px|right|none]]

The GRASS GIS project offers a mentoring program to help students, researchers, and software developers integrate GRASS GIS into their projects.

''The mentors hope to grow the GRASS community, so if you feel distant from the GRASS community or open-source development in general, this program is for you.''

== Why to Apply ==

You will:

* receive mentorship by experienced GRASS developers;
* work on a project of your choice;
* use GRASS GIS in the most efficient way for your use case;

Additionally, you may be able to turn a part of your project into a contribution to GRASS GIS. If you do that, you will:

* make your work more accessible;
* preserve your work for future;
* get recognition for open-source contribution.

== Topics ==

The use cases include (but are not limited to):
* developing workflow that uses GRASS GIS e.g., through Python, Bash, R API,
* contributing a research tool for GRASS GIS in Python, C, or C++,
* help with running GRASS GIS on a high-performance cluster,
* integrating GRASS GIS in another software.

== Mentoring ==

Mentoring will be provided free of charge by experienced GRASS developers in one-on-one setting allowing for remote and asynchronous communication.

Mentors will work with participants to select the most appropriate and efficient tools and techniques to run and integrate GRASS tools into the participants' workflow and provide advice and feedback during the implementation. Mentors will try to be flexible to accommodate the timing of participants' projects.

== Eligibility ==

The program is open to people from all walks of life regardless of employment or student status. Projects on beginner technical level are welcome. You may be asked to demonstrate your skills for more advanced projects.

The project must use GRASS GIS or contribute to GRASS GIS. Mentors are not able to support other parts of the project, e.g. research aspect or interfacing other software, as part of this program.

The project and applicant eligibility is evaluated by the mentors who may suggest the applicant to modify the proposed topic to make it more suitable for the program or applicant skill set. The final decision on eligibility, admission, and continuation is at the discretion of the mentors.

== How to Apply ==

Fill out [https://forms.gle/ttkMok4cfXD5r4pMA the application form].

== Acknowledgements ==

The funding to cover the time of mentors is provided by the U.S. National Science Foundation, award 2303651.

Student Grants

2023-08-22T19:42:49Z

⚠️Wenzeslaus: toc on right, add logo

{{toc|right}}

[[File:Grassgis logo colorlogo text whitebg.png|300px|right|none]]

GRASS GIS offers a limited number of student grants for projects related to GRASS GIS. These can include actual coding, bug fixing, or documentation and the creation of educational resources.

== Why to apply ==

You will:
* receive mentorship by experienced open-source developers;
* gain programming skills;
* be able to add open-source development into your portfolio;
* get stipend.

== Eligibility ==

To apply for a grant, a student must:
* be eighteen (18) years of age or older upon application;
* be enrolled into a post-secondary academic program, as of the beginning of the grant;
* for the duration of the grant, be eligible to work in the country in which they reside;
* and not be a [https://trac.osgeo.org/grass/wiki/PSC GRASS GIS Project Steering Committee (PSC)] member.

In addition, the student has to:
* demonstrate necessary skills and ability to contribute to GRASS GIS through a [https://github.com/OSGeo/grass/pulls GitHub pull request (PR)].

One person can be awarded one grant at a time, but can apply more than once at different times.

== Stipend ==

* The maximum per grant is 1000 USD. Proposals can be for lower amounts.
* The time to complete the grant should be maximum 3 months, but shorter projects are possible. This depends on the money requested and applicant's availability.
* Start date is flexible.
* For the 2023 deadline, GRASS GIS will offer a total of 4000 USD for stipends.

== Before you apply ==

* Express your interest in applying through the current GRASS community channels (grass-dev@osgeo.org mailing list, GitHub Discussions, or Gitter).
* Identify a topic matching your interest and skills.
* Look for ways to contribute to GRASS that are related to the selected topic (improve documentation, tests, fix bugs, etc.).
* Submit a PR.

== How to apply ==

Students should:
* write their proposals as Google Documents (or similar collaborative online document creation platform) and
* send an email to grass-grants@osgeo.org to notify of their application (with the link to the document).

The email should contain:
* proof of eligibility
** confirm you are 18 year of age or above and that you can work in the country in which you reside for the duration of the grant
** proof of student status (e.g., scanned PDF)
** link to a GRASS GIS PR or PRs (work in progress is okay at this point)

The proposal document should contain:
* applicant's name
* description of the proposed work
* timeline with activities and deliverables
* budget proposal

For timely proposals, applicants will receive feedback from the grants committee and mentors. Changes can be made to the proposal until the deadline.

For the current call, applications will be accepted until '''October 30, 2023'''.

== Approval process ==

Project proposals are evaluated by the [https://trac.osgeo.org/grass/wiki/PSC GRASS GIS Project Steering Committee] within two weeks after the deadline and a notification will be sent to successful applicants.

== Stipend payment ==

Stipend are paid in two amounts (unless stated otherwise for the specific grant):
* 50% at the beginning of the work phase
* 50% after reception and approval of the final report by the PSC

== Final report ==

The final report should be also written in the [[Student_Grants/2022|GRASS GIS wiki]] under the proposal up to two weeks after the final date planned originally. When finished, the student sends an email to [https://lists.osgeo.org/pipermail/grass-psc/ grass-psc mailing list] to announce the end of the work and share the link to the final report. The final report should include:
* A description of the state of affairs before the work
* A description of the work done

== Topics ==

The GRASS GIS community provides a list of topics highly relevant to the community. Applicants may suggest their own topics.

List of open topics:

* Improve documentation and tests for a set of tools
** includes revising text, add missing/update examples with pictures, notebook how to generate the pictures, add tests (pytest)
** requirements: Python
** $100-200 per tool (proposal should include the total amount requested and budget justification)
** list of suggested tools: r.sim.water, r.reclass, r.resample, r.resamp.filter, r.mask, r.mode, v.surf.idw, v.surf.rst, r.fillnulls, r.surf.*, …

* r.rescale - reimplement as a wrapper to r.recode (see https://github.com/OSGeo/grass/issues/1986), add tests, examples and documentation
** must include tests and documentation
** requirements: Python
** $500

* Parallelize a tool with OpenMP
** possible candidates: r.horizon, r.mapcalc, r.proj, v.surf.idw
** must include tests and benchmarks
** requirements: C, OpenMP experience
** $1000 (one tool)

* Implement ''History manager'' in GRASS GUI
** display history of executed commands and re-execute them
** requirements: Python
** $1000

* Improve d.vect.chart
** fix legend (see https://github.com/OSGeo/grass/issues/3100), update documentation, add tests
** must include documentation, examples, and basic tests
** requirements: basic C and Python
** $500

* Add JSON output to different tools in C
** r.report, r.mapsets, r.what, r.univar, r.info, v.info, r3.info
** must include tests and basic documentation
** requirements: C
** $500 for one tool (proposal should include the total amount requested and budget justification)

See selected topics from past years: [https://trac.osgeo.org/grass/wiki/GSoC/2021/JupyterAndGRASS/MiniGrant2022 Space-Time Dataset Visualization and Improved Interactive Maps for grass.jupyter], [https://trac.osgeo.org/grass/wiki/wxGUIDevelopment/RedesigningStatusbar Redesigning a map display status bar combo box into a new settings dialog]

[[Category:Community]]
[[Category:Development]]
[[Category:Student Grants]]

Student Grants

2023-08-22T18:55:30Z

⚠️Wenzeslaus: /* Topics */ add "selected topics from past years"

GRASS GIS offers a limited number of student grants for projects related to GRASS GIS. These can include actual coding, bug fixing, or documentation and the creation of educational resources.

== Why to apply ==

You will:
* receive mentorship by experienced open-source developers;
* gain programming skills;
* be able to add open-source development into your portfolio;
* get stipend.

== Eligibility ==

To apply for a grant, a student must:
* be eighteen (18) years of age or older upon application;
* be enrolled into a post-secondary academic program, as of the beginning of the grant;
* for the duration of the grant, be eligible to work in the country in which they reside;
* and not be a [https://trac.osgeo.org/grass/wiki/PSC GRASS GIS Project Steering Committee (PSC)] member.

In addition, the student has to:
* demonstrate necessary skills and ability to contribute to GRASS GIS through a [https://github.com/OSGeo/grass/pulls GitHub pull request (PR)].

One person can be awarded one grant at a time, but can apply more than once at different times.

== Stipend ==

* The maximum per grant is 1000 USD. Proposals can be for lower amounts.
* The time to complete the grant should be maximum 3 months, but shorter projects are possible. This depends on the money requested and applicant's availability.
* Start date is flexible.
* For the 2023 deadline, GRASS GIS will offer a total of 4000 USD for stipends.

== Before you apply ==

* Express your interest in applying through the current GRASS community channels (grass-dev@osgeo.org mailing list, GitHub Discussions, or Gitter).
* Identify a topic matching your interest and skills.
* Look for ways to contribute to GRASS that are related to the selected topic (improve documentation, tests, fix bugs, etc.).
* Submit a PR.

== How to apply ==

Students should:
* write their proposals as Google Documents (or similar collaborative online document creation platform) and
* send an email to grass-grants@osgeo.org to notify of their application (with the link to the document).

The email should contain:
* proof of eligibility
** confirm you are 18 year of age or above and that you can work in the country in which you reside for the duration of the grant
** proof of student status (e.g., scanned PDF)
** link to a GRASS GIS PR or PRs (work in progress is okay at this point)

The proposal document should contain:
* applicant's name
* description of the proposed work
* timeline with activities and deliverables
* budget proposal

For timely proposals, applicants will receive feedback from the grants committee and mentors. Changes can be made to the proposal until the deadline.

For the current call, applications will be accepted until '''October 30, 2023'''.

== Approval process ==

Project proposals are evaluated by the [https://trac.osgeo.org/grass/wiki/PSC GRASS GIS Project Steering Committee] within two weeks after the deadline and a notification will be sent to successful applicants.

== Stipend payment ==

Stipend are paid in two amounts (unless stated otherwise for the specific grant):
* 50% at the beginning of the work phase
* 50% after reception and approval of the final report by the PSC

== Final report ==

The final report should be also written in the [[Student_Grants/2022|GRASS GIS wiki]] under the proposal up to two weeks after the final date planned originally. When finished, the student sends an email to [https://lists.osgeo.org/pipermail/grass-psc/ grass-psc mailing list] to announce the end of the work and share the link to the final report. The final report should include:
* A description of the state of affairs before the work
* A description of the work done

== Topics ==

The GRASS GIS community provides a list of topics highly relevant to the community. Applicants may suggest their own topics.

List of open topics:

* Improve documentation and tests for a set of tools
** includes revising text, add missing/update examples with pictures, notebook how to generate the pictures, add tests (pytest)
** requirements: Python
** $100-200 per tool (proposal should include the total amount requested and budget justification)
** list of suggested tools: r.sim.water, r.reclass, r.resample, r.resamp.filter, r.mask, r.mode, v.surf.idw, v.surf.rst, r.fillnulls, r.surf.*, …

* r.rescale - reimplement as a wrapper to r.recode (see https://github.com/OSGeo/grass/issues/1986), add tests, examples and documentation
** must include tests and documentation
** requirements: Python
** $500

* Parallelize a tool with OpenMP
** possible candidates: r.horizon, r.mapcalc, r.proj, v.surf.idw
** must include tests and benchmarks
** requirements: C, OpenMP experience
** $1000 (one tool)

* Implement ''History manager'' in GRASS GUI
** display history of executed commands and re-execute them
** requirements: Python
** $1000

* Improve d.vect.chart
** fix legend (see https://github.com/OSGeo/grass/issues/3100), update documentation, add tests
** must include documentation, examples, and basic tests
** requirements: basic C and Python
** $500

* Add JSON output to different tools in C
** r.report, r.mapsets, r.what, r.univar, r.info, v.info, r3.info
** must include tests and basic documentation
** requirements: C
** $500 for one tool (proposal should include the total amount requested and budget justification)

See selected topics from past years: [https://trac.osgeo.org/grass/wiki/GSoC/2021/JupyterAndGRASS/MiniGrant2022 Space-Time Dataset Visualization and Improved Interactive Maps for grass.jupyter], [https://trac.osgeo.org/grass/wiki/wxGUIDevelopment/RedesigningStatusbar Redesigning a map display status bar combo box into a new settings dialog]

[[Category:Community]]
[[Category:Development]]
[[Category:Student Grants]]

Student Grants

2023-08-22T18:51:11Z

⚠️Wenzeslaus: /* Topics */ improve amounts are requirements

GRASS GIS offers a limited number of student grants for projects related to GRASS GIS. These can include actual coding, bug fixing, or documentation and the creation of educational resources.

== Why to apply ==

You will:
* receive mentorship by experienced open-source developers;
* gain programming skills;
* be able to add open-source development into your portfolio;
* get stipend.

== Eligibility ==

To apply for a grant, a student must:
* be eighteen (18) years of age or older upon application;
* be enrolled into a post-secondary academic program, as of the beginning of the grant;
* for the duration of the grant, be eligible to work in the country in which they reside;
* and not be a [https://trac.osgeo.org/grass/wiki/PSC GRASS GIS Project Steering Committee (PSC)] member.

In addition, the student has to:
* demonstrate necessary skills and ability to contribute to GRASS GIS through a [https://github.com/OSGeo/grass/pulls GitHub pull request (PR)].

One person can be awarded one grant at a time, but can apply more than once at different times.

== Stipend ==

* The maximum per grant is 1000 USD. Proposals can be for lower amounts.
* The time to complete the grant should be maximum 3 months, but shorter projects are possible. This depends on the money requested and applicant's availability.
* Start date is flexible.
* For the 2023 deadline, GRASS GIS will offer a total of 4000 USD for stipends.

== Before you apply ==

* Express your interest in applying through the current GRASS community channels (grass-dev@osgeo.org mailing list, GitHub Discussions, or Gitter).
* Identify a topic matching your interest and skills.
* Look for ways to contribute to GRASS that are related to the selected topic (improve documentation, tests, fix bugs, etc.).
* Submit a PR.

== How to apply ==

Students should:
* write their proposals as Google Documents (or similar collaborative online document creation platform) and
* send an email to grass-grants@osgeo.org to notify of their application (with the link to the document).

The email should contain:
* proof of eligibility
** confirm you are 18 year of age or above and that you can work in the country in which you reside for the duration of the grant
** proof of student status (e.g., scanned PDF)
** link to a GRASS GIS PR or PRs (work in progress is okay at this point)

The proposal document should contain:
* applicant's name
* description of the proposed work
* timeline with activities and deliverables
* budget proposal

For timely proposals, applicants will receive feedback from the grants committee and mentors. Changes can be made to the proposal until the deadline.

For the current call, applications will be accepted until '''October 30, 2023'''.

== Approval process ==

Project proposals are evaluated by the [https://trac.osgeo.org/grass/wiki/PSC GRASS GIS Project Steering Committee] within two weeks after the deadline and a notification will be sent to successful applicants.

== Stipend payment ==

Stipend are paid in two amounts (unless stated otherwise for the specific grant):
* 50% at the beginning of the work phase
* 50% after reception and approval of the final report by the PSC

== Final report ==

The final report should be also written in the [[Student_Grants/2022|GRASS GIS wiki]] under the proposal up to two weeks after the final date planned originally. When finished, the student sends an email to [https://lists.osgeo.org/pipermail/grass-psc/ grass-psc mailing list] to announce the end of the work and share the link to the final report. The final report should include:
* A description of the state of affairs before the work
* A description of the work done

== Topics ==

The GRASS GIS community provides a list of topics highly relevant to the community. Applicants may come up with their own topics. Relevance of the topic to the project will be evaluated individually. Topics contributing to the core GRASS project are usually more relevant than others.

List of open topics:

* Improve documentation and tests for a set of tools
** includes revising text, add missing/update examples with pictures, notebook how to generate the pictures, add tests (pytest)
** requirements: Python
** $100-200 per tool (proposal should include the total amount requested and budget justification)
** list of suggested tools: r.sim.water, r.reclass, r.resample, r.resamp.filter, r.mask, r.mode, v.surf.idw, v.surf.rst, r.fillnulls, r.surf.*, …

* r.rescale - reimplement as a wrapper to r.recode (see https://github.com/OSGeo/grass/issues/1986), add tests, examples and documentation
** must include tests and documentation
** requirements: Python
** $500

* Parallelize a tool with OpenMP
** possible candidates: r.horizon, r.mapcalc, r.proj, v.surf.idw
** must include tests and benchmarks
** requirements: C, OpenMP experience
** $1000 (one tool)

* Implement ''History manager'' in GRASS GUI
** display history of executed commands and re-execute them
** requirements: Python
** $1000

* Improve d.vect.chart
** fix legend (see https://github.com/OSGeo/grass/issues/3100), update documentation, add tests
** must include documentation, examples, and basic tests
** requirements: basic C and Python
** $500

* Add JSON output to different tools in C
** r.report, r.mapsets, r.what, r.univar, r.info, v.info, r3.info
** must include tests and basic documentation
** requirements: C
** $500 for one tool (proposal should include the total amount requested and budget justification)

[[Category:Community]]
[[Category:Development]]
[[Category:Student Grants]]

Student Grants

2023-08-22T18:38:54Z

⚠️Wenzeslaus: /* Grant payment */ rename to Stipend (Google uses "Contributor Stipends")

GRASS GIS offers a limited number of student grants for projects related to GRASS GIS. These can include actual coding, bug fixing, or documentation and the creation of educational resources.

== Why to apply ==

You will:
* receive mentorship by experienced open-source developers;
* gain programming skills;
* be able to add open-source development into your portfolio;
* get stipend.

== Eligibility ==

To apply for a grant, a student must:
* be eighteen (18) years of age or older upon application;
* be enrolled into a post-secondary academic program, as of the beginning of the grant;
* for the duration of the grant, be eligible to work in the country in which they reside;
* and not be a [https://trac.osgeo.org/grass/wiki/PSC GRASS GIS Project Steering Committee (PSC)] member.

In addition, the student has to:
* demonstrate necessary skills and ability to contribute to GRASS GIS through a [https://github.com/OSGeo/grass/pulls GitHub pull request (PR)].

One person can be awarded one grant at a time, but can apply more than once at different times.

== Stipend ==

* The maximum per grant is 1000 USD. Proposals can be for lower amounts.
* The time to complete the grant should be maximum 3 months, but shorter projects are possible. This depends on the money requested and applicant's availability.
* Start date is flexible.
* For the 2023 deadline, GRASS GIS will offer a total of 4000 USD for stipends.

== Before you apply ==

* Express your interest in applying through the current GRASS community channels (grass-dev@osgeo.org mailing list, GitHub Discussions, or Gitter).
* Identify a topic matching your interest and skills.
* Look for ways to contribute to GRASS that are related to the selected topic (improve documentation, tests, fix bugs, etc.).
* Submit a PR.

== How to apply ==

Students should:
* write their proposals as Google Documents (or similar collaborative online document creation platform) and
* send an email to grass-grants@osgeo.org to notify of their application (with the link to the document).

The email should contain:
* proof of eligibility
** confirm you are 18 year of age or above and that you can work in the country in which you reside for the duration of the grant
** proof of student status (e.g., scanned PDF)
** link to a GRASS GIS PR or PRs (work in progress is okay at this point)

The proposal document should contain:
* applicant's name
* description of the proposed work
* timeline with activities and deliverables
* budget proposal

For timely proposals, applicants will receive feedback from the grants committee and mentors. Changes can be made to the proposal until the deadline.

For the current call, applications will be accepted until '''October 30, 2023'''.

== Approval process ==

Project proposals are evaluated by the [https://trac.osgeo.org/grass/wiki/PSC GRASS GIS Project Steering Committee] within two weeks after the deadline and a notification will be sent to successful applicants.

== Stipend payment ==

Stipend are paid in two amounts (unless stated otherwise for the specific grant):
* 50% at the beginning of the work phase
* 50% after reception and approval of the final report by the PSC

== Final report ==

The final report should be also written in the [[Student_Grants/2022|GRASS GIS wiki]] under the proposal up to two weeks after the final date planned originally. When finished, the student sends an email to [https://lists.osgeo.org/pipermail/grass-psc/ grass-psc mailing list] to announce the end of the work and share the link to the final report. The final report should include:
* A description of the state of affairs before the work
* A description of the work done

== Topics ==

The GRASS GIS community provides a list of topics highly relevant to the community. Applicants may come up with their own topics. Relevance of the topic to the project will be evaluated individually. Topics contributing to the core GRASS project are usually more relevant than others.

List of open topics:

* Improve documentation and tests for a set of tools
** includes revising text, add missing/update examples with pictures, notebook how to generate the pictures, add tests (pytest)
** requirements: Python
** $100-200 per tool
** list of suggested tools: r.sim.water, r.reclass, r.resample, r.resamp.filter, r.mask, r.mode, v.surf.idw, v.surf.rst, r.fillnulls, r.surf.*, …

* r.rescale - reimplement as a wrapper to r.recode (see https://github.com/OSGeo/grass/issues/1986), add tests, examples and documentation
** requirements: Python
** $500

* Parallelize a tool with OpenMP
** possible candidates: r.horizon, r.mapcalc, r.proj, v.surf.idw
** requirements: C, OpenMP experience
** $1000 (one tool)

* Implement ''History manager'' in GRASS GUI
** display history of executed commands and re-execute them
** requirements: Python
** $1000

* Improve d.vect.chart
** fix legend (see https://github.com/OSGeo/grass/issues/3100), update documentation, add tests
** requirements: basic C and Python
** $500

* Add JSON output to different tools
** r.report, r.mapsets, r.what, r.univar, r.info, v.info, r3.info
** requirements: C
** $500 for 1

[[Category:Community]]
[[Category:Development]]
[[Category:Student Grants]]

Student Grants

2023-08-22T18:37:58Z

⚠️Wenzeslaus: /* How to apply */ Restructure to modify the proposal after submission and more clearly specify the eligibility proofs, remove required mentor (identified later, not by the student)

GRASS GIS offers a limited number of student grants for projects related to GRASS GIS. These can include actual coding, bug fixing, or documentation and the creation of educational resources.

== Why to apply ==

You will:
* receive mentorship by experienced open-source developers;
* gain programming skills;
* be able to add open-source development into your portfolio;
* get stipend.

== Eligibility ==

To apply for a grant, a student must:
* be eighteen (18) years of age or older upon application;
* be enrolled into a post-secondary academic program, as of the beginning of the grant;
* for the duration of the grant, be eligible to work in the country in which they reside;
* and not be a [https://trac.osgeo.org/grass/wiki/PSC GRASS GIS Project Steering Committee (PSC)] member.

In addition, the student has to:
* demonstrate necessary skills and ability to contribute to GRASS GIS through a [https://github.com/OSGeo/grass/pulls GitHub pull request (PR)].

One person can be awarded one grant at a time, but can apply more than once at different times.

== Stipend ==

* The maximum per grant is 1000 USD. Proposals can be for lower amounts.
* The time to complete the grant should be maximum 3 months, but shorter projects are possible. This depends on the money requested and applicant's availability.
* Start date is flexible.
* For the 2023 deadline, GRASS GIS will offer a total of 4000 USD for stipends.

== Before you apply ==

* Express your interest in applying through the current GRASS community channels (grass-dev@osgeo.org mailing list, GitHub Discussions, or Gitter).
* Identify a topic matching your interest and skills.
* Look for ways to contribute to GRASS that are related to the selected topic (improve documentation, tests, fix bugs, etc.).
* Submit a PR.

== How to apply ==

Students should:
* write their proposals as Google Documents (or similar collaborative online document creation platform) and
* send an email to grass-grants@osgeo.org to notify of their application (with the link to the document).

The email should contain:
* proof of eligibility
** confirm you are 18 year of age or above and that you can work in the country in which you reside for the duration of the grant
** proof of student status (e.g., scanned PDF)
** link to a GRASS GIS PR or PRs (work in progress is okay at this point)

The proposal document should contain:
* applicant's name
* description of the proposed work
* timeline with activities and deliverables
* budget proposal

For timely proposals, applicants will receive feedback from the grants committee and mentors. Changes can be made to the proposal until the deadline.

For the current call, applications will be accepted until '''October 30, 2023'''.

== Approval process ==

Project proposals are evaluated by the [https://trac.osgeo.org/grass/wiki/PSC GRASS GIS Project Steering Committee] within two weeks after the deadline and a notification will be sent to successful applicants.

== Grant payment ==

Grants are paid in two amounts (unless stated otherwise for the specific grant):
* 50% at the beginning of the work phase
* 50% after reception and approval of the final report by the PSC

== Final report ==

The final report should be also written in the [[Student_Grants/2022|GRASS GIS wiki]] under the proposal up to two weeks after the final date planned originally. When finished, the student sends an email to [https://lists.osgeo.org/pipermail/grass-psc/ grass-psc mailing list] to announce the end of the work and share the link to the final report. The final report should include:
* A description of the state of affairs before the work
* A description of the work done

== Topics ==

The GRASS GIS community provides a list of topics highly relevant to the community. Applicants may come up with their own topics. Relevance of the topic to the project will be evaluated individually. Topics contributing to the core GRASS project are usually more relevant than others.

List of open topics:

* Improve documentation and tests for a set of tools
** includes revising text, add missing/update examples with pictures, notebook how to generate the pictures, add tests (pytest)
** requirements: Python
** $100-200 per tool
** list of suggested tools: r.sim.water, r.reclass, r.resample, r.resamp.filter, r.mask, r.mode, v.surf.idw, v.surf.rst, r.fillnulls, r.surf.*, …

* r.rescale - reimplement as a wrapper to r.recode (see https://github.com/OSGeo/grass/issues/1986), add tests, examples and documentation
** requirements: Python
** $500

* Parallelize a tool with OpenMP
** possible candidates: r.horizon, r.mapcalc, r.proj, v.surf.idw
** requirements: C, OpenMP experience
** $1000 (one tool)

* Implement ''History manager'' in GRASS GUI
** display history of executed commands and re-execute them
** requirements: Python
** $1000

* Improve d.vect.chart
** fix legend (see https://github.com/OSGeo/grass/issues/3100), update documentation, add tests
** requirements: basic C and Python
** $500

* Add JSON output to different tools
** r.report, r.mapsets, r.what, r.univar, r.info, v.info, r3.info
** requirements: C
** $500 for 1

[[Category:Community]]
[[Category:Development]]
[[Category:Student Grants]]

Student Grants

2023-08-22T18:36:40Z

⚠️Wenzeslaus: /* Before you apply */

GRASS GIS offers a limited number of student grants for projects related to GRASS GIS. These can include actual coding, bug fixing, or documentation and the creation of educational resources.

== Why to apply ==

You will:
* receive mentorship by experienced open-source developers;
* gain programming skills;
* be able to add open-source development into your portfolio;
* get stipend.

== Eligibility ==

To apply for a grant, a student must:
* be eighteen (18) years of age or older upon application;
* be enrolled into a post-secondary academic program, as of the beginning of the grant;
* for the duration of the grant, be eligible to work in the country in which they reside;
* and not be a [https://trac.osgeo.org/grass/wiki/PSC GRASS GIS Project Steering Committee (PSC)] member.

In addition, the student has to:
* demonstrate necessary skills and ability to contribute to GRASS GIS through a [https://github.com/OSGeo/grass/pulls GitHub pull request (PR)].

One person can be awarded one grant at a time, but can apply more than once at different times.

== Stipend ==

* The maximum per grant is 1000 USD. Proposals can be for lower amounts.
* The time to complete the grant should be maximum 3 months, but shorter projects are possible. This depends on the money requested and applicant's availability.
* Start date is flexible.
* For the 2023 deadline, GRASS GIS will offer a total of 4000 USD for stipends.

== Before you apply ==

* Express your interest in applying through the current GRASS community channels (grass-dev@osgeo.org mailing list, GitHub Discussions, or Gitter).
* Identify a topic matching your interest and skills.
* Look for ways to contribute to GRASS that are related to the selected topic (improve documentation, tests, fix bugs, etc.).
* Submit a PR.

== How to apply ==

Students should submit their proposals through the [[Student_Grants/2022|GRASS GIS wiki]] and send an email to grass-grants@osgeo.org to notify of their application (i.e., link to the wiki page with the proposal). See [[Student Grants/2021|here]] for a previous round.
The email should contain:
* proof of eligibility (age, student status, link to accepted GRASS GIS PR, mail by active community member confirming mentorship)
The wiki page should contain:
* applicant's name
* a description of the proposed work
* a calendar of activities and deliverables
* a budget proposal

For the current call, applications will be accepted until '''October 30, 2023'''.

== Approval process ==

Project proposals are evaluated by the [https://trac.osgeo.org/grass/wiki/PSC GRASS GIS Project Steering Committee] within two weeks after the deadline and a notification will be sent to successful applicants.

== Grant payment ==

Grants are paid in two amounts (unless stated otherwise for the specific grant):
* 50% at the beginning of the work phase
* 50% after reception and approval of the final report by the PSC

== Final report ==

The final report should be also written in the [[Student_Grants/2022|GRASS GIS wiki]] under the proposal up to two weeks after the final date planned originally. When finished, the student sends an email to [https://lists.osgeo.org/pipermail/grass-psc/ grass-psc mailing list] to announce the end of the work and share the link to the final report. The final report should include:
* A description of the state of affairs before the work
* A description of the work done

== Topics ==

The GRASS GIS community provides a list of topics highly relevant to the community. Applicants may come up with their own topics. Relevance of the topic to the project will be evaluated individually. Topics contributing to the core GRASS project are usually more relevant than others.

List of open topics:

* Improve documentation and tests for a set of tools
** includes revising text, add missing/update examples with pictures, notebook how to generate the pictures, add tests (pytest)
** requirements: Python
** $100-200 per tool
** list of suggested tools: r.sim.water, r.reclass, r.resample, r.resamp.filter, r.mask, r.mode, v.surf.idw, v.surf.rst, r.fillnulls, r.surf.*, …

* r.rescale - reimplement as a wrapper to r.recode (see https://github.com/OSGeo/grass/issues/1986), add tests, examples and documentation
** requirements: Python
** $500

* Parallelize a tool with OpenMP
** possible candidates: r.horizon, r.mapcalc, r.proj, v.surf.idw
** requirements: C, OpenMP experience
** $1000 (one tool)

* Implement ''History manager'' in GRASS GUI
** display history of executed commands and re-execute them
** requirements: Python
** $1000

* Improve d.vect.chart
** fix legend (see https://github.com/OSGeo/grass/issues/3100), update documentation, add tests
** requirements: basic C and Python
** $500

* Add JSON output to different tools
** r.report, r.mapsets, r.what, r.univar, r.info, v.info, r3.info
** requirements: C
** $500 for 1

[[Category:Community]]
[[Category:Development]]
[[Category:Student Grants]]

Student Grants

2023-08-22T18:36:26Z

⚠️Wenzeslaus: /* Before you apply */

GRASS GIS offers a limited number of student grants for projects related to GRASS GIS. These can include actual coding, bug fixing, or documentation and the creation of educational resources.

== Why to apply ==

You will:
* receive mentorship by experienced open-source developers;
* gain programming skills;
* be able to add open-source development into your portfolio;
* get stipend.

== Eligibility ==

To apply for a grant, a student must:
* be eighteen (18) years of age or older upon application;
* be enrolled into a post-secondary academic program, as of the beginning of the grant;
* for the duration of the grant, be eligible to work in the country in which they reside;
* and not be a [https://trac.osgeo.org/grass/wiki/PSC GRASS GIS Project Steering Committee (PSC)] member.

In addition, the student has to:
* demonstrate necessary skills and ability to contribute to GRASS GIS through a [https://github.com/OSGeo/grass/pulls GitHub pull request (PR)].

One person can be awarded one grant at a time, but can apply more than once at different times.

== Stipend ==

* The maximum per grant is 1000 USD. Proposals can be for lower amounts.
* The time to complete the grant should be maximum 3 months, but shorter projects are possible. This depends on the money requested and applicant's availability.
* Start date is flexible.
* For the 2023 deadline, GRASS GIS will offer a total of 4000 USD for stipends.

== Before you apply ==

* Express your interest in applying through the current GRASS community channels (grass-dev@osgeo.org mailing list, GitHub Discussions, or Gitter).
* Identify a topic matching your interest and skills.
* Look for ways to contribute to GRASS that are related to the selected topic (improve documentation, tests, fix bugs, etc.)
* Submit a PR.

== How to apply ==

Students should submit their proposals through the [[Student_Grants/2022|GRASS GIS wiki]] and send an email to grass-grants@osgeo.org to notify of their application (i.e., link to the wiki page with the proposal). See [[Student Grants/2021|here]] for a previous round.
The email should contain:
* proof of eligibility (age, student status, link to accepted GRASS GIS PR, mail by active community member confirming mentorship)
The wiki page should contain:
* applicant's name
* a description of the proposed work
* a calendar of activities and deliverables
* a budget proposal

For the current call, applications will be accepted until '''October 30, 2023'''.

== Approval process ==

Project proposals are evaluated by the [https://trac.osgeo.org/grass/wiki/PSC GRASS GIS Project Steering Committee] within two weeks after the deadline and a notification will be sent to successful applicants.

== Grant payment ==

Grants are paid in two amounts (unless stated otherwise for the specific grant):
* 50% at the beginning of the work phase
* 50% after reception and approval of the final report by the PSC

== Final report ==

The final report should be also written in the [[Student_Grants/2022|GRASS GIS wiki]] under the proposal up to two weeks after the final date planned originally. When finished, the student sends an email to [https://lists.osgeo.org/pipermail/grass-psc/ grass-psc mailing list] to announce the end of the work and share the link to the final report. The final report should include:
* A description of the state of affairs before the work
* A description of the work done

== Topics ==

The GRASS GIS community provides a list of topics highly relevant to the community. Applicants may come up with their own topics. Relevance of the topic to the project will be evaluated individually. Topics contributing to the core GRASS project are usually more relevant than others.

List of open topics:

* Improve documentation and tests for a set of tools
** includes revising text, add missing/update examples with pictures, notebook how to generate the pictures, add tests (pytest)
** requirements: Python
** $100-200 per tool
** list of suggested tools: r.sim.water, r.reclass, r.resample, r.resamp.filter, r.mask, r.mode, v.surf.idw, v.surf.rst, r.fillnulls, r.surf.*, …

* r.rescale - reimplement as a wrapper to r.recode (see https://github.com/OSGeo/grass/issues/1986), add tests, examples and documentation
** requirements: Python
** $500

* Parallelize a tool with OpenMP
** possible candidates: r.horizon, r.mapcalc, r.proj, v.surf.idw
** requirements: C, OpenMP experience
** $1000 (one tool)

* Implement ''History manager'' in GRASS GUI
** display history of executed commands and re-execute them
** requirements: Python
** $1000

* Improve d.vect.chart
** fix legend (see https://github.com/OSGeo/grass/issues/3100), update documentation, add tests
** requirements: basic C and Python
** $500

* Add JSON output to different tools
** r.report, r.mapsets, r.what, r.univar, r.info, v.info, r3.info
** requirements: C
** $500 for 1

[[Category:Community]]
[[Category:Development]]
[[Category:Student Grants]]

Student Grants

2023-08-22T18:28:48Z

⚠️Wenzeslaus: /* Stipend */ Make it 3 months max because 2 are too short for student timing

GRASS GIS offers a limited number of student grants for projects related to GRASS GIS. These can include actual coding, bug fixing, or documentation and the creation of educational resources.

== Why to apply ==

You will:
* receive mentorship by experienced open-source developers;
* gain programming skills;
* be able to add open-source development into your portfolio;
* get stipend.

== Eligibility ==

To apply for a grant, a student must:
* be eighteen (18) years of age or older upon application;
* be enrolled into a post-secondary academic program, as of the beginning of the grant;
* for the duration of the grant, be eligible to work in the country in which they reside;
* and not be a [https://trac.osgeo.org/grass/wiki/PSC GRASS GIS Project Steering Committee (PSC)] member.

In addition, the student has to:
* demonstrate necessary skills and ability to contribute to GRASS GIS through a [https://github.com/OSGeo/grass/pulls GitHub pull request (PR)].

One person can be awarded one grant at a time, but can apply more than once at different times.

== Stipend ==

* The maximum per grant is 1000 USD. Proposals can be for lower amounts.
* The time to complete the grant should be maximum 3 months, but shorter projects are possible. This depends on the money requested and applicant's availability.
* Start date is flexible.
* For the 2023 deadline, GRASS GIS will offer a total of 4000 USD for stipends.

== Before you apply ==

== How to apply ==

Students should submit their proposals through the [[Student_Grants/2022|GRASS GIS wiki]] and send an email to grass-grants@osgeo.org to notify of their application (i.e., link to the wiki page with the proposal). See [[Student Grants/2021|here]] for a previous round.
The email should contain:
* proof of eligibility (age, student status, link to accepted GRASS GIS PR, mail by active community member confirming mentorship)
The wiki page should contain:
* applicant's name
* a description of the proposed work
* a calendar of activities and deliverables
* a budget proposal

For the current call, applications will be accepted until '''October 30, 2023'''.

== Approval process ==

Project proposals are evaluated by the [https://trac.osgeo.org/grass/wiki/PSC GRASS GIS Project Steering Committee] within two weeks after the deadline and a notification will be sent to successful applicants.

== Grant payment ==

Grants are paid in two amounts (unless stated otherwise for the specific grant):
* 50% at the beginning of the work phase
* 50% after reception and approval of the final report by the PSC

== Final report ==

The final report should be also written in the [[Student_Grants/2022|GRASS GIS wiki]] under the proposal up to two weeks after the final date planned originally. When finished, the student sends an email to [https://lists.osgeo.org/pipermail/grass-psc/ grass-psc mailing list] to announce the end of the work and share the link to the final report. The final report should include:
* A description of the state of affairs before the work
* A description of the work done

== Topics ==

The GRASS GIS community provides a list of topics highly relevant to the community. Applicants may come up with their own topics. Relevance of the topic to the project will be evaluated individually. Topics contributing to the core GRASS project are usually more relevant than others.

List of open topics:

* Improve documentation and tests for a set of tools
** includes revising text, add missing/update examples with pictures, notebook how to generate the pictures, add tests (pytest)
** requirements: Python
** $100-200 per tool
** list of suggested tools: r.sim.water, r.reclass, r.resample, r.resamp.filter, r.mask, r.mode, v.surf.idw, v.surf.rst, r.fillnulls, r.surf.*, …

* r.rescale - reimplement as a wrapper to r.recode (see https://github.com/OSGeo/grass/issues/1986), add tests, examples and documentation
** requirements: Python
** $500

* Parallelize a tool with OpenMP
** possible candidates: r.horizon, r.mapcalc, r.proj, v.surf.idw
** requirements: C, OpenMP experience
** $1000 (one tool)

* Implement ''History manager'' in GRASS GUI
** display history of executed commands and re-execute them
** requirements: Python
** $1000

* Improve d.vect.chart
** fix legend (see https://github.com/OSGeo/grass/issues/3100), update documentation, add tests
** requirements: basic C and Python
** $500

* Add JSON output to different tools
** r.report, r.mapsets, r.what, r.univar, r.info, v.info, r3.info
** requirements: C
** $500 for 1

[[Category:Community]]
[[Category:Development]]
[[Category:Student Grants]]

Student Grants

2023-08-22T18:28:10Z

⚠️Wenzeslaus: Add Why to apply and Before you apply, restucture Nature of Grant to Stipend, make it 3 instead of 2 m max

GRASS GIS offers a limited number of student grants for projects related to GRASS GIS. These can include actual coding, bug fixing, or documentation and the creation of educational resources.

== Why to apply ==

You will:
* receive mentorship by experienced open-source developers;
* gain programming skills;
* be able to add open-source development into your portfolio;
* get stipend.

== Eligibility ==

To apply for a grant, a student must:
* be eighteen (18) years of age or older upon application;
* be enrolled into a post-secondary academic program, as of the beginning of the grant;
* for the duration of the grant, be eligible to work in the country in which they reside;
* and not be a [https://trac.osgeo.org/grass/wiki/PSC GRASS GIS Project Steering Committee (PSC)] member.

In addition, the student has to:
* demonstrate necessary skills and ability to contribute to GRASS GIS through a [https://github.com/OSGeo/grass/pulls GitHub pull request (PR)].

One person can be awarded one grant at a time, but can apply more than once at different times.

== Stipend ==

* The maximum per grant is 1000 USD. Proposals can be for lower amounts.
* The time to complete the grant should be maximum 2 months, but shorter projects are possible. This depends on the money requested and applicant's availability.
* Start date is flexible.
* For the 2023 deadline, GRASS GIS will offer a total of 4000 USD for stipends.

== Before you apply ==

== How to apply ==

Students should submit their proposals through the [[Student_Grants/2022|GRASS GIS wiki]] and send an email to grass-grants@osgeo.org to notify of their application (i.e., link to the wiki page with the proposal). See [[Student Grants/2021|here]] for a previous round.
The email should contain:
* proof of eligibility (age, student status, link to accepted GRASS GIS PR, mail by active community member confirming mentorship)
The wiki page should contain:
* applicant's name
* a description of the proposed work
* a calendar of activities and deliverables
* a budget proposal

For the current call, applications will be accepted until '''October 30, 2023'''.

== Approval process ==

Project proposals are evaluated by the [https://trac.osgeo.org/grass/wiki/PSC GRASS GIS Project Steering Committee] within two weeks after the deadline and a notification will be sent to successful applicants.

== Grant payment ==

Grants are paid in two amounts (unless stated otherwise for the specific grant):
* 50% at the beginning of the work phase
* 50% after reception and approval of the final report by the PSC

== Final report ==

The final report should be also written in the [[Student_Grants/2022|GRASS GIS wiki]] under the proposal up to two weeks after the final date planned originally. When finished, the student sends an email to [https://lists.osgeo.org/pipermail/grass-psc/ grass-psc mailing list] to announce the end of the work and share the link to the final report. The final report should include:
* A description of the state of affairs before the work
* A description of the work done

== Topics ==

The GRASS GIS community provides a list of topics highly relevant to the community. Applicants may come up with their own topics. Relevance of the topic to the project will be evaluated individually. Topics contributing to the core GRASS project are usually more relevant than others.

List of open topics:

* Improve documentation and tests for a set of tools
** includes revising text, add missing/update examples with pictures, notebook how to generate the pictures, add tests (pytest)
** requirements: Python
** $100-200 per tool
** list of suggested tools: r.sim.water, r.reclass, r.resample, r.resamp.filter, r.mask, r.mode, v.surf.idw, v.surf.rst, r.fillnulls, r.surf.*, …

* r.rescale - reimplement as a wrapper to r.recode (see https://github.com/OSGeo/grass/issues/1986), add tests, examples and documentation
** requirements: Python
** $500

* Parallelize a tool with OpenMP
** possible candidates: r.horizon, r.mapcalc, r.proj, v.surf.idw
** requirements: C, OpenMP experience
** $1000 (one tool)

* Implement ''History manager'' in GRASS GUI
** display history of executed commands and re-execute them
** requirements: Python
** $1000

* Improve d.vect.chart
** fix legend (see https://github.com/OSGeo/grass/issues/3100), update documentation, add tests
** requirements: basic C and Python
** $500

* Add JSON output to different tools
** r.report, r.mapsets, r.what, r.univar, r.info, v.info, r3.info
** requirements: C
** $500 for 1

[[Category:Community]]
[[Category:Development]]
[[Category:Student Grants]]

Student Grants

2023-08-22T18:09:31Z

⚠️Wenzeslaus: /* Eligibility */

GRASS GIS offers a limited number of student grants for projects related to GRASS GIS. These can include actual coding, bug fixing, or documentation and the creation of educational resources.

== Eligibility ==

To apply for a grant, a student must:
* be eighteen (18) years of age or older upon application;
* be enrolled into a post-secondary academic program, as of the beginning of the grant;
* for the duration of the grant, be eligible to work in the country in which they reside;
* and not be a [https://trac.osgeo.org/grass/wiki/PSC GRASS GIS Project Steering Committee (PSC)] member.

In addition, the student has to:
* demonstrate necessary skills and ability to contribute to GRASS GIS through a [https://github.com/OSGeo/grass/pulls GitHub pull request (PR)].

== Nature of the grant ==

* '''In 2023, GRASS GIS will offer a total of 4000 USD for grants'''.
* The maximum per grant is 1000 USD. Grant requests can be for lower amounts.
* One person can be awarded one grant at a time, but can apply more than once at different times.
* The time to complete the work should be maximum 2 months, but much shorter projects are clearly possible. It will mostly depend on the student's availability.

== How to apply ==

Students should submit their proposals through the [[Student_Grants/2022|GRASS GIS wiki]] and send an email to grass-grants@osgeo.org to notify of their application (i.e., link to the wiki page with the proposal). See [[Student Grants/2021|here]] for a previous round.
The email should contain:
* proof of eligibility (age, student status, link to accepted GRASS GIS PR, mail by active community member confirming mentorship)
The wiki page should contain:
* applicant's name
* a description of the proposed work
* a calendar of activities and deliverables
* a budget proposal

For the current call, applications will be accepted until '''October 30, 2023'''.

== Approval process ==

Project proposals are evaluated by the [https://trac.osgeo.org/grass/wiki/PSC GRASS GIS Project Steering Committee] within two weeks after the deadline and a notification will be sent to successful applicants.

== Grant payment ==

Grants are paid in two amounts (unless stated otherwise for the specific grant):
* 50% at the beginning of the work phase
* 50% after reception and approval of the final report by the PSC

== Final report ==

The final report should be also written in the [[Student_Grants/2022|GRASS GIS wiki]] under the proposal up to two weeks after the final date planned originally. When finished, the student sends an email to [https://lists.osgeo.org/pipermail/grass-psc/ grass-psc mailing list] to announce the end of the work and share the link to the final report. The final report should include:
* A description of the state of affairs before the work
* A description of the work done

== Topics ==

The GRASS GIS community provides a list of topics highly relevant to the community. Applicants may come up with their own topics. Relevance of the topic to the project will be evaluated individually. Topics contributing to the core GRASS project are usually more relevant than others.

List of open topics:

* Improve documentation and tests for a set of tools
** includes revising text, add missing/update examples with pictures, notebook how to generate the pictures, add tests (pytest)
** requirements: Python
** $100-200 per tool
** list of suggested tools: r.sim.water, r.reclass, r.resample, r.resamp.filter, r.mask, r.mode, v.surf.idw, v.surf.rst, r.fillnulls, r.surf.*, …

* r.rescale - reimplement as a wrapper to r.recode (see https://github.com/OSGeo/grass/issues/1986), add tests, examples and documentation
** requirements: Python
** $500

* Parallelize a tool with OpenMP
** possible candidates: r.horizon, r.mapcalc, r.proj, v.surf.idw
** requirements: C, OpenMP experience
** $1000 (one tool)

* Implement ''History manager'' in GRASS GUI
** display history of executed commands and re-execute them
** requirements: Python
** $1000

* Improve d.vect.chart
** fix legend (see https://github.com/OSGeo/grass/issues/3100), update documentation, add tests
** requirements: basic C and Python
** $500

* Add JSON output to different tools
** r.report, r.mapsets, r.what, r.univar, r.info, v.info, r3.info
** requirements: C
** $500 for 1

[[Category:Community]]
[[Category:Development]]
[[Category:Student Grants]]

Student Grants

2023-08-22T18:09:02Z

⚠️Wenzeslaus: /* Additional criteria */ Additional criteria were just saying there are no restrictions and that better contribution record is a stronger proof of "demonstrated ability to contribute to GRASS GIS"

GRASS GIS offers a limited number of student grants for projects related to GRASS GIS. These can include actual coding, bug fixing, or documentation and the creation of educational resources.

== Eligibility ==

To apply for a grant, a student must:
* be eighteen (18) years of age or older upon application;
* be enrolled into a post-secondary academic program, as of the beginning of the grant;
* for the duration of the grant, be eligible to work in the country in which they reside;
* and not be a [https://trac.osgeo.org/grass/wiki/PSC GRASS GIS Project Steering Committee (PSC)] member.

In addition, the student has to:
* demonstrate ability to contribute to GRASS GIS through a [https://github.com/OSGeo/grass/pulls GitHub pull request (PR)].

== Nature of the grant ==

* '''In 2023, GRASS GIS will offer a total of 4000 USD for grants'''.
* The maximum per grant is 1000 USD. Grant requests can be for lower amounts.
* One person can be awarded one grant at a time, but can apply more than once at different times.
* The time to complete the work should be maximum 2 months, but much shorter projects are clearly possible. It will mostly depend on the student's availability.

== How to apply ==

Students should submit their proposals through the [[Student_Grants/2022|GRASS GIS wiki]] and send an email to grass-grants@osgeo.org to notify of their application (i.e., link to the wiki page with the proposal). See [[Student Grants/2021|here]] for a previous round.
The email should contain:
* proof of eligibility (age, student status, link to accepted GRASS GIS PR, mail by active community member confirming mentorship)
The wiki page should contain:
* applicant's name
* a description of the proposed work
* a calendar of activities and deliverables
* a budget proposal

For the current call, applications will be accepted until '''October 30, 2023'''.

== Approval process ==

Project proposals are evaluated by the [https://trac.osgeo.org/grass/wiki/PSC GRASS GIS Project Steering Committee] within two weeks after the deadline and a notification will be sent to successful applicants.

== Grant payment ==

Grants are paid in two amounts (unless stated otherwise for the specific grant):
* 50% at the beginning of the work phase
* 50% after reception and approval of the final report by the PSC

== Final report ==

The final report should be also written in the [[Student_Grants/2022|GRASS GIS wiki]] under the proposal up to two weeks after the final date planned originally. When finished, the student sends an email to [https://lists.osgeo.org/pipermail/grass-psc/ grass-psc mailing list] to announce the end of the work and share the link to the final report. The final report should include:
* A description of the state of affairs before the work
* A description of the work done

== Topics ==

The GRASS GIS community provides a list of topics highly relevant to the community. Applicants may come up with their own topics. Relevance of the topic to the project will be evaluated individually. Topics contributing to the core GRASS project are usually more relevant than others.

List of open topics:

* Improve documentation and tests for a set of tools
** includes revising text, add missing/update examples with pictures, notebook how to generate the pictures, add tests (pytest)
** requirements: Python
** $100-200 per tool
** list of suggested tools: r.sim.water, r.reclass, r.resample, r.resamp.filter, r.mask, r.mode, v.surf.idw, v.surf.rst, r.fillnulls, r.surf.*, …

* r.rescale - reimplement as a wrapper to r.recode (see https://github.com/OSGeo/grass/issues/1986), add tests, examples and documentation
** requirements: Python
** $500

* Parallelize a tool with OpenMP
** possible candidates: r.horizon, r.mapcalc, r.proj, v.surf.idw
** requirements: C, OpenMP experience
** $1000 (one tool)

* Implement ''History manager'' in GRASS GUI
** display history of executed commands and re-execute them
** requirements: Python
** $1000

* Improve d.vect.chart
** fix legend (see https://github.com/OSGeo/grass/issues/3100), update documentation, add tests
** requirements: basic C and Python
** $500

* Add JSON output to different tools
** r.report, r.mapsets, r.what, r.univar, r.info, v.info, r3.info
** requirements: C
** $500 for 1

[[Category:Community]]
[[Category:Development]]
[[Category:Student Grants]]

Student Grants

2023-08-22T17:59:34Z

⚠️Wenzeslaus: /* Eligibility */ Mentor is not up to the student to find, but up to the community to provide

GRASS GIS offers a limited number of student grants for projects related to GRASS GIS. These can include actual coding, bug fixing, or documentation and the creation of educational resources.

== Eligibility ==

To apply for a grant, a student must:
* be eighteen (18) years of age or older upon application;
* be enrolled into a post-secondary academic program, as of the beginning of the grant;
* for the duration of the grant, be eligible to work in the country in which they reside;
* and not be a [https://trac.osgeo.org/grass/wiki/PSC GRASS GIS Project Steering Committee (PSC)] member.

In addition, the student has to:
* demonstrate ability to contribute to GRASS GIS through a [https://github.com/OSGeo/grass/pulls GitHub pull request (PR)].

== Additional criteria ==

* Students that are already active in the community have a better chance of obtaining a grant.
* There is no limit on how many times a student can apply or receive the grant.
* There are no special rules for former GSoC students. They are eligible to this grant as well, as long as they still fulfill the above criteria.

== Nature of the grant ==

* '''In 2023, GRASS GIS will offer a total of 4000 USD for grants'''.
* The maximum per grant is 1000 USD. Grant requests can be for lower amounts.
* One person can be awarded one grant at a time, but can apply more than once at different times.
* The time to complete the work should be maximum 2 months, but much shorter projects are clearly possible. It will mostly depend on the student's availability.

== How to apply ==

Students should submit their proposals through the [[Student_Grants/2022|GRASS GIS wiki]] and send an email to grass-grants@osgeo.org to notify of their application (i.e., link to the wiki page with the proposal). See [[Student Grants/2021|here]] for a previous round.
The email should contain:
* proof of eligibility (age, student status, link to accepted GRASS GIS PR, mail by active community member confirming mentorship)
The wiki page should contain:
* applicant's name
* a description of the proposed work
* a calendar of activities and deliverables
* a budget proposal

For the current call, applications will be accepted until '''October 30, 2023'''.

== Approval process ==

Project proposals are evaluated by the [https://trac.osgeo.org/grass/wiki/PSC GRASS GIS Project Steering Committee] within two weeks after the deadline and a notification will be sent to successful applicants.

== Grant payment ==

Grants are paid in two amounts (unless stated otherwise for the specific grant):
* 50% at the beginning of the work phase
* 50% after reception and approval of the final report by the PSC

== Final report ==

The final report should be also written in the [[Student_Grants/2022|GRASS GIS wiki]] under the proposal up to two weeks after the final date planned originally. When finished, the student sends an email to [https://lists.osgeo.org/pipermail/grass-psc/ grass-psc mailing list] to announce the end of the work and share the link to the final report. The final report should include:
* A description of the state of affairs before the work
* A description of the work done

== Topics ==

The GRASS GIS community provides a list of topics highly relevant to the community. Applicants may come up with their own topics. Relevance of the topic to the project will be evaluated individually. Topics contributing to the core GRASS project are usually more relevant than others.

List of open topics:

* Improve documentation and tests for a set of tools
** includes revising text, add missing/update examples with pictures, notebook how to generate the pictures, add tests (pytest)
** requirements: Python
** $100-200 per tool
** list of suggested tools: r.sim.water, r.reclass, r.resample, r.resamp.filter, r.mask, r.mode, v.surf.idw, v.surf.rst, r.fillnulls, r.surf.*, …

* r.rescale - reimplement as a wrapper to r.recode (see https://github.com/OSGeo/grass/issues/1986), add tests, examples and documentation
** requirements: Python
** $500

* Parallelize a tool with OpenMP
** possible candidates: r.horizon, r.mapcalc, r.proj, v.surf.idw
** requirements: C, OpenMP experience
** $1000 (one tool)

* Implement ''History manager'' in GRASS GUI
** display history of executed commands and re-execute them
** requirements: Python
** $1000

* Improve d.vect.chart
** fix legend (see https://github.com/OSGeo/grass/issues/3100), update documentation, add tests
** requirements: basic C and Python
** $500

* Add JSON output to different tools
** r.report, r.mapsets, r.what, r.univar, r.info, v.info, r3.info
** requirements: C
** $500 for 1

[[Category:Community]]
[[Category:Development]]
[[Category:Student Grants]]

Student Grants

2023-08-22T17:56:55Z

⚠️Wenzeslaus: /* Eligibility */

GRASS GIS offers a limited number of student grants for projects related to GRASS GIS. These can include actual coding, bug fixing, or documentation and the creation of educational resources.

== Eligibility ==

To apply for a grant, a student must:
* be eighteen (18) years of age or older upon application;
* be enrolled into a post-secondary academic program, as of the beginning of the grant;
* for the duration of the grant, be eligible to work in the country in which they reside;
* and not be a [https://trac.osgeo.org/grass/wiki/PSC GRASS GIS Project Steering Committee (PSC)] member.

In addition, the student has to:
* demonstrate ability to contribute to GRASS GIS through a [https://github.com/OSGeo/grass/pulls GitHub pull request (PR)];
* have the agreement of an active member of the GRASS GIS community to mentor the student's work.

== Additional criteria ==

* Students that are already active in the community have a better chance of obtaining a grant.
* There is no limit on how many times a student can apply or receive the grant.
* There are no special rules for former GSoC students. They are eligible to this grant as well, as long as they still fulfill the above criteria.

== Nature of the grant ==

* '''In 2023, GRASS GIS will offer a total of 4000 USD for grants'''.
* The maximum per grant is 1000 USD. Grant requests can be for lower amounts.
* One person can be awarded one grant at a time, but can apply more than once at different times.
* The time to complete the work should be maximum 2 months, but much shorter projects are clearly possible. It will mostly depend on the student's availability.

== How to apply ==

Students should submit their proposals through the [[Student_Grants/2022|GRASS GIS wiki]] and send an email to grass-grants@osgeo.org to notify of their application (i.e., link to the wiki page with the proposal). See [[Student Grants/2021|here]] for a previous round.
The email should contain:
* proof of eligibility (age, student status, link to accepted GRASS GIS PR, mail by active community member confirming mentorship)
The wiki page should contain:
* applicant's name
* a description of the proposed work
* a calendar of activities and deliverables
* a budget proposal

For the current call, applications will be accepted until '''October 30, 2023'''.

== Approval process ==

Project proposals are evaluated by the [https://trac.osgeo.org/grass/wiki/PSC GRASS GIS Project Steering Committee] within two weeks after the deadline and a notification will be sent to successful applicants.

== Grant payment ==

Grants are paid in two amounts (unless stated otherwise for the specific grant):
* 50% at the beginning of the work phase
* 50% after reception and approval of the final report by the PSC

== Final report ==

The final report should be also written in the [[Student_Grants/2022|GRASS GIS wiki]] under the proposal up to two weeks after the final date planned originally. When finished, the student sends an email to [https://lists.osgeo.org/pipermail/grass-psc/ grass-psc mailing list] to announce the end of the work and share the link to the final report. The final report should include:
* A description of the state of affairs before the work
* A description of the work done

== Topics ==

The GRASS GIS community provides a list of topics highly relevant to the community. Applicants may come up with their own topics. Relevance of the topic to the project will be evaluated individually. Topics contributing to the core GRASS project are usually more relevant than others.

List of open topics:

* Improve documentation and tests for a set of tools
** includes revising text, add missing/update examples with pictures, notebook how to generate the pictures, add tests (pytest)
** requirements: Python
** $100-200 per tool
** list of suggested tools: r.sim.water, r.reclass, r.resample, r.resamp.filter, r.mask, r.mode, v.surf.idw, v.surf.rst, r.fillnulls, r.surf.*, …

* r.rescale - reimplement as a wrapper to r.recode (see https://github.com/OSGeo/grass/issues/1986), add tests, examples and documentation
** requirements: Python
** $500

* Parallelize a tool with OpenMP
** possible candidates: r.horizon, r.mapcalc, r.proj, v.surf.idw
** requirements: C, OpenMP experience
** $1000 (one tool)

* Implement ''History manager'' in GRASS GUI
** display history of executed commands and re-execute them
** requirements: Python
** $1000

* Improve d.vect.chart
** fix legend (see https://github.com/OSGeo/grass/issues/3100), update documentation, add tests
** requirements: basic C and Python
** $500

* Add JSON output to different tools
** r.report, r.mapsets, r.what, r.univar, r.info, v.info, r3.info
** requirements: C
** $500 for 1

[[Category:Community]]
[[Category:Development]]
[[Category:Student Grants]]

Student Grants

2023-08-22T17:56:41Z

⚠️Wenzeslaus: /* Eligibility */ a PR which demonstrates the skill is required, but a merged PR is not required

GRASS GIS offers a limited number of student grants for projects related to GRASS GIS. These can include actual coding, bug fixing, or documentation and the creation of educational resources.

== Eligibility ==

To apply for a grant, a student must:
* be eighteen (18) years of age or older upon application;
* be enrolled into a post-secondary academic program, as of the beginning of the grant;
* for the duration of the grant, be eligible to work in the country in which they reside;
* and not be a [https://trac.osgeo.org/grass/wiki/PSC GRASS GIS Project Steering Committee (PSC)] member.

In addition, the student has to
* demonstrate ability to contribute to GRASS GIS through a [https://github.com/OSGeo/grass/pulls GitHub pull request (PR)];
* have the agreement of an active member of the GRASS GIS community to mentor the student's work.

== Additional criteria ==

* Students that are already active in the community have a better chance of obtaining a grant.
* There is no limit on how many times a student can apply or receive the grant.
* There are no special rules for former GSoC students. They are eligible to this grant as well, as long as they still fulfill the above criteria.

== Nature of the grant ==

* '''In 2023, GRASS GIS will offer a total of 4000 USD for grants'''.
* The maximum per grant is 1000 USD. Grant requests can be for lower amounts.
* One person can be awarded one grant at a time, but can apply more than once at different times.
* The time to complete the work should be maximum 2 months, but much shorter projects are clearly possible. It will mostly depend on the student's availability.

== How to apply ==

Students should submit their proposals through the [[Student_Grants/2022|GRASS GIS wiki]] and send an email to grass-grants@osgeo.org to notify of their application (i.e., link to the wiki page with the proposal). See [[Student Grants/2021|here]] for a previous round.
The email should contain:
* proof of eligibility (age, student status, link to accepted GRASS GIS PR, mail by active community member confirming mentorship)
The wiki page should contain:
* applicant's name
* a description of the proposed work
* a calendar of activities and deliverables
* a budget proposal

For the current call, applications will be accepted until '''October 30, 2023'''.

== Approval process ==

Project proposals are evaluated by the [https://trac.osgeo.org/grass/wiki/PSC GRASS GIS Project Steering Committee] within two weeks after the deadline and a notification will be sent to successful applicants.

== Grant payment ==

Grants are paid in two amounts (unless stated otherwise for the specific grant):
* 50% at the beginning of the work phase
* 50% after reception and approval of the final report by the PSC

== Final report ==

The final report should be also written in the [[Student_Grants/2022|GRASS GIS wiki]] under the proposal up to two weeks after the final date planned originally. When finished, the student sends an email to [https://lists.osgeo.org/pipermail/grass-psc/ grass-psc mailing list] to announce the end of the work and share the link to the final report. The final report should include:
* A description of the state of affairs before the work
* A description of the work done

== Topics ==

The GRASS GIS community provides a list of topics highly relevant to the community. Applicants may come up with their own topics. Relevance of the topic to the project will be evaluated individually. Topics contributing to the core GRASS project are usually more relevant than others.

List of open topics:

* Improve documentation and tests for a set of tools
** includes revising text, add missing/update examples with pictures, notebook how to generate the pictures, add tests (pytest)
** requirements: Python
** $100-200 per tool
** list of suggested tools: r.sim.water, r.reclass, r.resample, r.resamp.filter, r.mask, r.mode, v.surf.idw, v.surf.rst, r.fillnulls, r.surf.*, …

* r.rescale - reimplement as a wrapper to r.recode (see https://github.com/OSGeo/grass/issues/1986), add tests, examples and documentation
** requirements: Python
** $500

* Parallelize a tool with OpenMP
** possible candidates: r.horizon, r.mapcalc, r.proj, v.surf.idw
** requirements: C, OpenMP experience
** $1000 (one tool)

* Implement ''History manager'' in GRASS GUI
** display history of executed commands and re-execute them
** requirements: Python
** $1000

* Improve d.vect.chart
** fix legend (see https://github.com/OSGeo/grass/issues/3100), update documentation, add tests
** requirements: basic C and Python
** $500

* Add JSON output to different tools
** r.report, r.mapsets, r.what, r.univar, r.info, v.info, r3.info
** requirements: C
** $500 for 1

[[Category:Community]]
[[Category:Development]]
[[Category:Student Grants]]

Student Grants

2023-08-22T17:39:07Z

⚠️Wenzeslaus: /* Eligibility */

GRASS GIS offers a limited number of student grants for projects related to GRASS GIS. These can include actual coding, bug fixing, or documentation and the creation of educational resources.

== Eligibility ==

To apply for a grant, a student must:
* be eighteen (18) years of age or older upon application;
* be enrolled into a post-secondary academic program, as of the beginning of the grant;
* for the duration of the grant, be eligible to work in the country in which they reside;
* and not be a [https://trac.osgeo.org/grass/wiki/PSC GRASS GIS Project Steering Committee (PSC)] member

In addition, the student has to
* have had at least [https://github.com/OSGeo/grass/pulls one GitHub pull request] accepted concerning GRASS GIS code or documentation ''before the final application submission'';
* have the agreement of an active member of the GRASS GIS community to mentor the student's work.

== Additional criteria ==

* Students that are already active in the community have a better chance of obtaining a grant.
* There is no limit on how many times a student can apply or receive the grant.
* There are no special rules for former GSoC students. They are eligible to this grant as well, as long as they still fulfill the above criteria.

== Nature of the grant ==

* '''In 2023, GRASS GIS will offer a total of 4000 USD for grants'''.
* The maximum per grant is 1000 USD. Grant requests can be for lower amounts.
* One person can be awarded one grant at a time, but can apply more than once at different times.
* The time to complete the work should be maximum 2 months, but much shorter projects are clearly possible. It will mostly depend on the student's availability.

== How to apply ==

Students should submit their proposals through the [[Student_Grants/2022|GRASS GIS wiki]] and send an email to grass-grants@osgeo.org to notify of their application (i.e., link to the wiki page with the proposal). See [[Student Grants/2021|here]] for a previous round.
The email should contain:
* proof of eligibility (age, student status, link to accepted GRASS GIS PR, mail by active community member confirming mentorship)
The wiki page should contain:
* applicant's name
* a description of the proposed work
* a calendar of activities and deliverables
* a budget proposal

For the current call, applications will be accepted until '''October 30, 2023'''.

== Approval process ==

Project proposals are evaluated by the [https://trac.osgeo.org/grass/wiki/PSC GRASS GIS Project Steering Committee] within two weeks after the deadline and a notification will be sent to successful applicants.

== Grant payment ==

Grants are paid in two amounts (unless stated otherwise for the specific grant):
* 50% at the beginning of the work phase
* 50% after reception and approval of the final report by the PSC

== Final report ==

The final report should be also written in the [[Student_Grants/2022|GRASS GIS wiki]] under the proposal up to two weeks after the final date planned originally. When finished, the student sends an email to [https://lists.osgeo.org/pipermail/grass-psc/ grass-psc mailing list] to announce the end of the work and share the link to the final report. The final report should include:
* A description of the state of affairs before the work
* A description of the work done

== Topics ==

The GRASS GIS community provides a list of topics highly relevant to the community. Applicants may come up with their own topics. Relevance of the topic to the project will be evaluated individually. Topics contributing to the core GRASS project are usually more relevant than others.

List of open topics:

* Improve documentation and tests for a set of tools
** includes revising text, add missing/update examples with pictures, notebook how to generate the pictures, add tests (pytest)
** requirements: Python
** $100-200 per tool
** list of suggested tools: r.sim.water, r.reclass, r.resample, r.resamp.filter, r.mask, r.mode, v.surf.idw, v.surf.rst, r.fillnulls, r.surf.*, …

* r.rescale - reimplement as a wrapper to r.recode (see https://github.com/OSGeo/grass/issues/1986), add tests, examples and documentation
** requirements: Python
** $500

* Parallelize a tool with OpenMP
** possible candidates: r.horizon, r.mapcalc, r.proj, v.surf.idw
** requirements: C, OpenMP experience
** $1000 (one tool)

* Implement ''History manager'' in GRASS GUI
** display history of executed commands and re-execute them
** requirements: Python
** $1000

* Improve d.vect.chart
** fix legend (see https://github.com/OSGeo/grass/issues/3100), update documentation, add tests
** requirements: basic C and Python
** $500

* Add JSON output to different tools
** r.report, r.mapsets, r.what, r.univar, r.info, v.info, r3.info
** requirements: C
** $500 for 1

[[Category:Community]]
[[Category:Development]]
[[Category:Student Grants]]

Student Grants

2023-08-22T17:00:39Z

⚠️Wenzeslaus: /* Grant payment */ cumulative grants can't have 50% upfront payment

GRASS GIS offers a limited number of student grants for projects related to GRASS GIS. These can include actual coding, bug fixing, or documentation and the creation of educational resources.

== Eligibility ==

To apply for a grant, a student must:
* be eighteen (18) years of age or older upon application;
* be enrolled into a post-secondary academic program, as of the beginning of the grant; [following rules in GSoC 2021]
* for the duration of the grant, be eligible to work in the country in which they reside;
* and not be a [https://trac.osgeo.org/grass/wiki/PSC GRASS GIS Project Steering Committee (PSC)] member

In addition, the student has to
* have had at least [https://github.com/OSGeo/grass/pulls one GitHub pull request] accepted concerning GRASS GIS code or documentation ''before the application'';
* have the agreement of an active member of the GRASS GIS community to mentor the student's work.

== Additional criteria ==

* Students that are already active in the community have a better chance of obtaining a grant.
* There is no limit on how many times a student can apply or receive the grant.
* There are no special rules for former GSoC students. They are eligible to this grant as well, as long as they still fulfill the above criteria.

== Nature of the grant ==

* '''In 2023, GRASS GIS will offer a total of 4000 USD for grants'''.
* The maximum per grant is 1000 USD. Grant requests can be for lower amounts.
* One person can be awarded one grant at a time, but can apply more than once at different times.
* The time to complete the work should be maximum 2 months, but much shorter projects are clearly possible. It will mostly depend on the student's availability.

== How to apply ==

Students should submit their proposals through the [[Student_Grants/2022|GRASS GIS wiki]] and send an email to grass-grants@osgeo.org to notify of their application (i.e., link to the wiki page with the proposal). See [[Student Grants/2021|here]] for a previous round.
The email should contain:
* proof of eligibility (age, student status, link to accepted GRASS GIS PR, mail by active community member confirming mentorship)
The wiki page should contain:
* applicant's name
* a description of the proposed work
* a calendar of activities and deliverables
* a budget proposal

For the current call, applications will be accepted until '''October 30, 2022 23:59 UTC'''.

== Approval process ==

Project proposals are evaluated by the [https://trac.osgeo.org/grass/wiki/PSC GRASS GIS Project Steering Committee] within two weeks after the deadline and a notification will be sent to successful applicants.

== Grant payment ==

Grants are paid in two amounts (unless stated otherwise for the specific grant):
* 50% at the beginning of the work phase
* 50% after reception and approval of the final report by the PSC

== Final report ==

The final report should be also written in the [[Student_Grants/2022|GRASS GIS wiki]] under the proposal up to two weeks after the final date planned originally. When finished, the student sends an email to [https://lists.osgeo.org/pipermail/grass-psc/ grass-psc mailing list] to announce the end of the work and share the link to the final report. The final report should include:
* A description of the state of affairs before the work
* A description of the work done

== Topics ==

The GRASS GIS community provides a list of topics highly relevant to the community. Applicants may come up with their own topics. Relevance of the topic to the project will be evaluated individually. Topics contributing to the core GRASS project are usually more relevant than others.

List of open topics:

* Doc+test
* JSON
* GUI

[[Category:Community]]
[[Category:Development]]
[[Category:Student Grants]]

Student Grants

2023-08-22T16:58:52Z

⚠️Wenzeslaus: /* Nature of the grant */ 1000 EUR to 1000 USD (GRASS Open Collective is in USD), max increased from 3000 EUR to 4000 USD (we have money from sprint we said we will put towards the mini grants)

GRASS GIS offers a limited number of student grants for projects related to GRASS GIS. These can include actual coding, bug fixing, or documentation and the creation of educational resources.

== Eligibility ==

To apply for a grant, a student must:
* be eighteen (18) years of age or older upon application;
* be enrolled into a post-secondary academic program, as of the beginning of the grant; [following rules in GSoC 2021]
* for the duration of the grant, be eligible to work in the country in which they reside;
* and not be a [https://trac.osgeo.org/grass/wiki/PSC GRASS GIS Project Steering Committee (PSC)] member

In addition, the student has to
* have had at least [https://github.com/OSGeo/grass/pulls one GitHub pull request] accepted concerning GRASS GIS code or documentation ''before the application'';
* have the agreement of an active member of the GRASS GIS community to mentor the student's work.

== Additional criteria ==

* Students that are already active in the community have a better chance of obtaining a grant.
* There is no limit on how many times a student can apply or receive the grant.
* There are no special rules for former GSoC students. They are eligible to this grant as well, as long as they still fulfill the above criteria.

== Nature of the grant ==

* '''In 2023, GRASS GIS will offer a total of 4000 USD for grants'''.
* The maximum per grant is 1000 USD. Grant requests can be for lower amounts.
* One person can be awarded one grant at a time, but can apply more than once at different times.
* The time to complete the work should be maximum 2 months, but much shorter projects are clearly possible. It will mostly depend on the student's availability.

== How to apply ==

Students should submit their proposals through the [[Student_Grants/2022|GRASS GIS wiki]] and send an email to grass-grants@osgeo.org to notify of their application (i.e., link to the wiki page with the proposal). See [[Student Grants/2021|here]] for a previous round.
The email should contain:
* proof of eligibility (age, student status, link to accepted GRASS GIS PR, mail by active community member confirming mentorship)
The wiki page should contain:
* applicant's name
* a description of the proposed work
* a calendar of activities and deliverables
* a budget proposal

For the current call, applications will be accepted until '''October 30, 2022 23:59 UTC'''.

== Approval process ==

Project proposals are evaluated by the [https://trac.osgeo.org/grass/wiki/PSC GRASS GIS Project Steering Committee] within two weeks after the deadline and a notification will be sent to successful applicants.

== Grant payment ==

Grants are paid in two amounts:
* 50% at the beginning of the work phase
* 50% after reception and approval of the final report by the PSC

== Final report ==

The final report should be also written in the [[Student_Grants/2022|GRASS GIS wiki]] under the proposal up to two weeks after the final date planned originally. When finished, the student sends an email to [https://lists.osgeo.org/pipermail/grass-psc/ grass-psc mailing list] to announce the end of the work and share the link to the final report. The final report should include:
* A description of the state of affairs before the work
* A description of the work done

== Topics ==

The GRASS GIS community provides a list of topics highly relevant to the community. Applicants may come up with their own topics. Relevance of the topic to the project will be evaluated individually. Topics contributing to the core GRASS project are usually more relevant than others.

List of open topics:

* Doc+test
* JSON
* GUI

[[Category:Community]]
[[Category:Development]]
[[Category:Student Grants]]

Student Grants

2023-08-22T16:54:41Z

⚠️Wenzeslaus: /* Nature of the grant */

GRASS GIS offers a limited number of student grants for projects related to GRASS GIS. These can include actual coding, bug fixing, or documentation and the creation of educational resources.

== Eligibility ==

To apply for a grant, a student must:
* be eighteen (18) years of age or older upon application;
* be enrolled into a post-secondary academic program, as of the beginning of the grant; [following rules in GSoC 2021]
* for the duration of the grant, be eligible to work in the country in which they reside;
* and not be a [https://trac.osgeo.org/grass/wiki/PSC GRASS GIS Project Steering Committee (PSC)] member

In addition, the student has to
* have had at least [https://github.com/OSGeo/grass/pulls one GitHub pull request] accepted concerning GRASS GIS code or documentation ''before the application'';
* have the agreement of an active member of the GRASS GIS community to mentor the student's work.

== Additional criteria ==

* Students that are already active in the community have a better chance of obtaining a grant.
* There is no limit on how many times a student can apply or receive the grant.
* There are no special rules for former GSoC students. They are eligible to this grant as well, as long as they still fulfill the above criteria.

== Nature of the grant ==

* '''In 2023, GRASS GIS will offer a total of 3000€ for grants'''.
* The maximum per grant is 1000€. Grant requests can be for lower amounts.
* One person can be awarded one grant at a time, but can apply more than once at different times.
* The time to complete the work should be maximum 2 months, but much shorter projects are clearly possible. It will mostly depend on the student's availability.

== How to apply ==

Students should submit their proposals through the [[Student_Grants/2022|GRASS GIS wiki]] and send an email to grass-grants@osgeo.org to notify of their application (i.e., link to the wiki page with the proposal). See [[Student Grants/2021|here]] for a previous round.
The email should contain:
* proof of eligibility (age, student status, link to accepted GRASS GIS PR, mail by active community member confirming mentorship)
The wiki page should contain:
* applicant's name
* a description of the proposed work
* a calendar of activities and deliverables
* a budget proposal

For the current call, applications will be accepted until '''October 30, 2022 23:59 UTC'''.

== Approval process ==

Project proposals are evaluated by the [https://trac.osgeo.org/grass/wiki/PSC GRASS GIS Project Steering Committee] within two weeks after the deadline and a notification will be sent to successful applicants.

== Grant payment ==

Grants are paid in two amounts:
* 50% at the beginning of the work phase
* 50% after reception and approval of the final report by the PSC

== Final report ==

The final report should be also written in the [[Student_Grants/2022|GRASS GIS wiki]] under the proposal up to two weeks after the final date planned originally. When finished, the student sends an email to [https://lists.osgeo.org/pipermail/grass-psc/ grass-psc mailing list] to announce the end of the work and share the link to the final report. The final report should include:
* A description of the state of affairs before the work
* A description of the work done

== Topics ==

The GRASS GIS community provides a list of topics highly relevant to the community. Applicants may come up with their own topics. Relevance of the topic to the project will be evaluated individually. Topics contributing to the core GRASS project are usually more relevant than others.

List of open topics:

* Doc+test
* JSON
* GUI

[[Category:Community]]
[[Category:Development]]
[[Category:Student Grants]]

Student Grants

2023-08-22T16:33:21Z

⚠️Wenzeslaus: /* Topics */

GRASS GIS offers a limited number of student grants for projects related to GRASS GIS. These can include actual coding, bug fixing, or documentation and the creation of educational resources.

== Eligibility ==

To apply for a grant, a student must:
* be eighteen (18) years of age or older upon application;
* be enrolled into a post-secondary academic program, as of the beginning of the grant; [following rules in GSoC 2021]
* for the duration of the grant, be eligible to work in the country in which they reside;
* and not be a [https://trac.osgeo.org/grass/wiki/PSC GRASS GIS Project Steering Committee (PSC)] member

In addition, the student has to
* have had at least [https://github.com/OSGeo/grass/pulls one GitHub pull request] accepted concerning GRASS GIS code or documentation ''before the application'';
* have the agreement of an active member of the GRASS GIS community to mentor the student's work.

== Additional criteria ==

* Students that are already active in the community have a better chance of obtaining a grant.
* There is no limit on how many times a student can apply or receive the grant.
* There are no special rules for former GSoC students. They are eligible to this grant as well, as long as they still fulfill the above criteria.

== Nature of the grant ==

* '''In 2022, GRASS GIS will offer a total of 3000€ of grants'''.
* The maximum per grant is 1000€. Grant requests can be for lower amounts.
* The time to complete the work should be maximum 2 months, but much shorter projects are clearly possible. It will mostly depend on the student's availability.

== How to apply ==

Students should submit their proposals through the [[Student_Grants/2022|GRASS GIS wiki]] and send an email to grass-grants@osgeo.org to notify of their application (i.e., link to the wiki page with the proposal). See [[Student Grants/2021|here]] for a previous round.
The email should contain:
* proof of eligibility (age, student status, link to accepted GRASS GIS PR, mail by active community member confirming mentorship)
The wiki page should contain:
* applicant's name
* a description of the proposed work
* a calendar of activities and deliverables
* a budget proposal

For the current call, applications will be accepted until '''October 30, 2022 23:59 UTC'''.

== Approval process ==

Project proposals are evaluated by the [https://trac.osgeo.org/grass/wiki/PSC GRASS GIS Project Steering Committee] within two weeks after the deadline and a notification will be sent to successful applicants.

== Grant payment ==

Grants are paid in two amounts:
* 50% at the beginning of the work phase
* 50% after reception and approval of the final report by the PSC

== Final report ==

The final report should be also written in the [[Student_Grants/2022|GRASS GIS wiki]] under the proposal up to two weeks after the final date planned originally. When finished, the student sends an email to [https://lists.osgeo.org/pipermail/grass-psc/ grass-psc mailing list] to announce the end of the work and share the link to the final report. The final report should include:
* A description of the state of affairs before the work
* A description of the work done

== Topics ==

The GRASS GIS community provides a list of topics highly relevant to the community. Applicants may come up with their own topics. Relevance of the topic to the project will be evaluated individually. Topics contributing to the core GRASS project are usually more relevant than others.

List of open topics:

* Doc+test
* JSON
* GUI

[[Category:Community]]
[[Category:Development]]
[[Category:Student Grants]]

Student Grants

2023-08-22T16:29:05Z

⚠️Wenzeslaus: Add topics section (scratch the idea of subpages for years here)

GRASS GIS offers a limited number of student grants for projects related to GRASS GIS. These can include actual coding, bug fixing, or documentation and the creation of educational resources.

== Eligibility ==

To apply for a grant, a student must:
* be eighteen (18) years of age or older upon application;
* be enrolled into a post-secondary academic program, as of the beginning of the grant; [following rules in GSoC 2021]
* for the duration of the grant, be eligible to work in the country in which they reside;
* and not be a [https://trac.osgeo.org/grass/wiki/PSC GRASS GIS Project Steering Committee (PSC)] member

In addition, the student has to
* have had at least [https://github.com/OSGeo/grass/pulls one GitHub pull request] accepted concerning GRASS GIS code or documentation ''before the application'';
* have the agreement of an active member of the GRASS GIS community to mentor the student's work.

== Additional criteria ==

* Students that are already active in the community have a better chance of obtaining a grant.
* There is no limit on how many times a student can apply or receive the grant.
* There are no special rules for former GSoC students. They are eligible to this grant as well, as long as they still fulfill the above criteria.

== Nature of the grant ==

* '''In 2022, GRASS GIS will offer a total of 3000€ of grants'''.
* The maximum per grant is 1000€. Grant requests can be for lower amounts.
* The time to complete the work should be maximum 2 months, but much shorter projects are clearly possible. It will mostly depend on the student's availability.

== How to apply ==

Students should submit their proposals through the [[Student_Grants/2022|GRASS GIS wiki]] and send an email to grass-grants@osgeo.org to notify of their application (i.e., link to the wiki page with the proposal). See [[Student Grants/2021|here]] for a previous round.
The email should contain:
* proof of eligibility (age, student status, link to accepted GRASS GIS PR, mail by active community member confirming mentorship)
The wiki page should contain:
* applicant's name
* a description of the proposed work
* a calendar of activities and deliverables
* a budget proposal

For the current call, applications will be accepted until '''October 30, 2022 23:59 UTC'''.

== Approval process ==

Project proposals are evaluated by the [https://trac.osgeo.org/grass/wiki/PSC GRASS GIS Project Steering Committee] within two weeks after the deadline and a notification will be sent to successful applicants.

== Grant payment ==

Grants are paid in two amounts:
* 50% at the beginning of the work phase
* 50% after reception and approval of the final report by the PSC

== Final report ==

The final report should be also written in the [[Student_Grants/2022|GRASS GIS wiki]] under the proposal up to two weeks after the final date planned originally. When finished, the student sends an email to [https://lists.osgeo.org/pipermail/grass-psc/ grass-psc mailing list] to announce the end of the work and share the link to the final report. The final report should include:
* A description of the state of affairs before the work
* A description of the work done

== Topics ==

[[Category:Community]]
[[Category:Development]]
[[Category:Student Grants]]

GRASS Community Meeting Prague 2023

2023-08-14T21:01:08Z

⚠️Wenzeslaus: Use website press release

{{toc|right}}
The GRASS GIS team organized a ''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).

Quick links: [[Talk:GRASS Community Meeting Prague 2023|Full activity report]] | [[#Thanks_to_our_sponsors|Sponsors]] | [https://grass.osgeo.org/news/2023_08_13_grass_community_meeting_prague_june_2023_report/ Press release]

<gallery mode="slideshow">
Image:Prague-Community-Meeting-2023-crop.jpg|Prague 2023 Group Photo
Image:Day3-table.jpg|A full work table during the 3rd day
Image:Day3-collaboration.jpg|Lots of discussion and collaboration
Image:GRASS-smiles.jpg|GRASS GIS development brings smiles
Image:Day2-collaboration.jpg|Afternoon working and collaborating
Image:Beer-and-work-day4.jpg|The work and discussion continues over dinner
Image:Group-photo-hike.jpg|View at Alšova vyhlídka while taking a walk together
</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]]
* [https://www.osgeo.org/ OSGeo]: 7303 USD (approved budget contribution, [https://www.loomio.com/p/2m75BZkL/motion-to-approve-7303-to-support-grass-gis-community-meeting motion])
* Twitter: [https://twitter.com/OSGeo/ @OSGeo] | [https://fosstodon.org/@osgeo @osgeo@fosstodon.org]

[[File:FOSSGIS_eV_logo.png|none|left|400px|alt=Logo of FOSSGIS e.V.|FOSSGIS e.V.]]
* [https://www.fossgis.de/ FOSSGIS e.V.]: 5000 EUR (approved budget contribution, [https://www.fossgis.de/wiki/F%C3%B6rderantr%C3%A4ge/GRASS_GIS_Community_Meeting_2023 request])
* Twitter: [https://twitter.com/FOSSGIS_Verein @FOSSGIS_Verein] | [https://mastodon.online/@FOSSGISeV/ @FOSSGISeV@mastodon.online]

[[File:OSGeo JP logo for web.png|none|left|400px|alt=OSGeo.JP]]
* [https://www.osgeo.jp/ OSGeo Japan]: 550 USD (through Open Collective)

Individuals:
* Hernán De Angelis 20 USD
* MarWe 50 USD
* Nick Brady 50 USD
* José Ramón 50 USD
* Bon 50 USD
* Johannes Brauner 30 USD
* Peter Löwe 30 USD
* Evan Kay 10 USD
* Joaquin Perez Valera 5 USD
* Anonymous sponsors 2750 USD

In-kind contributions:

* Department of Geomatics Faculty of Civil Engineering Czech Technical University in Prague (FCE CTU) - space and personnel time (planning, preparation, participation)
* North Carolina State University, Center for Geospatial Analytics - personnel time (planning, preparation, participation)
* mundialis GmbH & Co. KG - personnel time (planning, preparation, participation)
* CONICET - personnel time (planning, preparation, participation)
* Research Institute for Nature and Forest (INBO | Brussels, Belgium) – personnel time + travel and hotel costs of INBO staff
* SunGIS – personnel time, travel, and hotel costs of Maris Nartiss
* OpenPlains Inc. – personnel time

Personal time and/or financial contributions:
* Martin Landa, Micha Silver, Helmut Kudrnovsky, Markus Neleter, Ondřej Pešek, Helena Mitasova, Vaclav Petras, Anna Petrasova, Corey White, Maris Nartiss, Aaron Saw Min Sern, Luís de Sousa, Caitlin Haedrich, Linda Kladivová, Carmen Tawalika, Floris Vanderhaeghe, Eva Stopkova, Brendan Harmon, Veronica Andreo, Daniel Torres, Loïc Bartoletti

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

* 9:00 meeting starts in the room B-868
* Lunch: 12:45 NTK
* 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
* Convert GRASS GIS documentation from HTML to Markdown and implement new documentation system (mkdocs?)
* Group photo 1
* Outdoor social evening

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

* Compilation CMake (Windows, Linux)
* Connections in general, rgrass, qgisprocess
* GRASS GIS addons overview generator for entire GitHub (and more?) based on tag "[https://github.com/topics/grass-gis-addons grass-gis-addons]"
* Group photo 2

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

* Connections in general, QGIS, rgrass, qgisprocess
* Parallelizations
* grass.jupyter
* [https://github.com/OSGeo/grass/discussions/3047 Meeting minutes from call with Nyall Dawson (QGIS)]

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

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

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

* Departure

=== Social events ===

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

Dinner at 7pm: [https://www.uveverky.com/kontakt/ U veverku pub] ([https://en.mapy.cz/s/jumomotupu map])

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

Dinner at 6pm: [https://unetickypivovar.cz/en Únětický pivovar] ([https://en.mapy.cz/s/mubutetoba map])

* 3:50pm train from Podbaba (15min walk) to Roztoky
* [https://en.mapy.cz/s/dabavojufa walk 1:30min]
* Bus (355) back from Unetice to Dejvicka: 21:57 or 23:18

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

Dinner at 7pm: [https://www.restauracevltava.cz/ Restaurace Vltava] ([https://en.mapy.cz/s/gonezofozo map])

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

Dinner at 7pm: [https://www.my-paprika.com/ My Paprika] ([https://en.mapy.cz/s/modekehepu map])

* Tram 26 from Dejvicka to Strossmayerovo namesti at 6:26pm

== 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 (14:30)
| June 6 (12:00)
| Improvements of imagery modules (push i.svm.*; i.signatures; ?)
|-
|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)
|
|-
|17
| Eva Stopkova
| Czech Republic
| June 3
| June 4
| Fixing v.nnstat
|
|-
|}

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]

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
|[[User:Baharmon|Brendan Harmon]]
| United States
| Update integration with QGIS
| Available 8:00 AM CST (UTC-6) onwards
|
|-
|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 ====

Follow Gitter.

=== Collaborative document scratching ===

Follow Gitter.

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

== Broadcast & Video ==

During the event :) Find the latest information on the [https://matrix.to/#/#grassgis_sprint:gitter.im Gitter Channel].

== Photos ==
Day 1
<gallery mode="slideshow">
Image:Devs at work.jpg|Hard at work on the first day
Image:Lively discussion.jpg|Lively discussion
Image:Dinner day 1.jpg|Dinner at a nearby pub
</gallery>

Day 2
<gallery mode="slideshow">
Image:Prague-Community-Meeting-2023.jpg|Group photo
Image:PXL 20230603 085440353.jpg|A full table on day 2
Image:GRASS-smiles.jpg|GRASS GIS development brings smiles
Image:Day2-pizza.jpg|Pizza fuels work!
Image:Day2-collaboration.jpg|Afternoon working and collaborating
Image:Group-photo-hike.jpg|View at Alšova vyhlídka on the way to Únětický pivovar (brewery)
Image:Únětický pivovar.jpg|Beer at Únětický pivovar, a 300-year-old brewery, after a day of hard work
</gallery>

Day 3
<gallery mode="slideshow">
Image:Day3-working.jpg|Working on new features, bug fixes, documentation and more..
Image:Day3-table.jpg|An even fuller table on day 3
Image:Day3-collaboration.jpg|Collaboration and discussion
Image:Beer-pano-day3.jpg|Panoramic photo of a cheers to GRASS's 40th Birthday at Vitala restaurant
</gallery>

Day 4
<gallery mode="slideshow">
Image:Group-photo2-day4.jpg|Group photo on Day 4 on the steps of CVUT Praha
Image:Qgis-call-day4.jpg|Discussing QGIS integration
Image:Toast-grass-40th-birthday.jpg|A toast to GRASS GIS's 40th Birthday and a successful meeting
Image:Beer-and-work-day4.jpg|The work and discussion continues over dinner
</gallery>

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

Published as [https://grass.osgeo.org/news/2023_08_13_grass_community_meeting_prague_june_2023_report/ Report of the GRASS GIS Community Meeting in Prague].

The GRASS GIS Community Meeting was held in the Czech Republic from June
2 to 6 at the Faculty of Civil Engineering of the Czech Technical
University in Prague. The meeting was a milestone event to celebrate the
40th birthday of GRASS GIS and brought together users, supporters,
contributors, power users and developers to celebrate, collaborate and
chart the future of GRASS GIS.

Thanks to the generous funding from OSGeo, FOSSGIS e.V., OSGeo.JP, and
individual financial contributors, we were able to welcome 17 in-person
participants from 9 countries on 3 continents and 4 remote participants.

The meeting was not only a celebration of 40 years of GRASS GIS, a free
geographic information system (GIS) software for managing, analysing and
visualising geospatial data, it was also a testament to the
collaborative spirit that has driven GRASS GIS for four decades.
Participants worked together on various aspects of GRASS GIS, including
source code, documentation, translations and the website. Participants
contributed new tools, enhancements to existing ones, and a large number
of bug fixes. The improvements to documentation, including onboarding
materials, and a draft of the 8.3.0 release was another important
outcome.

There was a strong focus on improving the sustainability of the GRASS
GIS ecosystem. Several participants made progress on the CMake
transition needed for improving Windows builds. Various technical
discussions were held on improving the GRASS GIS interfaces to QGIS,
GDAL, and R. These discussions were attended by special guests from QGIS
(Nyall Dawson) and R (Roger Bivand) communities, leading to valuable
insights and future collaboration plans on strengthening these GRASS
integrations.

Participants submitted detailed reports outlining their contributions,
collaborations and ongoing work. The event was meticulously planned,
with efforts made in fundraising, budgeting, venue selection, promotion
and virtual meeting organisation. Besides aforementioned financial
contributions, personnel time and other costs were covered by Department
of Geomatics Faculty of Civil Engineering Czech Technical University in
Prague (Czech Republic), Center for Geospatial Analytics at North
Carolina State University (USA), mundialis GmbH & Co. KG, (Germany),
CONICET (Argentina), INBO Research Institute for Nature and Forest
(Belgium), SunGIS (Latvia), and OpenPlains Inc. (USA). Special thanks
goes to Martin Landa, the local host, for planning local events and
keeping the participants well fed and productive.

For more details on the meeting, sponsorship, and individual reports,
please visit the [https://grasswiki.osgeo.org/wiki/Talk:GRASS_Community_Meeting_Prague_2023 GRASS Community Sprint Prague 2023 wiki page],
and follow us on social media ([https://twitter.com/GRASSGIS X],
[https://mastodon.social/@grassgis@fosstodon.org mastodon]),
join the chat channel in [https://app.gitter.im/#/room/#grassgis_community:gitter.im Gitter]
or the [https://lists.osgeo.org/mailman/listinfo/grass-user mailing lists] to
stay updated on future news and events. If you would like to see more
developments like this in the future, please consider contributing via
[https://opencollective.com/grass/contribute Open Collective].

''Markus Neteler, Anna Petrasova, Vaclav Petras, Veronica Andreo, August 2023''

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

Talk:GRASS Community Meeting Prague 2023

2023-08-14T21:00:47Z

⚠️Wenzeslaus: Fix links, use website press release

{{toc|right}}

Quick links: [[GRASS Community Meeting Prague 2023|Meeting page]] | [[#Reports|Reports]] | [[GRASS_Community_Meeting_Prague_2023#Thanks_to_our_sponsors|Sponsors]] | [https://grass.osgeo.org/news/2023_08_13_grass_community_meeting_prague_june_2023_report/ Press release]

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

== 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 about naming, advantages, and challenges
* Python API and CLI
** [https://github.com/OSGeo/grass/pull/2923 grass.experimental: Add object to access modules as functions #2923]
** Discussion about creating locations from Python ([https://github.com/OSGeo/grass/issues/3034 Issue: make gscript.create_location() callable from outside #3034])
** [https://github.com/OSGeo/grass/issues/3007 Issue: Add g.findfile alternative which hides format complexities #3007]
* QGIS
** Group call to identify priorities with Nyall Dawson
* R
** Discussion with Floris Vanderhaeghe, Roger Bivand, and others assessing the current state
* GUI
** Discussion about streamlined startup
** [https://github.com/OSGeo/grass/pull/3049 wxGUI: Ignore stderr of the GUI #3049]
* CI
** [https://github.com/OSGeo/grass/pull/3002 CI: Switch Travis to Ubuntu 22.04 (jammmy) #3002]
** [https://github.com/OSGeo/grass/pull/3014 CI: Reduce number of Python jobs #3014]
** [https://github.com/OSGeo/grass-addons/pull/921 CI: Test with v8.3, Python 3.7 #921]
* Release 8.3.0
** Work with Markus Neteler to prepare release
* Contributing:
** [https://github.com/OSGeo/grass/pull/3048 contributing: Add empty line after heading in release notes #3048]
** [https://github.com/OSGeo/grass/pull/3035 contributing: Add more expressions to match release notes groups #3035]
* Reviews:
** [https://github.com/OSGeo/grass/pull/2189 Imagery: add libsvm based imagery classification #2189]
** [https://github.com/OSGeo/grass/pull/2974 t.rast.algebra/testsuite: split file test_raster_algebra.py #2974]
** [https://github.com/OSGeo/grass-addons/pull/606 r.random.walk: Add module to create random walks #606]
** [https://github.com/OSGeo/grass/pull/2930 r.surf.random: Added seed option and flag to module #2930]
** [https://github.com/OSGeo/grass/pull/3008 i.signatures: Add imagery classifier signature management module #3008]
** [https://github.com/OSGeo/grass/pull/3037 r.patch: ensure r.in.ascii in relevant tests always create CELL #3037]
** [https://github.com/OSGeo/grass-addons/pull/911 r.mblend: basic tests #911]
** [https://github.com/OSGeo/grass/pull/3010 grass.unittest: Fix usage of assertRegexpMatches() removed from Python 3.12 #3010]
** [https://github.com/OSGeo/grass/pull/3011 grass.gunittest: Fix usage of assertNotRegexMatches() removed from Python 3.12 #3011]
** [https://github.com/OSGeo/grass/pull/3009 grass.gunittest: Fix usage of assertEquals() removed from Python 3.12 #3009]
** [https://github.com/OSGeo/grass-addons/pull/917 grass.gunittest: Fix usage of assertEquals() removed from Python 3.12 #917]
** [https://github.com/OSGeo/grass/pull/2992 wxGUI/query: set region matching the raster for each raster queried #2992]
** [https://github.com/OSGeo/grass/pull/2997 wxGUI/gmodeler: Show ModelRelation in white on dark mode #2997]
** [https://github.com/OSGeo/grass/pull/3015 Locale: extract translatable messages also from C++ files #3015]
** [https://github.com/OSGeo/grass/pull/3029 doc: Document that lists in parser must be NULL terminated #3029]
** [https://github.com/OSGeo/grass/pull/3006 contributing: Expand instructions on pre-commit #3006]
** [https://github.com/OSGeo/grass/pull/3030 contributing: minor release procedure updates (main) #3030]
** [https://github.com/OSGeo/grass/pull/3031 contributing: release procedure updates (G82) #3031]
** [https://github.com/OSGeo/grass/pull/3032 contributing: release procedure updates (G83) #3032]
** [https://github.com/OSGeo/grass-addons/pull/916 contributing: adds instructions on unit tests for add-ons #916]
** [https://github.com/OSGeo/grass/pull/3012 contributing: Remove parts of locale readme already present in submitting guidelines #3012]

See also [https://github.com/wenzeslaus?tab=overview&from=2023-06-01&to=2023-06-30 June activity log on GitHub].

=== 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 (https://github.com/rsbivand/rgrass/discussions/78)
* Participate in a two-hour meeting with Nyall Dawson (QGIS) and the GRASS Community about interfacing GRASS from QGIS (https://github.com/OSGeo/grass/discussions/3047)

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

Ideas for the meeting agenda:

* '''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

=== 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 on interfacing GRASS from QGIS ==

* Special guest: Nyall Dawson (QGIS)
* All meeting participants were part of the call.
* 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

Complete minutes are in the GitHub Discussion [https://github.com/OSGeo/grass/discussions/3047 ''Meeting minutes on interfacing GRASS from QGIS'' #3047].

== Discussion on using GRASS from R ==

* Special guest: Roger Bivand (rgrass, ...)
* Attended by 7+ participants

Complete minutes are in the GitHub Discussion [https://github.com/rsbivand/rgrass/discussions/78 ''Meeting minutes on interfacing GRASS from R'' #78].

== 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-08-14T20:58:41Z

⚠️Wenzeslaus: /* Report and press release */ Copy-paste press release text to the Press release section, add link to web page

{{toc|right}}
The GRASS GIS team organized a ''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).

Quick links: [[Talk:GRASS Community Meeting Prague 2023|Full activity report]] | [[#Thanks_to_our_sponsors|Sponsors]] | [[GRASS_Community_Meeting_Prague_2023#Report_and_press_release|Press release]]

<gallery mode="slideshow">
Image:Prague-Community-Meeting-2023-crop.jpg|Prague 2023 Group Photo
Image:Day3-table.jpg|A full work table during the 3rd day
Image:Day3-collaboration.jpg|Lots of discussion and collaboration
Image:GRASS-smiles.jpg|GRASS GIS development brings smiles
Image:Day2-collaboration.jpg|Afternoon working and collaborating
Image:Beer-and-work-day4.jpg|The work and discussion continues over dinner
Image:Group-photo-hike.jpg|View at Alšova vyhlídka while taking a walk together
</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]]
* [https://www.osgeo.org/ OSGeo]: 7303 USD (approved budget contribution, [https://www.loomio.com/p/2m75BZkL/motion-to-approve-7303-to-support-grass-gis-community-meeting motion])
* Twitter: [https://twitter.com/OSGeo/ @OSGeo] | [https://fosstodon.org/@osgeo @osgeo@fosstodon.org]

[[File:FOSSGIS_eV_logo.png|none|left|400px|alt=Logo of FOSSGIS e.V.|FOSSGIS e.V.]]
* [https://www.fossgis.de/ FOSSGIS e.V.]: 5000 EUR (approved budget contribution, [https://www.fossgis.de/wiki/F%C3%B6rderantr%C3%A4ge/GRASS_GIS_Community_Meeting_2023 request])
* Twitter: [https://twitter.com/FOSSGIS_Verein @FOSSGIS_Verein] | [https://mastodon.online/@FOSSGISeV/ @FOSSGISeV@mastodon.online]

[[File:OSGeo JP logo for web.png|none|left|400px|alt=OSGeo.JP]]
* [https://www.osgeo.jp/ OSGeo Japan]: 550 USD (through Open Collective)

Individuals:
* Hernán De Angelis 20 USD
* MarWe 50 USD
* Nick Brady 50 USD
* José Ramón 50 USD
* Bon 50 USD
* Johannes Brauner 30 USD
* Peter Löwe 30 USD
* Evan Kay 10 USD
* Joaquin Perez Valera 5 USD
* Anonymous sponsors 2750 USD

In-kind contributions:

* Department of Geomatics Faculty of Civil Engineering Czech Technical University in Prague (FCE CTU) - space and personnel time (planning, preparation, participation)
* North Carolina State University, Center for Geospatial Analytics - personnel time (planning, preparation, participation)
* mundialis GmbH & Co. KG - personnel time (planning, preparation, participation)
* CONICET - personnel time (planning, preparation, participation)
* Research Institute for Nature and Forest (INBO | Brussels, Belgium) – personnel time + travel and hotel costs of INBO staff
* SunGIS – personnel time, travel, and hotel costs of Maris Nartiss
* OpenPlains Inc. – personnel time

Personal time and/or financial contributions:
* Martin Landa, Micha Silver, Helmut Kudrnovsky, Markus Neleter, Ondřej Pešek, Helena Mitasova, Vaclav Petras, Anna Petrasova, Corey White, Maris Nartiss, Aaron Saw Min Sern, Luís de Sousa, Caitlin Haedrich, Linda Kladivová, Carmen Tawalika, Floris Vanderhaeghe, Eva Stopkova, Brendan Harmon, Veronica Andreo, Daniel Torres, Loïc Bartoletti

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

* 9:00 meeting starts in the room B-868
* Lunch: 12:45 NTK
* 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
* Convert GRASS GIS documentation from HTML to Markdown and implement new documentation system (mkdocs?)
* Group photo 1
* Outdoor social evening

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

* Compilation CMake (Windows, Linux)
* Connections in general, rgrass, qgisprocess
* GRASS GIS addons overview generator for entire GitHub (and more?) based on tag "[https://github.com/topics/grass-gis-addons grass-gis-addons]"
* Group photo 2

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

* Connections in general, QGIS, rgrass, qgisprocess
* Parallelizations
* grass.jupyter
* [https://github.com/OSGeo/grass/discussions/3047 Meeting minutes from call with Nyall Dawson (QGIS)]

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

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

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

* Departure

=== Social events ===

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

Dinner at 7pm: [https://www.uveverky.com/kontakt/ U veverku pub] ([https://en.mapy.cz/s/jumomotupu map])

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

Dinner at 6pm: [https://unetickypivovar.cz/en Únětický pivovar] ([https://en.mapy.cz/s/mubutetoba map])

* 3:50pm train from Podbaba (15min walk) to Roztoky
* [https://en.mapy.cz/s/dabavojufa walk 1:30min]
* Bus (355) back from Unetice to Dejvicka: 21:57 or 23:18

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

Dinner at 7pm: [https://www.restauracevltava.cz/ Restaurace Vltava] ([https://en.mapy.cz/s/gonezofozo map])

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

Dinner at 7pm: [https://www.my-paprika.com/ My Paprika] ([https://en.mapy.cz/s/modekehepu map])

* Tram 26 from Dejvicka to Strossmayerovo namesti at 6:26pm

== 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 (14:30)
| June 6 (12:00)
| Improvements of imagery modules (push i.svm.*; i.signatures; ?)
|-
|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)
|
|-
|17
| Eva Stopkova
| Czech Republic
| June 3
| June 4
| Fixing v.nnstat
|
|-
|}

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]

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
|[[User:Baharmon|Brendan Harmon]]
| United States
| Update integration with QGIS
| Available 8:00 AM CST (UTC-6) onwards
|
|-
|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 ====

Follow Gitter.

=== Collaborative document scratching ===

Follow Gitter.

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

== Broadcast & Video ==

During the event :) Find the latest information on the [https://matrix.to/#/#grassgis_sprint:gitter.im Gitter Channel].

== Photos ==
Day 1
<gallery mode="slideshow">
Image:Devs at work.jpg|Hard at work on the first day
Image:Lively discussion.jpg|Lively discussion
Image:Dinner day 1.jpg|Dinner at a nearby pub
</gallery>

Day 2
<gallery mode="slideshow">
Image:Prague-Community-Meeting-2023.jpg|Group photo
Image:PXL 20230603 085440353.jpg|A full table on day 2
Image:GRASS-smiles.jpg|GRASS GIS development brings smiles
Image:Day2-pizza.jpg|Pizza fuels work!
Image:Day2-collaboration.jpg|Afternoon working and collaborating
Image:Group-photo-hike.jpg|View at Alšova vyhlídka on the way to Únětický pivovar (brewery)
Image:Únětický pivovar.jpg|Beer at Únětický pivovar, a 300-year-old brewery, after a day of hard work
</gallery>

Day 3
<gallery mode="slideshow">
Image:Day3-working.jpg|Working on new features, bug fixes, documentation and more..
Image:Day3-table.jpg|An even fuller table on day 3
Image:Day3-collaboration.jpg|Collaboration and discussion
Image:Beer-pano-day3.jpg|Panoramic photo of a cheers to GRASS's 40th Birthday at Vitala restaurant
</gallery>

Day 4
<gallery mode="slideshow">
Image:Group-photo2-day4.jpg|Group photo on Day 4 on the steps of CVUT Praha
Image:Qgis-call-day4.jpg|Discussing QGIS integration
Image:Toast-grass-40th-birthday.jpg|A toast to GRASS GIS's 40th Birthday and a successful meeting
Image:Beer-and-work-day4.jpg|The work and discussion continues over dinner
</gallery>

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

Published as [https://grass.osgeo.org/news/2023_08_13_grass_community_meeting_prague_june_2023_report/ Report of the GRASS GIS Community Meeting in Prague].

The GRASS GIS Community Meeting was held in the Czech Republic from June
2 to 6 at the Faculty of Civil Engineering of the Czech Technical
University in Prague. The meeting was a milestone event to celebrate the
40th birthday of GRASS GIS and brought together users, supporters,
contributors, power users and developers to celebrate, collaborate and
chart the future of GRASS GIS.

Thanks to the generous funding from OSGeo, FOSSGIS e.V., OSGeo.JP, and
individual financial contributors, we were able to welcome 17 in-person
participants from 9 countries on 3 continents and 4 remote participants.

The meeting was not only a celebration of 40 years of GRASS GIS, a free
geographic information system (GIS) software for managing, analysing and
visualising geospatial data, it was also a testament to the
collaborative spirit that has driven GRASS GIS for four decades.
Participants worked together on various aspects of GRASS GIS, including
source code, documentation, translations and the website. Participants
contributed new tools, enhancements to existing ones, and a large number
of bug fixes. The improvements to documentation, including onboarding
materials, and a draft of the 8.3.0 release was another important
outcome.

There was a strong focus on improving the sustainability of the GRASS
GIS ecosystem. Several participants made progress on the CMake
transition needed for improving Windows builds. Various technical
discussions were held on improving the GRASS GIS interfaces to QGIS,
GDAL, and R. These discussions were attended by special guests from QGIS
(Nyall Dawson) and R (Roger Bivand) communities, leading to valuable
insights and future collaboration plans on strengthening these GRASS
integrations.

Participants submitted detailed reports outlining their contributions,
collaborations and ongoing work. The event was meticulously planned,
with efforts made in fundraising, budgeting, venue selection, promotion
and virtual meeting organisation. Besides aforementioned financial
contributions, personnel time and other costs were covered by Department
of Geomatics Faculty of Civil Engineering Czech Technical University in
Prague (Czech Republic), Center for Geospatial Analytics at North
Carolina State University (USA), mundialis GmbH & Co. KG, (Germany),
CONICET (Argentina), INBO Research Institute for Nature and Forest
(Belgium), SunGIS (Latvia), and OpenPlains Inc. (USA). Special thanks
goes to Martin Landa, the local host, for planning local events and
keeping the participants well fed and productive.

For more details on the meeting, sponsorship, and individual reports,
please visit the [https://grasswiki.osgeo.org/wiki/Talk:GRASS_Community_Meeting_Prague_2023 GRASS Community Sprint Prague 2023 wiki page],
and follow us on social media ([https://twitter.com/GRASSGIS X],
[https://mastodon.social/@grassgis@fosstodon.org mastodon]),
join the chat channel in [https://app.gitter.im/#/room/#grassgis_community:gitter.im Gitter]
or the [https://lists.osgeo.org/mailman/listinfo/grass-user mailing lists] to
stay updated on future news and events. If you would like to see more
developments like this in the future, please consider contributing via
[https://opencollective.com/grass/contribute Open Collective].

''Markus Neteler, Anna Petrasova, Vaclav Petras, Veronica Andreo, August 2023''

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

Talk:GRASS Community Meeting Prague 2023

2023-08-14T20:50:59Z

⚠️Wenzeslaus: Move ideas section under individual people to make report more clear (and not start with ideas)

{{toc|right}}

Quick links: [[GRASS Community Meeting Prague 2023|Meeting page]] | [[#Reports|Reports]] | [[Sponsors#Thanks_to_our_sponsors|Sponsors]] | [[GRASS_Community_Meeting_Prague_2023#Report_and_press_release|Press release]]

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

== 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 about naming, advantages, and challenges
* Python API and CLI
** [https://github.com/OSGeo/grass/pull/2923 grass.experimental: Add object to access modules as functions #2923]
** Discussion about creating locations from Python ([https://github.com/OSGeo/grass/issues/3034 Issue: make gscript.create_location() callable from outside #3034])
** [https://github.com/OSGeo/grass/issues/3007 Issue: Add g.findfile alternative which hides format complexities #3007]
* QGIS
** Group call to identify priorities with Nyall Dawson
* R
** Discussion with Floris Vanderhaeghe, Roger Bivand, and others assessing the current state
* GUI
** Discussion about streamlined startup
** [https://github.com/OSGeo/grass/pull/3049 wxGUI: Ignore stderr of the GUI #3049]
* CI
** [https://github.com/OSGeo/grass/pull/3002 CI: Switch Travis to Ubuntu 22.04 (jammmy) #3002]
** [https://github.com/OSGeo/grass/pull/3014 CI: Reduce number of Python jobs #3014]
** [https://github.com/OSGeo/grass-addons/pull/921 CI: Test with v8.3, Python 3.7 #921]
* Release 8.3.0
** Work with Markus Neteler to prepare release
* Contributing:
** [https://github.com/OSGeo/grass/pull/3048 contributing: Add empty line after heading in release notes #3048]
** [https://github.com/OSGeo/grass/pull/3035 contributing: Add more expressions to match release notes groups #3035]
* Reviews:
** [https://github.com/OSGeo/grass/pull/2189 Imagery: add libsvm based imagery classification #2189]
** [https://github.com/OSGeo/grass/pull/2974 t.rast.algebra/testsuite: split file test_raster_algebra.py #2974]
** [https://github.com/OSGeo/grass-addons/pull/606 r.random.walk: Add module to create random walks #606]
** [https://github.com/OSGeo/grass/pull/2930 r.surf.random: Added seed option and flag to module #2930]
** [https://github.com/OSGeo/grass/pull/3008 i.signatures: Add imagery classifier signature management module #3008]
** [https://github.com/OSGeo/grass/pull/3037 r.patch: ensure r.in.ascii in relevant tests always create CELL #3037]
** [https://github.com/OSGeo/grass-addons/pull/911 r.mblend: basic tests #911]
** [https://github.com/OSGeo/grass/pull/3010 grass.unittest: Fix usage of assertRegexpMatches() removed from Python 3.12 #3010]
** [https://github.com/OSGeo/grass/pull/3011 grass.gunittest: Fix usage of assertNotRegexMatches() removed from Python 3.12 #3011]
** [https://github.com/OSGeo/grass/pull/3009 grass.gunittest: Fix usage of assertEquals() removed from Python 3.12 #3009]
** [https://github.com/OSGeo/grass-addons/pull/917 grass.gunittest: Fix usage of assertEquals() removed from Python 3.12 #917]
** [https://github.com/OSGeo/grass/pull/2992 wxGUI/query: set region matching the raster for each raster queried #2992]
** [https://github.com/OSGeo/grass/pull/2997 wxGUI/gmodeler: Show ModelRelation in white on dark mode #2997]
** [https://github.com/OSGeo/grass/pull/3015 Locale: extract translatable messages also from C++ files #3015]
** [https://github.com/OSGeo/grass/pull/3029 doc: Document that lists in parser must be NULL terminated #3029]
** [https://github.com/OSGeo/grass/pull/3006 contributing: Expand instructions on pre-commit #3006]
** [https://github.com/OSGeo/grass/pull/3030 contributing: minor release procedure updates (main) #3030]
** [https://github.com/OSGeo/grass/pull/3031 contributing: release procedure updates (G82) #3031]
** [https://github.com/OSGeo/grass/pull/3032 contributing: release procedure updates (G83) #3032]
** [https://github.com/OSGeo/grass-addons/pull/916 contributing: adds instructions on unit tests for add-ons #916]
** [https://github.com/OSGeo/grass/pull/3012 contributing: Remove parts of locale readme already present in submitting guidelines #3012]

See also [https://github.com/wenzeslaus?tab=overview&from=2023-06-01&to=2023-06-30 June activity log on GitHub].

=== 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 (https://github.com/rsbivand/rgrass/discussions/78)
* Participate in a two-hour meeting with Nyall Dawson (QGIS) and the GRASS Community about interfacing GRASS from QGIS (https://github.com/OSGeo/grass/discussions/3047)

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

Ideas for the meeting agenda:

* '''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

=== 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 on interfacing GRASS from QGIS ==

* Special guest: Nyall Dawson (QGIS)
* All meeting participants were part of the call.
* 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

Complete minutes are in the GitHub Discussion [https://github.com/OSGeo/grass/discussions/3047 ''Meeting minutes on interfacing GRASS from QGIS'' #3047].

== Discussion on using GRASS from R ==

* Special guest: Roger Bivand (rgrass, ...)
* Attended by 7+ participants

Complete minutes are in the GitHub Discussion [https://github.com/rsbivand/rgrass/discussions/78 ''Meeting minutes on interfacing GRASS from R'' #78].

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

Talk:GRASS Community Meeting Prague 2023

2023-08-14T20:49:17Z

⚠️Wenzeslaus: add quick links

{{toc|right}}

Quick links: [[GRASS Community Meeting Prague 2023|Meeting page]] | [[#Reports|Reports]] | [[Sponsors#Thanks_to_our_sponsors|Sponsors]] | [[GRASS_Community_Meeting_Prague_2023#Report_and_press_release|Press release]]

== 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 about naming, advantages, and challenges
* Python API and CLI
** [https://github.com/OSGeo/grass/pull/2923 grass.experimental: Add object to access modules as functions #2923]
** Discussion about creating locations from Python ([https://github.com/OSGeo/grass/issues/3034 Issue: make gscript.create_location() callable from outside #3034])
** [https://github.com/OSGeo/grass/issues/3007 Issue: Add g.findfile alternative which hides format complexities #3007]
* QGIS
** Group call to identify priorities with Nyall Dawson
* R
** Discussion with Floris Vanderhaeghe, Roger Bivand, and others assessing the current state
* GUI
** Discussion about streamlined startup
** [https://github.com/OSGeo/grass/pull/3049 wxGUI: Ignore stderr of the GUI #3049]
* CI
** [https://github.com/OSGeo/grass/pull/3002 CI: Switch Travis to Ubuntu 22.04 (jammmy) #3002]
** [https://github.com/OSGeo/grass/pull/3014 CI: Reduce number of Python jobs #3014]
** [https://github.com/OSGeo/grass-addons/pull/921 CI: Test with v8.3, Python 3.7 #921]
* Release 8.3.0
** Work with Markus Neteler to prepare release
* Contributing:
** [https://github.com/OSGeo/grass/pull/3048 contributing: Add empty line after heading in release notes #3048]
** [https://github.com/OSGeo/grass/pull/3035 contributing: Add more expressions to match release notes groups #3035]
* Reviews:
** [https://github.com/OSGeo/grass/pull/2189 Imagery: add libsvm based imagery classification #2189]
** [https://github.com/OSGeo/grass/pull/2974 t.rast.algebra/testsuite: split file test_raster_algebra.py #2974]
** [https://github.com/OSGeo/grass-addons/pull/606 r.random.walk: Add module to create random walks #606]
** [https://github.com/OSGeo/grass/pull/2930 r.surf.random: Added seed option and flag to module #2930]
** [https://github.com/OSGeo/grass/pull/3008 i.signatures: Add imagery classifier signature management module #3008]
** [https://github.com/OSGeo/grass/pull/3037 r.patch: ensure r.in.ascii in relevant tests always create CELL #3037]
** [https://github.com/OSGeo/grass-addons/pull/911 r.mblend: basic tests #911]
** [https://github.com/OSGeo/grass/pull/3010 grass.unittest: Fix usage of assertRegexpMatches() removed from Python 3.12 #3010]
** [https://github.com/OSGeo/grass/pull/3011 grass.gunittest: Fix usage of assertNotRegexMatches() removed from Python 3.12 #3011]
** [https://github.com/OSGeo/grass/pull/3009 grass.gunittest: Fix usage of assertEquals() removed from Python 3.12 #3009]
** [https://github.com/OSGeo/grass-addons/pull/917 grass.gunittest: Fix usage of assertEquals() removed from Python 3.12 #917]
** [https://github.com/OSGeo/grass/pull/2992 wxGUI/query: set region matching the raster for each raster queried #2992]
** [https://github.com/OSGeo/grass/pull/2997 wxGUI/gmodeler: Show ModelRelation in white on dark mode #2997]
** [https://github.com/OSGeo/grass/pull/3015 Locale: extract translatable messages also from C++ files #3015]
** [https://github.com/OSGeo/grass/pull/3029 doc: Document that lists in parser must be NULL terminated #3029]
** [https://github.com/OSGeo/grass/pull/3006 contributing: Expand instructions on pre-commit #3006]
** [https://github.com/OSGeo/grass/pull/3030 contributing: minor release procedure updates (main) #3030]
** [https://github.com/OSGeo/grass/pull/3031 contributing: release procedure updates (G82) #3031]
** [https://github.com/OSGeo/grass/pull/3032 contributing: release procedure updates (G83) #3032]
** [https://github.com/OSGeo/grass-addons/pull/916 contributing: adds instructions on unit tests for add-ons #916]
** [https://github.com/OSGeo/grass/pull/3012 contributing: Remove parts of locale readme already present in submitting guidelines #3012]

See also [https://github.com/wenzeslaus?tab=overview&from=2023-06-01&to=2023-06-30 June activity log on GitHub].

=== 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 (https://github.com/rsbivand/rgrass/discussions/78)
* Participate in a two-hour meeting with Nyall Dawson (QGIS) and the GRASS Community about interfacing GRASS from QGIS (https://github.com/OSGeo/grass/discussions/3047)

=== 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 on interfacing GRASS from QGIS ==

* Special guest: Nyall Dawson (QGIS)
* All meeting participants were part of the call.
* 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

Complete minutes are in the GitHub Discussion [https://github.com/OSGeo/grass/discussions/3047 ''Meeting minutes on interfacing GRASS from QGIS'' #3047].

== Discussion on using GRASS from R ==

* Special guest: Roger Bivand (rgrass, ...)
* Attended by 7+ participants

Complete minutes are in the GitHub Discussion [https://github.com/rsbivand/rgrass/discussions/78 ''Meeting minutes on interfacing GRASS from R'' #78].

== 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-08-14T20:48:45Z

⚠️Wenzeslaus: Link to thanks to sponsors, not the Sponsors page

{{toc|right}}
The GRASS GIS team organized a ''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).

Quick links: [[Talk:GRASS Community Meeting Prague 2023|Full activity report]] | [[#Thanks_to_our_sponsors|Sponsors]] | [[GRASS_Community_Meeting_Prague_2023#Report_and_press_release|Press release]]

<gallery mode="slideshow">
Image:Prague-Community-Meeting-2023-crop.jpg|Prague 2023 Group Photo
Image:Day3-table.jpg|A full work table during the 3rd day
Image:Day3-collaboration.jpg|Lots of discussion and collaboration
Image:GRASS-smiles.jpg|GRASS GIS development brings smiles
Image:Day2-collaboration.jpg|Afternoon working and collaborating
Image:Beer-and-work-day4.jpg|The work and discussion continues over dinner
Image:Group-photo-hike.jpg|View at Alšova vyhlídka while taking a walk together
</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]]
* [https://www.osgeo.org/ OSGeo]: 7303 USD (approved budget contribution, [https://www.loomio.com/p/2m75BZkL/motion-to-approve-7303-to-support-grass-gis-community-meeting motion])
* Twitter: [https://twitter.com/OSGeo/ @OSGeo] | [https://fosstodon.org/@osgeo @osgeo@fosstodon.org]

[[File:FOSSGIS_eV_logo.png|none|left|400px|alt=Logo of FOSSGIS e.V.|FOSSGIS e.V.]]
* [https://www.fossgis.de/ FOSSGIS e.V.]: 5000 EUR (approved budget contribution, [https://www.fossgis.de/wiki/F%C3%B6rderantr%C3%A4ge/GRASS_GIS_Community_Meeting_2023 request])
* Twitter: [https://twitter.com/FOSSGIS_Verein @FOSSGIS_Verein] | [https://mastodon.online/@FOSSGISeV/ @FOSSGISeV@mastodon.online]

[[File:OSGeo JP logo for web.png|none|left|400px|alt=OSGeo.JP]]
* [https://www.osgeo.jp/ OSGeo Japan]: 550 USD (through Open Collective)

Individuals:
* Hernán De Angelis 20 USD
* MarWe 50 USD
* Nick Brady 50 USD
* José Ramón 50 USD
* Bon 50 USD
* Johannes Brauner 30 USD
* Peter Löwe 30 USD
* Evan Kay 10 USD
* Joaquin Perez Valera 5 USD
* Anonymous sponsors 2750 USD

In-kind contributions:

* Department of Geomatics Faculty of Civil Engineering Czech Technical University in Prague (FCE CTU) - space and personnel time (planning, preparation, participation)
* North Carolina State University, Center for Geospatial Analytics - personnel time (planning, preparation, participation)
* mundialis GmbH & Co. KG - personnel time (planning, preparation, participation)
* CONICET - personnel time (planning, preparation, participation)
* Research Institute for Nature and Forest (INBO | Brussels, Belgium) – personnel time + travel and hotel costs of INBO staff
* SunGIS – personnel time, travel, and hotel costs of Maris Nartiss
* OpenPlains Inc. – personnel time

Personal time and/or financial contributions:
* Martin Landa, Micha Silver, Helmut Kudrnovsky, Markus Neleter, Ondřej Pešek, Helena Mitasova, Vaclav Petras, Anna Petrasova, Corey White, Maris Nartiss, Aaron Saw Min Sern, Luís de Sousa, Caitlin Haedrich, Linda Kladivová, Carmen Tawalika, Floris Vanderhaeghe, Eva Stopkova, Brendan Harmon, Veronica Andreo, Daniel Torres, Loïc Bartoletti

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

* 9:00 meeting starts in the room B-868
* Lunch: 12:45 NTK
* 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
* Convert GRASS GIS documentation from HTML to Markdown and implement new documentation system (mkdocs?)
* Group photo 1
* Outdoor social evening

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

* Compilation CMake (Windows, Linux)
* Connections in general, rgrass, qgisprocess
* GRASS GIS addons overview generator for entire GitHub (and more?) based on tag "[https://github.com/topics/grass-gis-addons grass-gis-addons]"
* Group photo 2

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

* Connections in general, QGIS, rgrass, qgisprocess
* Parallelizations
* grass.jupyter
* [https://github.com/OSGeo/grass/discussions/3047 Meeting minutes from call with Nyall Dawson (QGIS)]

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

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

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

* Departure

=== Social events ===

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

Dinner at 7pm: [https://www.uveverky.com/kontakt/ U veverku pub] ([https://en.mapy.cz/s/jumomotupu map])

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

Dinner at 6pm: [https://unetickypivovar.cz/en Únětický pivovar] ([https://en.mapy.cz/s/mubutetoba map])

* 3:50pm train from Podbaba (15min walk) to Roztoky
* [https://en.mapy.cz/s/dabavojufa walk 1:30min]
* Bus (355) back from Unetice to Dejvicka: 21:57 or 23:18

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

Dinner at 7pm: [https://www.restauracevltava.cz/ Restaurace Vltava] ([https://en.mapy.cz/s/gonezofozo map])

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

Dinner at 7pm: [https://www.my-paprika.com/ My Paprika] ([https://en.mapy.cz/s/modekehepu map])

* Tram 26 from Dejvicka to Strossmayerovo namesti at 6:26pm

== 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 (14:30)
| June 6 (12:00)
| Improvements of imagery modules (push i.svm.*; i.signatures; ?)
|-
|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)
|
|-
|17
| Eva Stopkova
| Czech Republic
| June 3
| June 4
| Fixing v.nnstat
|
|-
|}

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]

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
|[[User:Baharmon|Brendan Harmon]]
| United States
| Update integration with QGIS
| Available 8:00 AM CST (UTC-6) onwards
|
|-
|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 ====

Follow Gitter.

=== Collaborative document scratching ===

Follow Gitter.

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

== Broadcast & Video ==

During the event :) Find the latest information on the [https://matrix.to/#/#grassgis_sprint:gitter.im Gitter Channel].

== Photos ==
Day 1
<gallery mode="slideshow">
Image:Devs at work.jpg|Hard at work on the first day
Image:Lively discussion.jpg|Lively discussion
Image:Dinner day 1.jpg|Dinner at a nearby pub
</gallery>

Day 2
<gallery mode="slideshow">
Image:Prague-Community-Meeting-2023.jpg|Group photo
Image:PXL 20230603 085440353.jpg|A full table on day 2
Image:GRASS-smiles.jpg|GRASS GIS development brings smiles
Image:Day2-pizza.jpg|Pizza fuels work!
Image:Day2-collaboration.jpg|Afternoon working and collaborating
Image:Group-photo-hike.jpg|View at Alšova vyhlídka on the way to Únětický pivovar (brewery)
Image:Únětický pivovar.jpg|Beer at Únětický pivovar, a 300-year-old brewery, after a day of hard work
</gallery>

Day 3
<gallery mode="slideshow">
Image:Day3-working.jpg|Working on new features, bug fixes, documentation and more..
Image:Day3-table.jpg|An even fuller table on day 3
Image:Day3-collaboration.jpg|Collaboration and discussion
Image:Beer-pano-day3.jpg|Panoramic photo of a cheers to GRASS's 40th Birthday at Vitala restaurant
</gallery>

Day 4
<gallery mode="slideshow">
Image:Group-photo2-day4.jpg|Group photo on Day 4 on the steps of CVUT Praha
Image:Qgis-call-day4.jpg|Discussing QGIS integration
Image:Toast-grass-40th-birthday.jpg|A toast to GRASS GIS's 40th Birthday and a successful meeting
Image:Beer-and-work-day4.jpg|The work and discussion continues over dinner
</gallery>

== 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]]

GRASS Community Meeting Prague 2023

2023-08-07T15:07:47Z

⚠️Wenzeslaus: Add quick links, Switch to past tense in header

{{toc|right}}
The GRASS GIS team organized a ''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).

Quick links: [[Talk:GRASS Community Meeting Prague 2023|Full activity report]] | [[Sponsors#Thanks_to_our_sponsors|Sponsors]] | [[GRASS_Community_Meeting_Prague_2023#Report_and_press_release|Press release]]

<gallery mode="slideshow">
Image:Prague-Community-Meeting-2023-crop.jpg|Prague 2023 Group Photo
Image:Day3-table.jpg|A full work table during the 3rd day
Image:Day3-collaboration.jpg|Lots of discussion and collaboration
Image:GRASS-smiles.jpg|GRASS GIS development brings smiles
Image:Day2-collaboration.jpg|Afternoon working and collaborating
Image:Beer-and-work-day4.jpg|The work and discussion continues over dinner
Image:Group-photo-hike.jpg|View at Alšova vyhlídka while taking a walk together
</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]]
* [https://www.osgeo.org/ OSGeo]: 7303 USD (approved budget contribution, [https://www.loomio.com/p/2m75BZkL/motion-to-approve-7303-to-support-grass-gis-community-meeting motion])
* Twitter: [https://twitter.com/OSGeo/ @OSGeo] | [https://fosstodon.org/@osgeo @osgeo@fosstodon.org]

[[File:FOSSGIS_eV_logo.png|none|left|400px|alt=Logo of FOSSGIS e.V.|FOSSGIS e.V.]]
* [https://www.fossgis.de/ FOSSGIS e.V.]: 5000 EUR (approved budget contribution, [https://www.fossgis.de/wiki/F%C3%B6rderantr%C3%A4ge/GRASS_GIS_Community_Meeting_2023 request])
* Twitter: [https://twitter.com/FOSSGIS_Verein @FOSSGIS_Verein] | [https://mastodon.online/@FOSSGISeV/ @FOSSGISeV@mastodon.online]

[[File:OSGeo JP logo for web.png|none|left|400px|alt=OSGeo.JP]]
* [https://www.osgeo.jp/ OSGeo Japan]: 550 USD (through Open Collective)

Individuals:
* Hernán De Angelis 20 USD
* MarWe 50 USD
* Nick Brady 50 USD
* José Ramón 50 USD
* Bon 50 USD
* Johannes Brauner 30 USD
* Peter Löwe 30 USD
* Evan Kay 10 USD
* Joaquin Perez Valera 5 USD
* Anonymous sponsors 2750 USD

In-kind contributions:

* Department of Geomatics Faculty of Civil Engineering Czech Technical University in Prague (FCE CTU) - space and personnel time (planning, preparation, participation)
* North Carolina State University, Center for Geospatial Analytics - personnel time (planning, preparation, participation)
* mundialis GmbH & Co. KG - personnel time (planning, preparation, participation)
* CONICET - personnel time (planning, preparation, participation)
* Research Institute for Nature and Forest (INBO | Brussels, Belgium) – personnel time + travel and hotel costs of INBO staff
* SunGIS – personnel time, travel, and hotel costs of Maris Nartiss
* OpenPlains Inc. – personnel time

Personal time and/or financial contributions:
* Martin Landa, Micha Silver, Helmut Kudrnovsky, Markus Neleter, Ondřej Pešek, Helena Mitasova, Vaclav Petras, Anna Petrasova, Corey White, Maris Nartiss, Aaron Saw Min Sern, Luís de Sousa, Caitlin Haedrich, Linda Kladivová, Carmen Tawalika, Floris Vanderhaeghe, Eva Stopkova, Brendan Harmon, Veronica Andreo, Daniel Torres, Loïc Bartoletti

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

* 9:00 meeting starts in the room B-868
* Lunch: 12:45 NTK
* 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
* Convert GRASS GIS documentation from HTML to Markdown and implement new documentation system (mkdocs?)
* Group photo 1
* Outdoor social evening

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

* Compilation CMake (Windows, Linux)
* Connections in general, rgrass, qgisprocess
* GRASS GIS addons overview generator for entire GitHub (and more?) based on tag "[https://github.com/topics/grass-gis-addons grass-gis-addons]"
* Group photo 2

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

* Connections in general, QGIS, rgrass, qgisprocess
* Parallelizations
* grass.jupyter
* [https://github.com/OSGeo/grass/discussions/3047 Meeting minutes from call with Nyall Dawson (QGIS)]

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

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

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

* Departure

=== Social events ===

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

Dinner at 7pm: [https://www.uveverky.com/kontakt/ U veverku pub] ([https://en.mapy.cz/s/jumomotupu map])

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

Dinner at 6pm: [https://unetickypivovar.cz/en Únětický pivovar] ([https://en.mapy.cz/s/mubutetoba map])

* 3:50pm train from Podbaba (15min walk) to Roztoky
* [https://en.mapy.cz/s/dabavojufa walk 1:30min]
* Bus (355) back from Unetice to Dejvicka: 21:57 or 23:18

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

Dinner at 7pm: [https://www.restauracevltava.cz/ Restaurace Vltava] ([https://en.mapy.cz/s/gonezofozo map])

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

Dinner at 7pm: [https://www.my-paprika.com/ My Paprika] ([https://en.mapy.cz/s/modekehepu map])

* Tram 26 from Dejvicka to Strossmayerovo namesti at 6:26pm

== 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 (14:30)
| June 6 (12:00)
| Improvements of imagery modules (push i.svm.*; i.signatures; ?)
|-
|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)
|
|-
|17
| Eva Stopkova
| Czech Republic
| June 3
| June 4
| Fixing v.nnstat
|
|-
|}

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]

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
|[[User:Baharmon|Brendan Harmon]]
| United States
| Update integration with QGIS
| Available 8:00 AM CST (UTC-6) onwards
|
|-
|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 ====

Follow Gitter.

=== Collaborative document scratching ===

Follow Gitter.

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

== Broadcast & Video ==

During the event :) Find the latest information on the [https://matrix.to/#/#grassgis_sprint:gitter.im Gitter Channel].

== Photos ==
Day 1
<gallery mode="slideshow">
Image:Devs at work.jpg|Hard at work on the first day
Image:Lively discussion.jpg|Lively discussion
Image:Dinner day 1.jpg|Dinner at a nearby pub
</gallery>

Day 2
<gallery mode="slideshow">
Image:Prague-Community-Meeting-2023.jpg|Group photo
Image:PXL 20230603 085440353.jpg|A full table on day 2
Image:GRASS-smiles.jpg|GRASS GIS development brings smiles
Image:Day2-pizza.jpg|Pizza fuels work!
Image:Day2-collaboration.jpg|Afternoon working and collaborating
Image:Group-photo-hike.jpg|View at Alšova vyhlídka on the way to Únětický pivovar (brewery)
Image:Únětický pivovar.jpg|Beer at Únětický pivovar, a 300-year-old brewery, after a day of hard work
</gallery>

Day 3
<gallery mode="slideshow">
Image:Day3-working.jpg|Working on new features, bug fixes, documentation and more..
Image:Day3-table.jpg|An even fuller table on day 3
Image:Day3-collaboration.jpg|Collaboration and discussion
Image:Beer-pano-day3.jpg|Panoramic photo of a cheers to GRASS's 40th Birthday at Vitala restaurant
</gallery>

Day 4
<gallery mode="slideshow">
Image:Group-photo2-day4.jpg|Group photo on Day 4 on the steps of CVUT Praha
Image:Qgis-call-day4.jpg|Discussing QGIS integration
Image:Toast-grass-40th-birthday.jpg|A toast to GRASS GIS's 40th Birthday and a successful meeting
Image:Beer-and-work-day4.jpg|The work and discussion continues over dinner
</gallery>

== 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]]

GRASS Community Meeting Prague 2023

2023-08-07T15:04:52Z

⚠️Wenzeslaus:

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

Quick links:

* [[GRASS Community Meeting Prague 2023:Talk|Full activity report]]
* [[Sponsors#Thanks_to_our_sponsors|Sponsors]]
* [[GRASS_Community_Meeting_Prague_2023#Report_and_press_release|Press release]]

<gallery mode="slideshow">
Image:Prague-Community-Meeting-2023-crop.jpg|Prague 2023 Group Photo
Image:Day3-table.jpg|A full work table during the 3rd day
Image:Day3-collaboration.jpg|Lots of discussion and collaboration
Image:GRASS-smiles.jpg|GRASS GIS development brings smiles
Image:Day2-collaboration.jpg|Afternoon working and collaborating
Image:Beer-and-work-day4.jpg|The work and discussion continues over dinner
Image:Group-photo-hike.jpg|View at Alšova vyhlídka while taking a walk together
</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]]
* [https://www.osgeo.org/ OSGeo]: 7303 USD (approved budget contribution, [https://www.loomio.com/p/2m75BZkL/motion-to-approve-7303-to-support-grass-gis-community-meeting motion])
* Twitter: [https://twitter.com/OSGeo/ @OSGeo] | [https://fosstodon.org/@osgeo @osgeo@fosstodon.org]

[[File:FOSSGIS_eV_logo.png|none|left|400px|alt=Logo of FOSSGIS e.V.|FOSSGIS e.V.]]
* [https://www.fossgis.de/ FOSSGIS e.V.]: 5000 EUR (approved budget contribution, [https://www.fossgis.de/wiki/F%C3%B6rderantr%C3%A4ge/GRASS_GIS_Community_Meeting_2023 request])
* Twitter: [https://twitter.com/FOSSGIS_Verein @FOSSGIS_Verein] | [https://mastodon.online/@FOSSGISeV/ @FOSSGISeV@mastodon.online]

[[File:OSGeo JP logo for web.png|none|left|400px|alt=OSGeo.JP]]
* [https://www.osgeo.jp/ OSGeo Japan]: 550 USD (through Open Collective)

Individuals:
* Hernán De Angelis 20 USD
* MarWe 50 USD
* Nick Brady 50 USD
* José Ramón 50 USD
* Bon 50 USD
* Johannes Brauner 30 USD
* Peter Löwe 30 USD
* Evan Kay 10 USD
* Joaquin Perez Valera 5 USD
* Anonymous sponsors 2750 USD

In-kind contributions:

* Department of Geomatics Faculty of Civil Engineering Czech Technical University in Prague (FCE CTU) - space and personnel time (planning, preparation, participation)
* North Carolina State University, Center for Geospatial Analytics - personnel time (planning, preparation, participation)
* mundialis GmbH & Co. KG - personnel time (planning, preparation, participation)
* CONICET - personnel time (planning, preparation, participation)
* Research Institute for Nature and Forest (INBO | Brussels, Belgium) – personnel time + travel and hotel costs of INBO staff
* SunGIS – personnel time, travel, and hotel costs of Maris Nartiss
* OpenPlains Inc. – personnel time

Personal time and/or financial contributions:
* Martin Landa, Micha Silver, Helmut Kudrnovsky, Markus Neleter, Ondřej Pešek, Helena Mitasova, Vaclav Petras, Anna Petrasova, Corey White, Maris Nartiss, Aaron Saw Min Sern, Luís de Sousa, Caitlin Haedrich, Linda Kladivová, Carmen Tawalika, Floris Vanderhaeghe, Eva Stopkova, Brendan Harmon, Veronica Andreo, Daniel Torres, Loïc Bartoletti

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

* 9:00 meeting starts in the room B-868
* Lunch: 12:45 NTK
* 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
* Convert GRASS GIS documentation from HTML to Markdown and implement new documentation system (mkdocs?)
* Group photo 1
* Outdoor social evening

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

* Compilation CMake (Windows, Linux)
* Connections in general, rgrass, qgisprocess
* GRASS GIS addons overview generator for entire GitHub (and more?) based on tag "[https://github.com/topics/grass-gis-addons grass-gis-addons]"
* Group photo 2

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

* Connections in general, QGIS, rgrass, qgisprocess
* Parallelizations
* grass.jupyter
* [https://github.com/OSGeo/grass/discussions/3047 Meeting minutes from call with Nyall Dawson (QGIS)]

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

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

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

* Departure

=== Social events ===

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

Dinner at 7pm: [https://www.uveverky.com/kontakt/ U veverku pub] ([https://en.mapy.cz/s/jumomotupu map])

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

Dinner at 6pm: [https://unetickypivovar.cz/en Únětický pivovar] ([https://en.mapy.cz/s/mubutetoba map])

* 3:50pm train from Podbaba (15min walk) to Roztoky
* [https://en.mapy.cz/s/dabavojufa walk 1:30min]
* Bus (355) back from Unetice to Dejvicka: 21:57 or 23:18

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

Dinner at 7pm: [https://www.restauracevltava.cz/ Restaurace Vltava] ([https://en.mapy.cz/s/gonezofozo map])

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

Dinner at 7pm: [https://www.my-paprika.com/ My Paprika] ([https://en.mapy.cz/s/modekehepu map])

* Tram 26 from Dejvicka to Strossmayerovo namesti at 6:26pm

== 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 (14:30)
| June 6 (12:00)
| Improvements of imagery modules (push i.svm.*; i.signatures; ?)
|-
|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)
|
|-
|17
| Eva Stopkova
| Czech Republic
| June 3
| June 4
| Fixing v.nnstat
|
|-
|}

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]

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
|[[User:Baharmon|Brendan Harmon]]
| United States
| Update integration with QGIS
| Available 8:00 AM CST (UTC-6) onwards
|
|-
|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 ====

Follow Gitter.

=== Collaborative document scratching ===

Follow Gitter.

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

== Broadcast & Video ==

During the event :) Find the latest information on the [https://matrix.to/#/#grassgis_sprint:gitter.im Gitter Channel].

== Photos ==
Day 1
<gallery mode="slideshow">
Image:Devs at work.jpg|Hard at work on the first day
Image:Lively discussion.jpg|Lively discussion
Image:Dinner day 1.jpg|Dinner at a nearby pub
</gallery>

Day 2
<gallery mode="slideshow">
Image:Prague-Community-Meeting-2023.jpg|Group photo
Image:PXL 20230603 085440353.jpg|A full table on day 2
Image:GRASS-smiles.jpg|GRASS GIS development brings smiles
Image:Day2-pizza.jpg|Pizza fuels work!
Image:Day2-collaboration.jpg|Afternoon working and collaborating
Image:Group-photo-hike.jpg|View at Alšova vyhlídka on the way to Únětický pivovar (brewery)
Image:Únětický pivovar.jpg|Beer at Únětický pivovar, a 300-year-old brewery, after a day of hard work
</gallery>

Day 3
<gallery mode="slideshow">
Image:Day3-working.jpg|Working on new features, bug fixes, documentation and more..
Image:Day3-table.jpg|An even fuller table on day 3
Image:Day3-collaboration.jpg|Collaboration and discussion
Image:Beer-pano-day3.jpg|Panoramic photo of a cheers to GRASS's 40th Birthday at Vitala restaurant
</gallery>

Day 4
<gallery mode="slideshow">
Image:Group-photo2-day4.jpg|Group photo on Day 4 on the steps of CVUT Praha
Image:Qgis-call-day4.jpg|Discussing QGIS integration
Image:Toast-grass-40th-birthday.jpg|A toast to GRASS GIS's 40th Birthday and a successful meeting
Image:Beer-and-work-day4.jpg|The work and discussion continues over dinner
</gallery>

== 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]]

GRASS Community Meeting Prague 2023

2023-08-02T16:52:19Z

⚠️Wenzeslaus: /* In person */ fix table syntax

{{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:Prague-Community-Meeting-2023-crop.jpg|Prague 2023 Group Photo
Image:Day3-table.jpg|A full work table during the 3rd day
Image:Day3-collaboration.jpg|Lots of discussion and collaboration
Image:GRASS-smiles.jpg|GRASS GIS development brings smiles
Image:Day2-collaboration.jpg|Afternoon working and collaborating
Image:Beer-and-work-day4.jpg|The work and discussion continues over dinner
Image:Group-photo-hike.jpg|View at Alšova vyhlídka while taking a walk together
</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]]
* [https://www.osgeo.org/ OSGeo]: 7303 USD (approved budget contribution, [https://www.loomio.com/p/2m75BZkL/motion-to-approve-7303-to-support-grass-gis-community-meeting motion])
* Twitter: [https://twitter.com/OSGeo/ @OSGeo] | [https://fosstodon.org/@osgeo @osgeo@fosstodon.org]

[[File:FOSSGIS_eV_logo.png|none|left|400px|alt=Logo of FOSSGIS e.V.|FOSSGIS e.V.]]
* [https://www.fossgis.de/ FOSSGIS e.V.]: 5000 EUR (approved budget contribution, [https://www.fossgis.de/wiki/F%C3%B6rderantr%C3%A4ge/GRASS_GIS_Community_Meeting_2023 request])
* Twitter: [https://twitter.com/FOSSGIS_Verein @FOSSGIS_Verein] | [https://mastodon.online/@FOSSGISeV/ @FOSSGISeV@mastodon.online]

[[File:OSGeo JP logo for web.png|none|left|400px|alt=OSGeo.JP]]
* [https://www.osgeo.jp/ OSGeo Japan]: 550 USD (through Open Collective)

Individuals:
* Hernán De Angelis 20 USD
* MarWe 50 USD
* Nick Brady 50 USD
* José Ramón 50 USD
* Bon 50 USD
* Johannes Brauner 30 USD
* Peter Löwe 30 USD
* Evan Kay 10 USD
* Joaquin Perez Valera 5 USD
* Anonymous sponsors 2750 USD

In-kind contributions:

* Department of Geomatics Faculty of Civil Engineering Czech Technical University in Prague (FCE CTU) - space and personnel time (planning, preparation, participation)
* North Carolina State University, Center for Geospatial Analytics - personnel time (planning, preparation, participation)
* mundialis GmbH & Co. KG - personnel time (planning, preparation, participation)
* CONICET - personnel time (planning, preparation, participation)
* Research Institute for Nature and Forest (INBO | Brussels, Belgium) – personnel time + travel and hotel costs of INBO staff
* SunGIS – personnel time, travel, and hotel costs of Maris Nartiss
* OpenPlains Inc. – personnel time

Personal time and/or financial contributions:
* Martin Landa, Micha Silver, Helmut Kudrnovsky, Markus Neleter, Ondřej Pešek, Helena Mitasova, Vaclav Petras, Anna Petrasova, Corey White, Maris Nartiss, Aaron Saw Min Sern, Luís de Sousa, Caitlin Haedrich, Linda Kladivová, Carmen Tawalika, Floris Vanderhaeghe, Eva Stopkova, Brendan Harmon, Veronica Andreo, Daniel Torres, Loïc Bartoletti

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

* 9:00 meeting starts in the room B-868
* Lunch: 12:45 NTK
* 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
* Convert GRASS GIS documentation from HTML to Markdown and implement new documentation system (mkdocs?)
* Group photo 1
* Outdoor social evening

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

* Compilation CMake (Windows, Linux)
* Connections in general, rgrass, qgisprocess
* GRASS GIS addons overview generator for entire GitHub (and more?) based on tag "[https://github.com/topics/grass-gis-addons grass-gis-addons]"
* Group photo 2

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

* Connections in general, QGIS, rgrass, qgisprocess
* Parallelizations
* grass.jupyter
* [https://github.com/OSGeo/grass/discussions/3047 Meeting minutes from call with Nyall Dawson (QGIS)]

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

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

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

* Departure

=== Social events ===

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

Dinner at 7pm: [https://www.uveverky.com/kontakt/ U veverku pub] ([https://en.mapy.cz/s/jumomotupu map])

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

Dinner at 6pm: [https://unetickypivovar.cz/en Únětický pivovar] ([https://en.mapy.cz/s/mubutetoba map])

* 3:50pm train from Podbaba (15min walk) to Roztoky
* [https://en.mapy.cz/s/dabavojufa walk 1:30min]
* Bus (355) back from Unetice to Dejvicka: 21:57 or 23:18

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

Dinner at 7pm: [https://www.restauracevltava.cz/ Restaurace Vltava] ([https://en.mapy.cz/s/gonezofozo map])

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

Dinner at 7pm: [https://www.my-paprika.com/ My Paprika] ([https://en.mapy.cz/s/modekehepu map])

* Tram 26 from Dejvicka to Strossmayerovo namesti at 6:26pm

== 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 (14:30)
| June 6 (12:00)
| Improvements of imagery modules (push i.svm.*; i.signatures; ?)
|-
|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)
|
|-
|17
| Eva Stopkova
| Czech Republic
| June 3
| June 4
| Fixing v.nnstat
|
|-
|}

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]

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
|[[User:Baharmon|Brendan Harmon]]
| United States
| Update integration with QGIS
| Available 8:00 AM CST (UTC-6) onwards
|
|-
|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 ====

Follow Gitter.

=== Collaborative document scratching ===

Follow Gitter.

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

== Broadcast & Video ==

During the event :) Find the latest information on the [https://matrix.to/#/#grassgis_sprint:gitter.im Gitter Channel].

== Photos ==
Day 1
<gallery mode="slideshow">
Image:Devs at work.jpg|Hard at work on the first day
Image:Lively discussion.jpg|Lively discussion
Image:Dinner day 1.jpg|Dinner at a nearby pub
</gallery>

Day 2
<gallery mode="slideshow">
Image:Prague-Community-Meeting-2023.jpg|Group photo
Image:PXL 20230603 085440353.jpg|A full table on day 2
Image:GRASS-smiles.jpg|GRASS GIS development brings smiles
Image:Day2-pizza.jpg|Pizza fuels work!
Image:Day2-collaboration.jpg|Afternoon working and collaborating
Image:Group-photo-hike.jpg|View at Alšova vyhlídka on the way to Únětický pivovar (brewery)
Image:Únětický pivovar.jpg|Beer at Únětický pivovar, a 300-year-old brewery, after a day of hard work
</gallery>

Day 3
<gallery mode="slideshow">
Image:Day3-working.jpg|Working on new features, bug fixes, documentation and more..
Image:Day3-table.jpg|An even fuller table on day 3
Image:Day3-collaboration.jpg|Collaboration and discussion
Image:Beer-pano-day3.jpg|Panoramic photo of a cheers to GRASS's 40th Birthday at Vitala restaurant
</gallery>

Day 4
<gallery mode="slideshow">
Image:Group-photo2-day4.jpg|Group photo on Day 4 on the steps of CVUT Praha
Image:Qgis-call-day4.jpg|Discussing QGIS integration
Image:Toast-grass-40th-birthday.jpg|A toast to GRASS GIS's 40th Birthday and a successful meeting
Image:Beer-and-work-day4.jpg|The work and discussion continues over dinner
</gallery>

== 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]]

Talk:GRASS Community Meeting Prague 2023

2023-07-13T21:09:14Z

⚠️Wenzeslaus: /* Discussion with Nyall (QGIS) */ rename section and link minutes, Add one for R

__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 about naming, advantages, and challenges
* Python API and CLI
** [https://github.com/OSGeo/grass/pull/2923 grass.experimental: Add object to access modules as functions #2923]
** Discussion about creating locations from Python ([https://github.com/OSGeo/grass/issues/3034 Issue: make gscript.create_location() callable from outside #3034])
** [https://github.com/OSGeo/grass/issues/3007 Issue: Add g.findfile alternative which hides format complexities #3007]
* QGIS
** Group call to identify priorities with Nyall Dawson
* R
** Discussion with Floris Vanderhaeghe, Roger Bivand, and others assessing the current state
* GUI
** Discussion about streamlined startup
** [https://github.com/OSGeo/grass/pull/3049 wxGUI: Ignore stderr of the GUI #3049]
* CI
** [https://github.com/OSGeo/grass/pull/3002 CI: Switch Travis to Ubuntu 22.04 (jammmy) #3002]
** [https://github.com/OSGeo/grass/pull/3014 CI: Reduce number of Python jobs #3014]
** [https://github.com/OSGeo/grass-addons/pull/921 CI: Test with v8.3, Python 3.7 #921]
* Release 8.3.0
** Work with Markus Neteler to prepare release
* Contributing:
** [https://github.com/OSGeo/grass/pull/3048 contributing: Add empty line after heading in release notes #3048]
** [https://github.com/OSGeo/grass/pull/3035 contributing: Add more expressions to match release notes groups #3035]
* Reviews:
** [https://github.com/OSGeo/grass/pull/2189 Imagery: add libsvm based imagery classification #2189]
** [https://github.com/OSGeo/grass/pull/2974 t.rast.algebra/testsuite: split file test_raster_algebra.py #2974]
** [https://github.com/OSGeo/grass-addons/pull/606 r.random.walk: Add module to create random walks #606]
** [https://github.com/OSGeo/grass/pull/2930 r.surf.random: Added seed option and flag to module #2930]
** [https://github.com/OSGeo/grass/pull/3008 i.signatures: Add imagery classifier signature management module #3008]
** [https://github.com/OSGeo/grass/pull/3037 r.patch: ensure r.in.ascii in relevant tests always create CELL #3037]
** [https://github.com/OSGeo/grass-addons/pull/911 r.mblend: basic tests #911]
** [https://github.com/OSGeo/grass/pull/3010 grass.unittest: Fix usage of assertRegexpMatches() removed from Python 3.12 #3010]
** [https://github.com/OSGeo/grass/pull/3011 grass.gunittest: Fix usage of assertNotRegexMatches() removed from Python 3.12 #3011]
** [https://github.com/OSGeo/grass/pull/3009 grass.gunittest: Fix usage of assertEquals() removed from Python 3.12 #3009]
** [https://github.com/OSGeo/grass-addons/pull/917 grass.gunittest: Fix usage of assertEquals() removed from Python 3.12 #917]
** [https://github.com/OSGeo/grass/pull/2992 wxGUI/query: set region matching the raster for each raster queried #2992]
** [https://github.com/OSGeo/grass/pull/2997 wxGUI/gmodeler: Show ModelRelation in white on dark mode #2997]
** [https://github.com/OSGeo/grass/pull/3015 Locale: extract translatable messages also from C++ files #3015]
** [https://github.com/OSGeo/grass/pull/3029 doc: Document that lists in parser must be NULL terminated #3029]
** [https://github.com/OSGeo/grass/pull/3006 contributing: Expand instructions on pre-commit #3006]
** [https://github.com/OSGeo/grass/pull/3030 contributing: minor release procedure updates (main) #3030]
** [https://github.com/OSGeo/grass/pull/3031 contributing: release procedure updates (G82) #3031]
** [https://github.com/OSGeo/grass/pull/3032 contributing: release procedure updates (G83) #3032]
** [https://github.com/OSGeo/grass-addons/pull/916 contributing: adds instructions on unit tests for add-ons #916]
** [https://github.com/OSGeo/grass/pull/3012 contributing: Remove parts of locale readme already present in submitting guidelines #3012]

See also [https://github.com/wenzeslaus?tab=overview&from=2023-06-01&to=2023-06-30 June activity log on GitHub].

=== 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 (https://github.com/rsbivand/rgrass/discussions/78)
* Participate in a two-hour meeting with Nyall Dawson (QGIS) and the GRASS Community about interfacing GRASS from QGIS (https://github.com/OSGeo/grass/discussions/3047)

=== 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 on interfacing GRASS from QGIS ==

* Special guest: Nyall Dawson (QGIS)
* All meeting participants were part of the call.
* 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

Complete minutes are in the GitHub Discussion [https://github.com/OSGeo/grass/discussions/3047 ''Meeting minutes on interfacing GRASS from QGIS'' #3047].

== Discussion on using GRASS from R ==

* Special guest: Roger Bivand (rgrass, ...)
* Attended by 7+ participants

Complete minutes are in the GitHub Discussion [https://github.com/rsbivand/rgrass/discussions/78 ''Meeting minutes on interfacing GRASS from R'' #78].

== 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-07-13T18:21:51Z

⚠️Wenzeslaus: /* Thanks to our sponsors */ Add sponsor for Prague meeting tier from June 11

{{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:Prague-Community-Meeting-2023-crop.jpg|Prague 2023 Group Photo
Image:Day3-table.jpg|A full work table during the 3rd day
Image:Day3-collaboration.jpg|Lots of discussion and collaboration
Image:GRASS-smiles.jpg|GRASS GIS development brings smiles
Image:Day2-collaboration.jpg|Afternoon working and collaborating
Image:Beer-and-work-day4.jpg|The work and discussion continues over dinner
Image:Group-photo-hike.jpg|View at Alšova vyhlídka while taking a walk together
</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]]
* [https://www.osgeo.org/ OSGeo]: 7303 USD (approved budget contribution, [https://www.loomio.com/p/2m75BZkL/motion-to-approve-7303-to-support-grass-gis-community-meeting motion])
* Twitter: [https://twitter.com/OSGeo/ @OSGeo] | [https://fosstodon.org/@osgeo @osgeo@fosstodon.org]

[[File:FOSSGIS_eV_logo.png|none|left|400px|alt=Logo of FOSSGIS e.V.|FOSSGIS e.V.]]
* [https://www.fossgis.de/ FOSSGIS e.V.]: 5000 EUR (approved budget contribution, [https://www.fossgis.de/wiki/F%C3%B6rderantr%C3%A4ge/GRASS_GIS_Community_Meeting_2023 request])
* Twitter: [https://twitter.com/FOSSGIS_Verein @FOSSGIS_Verein] | [https://mastodon.online/@FOSSGISeV/ @FOSSGISeV@mastodon.online]

[[File:OSGeo JP logo for web.png|none|left|400px|alt=OSGeo.JP]]
* [https://www.osgeo.jp/ OSGeo Japan]: 550 USD (through Open Collective)

Individuals:
* Hernán De Angelis 20 USD
* MarWe 50 USD
* Nick Brady 50 USD
* José Ramón 50 USD
* Bon 50 USD
* Johannes Brauner 30 USD
* Peter Löwe 30 USD
* Evan Kay 10 USD
* Joaquin Perez Valera 5 USD
* Anonymous sponsors 2750 USD

In-kind contributions:

* Department of Geomatics Faculty of Civil Engineering Czech Technical University in Prague (FCE CTU) - space and personnel time (planning, preparation, participation)
* North Carolina State University, Center for Geospatial Analytics - personnel time (planning, preparation, participation)
* mundialis GmbH & Co. KG - personnel time (planning, preparation, participation)
* CONICET - personnel time (planning, preparation, participation)
* Research Institute for Nature and Forest (INBO | Brussels, Belgium) – personnel time + travel and hotel costs of INBO staff
* SunGIS – personnel time, travel, and hotel costs of Maris Nartiss
* OpenPlains Inc. – personnel time

Personal time and/or financial contributions:
* Martin Landa, Micha Silver, Helmut Kudrnovsky, Markus Neleter, Ondřej Pešek, Helena Mitasova, Vaclav Petras, Anna Petrasova, Corey White, Maris Nartiss, Aaron Saw Min Sern, Luís de Sousa, Caitlin Haedrich, Linda Kladivová, Carmen Tawalika, Floris Vanderhaeghe, Eva Stopkova, Brendan Harmon, Veronica Andreo, Daniel Torres, Loïc Bartoletti

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

* 9:00 meeting starts in the room B-868
* Lunch: 12:45 NTK
* 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
* Convert GRASS GIS documentation from HTML to Markdown and implement new documentation system (mkdocs?)
* Group photo 1
* Outdoor social evening

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

* Compilation CMake (Windows, Linux)
* Connections in general, rgrass, qgisprocess
* GRASS GIS addons overview generator for entire GitHub (and more?) based on tag "[https://github.com/topics/grass-gis-addons grass-gis-addons]"
* Group photo 2

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

* Connections in general, QGIS, rgrass, qgisprocess
* Parallelizations
* grass.jupyter
* [https://github.com/OSGeo/grass/discussions/3047 Meeting minutes from call with Nyall Dawson (QGIS)]

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

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

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

* Departure

=== Social events ===

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

Dinner at 7pm: [https://www.uveverky.com/kontakt/ U veverku pub] ([https://en.mapy.cz/s/jumomotupu map])

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

Dinner at 6pm: [https://unetickypivovar.cz/en Únětický pivovar] ([https://en.mapy.cz/s/mubutetoba map])

* 3:50pm train from Podbaba (15min walk) to Roztoky
* [https://en.mapy.cz/s/dabavojufa walk 1:30min]
* Bus (355) back from Unetice to Dejvicka: 21:57 or 23:18

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

Dinner at 7pm: [https://www.restauracevltava.cz/ Restaurace Vltava] ([https://en.mapy.cz/s/gonezofozo map])

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

Dinner at 7pm: [https://www.my-paprika.com/ My Paprika] ([https://en.mapy.cz/s/modekehepu map])

* Tram 26 from Dejvicka to Strossmayerovo namesti at 6:26pm

== 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 (14:30)
| June 6 (12:00)
| Improvements of imagery modules (push i.svm.*; i.signatures; ?)
|-
|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)
|
|-|17
| Eva Stopkova
| Czech Republic
| June 3
| June 4
| Fixing v.nnstat
|
|-
|}

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]

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
|[[User:Baharmon|Brendan Harmon]]
| United States
| Update integration with QGIS
| Available 8:00 AM CST (UTC-6) onwards
|
|-
|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 ====

Follow Gitter.

=== Collaborative document scratching ===

Follow Gitter.

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

== Broadcast & Video ==

During the event :) Find the latest information on the [https://matrix.to/#/#grassgis_sprint:gitter.im Gitter Channel].

== Photos ==
Day 1
<gallery mode="slideshow">
Image:Devs at work.jpg|Hard at work on the first day
Image:Lively discussion.jpg|Lively discussion
Image:Dinner day 1.jpg|Dinner at a nearby pub
</gallery>

Day 2
<gallery mode="slideshow">
Image:Prague-Community-Meeting-2023.jpg|Group photo
Image:PXL 20230603 085440353.jpg|A full table on day 2
Image:GRASS-smiles.jpg|GRASS GIS development brings smiles
Image:Day2-pizza.jpg|Pizza fuels work!
Image:Day2-collaboration.jpg|Afternoon working and collaborating
Image:Group-photo-hike.jpg|View at Alšova vyhlídka on the way to Únětický pivovar (brewery)
Image:Únětický pivovar.jpg|Beer at Únětický pivovar, a 300-year-old brewery, after a day of hard work
</gallery>

Day 3
<gallery mode="slideshow">
Image:Day3-working.jpg|Working on new features, bug fixes, documentation and more..
Image:Day3-table.jpg|An even fuller table on day 3
Image:Day3-collaboration.jpg|Collaboration and discussion
Image:Beer-pano-day3.jpg|Panoramic photo of a cheers to GRASS's 40th Birthday at Vitala restaurant
</gallery>

Day 4
<gallery mode="slideshow">
Image:Group-photo2-day4.jpg|Group photo on Day 4 on the steps of CVUT Praha
Image:Qgis-call-day4.jpg|Discussing QGIS integration
Image:Toast-grass-40th-birthday.jpg|A toast to GRASS GIS's 40th Birthday and a successful meeting
Image:Beer-and-work-day4.jpg|The work and discussion continues over dinner
</gallery>

== 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]]

Talk:GRASS Community Meeting Prague 2023

2023-07-13T18:19:15Z

⚠️Wenzeslaus: /* Vaclav Petras */

__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 about naming, advantages, and challenges
* Python API and CLI
** [https://github.com/OSGeo/grass/pull/2923 grass.experimental: Add object to access modules as functions #2923]
** Discussion about creating locations from Python ([https://github.com/OSGeo/grass/issues/3034 Issue: make gscript.create_location() callable from outside #3034])
** [https://github.com/OSGeo/grass/issues/3007 Issue: Add g.findfile alternative which hides format complexities #3007]
* QGIS
** Group call to identify priorities with Nyall Dawson
* R
** Discussion with Floris Vanderhaeghe, Roger Bivand, and others assessing the current state
* GUI
** Discussion about streamlined startup
** [https://github.com/OSGeo/grass/pull/3049 wxGUI: Ignore stderr of the GUI #3049]
* CI
** [https://github.com/OSGeo/grass/pull/3002 CI: Switch Travis to Ubuntu 22.04 (jammmy) #3002]
** [https://github.com/OSGeo/grass/pull/3014 CI: Reduce number of Python jobs #3014]
** [https://github.com/OSGeo/grass-addons/pull/921 CI: Test with v8.3, Python 3.7 #921]
* Release 8.3.0
** Work with Markus Neteler to prepare release
* Contributing:
** [https://github.com/OSGeo/grass/pull/3048 contributing: Add empty line after heading in release notes #3048]
** [https://github.com/OSGeo/grass/pull/3035 contributing: Add more expressions to match release notes groups #3035]
* Reviews:
** [https://github.com/OSGeo/grass/pull/2189 Imagery: add libsvm based imagery classification #2189]
** [https://github.com/OSGeo/grass/pull/2974 t.rast.algebra/testsuite: split file test_raster_algebra.py #2974]
** [https://github.com/OSGeo/grass-addons/pull/606 r.random.walk: Add module to create random walks #606]
** [https://github.com/OSGeo/grass/pull/2930 r.surf.random: Added seed option and flag to module #2930]
** [https://github.com/OSGeo/grass/pull/3008 i.signatures: Add imagery classifier signature management module #3008]
** [https://github.com/OSGeo/grass/pull/3037 r.patch: ensure r.in.ascii in relevant tests always create CELL #3037]
** [https://github.com/OSGeo/grass-addons/pull/911 r.mblend: basic tests #911]
** [https://github.com/OSGeo/grass/pull/3010 grass.unittest: Fix usage of assertRegexpMatches() removed from Python 3.12 #3010]
** [https://github.com/OSGeo/grass/pull/3011 grass.gunittest: Fix usage of assertNotRegexMatches() removed from Python 3.12 #3011]
** [https://github.com/OSGeo/grass/pull/3009 grass.gunittest: Fix usage of assertEquals() removed from Python 3.12 #3009]
** [https://github.com/OSGeo/grass-addons/pull/917 grass.gunittest: Fix usage of assertEquals() removed from Python 3.12 #917]
** [https://github.com/OSGeo/grass/pull/2992 wxGUI/query: set region matching the raster for each raster queried #2992]
** [https://github.com/OSGeo/grass/pull/2997 wxGUI/gmodeler: Show ModelRelation in white on dark mode #2997]
** [https://github.com/OSGeo/grass/pull/3015 Locale: extract translatable messages also from C++ files #3015]
** [https://github.com/OSGeo/grass/pull/3029 doc: Document that lists in parser must be NULL terminated #3029]
** [https://github.com/OSGeo/grass/pull/3006 contributing: Expand instructions on pre-commit #3006]
** [https://github.com/OSGeo/grass/pull/3030 contributing: minor release procedure updates (main) #3030]
** [https://github.com/OSGeo/grass/pull/3031 contributing: release procedure updates (G82) #3031]
** [https://github.com/OSGeo/grass/pull/3032 contributing: release procedure updates (G83) #3032]
** [https://github.com/OSGeo/grass-addons/pull/916 contributing: adds instructions on unit tests for add-ons #916]
** [https://github.com/OSGeo/grass/pull/3012 contributing: Remove parts of locale readme already present in submitting guidelines #3012]

See also [https://github.com/wenzeslaus?tab=overview&from=2023-06-01&to=2023-06-30 June activity log on GitHub].

=== 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 (https://github.com/rsbivand/rgrass/discussions/78)
* Participate in a two-hour meeting with Nyall Dawson (QGIS) and the GRASS Community about interfacing GRASS from QGIS (https://github.com/OSGeo/grass/discussions/3047)

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

Talk:GRASS Community Meeting Prague 2023

2023-07-13T18:17:36Z

⚠️Wenzeslaus: /* Vaclav Petras */ add release

__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 about naming, advantages, and challenges
* Python API and CLI
** [https://github.com/OSGeo/grass/pull/2923 grass.experimental: Add object to access modules as functions #2923]
** Discussion about creating locations from Python ([https://github.com/OSGeo/grass/issues/3034 Issue make gscript.create_location() callable from outside #3034)
** [https://github.com/OSGeo/grass/issues/3007 Issue Add g.findfile alternative which hides format complexities #3007]
* QGIS
** Group call to identify priorities with Nyall Dawson
* R
** Discussion with Floris Vanderhaeghe, Roger Bivand, and others assessing the current state
* GUI
** Discussion about streamlined startup
** [https://github.com/OSGeo/grass/pull/3049 wxGUI: Ignore stderr of the GUI #3049]
* CI
** [https://github.com/OSGeo/grass/pull/3002 CI: Switch Travis to Ubuntu 22.04 (jammmy) #3002]
** [https://github.com/OSGeo/grass/pull/3014 CI: Reduce number of Python jobs #3014]
** [https://github.com/OSGeo/grass-addons/pull/921 CI: Test with v8.3, Python 3.7 #921]
* Release 8.3.0
** Work with Markus Neteler to prepare release
* Contributing:
** [https://github.com/OSGeo/grass/pull/3048 contributing: Add empty line after heading in release notes #3048]
** [https://github.com/OSGeo/grass/pull/3035 contributing: Add more expressions to match release notes groups #3035]
* Reviews:
** [https://github.com/OSGeo/grass/pull/2189 Imagery: add libsvm based imagery classification #2189]
** [https://github.com/OSGeo/grass/pull/2974 t.rast.algebra/testsuite: split file test_raster_algebra.py #2974]
** [https://github.com/OSGeo/grass-addons/pull/606 r.random.walk: Add module to create random walks #606]
** [https://github.com/OSGeo/grass/pull/2930 r.surf.random: Added seed option and flag to module #2930]
** [https://github.com/OSGeo/grass/pull/3008 i.signatures: Add imagery classifier signature management module #3008]
** [https://github.com/OSGeo/grass/pull/3037 r.patch: ensure r.in.ascii in relevant tests always create CELL #3037]
** [https://github.com/OSGeo/grass-addons/pull/911 r.mblend: basic tests #911]
** [https://github.com/OSGeo/grass/pull/3010 grass.unittest: Fix usage of assertRegexpMatches() removed from Python 3.12 #3010]
** [https://github.com/OSGeo/grass/pull/3011 grass.gunittest: Fix usage of assertNotRegexMatches() removed from Python 3.12 #3011]
** [https://github.com/OSGeo/grass/pull/3009 grass.gunittest: Fix usage of assertEquals() removed from Python 3.12 #3009]
** [https://github.com/OSGeo/grass-addons/pull/917 grass.gunittest: Fix usage of assertEquals() removed from Python 3.12 #917]
** [https://github.com/OSGeo/grass/pull/2992 wxGUI/query: set region matching the raster for each raster queried #2992]
** [https://github.com/OSGeo/grass/pull/2997 wxGUI/gmodeler: Show ModelRelation in white on dark mode #2997]
** [https://github.com/OSGeo/grass/pull/3015 Locale: extract translatable messages also from C++ files #3015]
** [https://github.com/OSGeo/grass/pull/3029 doc: Document that lists in parser must be NULL terminated #3029]
** [https://github.com/OSGeo/grass/pull/3006 contributing: Expand instructions on pre-commit #3006]
** [https://github.com/OSGeo/grass/pull/3030 contributing: minor release procedure updates (main) #3030]
** [https://github.com/OSGeo/grass/pull/3031 contributing: release procedure updates (G82) #3031]
** [https://github.com/OSGeo/grass/pull/3032 contributing: release procedure updates (G83) #3032]
** [https://github.com/OSGeo/grass-addons/pull/916 contributing: adds instructions on unit tests for add-ons #916]
** [https://github.com/OSGeo/grass/pull/3012 contributing: Remove parts of locale readme already present in submitting guidelines #3012]

See also [https://github.com/wenzeslaus?tab=overview&from=2023-06-01&to=2023-06-30 June activity log on GitHub].

=== 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 (https://github.com/rsbivand/rgrass/discussions/78)
* Participate in a two-hour meeting with Nyall Dawson (QGIS) and the GRASS Community about interfacing GRASS from QGIS (https://github.com/OSGeo/grass/discussions/3047)

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