Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1qpqQB-007FQc-UN for pgsql-www@arkaria.postgresql.org; Mon, 09 Oct 2023 13:35:44 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1qpqQ9-00DyRp-Sh for pgsql-www@arkaria.postgresql.org; Mon, 09 Oct 2023 13:35:42 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1qpqQ9-00DyRb-Kz for pgsql-www@lists.postgresql.org; Mon, 09 Oct 2023 13:35:42 +0000 Received: from mail-ej1-x62d.google.com ([2a00:1450:4864:20::62d]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1qpqQ7-000nB7-Qc for pgsql-www@lists.postgresql.org; Mon, 09 Oct 2023 13:35:41 +0000 Received: by mail-ej1-x62d.google.com with SMTP id a640c23a62f3a-9ae75ece209so829028966b.3 for ; Mon, 09 Oct 2023 06:35:39 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=pgadmin.org; s=google; t=1696858538; x=1697463338; darn=lists.postgresql.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=Yk9MY6qEfz9kMgN16AJ6HjDTVCvJMqzkd592Fa9ulw4=; b=CAuiWKD7x+0Le+dsOO/AuTYvLuR/loNhLn12W6GiVY2J+98v+JIHZmyVSRTOFSyGSj wuBp2eJBfU+OHVugee0k40kBpjnYK/hnGfh7WfX5BII2Fl5D5xlq5qOeBogGlrLMtd1z XzyqkV1uNmInjw5YLwfi5R6KUe5+Cz1Q/fsuWfwx9h/jWtZo/GHxtca0mIxHRNaRwvch OUlWQbxebqWwzku7XLFT2uchjxHjseyW1VRXiZyd81qboSpYrBJ6cXxUBMfKQlxA8svS Cl9NUHk/NaN+aaww5zbCiJjA69OFOd//8wBm4Hmg0xZPBp2/bnPyNz/wO5cHT8hubNXJ T7rw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1696858538; x=1697463338; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=Yk9MY6qEfz9kMgN16AJ6HjDTVCvJMqzkd592Fa9ulw4=; b=d63y9o9t9VHLv4l9AQxc2OYKbSbUlvruznrJ15L1u2QuYb0KicDStYbj++fWZHkRYw 7SbW0LM/N9eOvdnybwDL5IfXreEeA0iBDKQy2OPYvCA5f2OmB4CSdxJqCZv+yeCvcMu+ FFS/qMDPHX17G6/yFJFNP2YkmAy456topMUzPWdINANK4Zj+GvlbK2BBBuHObnZwi7mq TA5QhsB0JKaiLGwmDYbLDBSLIBOehMmPq1Jk+CJv3Z4iToB0CEtIaufpv+VGMZlu6rmj 0wZHucSgVTctnNK9zN/HliOMoF2JKf/7zHSpx+MzBwaach6x9ytmw6ZcucVGPnqwA1Wu EWgg== X-Gm-Message-State: AOJu0YxcMFSOiphH5pwzd5Qc98ITamDyyRcIMaBGmVuPpt4TSKDlVH9U +2Gqahuwcdg5GEIXBDB/asYoW2p2MZ+MLDKMGFovSg== X-Google-Smtp-Source: AGHT+IGc0Kg8a4F4wrnEUqH14bHyZe+AzwOOXUANPd0Tti0QnqOXSPgWD7XYWeG9C9r/6zBkalpBDqE9IEwp/SNrxko= X-Received: by 2002:a17:906:ce:b0:9a6:426f:7dfd with SMTP id 14-20020a17090600ce00b009a6426f7dfdmr12015649eji.66.1696858538067; Mon, 09 Oct 2023 06:35:38 -0700 (PDT) MIME-Version: 1.0 References: <87970758-9EF7-401A-8B91-D4A99ADA9EC1@yesql.se> <7031a8d39e8a5f2545c9c7ad2c17d763@postgresql.org> In-Reply-To: From: Dave Page Date: Mon, 9 Oct 2023 14:35:26 +0100 Message-ID: Subject: Re: Accidental inclusion of core team on funds policy? To: Daniel Gustafsson Cc: Jonathan Katz , Dave Cramer , pgsql-www@lists.postgresql.org Content-Type: multipart/alternative; boundary="000000000000655fab060748aac9" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --000000000000655fab060748aac9 Content-Type: text/plain; charset="UTF-8" On Mon, 9 Oct 2023 at 14:29, Daniel Gustafsson wrote: > > On 9 Oct 2023, at 15:25, Jonathan Katz wrote: > > > > On 2023-10-09 08:48, Dave Cramer wrote: > >> On Mon, 9 Oct 2023 at 08:46, Daniel Gustafsson wrote: > >>> I happened to notice what seems like a copy/paste error in the funds > group > >>> policy document on the website. The first para on the page explains > Core > >>> Team > >>> membership which seems incorrect as they are separate entities. > >>> https://www.postgresql.org/about/policies/funds-group/ > >>> Shouldn't we do something like the attached? > >> +1 from me > > > > -1. This is part of the charter that was sent to SPI. Please do not > > modify it. > > Fair enough, but should it really be there or is it something which should > be > changed at some point? Right now it implies that the Funds group reports > to > the Core Team, or that the Core Team has influence on the Funds group, > which > AFAIK isn't correct. > Yes, it is. The core team has the power of veto over the Liaison and Deputy Liaison. This page is the charter which describes the relationship between the project and the funds group, so it makes sense (because others within SPI don't know our project) to have all the key details in one place. -- Dave Page pgAdmin: https://www.pgadmin.org PostgreSQL: https://www.postgresql.org EDB: https://www.enterprisedb.com --000000000000655fab060748aac9 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


=
On Mon, 9 Oct 2023 at 14:29, Daniel G= ustafsson <daniel@yesql.se> wr= ote:
> On 9 Oct 2023, at 15:25, Jonathan Katz = <jkatz@postgre= sql.org> wrote:
>
> On 2023-10-09 08:48, Dave Cramer wrote:
>> On Mon, 9 Oct 2023 at 08:46, Daniel Gustafsson <daniel@yesql.se> wrote:
>>> I happened to notice what seems like a copy/paste error in the= funds group
>>> policy document on the website.=C2=A0 The first para on the pa= ge explains Core
>>> Team
>>> membership which seems incorrect as they are separate entities= .
>>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 https:= //www.postgresql.org/about/policies/funds-group/
>>> Shouldn't we do something like the attached?
>> +1 from me
>
> -1. This is part of the charter that was sent to SPI. Please do not > modify it.

Fair enough, but should it really be there or is it something which should = be
changed at some point?=C2=A0 Right now it implies that the Funds group repo= rts to
the Core Team, or that the Core Team has influence on the Funds group, whic= h
AFAIK isn't correct.

Yes, it is. Th= e core team has the power of veto over the Liaison and Deputy Liaison.

This page is the charter which describes the relations= hip between the project and the funds group, so it makes sense (because oth= ers within SPI don't know our project) to have all the key details in o= ne place.=C2=A0

--
--000000000000655fab060748aac9--