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 1qppgx-007CFt-AA for pgsql-www@arkaria.postgresql.org; Mon, 09 Oct 2023 12:48:59 +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 1qppgu-00Djsf-Rg for pgsql-www@arkaria.postgresql.org; Mon, 09 Oct 2023 12:48:57 +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 1qppgu-00DjsX-Jz for pgsql-www@lists.postgresql.org; Mon, 09 Oct 2023 12:48:57 +0000 Received: from mail-ed1-x52d.google.com ([2a00:1450:4864:20::52d]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1qppgt-000mt6-0T for pgsql-www@lists.postgresql.org; Mon, 09 Oct 2023 12:48:56 +0000 Received: by mail-ed1-x52d.google.com with SMTP id 4fb4d7f45d1cf-5384975e34cso7997327a12.0 for ; Mon, 09 Oct 2023 05:48:54 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1696855733; x=1697460533; 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=pdtaTZz1lQWFgcYT37CAxhVY60RHEITGMdjCFk2c1wU=; b=BITkZMdJqtLhcHkYBkwOsCmSPJgDZeliILM0/ooCbv4fHBV25vDXIGShgTkj4OkBYi 8w+aRI1dtmlLrxBa1N04BsQK2p5xPyX00cXkqHd3ZAdL/nk+Lb/UVgUmccvt/Woa0jxH EwnX74En0UlJNuONlPBRNrP5noKyHZ2h19y4uSxo1KnAi6Z1olFyhLExyCWACCUOSXzB n7QIganan9eYVUW5jpL6jOUh2OzlNobEpwauBu/AtoiO8EzHeKQGShl1B5xywRFWTCbg cgYe4SH8PSOZoC888LVvAZgkhl2P5QZjfxlCC2rOPEn8mhpDVLx/PHcmGNWxoOPP8JsC G93Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1696855733; x=1697460533; 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=pdtaTZz1lQWFgcYT37CAxhVY60RHEITGMdjCFk2c1wU=; b=Vu7ov2rMnAcStUMoWHF5eNJWrze+RMHjVEAapvyzWMZJC2Lw+EIfL5t1HwM3yFz3ED KbvYtZYozFu/4GSv0Xw6Fdkg/qxE+58uUYUv/PjSyRH41EY0hZCLGkl3UDI4GhBFhpx5 e5oNFXfJqlIguLgxXG19LoUBjq8YorL2XZF8dDd599WPB3e7xSgKlKCaIh61qNyf+366 Uz3ZmOj3X90MsRrEdhSATwJrtGk+0Uu/8dDyusfCKjeDE249bBvKSuf1xqAciv7dFA0e +C2bg7DkkrvzWAZ/dgCoKAIv3gBXNmNXy6jJgM+yLVI3sWxW3o6JTBNPJEEyoB0RuFPa kl2A== X-Gm-Message-State: AOJu0YyS/witkLkpuDjfHBeDaW72dSNPIdanaG81ofA0T9nAAO0NL15m aFEjrH0LnX8a6UZK7SKXoH1K8FhEBRsHj9SmzRqSR7hLuY+Vgg== X-Google-Smtp-Source: AGHT+IGPatYKh4AgNsgbLe0kBMzQWjzDQIAbY/sh5lhN0nyStfwRrDW+lbRxMGM8TaZu9oxEtg8km3dXe8TEIsVhRCs= X-Received: by 2002:aa7:c904:0:b0:525:7f37:e87a with SMTP id b4-20020aa7c904000000b005257f37e87amr13941656edt.16.1696855733081; Mon, 09 Oct 2023 05:48:53 -0700 (PDT) MIME-Version: 1.0 References: <87970758-9EF7-401A-8B91-D4A99ADA9EC1@yesql.se> In-Reply-To: <87970758-9EF7-401A-8B91-D4A99ADA9EC1@yesql.se> From: Dave Cramer Date: Mon, 9 Oct 2023 08:48:35 -0400 Message-ID: Subject: Re: Accidental inclusion of core team on funds policy? To: Daniel Gustafsson Cc: pgsql-www@lists.postgresql.org Content-Type: multipart/alternative; boundary="000000000000349d290607480342" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --000000000000349d290607480342 Content-Type: text/plain; charset="UTF-8" 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 Dave > > -- > Daniel Gustafsson > > --000000000000349d290607480342 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable



On Mon, 9 Oct 2023 at 08:46, Daniel Gustafsson &= lt;daniel@yesql.se> wrote:
I happened to notice w= hat seems like a copy/paste error in the funds group
policy document on the website.=C2=A0 The first para on the page explains C= ore Team
membership which seems incorrect as they are separate entities.

=C2=A0 =C2=A0 =C2=A0 =C2=A0 https://www.postgr= esql.org/about/policies/funds-group/

Shouldn't we do something like the attached?

<= /div>
+1 from me

Dave=C2=A0

--
Daniel Gustafsson

--000000000000349d290607480342--