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 1qpqVg-007Fni-OX for pgsql-www@arkaria.postgresql.org; Mon, 09 Oct 2023 13:41:25 +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 1qpqVe-00DzbX-K5 for pgsql-www@arkaria.postgresql.org; Mon, 09 Oct 2023 13:41:23 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1qpqVe-00DzbP-BZ for pgsql-www@lists.postgresql.org; Mon, 09 Oct 2023 13:41:23 +0000 Received: from mail-ed1-x535.google.com ([2a00:1450:4864:20::535]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1qpqVY-0015ny-0d for pgsql-www@lists.postgresql.org; Mon, 09 Oct 2023 13:41:22 +0000 Received: by mail-ed1-x535.google.com with SMTP id 4fb4d7f45d1cf-53636f98538so7883224a12.1 for ; Mon, 09 Oct 2023 06:41:15 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=pgadmin.org; s=google; t=1696858875; x=1697463675; 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=AuTRmMjy/yI9IhnNGvYwp29wf7SXW/Pt1+QfWnfBR18=; b=OLzxtegoX0LzdHlwbILAhiGuAI1fuejjBzC6YtgYjftcruWYnpBBU5XmCWvzLcLppX O/D2etaNoqupEE4mriZaaoaXRC5cwdqZcXjikBrXTuCjHasdOS4q7cG4lDCC/64eFZxf bzSi8UwIOA2KoWaNbLcFtJkzlPSK2iQpDI2xQ5dz1qVnlMXSWVuIKlivrGNEEi1GrF28 1gSWOP0SckB3ij4Z70g2KzAGnGC2lh3LxENuLl6wks2GHrrgV4ZQWYEoYQfYw4uxo1Gb yylBflz6cXsyDBSLoBVQb42HhP7vfXrOszI7SUNAeSWYqUJSMimQuudbSywewAx9QJcA gYBg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1696858875; x=1697463675; 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=AuTRmMjy/yI9IhnNGvYwp29wf7SXW/Pt1+QfWnfBR18=; b=v2D7CPqTDMhgdsYKhejWXJlU0/BN5V4b5peM2Tzzi/agLZrJ3LUrXLCUcLkpj+vVJ1 s2f8VS/81g8WXQwUoEQzL+9+X0o5bjkknpzrSjWGrhj1WHnDgC/cchwTBUMlFvCZQazl 6KegXYokw4yPO3Zc1VpsDBJvkKqStDu+ecU3kf84zj3Ofq5rcwT98H5H2PBVK/owGIWz WOS5gtve0AfM/UJ6mWUZcduuNC6ONMv3u4kmt5hnEEPWyO5g5rH9LsR1Ha1YATd66aWW VGxXRzFuYlbF5sC38W3kUPV2RefVIhKxzqs2ZgW8KlxOxwIezfymdhMGyu3RacybPV7z OzgQ== X-Gm-Message-State: AOJu0YztIelGd30lAffJIs8NoTRq9p+xpoK8azFfjSl1QOVZK2J9l+NO XTDiS9RvhD/1eOkCfZD0hzT8/YzPdDIIrHXNAh3T1Q== X-Google-Smtp-Source: AGHT+IHkJHPzE6gx2TxLuteTcWLwKjQf77JolM/H2F7mPSLRH7HZ3p6gFbnle1/BVHarBR+LcDSGa14jvCdTVZeekVE= X-Received: by 2002:a17:906:3081:b0:9ae:73ca:bbad with SMTP id 1-20020a170906308100b009ae73cabbadmr13935201ejv.43.1696858874884; Mon, 09 Oct 2023 06:41:14 -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:41:03 +0100 Message-ID: Subject: Re: Accidental inclusion of core team on funds policy? To: Magnus Hagander Cc: Daniel Gustafsson , Jonathan Katz , Dave Cramer , pgsql-www@lists.postgresql.org Content-Type: multipart/alternative; boundary="00000000000078c99b060748bece" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --00000000000078c99b060748bece Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Mon, 9 Oct 2023 at 14:37, Magnus Hagander wrote: > On Mon, Oct 9, 2023 at 3:35=E2=80=AFPM Dave Page wrot= e: > > > > > > > > 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. > > Perhaps it should not actually be listed under "general policies" > then, and instead have a separate heading for charters? I think it's > the only such page we have, right? > At the moment, I believe it is. We should probably add something similar for PGCA though. --=20 Dave Page pgAdmin: https://www.pgadmin.org PostgreSQL: https://www.postgresql.org EDB: https://www.enterprisedb.com --00000000000078c99b060748bece Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


=
On Mon, 9 Oct 2023 at 14:37, Magnus H= agander <magnus@hagander.net&= gt; wrote:
On Mon, Oct 9, 2023 at 3:35=E2=80=AFPM= Dave Page <dpage= @pgadmin.org> wrote:
>
>
>
> On Mon, 9 Oct 2023 at 14:29, Daniel Gustafsson <daniel@yesql.se> wrote:
>>
>> > On 9 Oct 2023, at 15:25, Jonathan Katz <jkatz@postgresql.org> wrote:=
>> >
>> > On 2023-10-09 08:48, Dave Cramer wrote:
>> >> On Mon, 9 Oct 2023 at 08:46, Daniel Gustafsson <daniel@yesql.se> wrot= e:
>> >>> I happened to notice what seems like a copy/paste err= or in the funds group
>> >>> policy document on the website.=C2=A0 The first para = on the page 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 whic= h should be
>> changed at some point?=C2=A0 Right now it implies that the Funds g= roup reports to
>> the Core Team, or that the Core Team has influence on the Funds gr= oup, which
>> AFAIK isn't correct.
>
>
> Yes, it is. The core team has the power of veto over the Liaison and D= eputy 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 d= on't know our project) to have all the key details in one place.

Perhaps it should not actually be listed under "general policies"=
then, and instead have a separate heading for charters? I think it's the only such page we have, right?

At t= he moment, I believe it is. We should probably add something similar for PG= CA though.
=C2=A0
--
--00000000000078c99b060748bece--