21 | | * FOSSGIS 2024 (https://fossgis-konferenz.de/2024/) |
22 | | * FOSS4G Europe (https://2024.europe.foss4g.org/) |
| 22 | * FOSSGIS, 20-23 March (https://fossgis-konferenz.de/2024/) |
| 23 | * Tennessee Geographic Information Council (TNGIC), 9-11 April (https://www.tngic.org/annual-conference-2024-) |
| 24 | * FOSS4G Europe, 01-07 July (https://2024.europe.foss4g.org/) |
| 25 | * useR! — International R User Conference, 8-11 July (https://user2024.r-project.org/) |
26 | | * 8.4.0 planned for April (how about anticipating this a bit? |
| 31 | * 8.4.0 planned for April (how about anticipating this a bit?) |
| 32 | * Access rights reformed on !GitHub (Vaclav) |
| 33 | * Unified structure for teams with write and triage access |
| 34 | * Historical Subversion committers now have triage access (not write) |
| 35 | * Current teams are grass-write, grass-addons-write, grass-website-write, grass-promo-write, grass-maintain, grass-admin, grass-triage, grass-discussion-moderators ([https://github.com/orgs/OSGeo/teams/?query=grass list of teams]) |
| 36 | * PR procedures updated (Vaclav) |
| 37 | * At least one review from a person with write access required |
| 38 | * anyone can still leave reviews which can be taken into account by the reviewer with write access |
| 39 | * discussions which have a Resolve button need to be resolved |
| 40 | * A button to easily update the the PR branch from main (merge or rebase) |
| 41 | * A button to enable automatic merging of PR once reviews are done and checks passed (aka auto-merge) |