| | 54 | == Minutes == |
| | 55 | |
| | 56 | * We reviewed last minutes and set new action points |
| | 57 | * Ask Michael Smith to remove Moritz from OpenCollective and check his duplicate account |
| | 58 | * Student grants: |
| | 59 | * We'll offer USD 4k, max per stipend/project is USD 1K, but it can be less. |
| | 60 | * Yann Chemin offered himself as mentor. |
| | 61 | * Michael Barton will add a couple of ideas to the [https://grasswiki.osgeo.org/wiki/Student_Grants wiki]. |
| | 62 | * [https://grass.osgeo.org/news/2023_11_09_student_grants_announced/ News] item about student grants was merged, so the call is on. |
| | 63 | * **All: spam it around.** |
| | 64 | * Budget: |
| | 65 | * Martin will ask Angeloz if those participating of the Vienna code sprint can be reimbursed directly from OSGeo money. |
| | 66 | * Budget for 2024: |
| | 67 | * Code sprint in Prague before/after FOSS4G Europe. We would need less money than in 2023, because POSE money might cover part of it. |
| | 68 | * Travel money to other conferences. |
| | 69 | * Student grants. |
| | 70 | * Swag. |
| | 71 | * Set up a call with Markus to do the number crunching. |
| | 72 | * Past events: |
| | 73 | * FOSS4G-NA: People willing to pay for the t-shirt but not add more money to it. |
| | 74 | * OSGeo code sprint in Vienna. |
| | 75 | * Future events: |
| | 76 | * FOSS4G Asia: Huidae will attend. |
| | 77 | * FOSS4G Europe, July 2024. |
| | 78 | * Code sprint in Prague before/after FOSS4G Europe 2024. |
| | 79 | * Releases: |
| | 80 | * Vashek: check on Zenodo to get the DOI working again for new releases. |
| | 81 | * Release procedure agenda item was postponed. |
| | 82 | * RFCs: |
| | 83 | * Python Language support was merged, the rest was postponed as they require more time to discuss. |
| | 84 | * Accounts: |
| | 85 | * We don't know who is behind https://codeberg.org/Grass-Development-Team. It's empty. |
| | 86 | * PRs: |
| | 87 | * Too many open PRs, this is not motivating for newcomers that invest time in creating the PRs. |
| | 88 | * Martin did a comprehensive analysis of open PRs status in this [https://docs.google.com/spreadsheets/d/1X65Ms9qUsXlI2hL1421MgnGMA3ewdXG2QNTrr-Czl_g/edit?usp=sharing doc] |
| | 89 | * We discussed the need to set up some rules to deal with open PRs while maintaining code quality, eg. if you create a PR and have writing access to the repo, you are automatically responsible for that PR, if you get an approval and no request for changes, go ahead and merge; for those without writing access, we should split topics, and take care of reviews or assign reviewers, set a period to wait for a response from PR author to merge or close the PR, etc. |
| | 90 | * **All: think and write up rules for managing PRs in this [https://github.com/OSGeo/grass/issues/3235 issue].** |
| | 91 | * Location --> Project: |
| | 92 | * Send executive summary of Vashek’s location document to mailing list and link the full thing to get more feedback. |
| | 93 | * Swag shop: |
| | 94 | * Red bubble: base price does not include their fees, it helps with marketing, people can search keywords and they are offered options. |
| | 95 | * Smtg with spring: easier pricing system, but no way people can reach your store with keywords: https://my-store-9f5dbe.creator-spring.com/listing/gdal |
| | 96 | * https://qgis.myspreadshop.net/ |
| | 97 | * Vero: Check with Ariel what they used for FOSS4G 2021, since RB does not deliver to South America. |
| | 98 | * Try to set up a store. |
| | 99 | * Extras: |
| | 100 | * grasswiki authentication: Anna pinged Regina and Vicky in the [https://trac.osgeo.org/osgeo/ticket/2966 SAC-trac ticket]. |
| | 101 | * mailman issue: postponed, more context needed. |
| | 102 | * Create a news item with GRASS yearly recap and do a end of year virtual toast as the last couple of years. |
