Difference between revisions of "Board Meeting 2023-07-25"

From OSGeo
Jump to navigation Jump to search
 
(4 intermediate revisions by the same user not shown)
Line 44: Line 44:
 
* https://lists.osgeo.org/pipermail/board/2023-July/013312.html  
 
* https://lists.osgeo.org/pipermail/board/2023-July/013312.html  
 
* ACTION: Angelos to make a motion on Loomio (Done).
 
* ACTION: Angelos to make a motion on Loomio (Done).
* Motion open on Loomio: https://www.loomio.com/p/FQ7Ty1u3/motion-to-approve-bolsena-code-sprint-request-for-2000-euros
+
* Motion passed on Loomio: https://www.loomio.com/p/FQ7Ty1u3/motion-to-approve-bolsena-code-sprint-request-for-2000-euros
  
 
=== OpenGIS harmonization initiative ===
 
=== OpenGIS harmonization initiative ===
Line 64: Line 64:
 
* MOTION: Lior to become a member of the Finance Committee and have access to the sponsor's information. Motion by Michael, seconded by Angelos, all in favor. Approved during the meeting.
 
* MOTION: Lior to become a member of the Finance Committee and have access to the sponsor's information. Motion by Michael, seconded by Angelos, all in favor. Approved during the meeting.
 
* ACTION Angelos to move to Loomio and get everyone to vote (Done).
 
* ACTION Angelos to move to Loomio and get everyone to vote (Done).
* Motion open on Loomio: https://www.loomio.com/p/ZkUPCQAi/motion-for-lior-kaplan-to-become-a-member-of-the-finance-committee-and-have-access-to-the-sponsor-s-information-
+
* Motion passed on Loomio: https://www.loomio.com/p/ZkUPCQAi/motion-for-lior-kaplan-to-become-a-member-of-the-finance-committee-and-have-access-to-the-sponsor-s-information-
  
 
=== ESA MOI ===
 
=== ESA MOI ===
Line 70: Line 70:
 
* https://wiki.osgeo.org/wiki/MoU_ESA
 
* https://wiki.osgeo.org/wiki/MoU_ESA
 
* Discussion about the draft document and the feedback given on chat discussion.
 
* Discussion about the draft document and the feedback given on chat discussion.
** Adam has expressed the opinion that the word "enforce" in Exhibit A could be changed to "use". The reasons are:  1. the MoI(U) doesn't give either organization power to enforce anything. 2. OSGeo shouldn't be about enforcing things, with external organizations - we can lead, mentor, encourage...
+
** Adam has expressed the opinion that the word "enforce" in Exhibit A could be changed to "use". The reasons are:  1. the MoI(U) doesn't give either organization power to enforce anything. 2. OSGeo shouldn't be about enforcing things, with external organizations - we can lead, mentor, encourage.
** During the meeting the wording was discussed. The word "enforce" is on ESA side and we agreed that this is ok on OSGeo side (actually in our favor as open source community). Some organizations need/use such language on regulations.
+
** During the meeting the wording was discussed. The word "enforce" is on ESA’s side and not OSGeo. It explains why ESA signs this MoI: “In this context, the current MoI represents a key strategic element to enforce open source practices and maximise outreach and community building for the open source components developed under the ESA EO Science for Society activities.”
 +
** We agreed that this is ok on OSGeo side. It does not imply whatsoever that OSGeo is an enforcer. Some organizations need/use such language on regulations and agreements.
 
* ACTION: Codrina to send an e-mail to the board mailing list with the draft to make it publicly available (Done) [https://lists.osgeo.org/pipermail/board/2023-July/013324.html]
 
* ACTION: Codrina to send an e-mail to the board mailing list with the draft to make it publicly available (Done) [https://lists.osgeo.org/pipermail/board/2023-July/013324.html]
 
* ACTION: Angelos to open a motion to approve (Done)
 
* ACTION: Angelos to open a motion to approve (Done)
* Motion open on Loomio: https://www.loomio.com/p/QlL45DxV/motion-to-approve-the-memorandum-of-intent-with-the-european-space-agency
+
* Motion passed on Loomio: https://www.loomio.com/p/QlL45DxV/motion-to-approve-the-memorandum-of-intent-with-the-european-space-agency
  
 
=== Code sprint announce ===
 
=== Code sprint announce ===
Line 86: Line 87:
 
* https://lists.osgeo.org/pipermail/qgis-psc/2023-July/010092.html
 
* https://lists.osgeo.org/pipermail/qgis-psc/2023-July/010092.html
 
* We need to raise awareness of this issue.
 
* We need to raise awareness of this issue.
* ACTION: Angelos to plan a working session to involve projects and committees and prepare material for reaching out. Proposed date Thu 3rd August 18:00UTC or 13:00UTC. (Done)
+
* ACTION: Angelos to plan a working session to involve projects and committees and prepare material for reaching out. Proposed date Tue 8th August 13:00UTC. (Done)
  
 
=== Actions ===
 
=== Actions ===

Latest revision as of 03:23, 8 August 2023

This board meeting is scheduled Tuesday 25 July 2023 at 18:00 UTC through Jitsi, a record of motions is preserved on Loomio and actions on the OSGeo todo issue tracker.

Agenda

Current items

  1. roll call
  2. appoint meeting chair, meeting scribe/secretary
  3. Review and approve past minutes
  4. Global Land Tool Network (GLTN) Secretariat at UN-Habitat request
  5. Bolsena code sprint request for €2,000 EUR
  6. OpenGIS harmonization initiative
  7. GeoMajas project status
  8. Sponsors relationship maintenance
  9. ESA MOI
  10. Code sprint announcement
  11. EU CRA directive [1]
  12. Add your topic here

Minutes

  • Presiding: Angelos
  • Scribing: all
  • Attending: Michael, Vicky, Angelos, Marco, Ariel, Rajat, Codrina
  • Guests: John Gitau (UN habitat), Jody, Lior Kaplan

Review and approve past minutes

Global Land Tool Network (GLTN) Secretariat at UN-Habitat request

Bolsena code sprint request

OpenGIS harmonization initiative

  • Discussion about the approved budget and the results of FOSS4G code sprint.
  • The board will discuss through e-mail about the path forward.

GeoMajas project status

Sponsors relationship maintenance

ESA MOI

  • https://wiki.osgeo.org/wiki/MoU_ESA
  • Discussion about the draft document and the feedback given on chat discussion.
    • Adam has expressed the opinion that the word "enforce" in Exhibit A could be changed to "use". The reasons are: 1. the MoI(U) doesn't give either organization power to enforce anything. 2. OSGeo shouldn't be about enforcing things, with external organizations - we can lead, mentor, encourage.
    • During the meeting the wording was discussed. The word "enforce" is on ESA’s side and not OSGeo. It explains why ESA signs this MoI: “In this context, the current MoI represents a key strategic element to enforce open source practices and maximise outreach and community building for the open source components developed under the ESA EO Science for Society activities.”
    • We agreed that this is ok on OSGeo side. It does not imply whatsoever that OSGeo is an enforcer. Some organizations need/use such language on regulations and agreements.
  • ACTION: Codrina to send an e-mail to the board mailing list with the draft to make it publicly available (Done) [2]
  • ACTION: Angelos to open a motion to approve (Done)
  • Motion passed on Loomio: https://www.loomio.com/p/QlL45DxV/motion-to-approve-the-memorandum-of-intent-with-the-european-space-agency

Code sprint announce

  • Already published on the website [3].
  • We need to make a follow up announcement with QGIS and Pangeo participation.
  • ACTION: Angelos to follow up on e-mail (Done)

EU CRA directive

Actions

IRC Log

  • no log, Jitsi meeting

Next meeting