Board Meeting 2020-11-30 - Revision history

Kalxas: /* Minutes */

2020-12-07T07:55:52Z

Minutes

Kalxas: /* Minutes */

2020-12-07T07:55:36Z

Minutes

Kalxas at 07:54, 7 December 2020

2020-12-07T07:54:57Z

Tadams: /* Minutes */

2020-12-02T08:02:55Z

Minutes

Kalxas at 16:33, 30 November 2020

2020-11-30T16:33:42Z

Tadams at 16:24, 30 November 2020

2020-11-30T16:24:37Z

Tadams at 16:10, 30 November 2020

2020-11-30T16:10:43Z

Tadams at 16:06, 30 November 2020

2020-11-30T16:06:04Z

Tadams at 15:47, 29 November 2020

2020-11-29T15:47:51Z

Cvvergara: /* Current items */

2020-11-28T16:02:07Z

Current items

@@ Line 42: / Line 42: @@
 * Vicky explains, that if a sponsor donates, the date of donation is changed, and during 365 days the sponsor's logo is automatically shown on the website. So, that information on the website could be used for contacting the sponsor for sponsorship renewal. As an initial stage Vicky proposes to send a mail to board & treasure with the monthly report of who needs to be reminded for new sponsorship
 *Vicky to create an action item.
 === CRO meeting with SAC ===

@@ Line 31: / Line 31: @@
 * Presiding: Till
-* Scribing: Till
+* Scribing: Till, Angelos
 * Attending: Angelos, Till, Victoria, Tom, Vicky, Astrid, Mike
 * Guests: Jorge

@@ Line 35: / Line 35: @@
 * Guests: Jorge
-* approve last meeting minutes:
+=== Idea: Sponsors automatic information gathering ===
-** https://www.loomio.org/d/ezxYLZDH/approve-meeting-minutes-from-board-meeting-2020-10-26
+* Vicky explains, that if a sponsor donates, the date of donation is changed, and during 365 days the sponsor's logo is automatically shown on the website. So, that information on the website could be used for contacting the sponsor for sponsorship renewal. As an initial stage Vicky proposes to send a mail to board & treasure with the monthly report of who needs to be reminded for new sponsorship
-* CRO meeting with SAC
+=== CRO meeting with SAC ===
-** We have two problems - not existing or non-updated profiles and not attractive profiles.
+* We have two problems - not existing or non-updated profiles and not attractive profiles.
-** We want to allow HTML blocks in the profiles, changes on the website are needed.
+* We want to allow HTML blocks in the profiles, changes on the website are needed.
-** MOT2: Allow changes needed by CRO on the website
+MOT2: Allow changes needed by CRO on the website
-*** motion passed.
+* Vicky: +1 (initial motion)
-* Donations trac issue #2056
+=== Donations trac issue #2056 ===
-** We can have the conversation on the ticket, decide there, and once decided make the ticket "critical"
+* We can have the conversation on the ticket, decide there, and once decided make the ticket "critical"
-* Code of Conduct trac issue #2531
+=== Code of Conduct trac issue #2531 ===
-** Problem is that we have different version of CoC and that projects do not use our CoC.
+* Problem is that we have different version of CoC and that projects do not use our CoC.
-** We start with trying to get feedback from our comunity about the current status of the code of conduct
+* We start with trying to get feedback from our comunity about the current status of the code of conduct
-* Call FOSS4G 2020
+=== Call FOSS4G 2022 ===
-** There was a discussion in the conference committee whether we sohuld ope n the call for both Europe (which is the turn) and NA. After a long email discussion I opened a vote and the result in CC is 5 +1 for both, EU and NA and 4 +1 for EU only and NA in 2023 The question is, whether we want to discuss this or do we accept the vote from CC.
+* There was a discussion in the conference committee whether we sohuld ope n the call for both Europe (which is the turn) and NA. After a long email discussion I opened a vote and the result in CC is 5 +1 for both, EU and NA and 4 +1 for EU only and NA in 2023 The question is, whether we want to discuss this or do we accept the vote from CC.
-* We agreed on having an offboarding meeting and review of the year
+MOT3: Accept the vote from CC about FOSS4G call for 2022 and make an open call to EU and NA
-** Date 7th of December 2020, 16hrs UTC on Jitsy
+* Till: +1 (initial motion)
 == Actions ==
@@ Line 72: / Line 87: @@
 * http://irclogs.geoapt.com/osgeo/%23osgeo.2020-11-30.log
 [[Category:Board]]
 [[Category:Board Meetings 2020]]

← Older revision		Revision as of 08:02, 2 December 2020
Line 35:		Line 35:
	* Guests: Jorge		* Guests: Jorge

		+
		+	* approve last meeting minutes:
		+	** https://www.loomio.org/d/ezxYLZDH/approve-meeting-minutes-from-board-meeting-2020-10-26
		+
		+	* "Idea: Sponsors automatic information gathering (No ticket yet)"
		+	** Vicky explains, that if a soponsor donates, the date of donation is changed, and during 365 days the sponsor's logo is automatically shown on the website. So, that information on the website could be used for contacting the sponsor for sponsorship renewal. As an initial stage Vicky proposes to send a mail to board & treasure with the monthly report of who needs to be remininded for new sponsorship
		+	Vicky to create an action item.
		+	** MOT1: Approve proposals of Vicky
		+	*** motion passed
		+
		+	* CRO meeting with SAC
		+	** We have two problems - not existing or non-updated profiles and not attractive profiles.
		+	** We want to allow HTML blocks in the profiles, changes on the website are needed.
		+	** MOT2: Allow changes needed by CRO on the website
		+	*** motion passed.
		+
		+	* Donations trac issue #2056
		+	** We can have the conversation on the ticket, decide there, and once decided make the ticket "critical"
		+
		+	* Code of Conduct trac issue #2531
		+	** Problem is that we have different version of CoC and that projects do not use our CoC.
		+	** We start with trying to get feedback from our comunity about the current status of the code of conduct
		+
		+	* Call FOSS4G 2020
		+	** There was a discussion in the conference committee whether we sohuld ope n the call for both Europe (which is the turn) and NA. After a long email discussion I opened a vote and the result in CC is 5 +1 for both, EU and NA and 4 +1 for EU only and NA in 2023 The question is, whether we want to discuss this or do we accept the vote from CC.
		+	** MOT3: Accept the vote from CC about FOSS4G call for 2022 and make an open call to EU and NA
		+	*** Motion passed.
		+
		+	* We agreed on having an offboarding meeting and review of the year
		+	** Date 7th of December 2020, 16hrs UTC on Jitsy

	== Actions ==		== Actions ==

@@ Line 9: / Line 9: @@
 # ''Review and approve past minutes''
 #* [[Board_Meeting_2020-10-26]]
 # ''please add items''
 == Minutes ==

@@ Line 25: / Line 25: @@
 ## Donations [https://trac.osgeo.org/osgeo/ticket/2056 trac issue #2056]
 ## Code of Conduct [https://trac.osgeo.org/osgeo/ticket/2531 trac issue #2531]
 # Review action items

@@ Line 10: / Line 10: @@
 #* [[Board_Meeting_2020-10-26]]
 # ''please add items''
 ## Idea: Sponsors automatic information gathering (No ticket yet)
 ## CRO meeting with SAC
@@ Line 20: / Line 19: @@
 ##** The Wiki pages is on transition to be accessed with ldap (osgeoid)
 ##* Planned Solutions (tickets to be opened after elections where it applies):
-##** Annoucement that for next elections the email data will be gathered from the website database
+##** Announcement that for next elections the email data will be gathered from the website database
 ##** Change section: Bio -> Personal Mission Statement (A one sentence statement)
 ##** Add section: OSGeo Related activities (Final title to be defined)
 ##** Start contacting member so promote the creating and update of the profile
 # Review action items