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 1qpqKJ-007Ez5-VO for pgsql-www@arkaria.postgresql.org; Mon, 09 Oct 2023 13:29:40 +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 1qpqKH-00DvvF-UT for pgsql-www@arkaria.postgresql.org; Mon, 09 Oct 2023 13:29:38 +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 1qpqKH-00Dvuz-NW for pgsql-www@lists.postgresql.org; Mon, 09 Oct 2023 13:29:38 +0000 Received: from smtp.outgoing.loopia.se ([93.188.3.37]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1qpqKF-0015iG-Rx for pgsql-www@lists.postgresql.org; Mon, 09 Oct 2023 13:29:38 +0000 Received: from s807.loopia.se (localhost [127.0.0.1]) by s807.loopia.se (Postfix) with ESMTP id 074A22FB5E54 for ; Mon, 9 Oct 2023 15:29:21 +0200 (CEST) Received: from s979.loopia.se (unknown [172.22.191.6]) by s807.loopia.se (Postfix) with ESMTP id E7A522E2CC34; Mon, 9 Oct 2023 15:29:20 +0200 (CEST) Received: from s474.loopia.se (unknown [172.22.191.5]) by s979.loopia.se (Postfix) with ESMTP id E5F8710BC384; Mon, 9 Oct 2023 15:29:20 +0200 (CEST) X-Virus-Scanned: amavisd-new at amavis.loopia.se X-Spam-Flag: NO X-Spam-Score: -1.01 X-Spam-Level: X-Spam-Status: No, score=-1.01 tagged_above=-999 required=6.2 tests=[ALL_TRUSTED=-1, T_SCC_BODY_TEXT_LINE=-0.01] autolearn=disabled Received: from s934.loopia.se ([172.22.191.5]) by s474.loopia.se (s474.loopia.se [172.22.190.14]) (amavisd-new, port 10024) with LMTP id zqHT-J6JoASL; Mon, 9 Oct 2023 15:29:20 +0200 (CEST) X-Loopia-Auth: user X-Loopia-User: daniel@yesql.se X-Loopia-Originating-IP: 89.255.232.193 Received: from smtpclient.apple (customer-89-255-232-193.stosn.net [89.255.232.193]) (Authenticated sender: daniel@yesql.se) by s934.loopia.se (Postfix) with ESMTPSA id 6F5407CEAA5; Mon, 9 Oct 2023 15:29:20 +0200 (CEST) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3696.120.41.1.3\)) Subject: Re: Accidental inclusion of core team on funds policy? From: Daniel Gustafsson In-Reply-To: <7031a8d39e8a5f2545c9c7ad2c17d763@postgresql.org> Date: Mon, 9 Oct 2023 15:29:20 +0200 Cc: Dave Cramer , pgsql-www@lists.postgresql.org Content-Transfer-Encoding: quoted-printable Message-Id: References: <87970758-9EF7-401A-8B91-D4A99ADA9EC1@yesql.se> <7031a8d39e8a5f2545c9c7ad2c17d763@postgresql.org> To: Jonathan Katz X-Mailer: Apple Mail (2.3696.120.41.1.3) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk > On 9 Oct 2023, at 15:25, Jonathan Katz wrote: >=20 > 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 >=20 > -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. -- Daniel Gustafsson