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


Ignore:
Timestamp:
Feb 11, 2022, 12:43:14 PM (2 years ago)
Author:
neteler
Comment:

some updates

Legend:

Unmodified
Added
Removed
Modified

  • PSC/Minutes/PSC_Meeting_20220211

    v3 v4  
    3030  * 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 it's done in conferences or in the OSGeo website.
     32  * Vero commented on the idea to add other kind of contributions to [https://opencollective.com/osgeo/projects/grass Open collective] (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.
    3333  * 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.
    3434  * Vero will ask Michael Smith from the OSGeo board how that would be handled.
    … …  
    4242    * 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]
     44    * Markus and mundialis will probably submit an actinia workshop (there's a new [https://github.com/mundialis/actinia-stac-plugin actinia-STAC plugin]) and potentially one about [https://github.com/mundialis/geoserver-grass-raster-datastore Geoserver GRASS raster datastore]
    4545  * 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:
    … …  
    4848* Bugs related to Windows:
    4949  * 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    * Update: https://grass.osgeo.org/grass80/binary/mswindows/native/WinGRASS-8.0.0-2-Setup.exe has been fixed
    5051  * Modules not working in Windows: See [https://github.com/OSGeo/grass/issues/2013 #2013]. Martin will check.
    5152  * wxlocale error upon starting: See [https://github.com/OSGeo/grass/issues/2101 #2101]. Martin will have a look (?).
    5253* 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 to avoid waiting forever to get the new features out.
    54   * 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). Vaclav, please correct me here in case I misunderstood.
     54  * 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, in addition, release more frequently to avoid waiting forever to get the new features out.
     55  * Adopting feature freezing for releases would prevent these last minute new features backport as it is already defined in [wiki:RFC/4_ReleaseProcedure RFC 4: Release Procedure]
     56  * We should add 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.
    5657* Google Summer of Code 2022:
    5758  * 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.
    … …  
    6061  * Anna also suggested the cmake compilation as a potential project.
    6162* DOI/Citation - which and how many contributors should be cited?:
    62   * Markus proposed to order the n contributors from the last 12 months counting backwards from the release date (a sort of moving windows).
     63  * Markus proposed to order by the top n contributors from the last 12 months counting backwards from the release date (a sort of moving windows).
    6364  * We discussed which criteria to use for the ordering and opted for number of lines changed over number of commits.
    6465  * Automation using GitHub api to be studied (Vaclav?).
    … …  
    7273* Releases:
    7374  * 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 (?).
     75  * ctypes error bugfix for Alpine has be bumped to the 8.0.2 miletone.
    7576