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 1qpqSK-007Fa1-6Q for pgsql-www@arkaria.postgresql.org; Mon, 09 Oct 2023 13:37:56 +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 1qpqSI-00Dyxz-1i for pgsql-www@arkaria.postgresql.org; Mon, 09 Oct 2023 13:37:54 +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 1qpqSH-00Dyxr-Q5 for pgsql-www@lists.postgresql.org; Mon, 09 Oct 2023 13:37:54 +0000 Received: from mail-pj1-x1035.google.com ([2607:f8b0:4864:20::1035]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1qpqSF-0015mJ-V6 for pgsql-www@lists.postgresql.org; Mon, 09 Oct 2023 13:37:54 +0000 Received: by mail-pj1-x1035.google.com with SMTP id 98e67ed59e1d1-279294d94acso4193792a91.0 for ; Mon, 09 Oct 2023 06:37:51 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hagander-net.20230601.gappssmtp.com; s=20230601; t=1696858669; x=1697463469; darn=lists.postgresql.org; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=VZ+mGTfw6xHzKPQAO1EkT3DTR9bkgXIu/uGJAP1s3Bc=; b=2BZibxjDkWvLup6V9TnS1sK4Zc+0OeTxkaIQO2Zm7tmx2JbLPM6Yjegxyw1uBcx/HG 1Uasz+5r3qAMTbLWC8FVzu9GqGNhg6/dKzwMrDvQwGa8RaeeAxgxIR+cY49KVXHlCH9l xaQUxX4ObX+W6Yj5bMjYTfkN6ofjfswLfHjjzC7+N+LWH8WTkMang5BKI9/nQjx//W0g Xvlrq6+1Z5Z/XfyrdVzHqMqkvIziBR3TrDJLmw0IoMKOXmFXZHN4iR2S7hYjRfOfYjcC Aa0cElSvy/MGRu/7U5OdK+mVZ/pt/jDXZT+raelpTW85UIVxmtBApIxWdxeqd4dnZJB5 Xd3Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1696858669; x=1697463469; h=content-transfer-encoding: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=VZ+mGTfw6xHzKPQAO1EkT3DTR9bkgXIu/uGJAP1s3Bc=; b=SAH1mOQdlL/BmUraQ7Py0Y+K/7/OFhgeNRt/H8577Wa5YsQ9tUoO4JKHMWRZFEIaN4 IBevuVJFz2uSNJeld7xPq6kg/E8WLP9Db5dCgTdltcqGjISeawU+WIs63AcsrPpMrHQu 89J9K1SHdm50Gw7vkwmqidecYJe0btYhHaqlH3PsXAU9OcfU5u2aVD/MvrXFPR9bo4EU hpniY01BpEuWdh3gMZMAMkxrWd9rh6FvH1rDF86YqLf+eYIZaHMKuvJ8olql9N5VXk0i s4nlKu5yvbQjBbnGfRGlYHkYOlZiv2Oc7K7xOJT90Ar39BX+Dnf/pXLnexSyoU43F1hq RABg== X-Gm-Message-State: AOJu0YxI+BMmnQNxx0svCGxyZAUTKkaSM4oZXwm3IDlSW14dx0fQ+wni S/Ki4zZpUy2BjFp9+2xf06L/5LJkVpMnoWMvpt4oiQ== X-Google-Smtp-Source: AGHT+IGieI4+vbxIpTTyxEJZFRhM2aaqGdRckN3s4mrmO7fQ/LsNPFOEZGJLoR/ikRMeFQxXbWSX97K4DDLmyXtyOH4= X-Received: by 2002:a17:90a:898a:b0:26f:392f:f901 with SMTP id v10-20020a17090a898a00b0026f392ff901mr19241547pjn.14.1696858669454; Mon, 09 Oct 2023 06:37:49 -0700 (PDT) MIME-Version: 1.0 References: <87970758-9EF7-401A-8B91-D4A99ADA9EC1@yesql.se> <7031a8d39e8a5f2545c9c7ad2c17d763@postgresql.org> In-Reply-To: From: Magnus Hagander Date: Mon, 9 Oct 2023 15:37:36 +0200 Message-ID: Subject: Re: Accidental inclusion of core team on funds policy? To: Dave Page Cc: Daniel Gustafsson , Jonathan Katz , Dave Cramer , pgsql-www@lists.postgresql.org Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Mon, Oct 9, 2023 at 3:35=E2=80=AFPM Dave Page wrote: > > > > 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 wrot= e: >> >>> 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 shou= ld be >> changed at some point? Right now it implies that the Funds group report= s to >> the Core Team, or that the Core Team has influence on the Funds group, w= hich >> AFAIK isn't correct. > > > Yes, it is. The core team has the power of veto over the Liaison and Depu= ty Liaison. > > This page is the charter which describes the relationship between the pro= ject 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? //Magnus