Thread: Accidental inclusion of core team on funds policy?

Accidental inclusion of core team on funds policy?

From
Daniel Gustafsson
Date:
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?

--
Daniel Gustafsson


Attachment

Re: Accidental inclusion of core team on funds policy?

From
Dave Cramer
Date:



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.  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

Re: Accidental inclusion of core team on funds policy?

From
Jonathan Katz
Date:
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.  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.

Jonathan



Re: Accidental inclusion of core team on funds policy?

From
Daniel Gustafsson
Date:
> 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.  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.

--
Daniel Gustafsson




Re: Accidental inclusion of core team on funds policy?

From
Dave Cramer
Date:

Dave Cramer


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

Re: Accidental inclusion of core team on funds policy?

From
Dave Page
Date:


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> 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. 

--

Re: Accidental inclusion of core team on funds policy?

From
Magnus Hagander
Date:
On Mon, Oct 9, 2023 at 3:35 PM 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> 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
(becauseothers 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



Re: Accidental inclusion of core team on funds policy?

From
Dave Page
Date:


On Mon, 9 Oct 2023 at 14:37, Magnus Hagander <magnus@hagander.net> wrote:
On Mon, Oct 9, 2023 at 3:35 PM 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> 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.
 
--