We plan to establish working groups to coordinate the GRASS GIS community activities such as software development, documentation, promotion and fostering relations with other communities. The proposed working groups and their tentative scopes include:
Geoprocessing Engine Working Group
- coordinate development of GRASS GIS as a geoprocessing engine
- coordinate development of Python API
- coordinate software distribution
- quality assurance
Open-Source Ecosystem Working Group- foster relation with other software communities such as R and QGIS
- provide guidance to communities how to best integrate GRASS GIS
- identify issues other communities are facing when integrating GRASS GIS
- lower maintenance of GRASS integrations with other software
Documentation and Education Working Group- coordinate development of documentation and education materials
- decide on best formats and place for documentation, tutorials
- coordinate development of sample datasets and localized datasets
- develop onboarding materials for contributors of documentation and education materials
Community Engagement Working Group
- engaging geospatial communities via social networks
- updating GRASS website with news
- coordinate social events (conferences, sprints)
- develop promotional materials (e.g., graphics, swag)
Notes:
- The scope of each group is just a suggestion and each working group would set its priorities.
- You can be part of multiple working groups.
- You don't need to engage in all working group activities, depends on your interest, expertise and available time.
- Managing group activities could be done on grasswiki.osgeo.org, with creating issues in GRASS GitHub repositories. Communication could be done by joining a working group-specific Gitter room for internal discussions and on GRASS mailing lists when addressing entire community. These are just suggestions, each group can decide themselves.
- Working groups are separate from the Project Steering Committee, but will work together as needed.
