Board Meeting 2022-08-27 - Revision history

Kalxas: /* Website */

2022-09-24T09:52:08Z

Website

Kalxas at 09:50, 24 September 2022

2022-09-24T09:50:45Z

Cvvergara: /* Summary of F2F meeting with OSGeo/OSM/HOT communities */

2022-09-06T16:04:38Z

Summary of F2F meeting with OSGeo/OSM/HOT communities

Cvvergara: /* Projects status action done*/

2022-09-06T15:55:15Z

Projects status action done

Kalxas at 08:34, 5 September 2022

2022-09-05T08:34:11Z

Kalxas at 08:33, 5 September 2022

2022-09-05T08:33:31Z

Show changes

Tomkralidis: /* Current items */

2022-08-27T07:25:38Z

Current items

Kalxas at 06:29, 27 August 2022

2022-08-27T06:29:02Z

Kalxas: /* Current items */

2022-08-27T06:24:59Z

Current items

Lucadelu: /* Current items */ added new item for board meeting

2022-08-26T10:46:24Z

Current items: added new item for board meeting

← Older revision		Revision as of 09:52, 24 September 2022
Line 168:		Line 168:

	Moved to next meeting		Moved to next meeting
−	* Discuss: Member pages (hide members without filled profile)
−	* Action: Project's update officer's/representative
−	** Post Action: Generate automatically the list of project officers
−	* Discuss: Statement on report slide mentions that: "From the committees' pages you will find the missions, names of the people involved, and links to the working documents." That is not true.
−	** Post Action?: Work the committees similarly as projects. Where officers can be assigned, and active members of the committee can be listed.
−	* Discuss: Charter member pages: User name + last name.
−	* Discuss: Use tags on news items (to help out with the Annual report).
−	* Discuss: Auto move the old un-format-able "Biography" (Now Mission) to the format-able Biography.
−	* News Vs Community news
−
−
−

	===OSGeo EU - ESA===		===OSGeo EU - ESA===

@@ Line 48: / Line 48: @@
 * MOU completed, presented at FOSS4G keynote
 * Action: Complete the membership agreement
-A new committee - OSGeo OGC Committee -  to handle the OGC activities within the next 4 weeks and also define an architecture of the participation of OSGeo reps in OGC;
+** A new committee - OSGeo OGC Committee -  to handle the OGC activities within the next 4 weeks and also define an architecture of the participation of OSGeo reps in OGC; Report back to standards mailing list
 * OSGeo OGC Committee
 * Reference implementations
-Max 2 reference implementations
+** Max 2 reference implementations
-Figure out how to list all OSGeo related projects in the compliance list on OGC web site.
+** Figure out how to list all OSGeo related projects in the compliance list on OGC web site.
 * Budget for OGC participation (meetings/code sprint attendance, etc.)
-next in person OGC meeting: https://portal.ogc.org/meet/
+** next in person OGC meeting: https://portal.ogc.org/meet/
-Amendment of the budget to include the travel to the member meeting
+** Amendment of the budget to include the travel to the member meeting
-There is an online option for the OGC member meetings.
+** There is an online option for the OGC member meetings.
-CI for Cite testing
+* CI for Cite testing
 ===Elections and CRO members for 2022===
-Vicky willing to step in to help Jorge
+* Vicky willing to step in to help Jorge
-Discussion about members list and how to maintain it. Several points of truth.
+* Discussion about members list and how to maintain it. Several points of truth.
-Action: Send an email to all members 3 weeks  before elections to check email; and then announce on discuss list about it so people that didn’t receive it can contact us or update their email on the website. Perhaps also use social media as well.Need the marketing committee to help with social media for e-mail updates.
+* Action: Send an email to all members 3 weeks  before elections to check email; and then announce on discuss list about it so people that didn’t receive it can contact us or update their email on the website. Perhaps also use social media as well.Need the marketing committee to help with social media for e-mail updates.
-Start nominations now, leave September for nominations, finish in October - keep this calendar consistent over the years;
+* Start nominations now, leave September for nominations, finish in October - keep this calendar consistent over the years;
-Perhaps avoid summer months for nominations.
+* Perhaps avoid summer months for nominations.
-We need to reach out to find people that are not nominated? No self nomination.
+* We need to reach out to find people that are not nominated? No self nomination.
-Action: Astrid will go through all projects and check if the members are charter members
+* Action: Astrid will go through all projects and check if the members are charter members
-Discussion about CRO technical issues (LimeSurvey etc)
+* Discussion about CRO technical issues (LimeSurvey etc)
-Update the columns in the database to be shared by CRO
+* Update the columns in the database to be shared by CRO
-Discussion about charter members not voting the last 4 years: reach out to people not voted to check with them if possible.
+* Discussion about charter members not voting the last 4 years: reach out to people not voted to check with them if possible.
-Action: Create an e-mail template.
+* Action: Create an e-mail template.
-Discussion about attracting more board member nominations. Should the CRO email include this wiki page? https://wiki.osgeo.org/wiki/Board_of_Directors/OnboardingChecklist
+* Discussion about attracting more board member nominations. Should the CRO email include this wiki page? https://wiki.osgeo.org/wiki/Board_of_Directors/OnboardingChecklist
-Discussion about treasurer role.
+* Discussion about treasurer role.
-Discussion about creating a youth group to attract young people on places/technologies they are active on. What would be the target group?
+* Discussion about creating a youth group to attract young people on places/technologies they are active on. What would be the target group?
-Action: Rajat to write an email to GeoForAll and GSOC to let them know of this idea from the board to ask of their opinion and support.
+* Action: Rajat to write an email to GeoForAll and GSOC to let them know of this idea from the board to ask of their opinion and support.
-* Motion to appoint Jorge and Vicky as CRO for 2022 (Angelos).
+* Motion to appoint Jorge and Vicky as CRO for 2022 passed on Loomio.
 https://www.loomio.org/p/MCtRH2Jg/motion-to-appoint-jorge-gustavo-rocha-and-vicky-vergara-for-cro-2022

@@ Line 87: / Line 87: @@
 * Going to happen online
 * Action: Vicky to contact Miriam.
 ===FOSS4G locations===

@@ Line 153: / Line 153: @@
 * Action: Vicky to answer to Jody about incubation of an project of an association
 * 2018: https://git.osgeo.org/gitea/osgeo/todo/issues/11
 * 2019: https://git.osgeo.org/gitea/osgeo/todo/issues/40
@@ Line 163: / Line 164: @@
 * Marble has not reported for 2 years
 * OTB wants to change officer (they will report to board soon)
 ===Website===

@@ Line 18: / Line 18: @@
 # Feedback from AGM
 # OSGeo Code Sprint 2023
-# Projects
+# Projects status
 # Website - mailing list discussion
 # OSGeo EU - ESA

@@ Line 11: / Line 11: @@
 #* [[Board_Meeting_2022-07-25]]
 # approve pygeoapi as OSGeo project
-## currently in vote on Loomio: https://www.loomio.org/p/XjpcFNvf/graduate-pygeoapi-as-an-osgeo-project
+## completed vote on Loomio: https://www.loomio.org/p/XjpcFNvf/graduate-pygeoapi-as-an-osgeo-project
 ## https://lists.osgeo.org/pipermail/incubator/2022-August/004535.html
 ## https://lists.osgeo.org/pipermail/board/2022-August/013087.html

@@ Line 42: / Line 42: @@
 # Creation of Conference Working Group
 # Feedback from AGM
 # ''Add your topic here''