| | 1 | = PSC Meeting 2021-02-03 = |
| | 2 | |
| | 3 | == Election debrief == |
| | 4 | * List of voters |
| | 5 | * All contributers |
| | 6 | * + (for next elections) users who answered questions on list/stackexchange |
| | 7 | * define threshold of number of posts |
| | 8 | * Organize a hackfest before the elections to invite power users to contribute |
| | 9 | * How to avoid duplicates ? |
| | 10 | * Warn future CRO about duplicates |
| | 11 | * Merge all lists into one, sort by emails and delete duplicates |
| | 12 | * Then ask voters to check |
| | 13 | * List of voters of 2020 will be stored in OSGeo Nextcloud |
| | 14 | |
| | 15 | * Length of mandates: Staggered mandates to ensure continuity ? |
| | 16 | * **Decision: mandates of 6 years with 1/2 elected every 3 years** |
| | 17 | * Seats up at for next elections (i.e. only 3 year mandate): |
| | 18 | * Moritz |
| | 19 | * Martin |
| | 20 | * Helena |
| | 21 | * Michael |
| | 22 | * How to handle resignations ? |
| | 23 | * **Decision: Replace by the first on the "waiting list" (list of people standing for elections, but not elected, ranked by number of votes)** |
| | 24 | |
| | 25 | == PSC roles & tasks (for 3 years) == |
| | 26 | * Chairperson - Vero |
| | 27 | * Treasurer - Moritz |
| | 28 | * Release manager - Markus, Martin |
| | 29 | * Infrastructure manager - Markus |
| | 30 | * Translation manager - Huidae |
| | 31 | * Website & Marketing manager - Michael, Vero |
| | 32 | * Github manager - Vaclav |
| | 33 | |
| | 34 | == Do we need a mission statement of the GRASS GIS project ? |
| | 35 | * Make internalized approach and philosophy more explicit |
| | 36 | * Express what GRASS GIS' audience is |
| | 37 | * **Decision: Michael will provide a first proposal on the wiki** |
| | 38 | |
| | 39 | == How do decide on minimum requirements for programming languages (from grass-dev: https://lists.osgeo.org/pipermail/grass-dev/2021-January/094899.html) |
| | 40 | * Which platforms should we support ? |
| | 41 | * Proposal: GNU/Linux, FreeBSD, MS Windows, OSX |
| | 42 | * Python |
| | 43 | * Issue is more with Python libraries than the core Python |
| | 44 | * target: 3.7 (3.6 end of life at end of 2020) |
| | 45 | * **Decision: Ask devs discussing the issue to write RFC** |
| | 46 | |
| | 47 | == Proposal: Use of RFCs for fundamental changes in the code == |
| | 48 | * RFCs |
| | 49 | * are very visible |
| | 50 | * clearly mark the discussion as more important than a standard PR/Issue |
| | 51 | * make rationals explicit and easily retrievable |
| | 52 | * See https://gdal.org/development/rfc/index.html as example |
| | 53 | * Where to post them ? |
| | 54 | * Trac wiki |
| | 55 | * Github wiki |
| | 56 | * Github repository |
| | 57 | * To be discussed further |
| | 58 | * Use discussion on programming language versions (above) as test case |
| | 59 | |
| | 60 | == PSC meeting frequency == |
| | 61 | * **Decision: one meeting / trimestre** |
