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 1qpqMF-007FAy-5P for pgsql-www@arkaria.postgresql.org; Mon, 09 Oct 2023 13:31:39 +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 1qpqMB-00Dx52-Ti for pgsql-www@arkaria.postgresql.org; Mon, 09 Oct 2023 13:31:36 +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 1qpqMB-00Dx4S-LT for pgsql-www@lists.postgresql.org; Mon, 09 Oct 2023 13:31:36 +0000 Received: from mail-ej1-x630.google.com ([2a00:1450:4864:20::630]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1qpqM9-0015jV-Ut for pgsql-www@lists.postgresql.org; Mon, 09 Oct 2023 13:31:36 +0000 Received: by mail-ej1-x630.google.com with SMTP id a640c23a62f3a-9ba081173a3so401877566b.1 for ; Mon, 09 Oct 2023 06:31:33 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1696858293; x=1697463093; 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=I0GuXmbwaecNNaYv7uhD2cOGTBpRDOY1MXhy3aPmA4c=; b=RRL6YOmKC//gRKVSJZKzU70Aim4GqIfCAjsj6iSNURxw2Gsfd74jatWl2yv+m0AFDX yId5L1axYfvbIieCZbtI/zy94m+XcIyI3CunIlK6kVT0TvF/lQE2EoIP6TahzbdjuLDg X6p0F+3fi+y7+gt9b7dxAgCStTiOPFOqMBcFWbNiH2XIRbzf0A2P38B2BM7IqVlozyyN 3YK1dMWw1ju6L73Vt6tIBNBqf7pe1hEdFyO6vE5PF7+WUVNQTK/VZ+m9259FYhOMc8Yb qJu6wPU847Y1Ir6RqeIiECDWVIL/wPFVoOW4k98j4efE+2/V5HJmU1hdmCzDm7DZQ7tf 4xDg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1696858293; x=1697463093; 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=I0GuXmbwaecNNaYv7uhD2cOGTBpRDOY1MXhy3aPmA4c=; b=UVMMqStWLPc3jR8HT0ojsqMCWDhk6CHsTdDjBGbGnhEOgoxMEZBTfAimHRKs3Qys5p CN4Gor+dgP1TexQJWTFF+9w1Lant6xfZgBdR3UeAHNIPN26OkExq8J87Md9cDQNWWqPm q9eJqtdjbXYWNCvG1xStEV4QJ1F3cn699xsr8s3FmVSk3Ab1rI6Pe2Flgyi7+w2ZDp2A rkzz2uvFcDj3q/h/SC5weYhWNLz13HpNU0FZ7Nv72OemEDJ9sFhiTL9ngsOUTdGMj5x5 HRYrvorQEeKIeqCyEb/wey0sU8WyIugKYQow7bZD6nCw5CuaI2kbZqRXUrMemKSibNRO zbng== X-Gm-Message-State: AOJu0Yw0CCuYftnyiYI9tEaEuzDbl0P7oBba5ctB3ySv2DtYKGLTqmdf QhHV/oKdBZc43SvHHYAWLHnsJ59H/YCTpAWgQkc= X-Google-Smtp-Source: AGHT+IFb9jFSTTtXKgTrvH7uzRqcTACRtM0WGWuOrKsZb+wDZ7nez043Mk20TCgm2HL8iAyJbhhgFj1stQ3N7vbZ/QQ= X-Received: by 2002:a17:906:314c:b0:9a5:d657:47e1 with SMTP id e12-20020a170906314c00b009a5d65747e1mr14381416eje.43.1696858292689; Mon, 09 Oct 2023 06:31:32 -0700 (PDT) MIME-Version: 1.0 References: <87970758-9EF7-401A-8B91-D4A99ADA9EC1@yesql.se> <7031a8d39e8a5f2545c9c7ad2c17d763@postgresql.org> In-Reply-To: From: Dave Cramer Date: Mon, 9 Oct 2023 09:31:16 -0400 Message-ID: Subject: Re: Accidental inclusion of core team on funds policy? To: Daniel Gustafsson Cc: Jonathan Katz , pgsql-www@lists.postgresql.org Content-Type: multipart/alternative; boundary="000000000000c525e50607489b9f" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --000000000000c525e50607489b9f Content-Type: text/plain; charset="UTF-8" Dave Cramer On Mon, 9 Oct 2023 at 09: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. > > Why is the Core Team membership mentioned there ? Dave --000000000000c525e50607489b9f Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable

Dave Cramer


On Mon, 9 Oct 2023 at 0= 9: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> 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.

Why is the Core Team membership mentioned there ?

Dave
--000000000000c525e50607489b9f--