Changes between Version 2 and Version 3 of PSC/Minutes/PSC_Meeting_20220211


Ignore:
Timestamp:
Feb 11, 2022, 12:00:24 PM (2 years ago)
Author:
veroandreo
Comment:

minutes 2022-02-11, part 3

Legend:

Unmodified
Added
Removed
Modified

  • PSC/Minutes/PSC_Meeting_20220211

    v2 v3  
    44== Participants ==
    55
    6 * Vero Andreo (PSC chair)
    76* Anna Petrasova
    8 * Vaclav Petras
    97* Huidae Cho
    10 * Moritz Lennert
    118* Markus Neteler
    129* Martin Landa
    1310* Michael Barton
     11* Moritz Lennert
     12* Vaclav Petras
     13* Vero Andreo
    1414
    1515== Agenda ==
    … …  
    2828
    2929* Planned budget for 2022:
    30   * Submitted to OSGeo
     30  * Already submitted to OSGeo: https://grasswiki.osgeo.org/wiki/GRASS_GIS_Budget_2022
    3131* Sponsoring:
    32   * Vero commented on the idea to add other kind of contributions to opencollective (for regular contributions) and maybe if contributors are companies, have a plan to add their logos to the website as in conferences or the OSGeo website.
    33   * Moritz suggested to search for some legal advice as probably if we offer a counterpart, we need to do contracts and that wouldn't go as donation for companies but marketing, hence no tax reduction. The donation button will remain anyway, so companies could choose how to contribute.
    34   * Vero will ask Michael Smith from the OSGeo board.
     32  * Vero commented on the idea to add other kind of contributions to opencollective (for regular contributions) and maybe if contributors are companies, have a plan to add their logos to the website as it's done in conferences or in the OSGeo website.
     33  * Moritz suggested to search for legal advice as probably if we offer a counterpart, we need to do contracts and for companies that wouldn't go as donation but as marketing, hence no tax reduction. The donation button will remain anyway, so companies could choose how to contribute.
     34  * Vero will ask Michael Smith from the OSGeo board how that would be handled.
    3535  * Michael suggested that GRASS could evaluate the possibility to have some sort of legal entity.
    3636* FOSS4G 2022:
    3737  * Presentations:
    38     * We will submit a "State of GRASS GIS" talk as usual (we'll share a doc to put that up together). Markus, Martin and Moritz are planning to attend so potentially they could present. The presentation should show off GRASS 8.2.
    39     * Linda and Caitlin may also submit something of theirs.
     38    * We will submit a "State of GRASS GIS" talk as usual. We'll share a doc to put that up together - Volunteers?. Markus, Martin and Moritz are planning to attend so potentially they could present. The presentation should show off GRASS 8.2.
     39    * Linda and Caitlin will also submit something of theirs.
    4040  * Workshops:
    4141    * An intro to GRASS for beginners with all the new GUI stuff
    42     * A general GRASS workshop with Jupyter lab and python (not sure if this will go together with the beginner's one or not - please edit here!)
     42    * A general GRASS workshop with Jupyter lab and python (not sure if this will go together with the beginner's one or not - Anna, please edit here!)
    4343    * One about remote sensing processing and analysis in GRASS (Vero might take the lead here, others are mostly welcome to join)
    44     * Markus and mundialis will probably submit an actinia workshop (there's a new STAC plugin) and potentially one about [[https://github.com/mundialis/geoserver-grass-raster-datastore Geoserver GRASS datastore]]
    45   * We mentioned the possibility of an extended GRASS code sprint as we did in Como 2015, but it will mostly depend on who will be attending, so this was left in stand-by
     44    * Markus and mundialis will probably submit an actinia workshop (there's a new STAC plugin) and potentially one about [https://github.com/mundialis/geoserver-grass-raster-datastore Geoserver GRASS datastore]
     45  * We mentioned the possibility of an extended GRASS code sprint as we did in Como 2015, but it will mostly depend on who will be attending, so this idea was left in stand-by for now.
    4646* Other conferences:
    47   * Michael commented that there's also the [[https://www.iemss.org/ International Environmental Modelling and Software Society]] happening in Brussels. Sounds like a good fit for GRASS applications too.
     47  * Michael commented that there's also the [https://www.iemss.org/ International Environmental Modelling and Software Society] happening in Brussels. Sounds like a good fit for GRASS applications too.
    4848* Bugs related to Windows:
    49   * Broken addon installation: The standalone installer was fixed by Martin and the link in the website was fixed accordingly. The problem was that during packaging, something went wrong and instead of getting 8.0.0, the installer got the dev version. The problem was originally reported in this [[https://lists.osgeo.org/pipermail/grass-user/2022-February/082861.html thread]] in the mailing list.
    50   * Modules not working in Windows: See https://github.com/OSGeo/grass/issues/2013. Martin will check.
    51   * wxlocale error upon starting: See https://github.com/OSGeo/grass/issues/2101. Martin will have a look.
     49  * Broken addon installation: The standalone installer was fixed by Martin and the link in the website was fixed accordingly. The problem was that during packaging, something went wrong and instead of getting 8.0.0, the installer got the dev version. The problem was originally reported in this [https://lists.osgeo.org/pipermail/grass-user/2022-February/082861.html thread] in the mailing list.
     50  * Modules not working in Windows: See [https://github.com/OSGeo/grass/issues/2013 #2013]. Martin will check.
     51  * wxlocale error upon starting: See [https://github.com/OSGeo/grass/issues/2101 #2101]. Martin will have a look (?).
    5252* Backporting:
    53   * To avoid that future releases have problems, it would be better to let new features stay in main for a while so they get tested better and, instead release more frequently so to avoid waiting forever to get the new features out.
     53  * To avoid that future releases have problems, it would be better to let new features stay in main for a while so they get tested better and, instead, release more frequently to avoid waiting forever to get the new features out.
    5454  * Adopting feature freezing for releases would prevent these last minute new features backport.
    55   * We should make more tests in GitHub actions to avoid bugs like the compilation bug shipped with 8.0.0, though recreating a no-network env within GitHub might be tricky (if possible).
     55  * We should make more tests in GitHub actions to avoid bugs like the compilation bug shipped with 8.0.0, though recreating a no-network env within GitHub might be tricky (if possible). Vaclav, please correct me here in case I misunderstood.
    5656* Google Summer of Code 2022:
    57   * Anna created the wiki page and called for ideas and mentors. She also sent a reminder/invitation to grass-dev.
    58   * This year GSoC will also admit non-students as long as this is their first contribution to open source software.
    59   * Parallelization will be again part of the ideas as other modules may take advantage of running in parallel. Huidae agree to mentor this idea.
     57  * Anna created the [https://trac.osgeo.org/grass/wiki/GSoC/2022 wiki] page and called for ideas and mentors. She also sent a reminder/invitation to grass-dev.
     58  * This year GSoC will also admit non-students as long as this is their first contribution to open source software. So, there's potentially a larger population that could apply.
     59  * Parallelization will be again part of the ideas as other modules may take advantage of running in parallel. Huidae agreed to mentor this idea.
    6060  * Anna also suggested the cmake compilation as a potential project.
    61 * DOI/Citation:
     61* DOI/Citation - which and how many contributors should be cited?:
    6262  * Markus proposed to order the n contributors from the last 12 months counting backwards from the release date (a sort of moving windows).
    6363  * We discussed which criteria to use for the ordering and opted for number of lines changed over number of commits.
    … …  
    6565  * Markus found a command line call, but it lists contributors by number of commits:
    6666  `curl -H "Accept: application/vnd.github.v3+json" https://api.github.com/repos/OSGeo/grass/contributors`
     67  * GitHub api docs [https://docs.github.com/en/rest/reference/repos#list-repository-contributors--code-samples here]
     68* RFC about [https://trac.osgeo.org/grass/wiki/RFC/8_LanguageStandardsSupportPython Python language]:
     69  * There's a formula there to get the minimum supported python version, but there were no comments on it, hence no voting.
     70  * It was not clear how would that work for addons as we support addons for/during major versions, but Python version is set to change with grass minor versions. Vaclav suggested that addons should inherit the python version that is currently supported in GRASS minor version and added some clarifications to the RFC. Please review and comment so we can vote on it.
     71  * Shall we already change Python version [https://github.com/OSGeo/grass/blob/main/REQUIREMENTS.html here]?
     72* Releases:
     73  * Markus will prepare 8.0.1 RC1 this weekend to provide a quick fix for the compilation bug shipped with 8.0.0.
     74  * ctypes error will be bumped to 8.0.2 (?).
    6775
    68 
    69