GRASS Community Meeting Prague 2023: Difference between revisions

From GRASS-Wiki
Jump to navigation Jump to search
(add more program items)
mNo edit summary
Line 11: Line 11:
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 statistics, OGC Services and willing to '''celebrate with us the 40th GRASS GIS birthday!!'''
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 statistics, OGC Services and willing to '''celebrate with us the 40th GRASS GIS birthday!!'''


During the meeting we will work on GRASS GIS as follows:
For the detailed agenda, see below.
 
* 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.


== Sponsors ==
== Sponsors ==
Line 73: Line 65:


'''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.
'''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 Sprint Prague 2023|here]]''' and below. Topics cover non-technical, semi-technical, and technical issues.
Further details about the action items you '''find [[Talk:GRASS Community Sprint Prague 2023|here]]''' and below. Topics cover non-technical, semi-technical, and technical issues.

Revision as of 09:13, 31 March 2023

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.

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 statistics, OGC Services and willing to celebrate with us the 40th GRASS GIS birthday!!

For the detailed agenda, 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 travelling and accommodation expenses for GRASS developers with far arrival. If you are interested in sponsoring the GRASS Community Meeting, please read about

sponsoring the GRASS GIS project at https://grass.osgeo.org/contribute/sponsoring/

Note that it is also possible to buy a round of beers for the developers with a quick click using the Open Collective "Contribute Money" button https://opencollective.com/osgeo/projects/grass

Any surplus at the end of the event will be turned over to the GRASS GIS project.

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:

TBD

Timing

When: June 2-6, 2023

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

Venue

Department of Geomatics
Faculty of Civil Engineering
Czech Technical University in Prague, Czech Republic
Thákurova 7/2077, Prague
Room B868
Map

Prague has an international 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
  • 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 Czech crown (CZK, koruna, Kč). 100 Czech crowns are about 4 Euros (see 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 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 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 here and below. Topics cover non-technical, semi-technical, and technical issues.

Timeline

Will be specified later.

Friday, 2 June

Saturday, 3 June

Sunday, 4 June

Monday, 5 June

Tuesday, 6 June

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 Martin Landa <landa.martin at gmail.com>:

In person

Number Participant Country Arrival Departure Topics T-Shirt Notes
1 Martin Landa Czech Republic June 2 June 6 XL
2 Micha Silver Israel June 2 June 6 Addon to derive soil moisture from Sentinel 2 XXL
3 Helmut Kudrnovsky Austria June 2 June 4 L
4 Markus Neteler Germany June 2 June 6 L
5 Ondřej Pešek Czech Republic June 2 June 6 M
x Add your name

Via chat or hangout

Join our Gitter chatroom

TBD: Google Meet / Zoom / ???

Timing of hangout meetings

TBD

Collaborative document scratching

TBD

Individual Preparation

  • Bring your own computer
  • Bring power connector adapter if needed (Czech Republic: 230V, 50Hz, Type C Europlugs are common and also Type E)
  • Install subversion and the compiler tools, and come with a working GRASS development environment if possible.

Broadcast & Video

During the event :)

Photos

Also during the event :)

FAQ

  • How was it last time?
  • 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?

Press Release

TBD: After the event :-)