Re: Commitfest manager for July 2024

From: "Andrey M(dot) Borodin" <x4mmm(at)yandex-team(dot)ru>
To: Corey Huinker <corey(dot)huinker(at)gmail(dot)com>, Tomas Vondra <tomas(dot)vondra(at)enterprisedb(dot)com>
Cc: Kirill Reshke <reshkekirill(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Commitfest manager for July 2024
Date: 2024-07-03 16:51:23
Message-ID: 3FFFC6CB-DB78-46CB-ADE3-EEC7667B2FB8@yandex-team.ru
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> On 3 Jul 2024, at 01:08, Corey Huinker <corey(dot)huinker(at)gmail(dot)com> wrote:
>
> I'll give it a shot.

Great, thank you! Do you have extended access to CF? Like activity log and mass-mail functions?
If no I think someone from PG_INFRA can grant you necessary access.

> On 3 Jul 2024, at 20:21, Tomas Vondra <tomas(dot)vondra(at)enterprisedb(dot)com> wrote:
>
> This reminded me that one of the changes proposed at pgconf.dev was
> having multiple CF managers, each responsible for a subset of the CF
> entries. Do we want to do try that?
>
> IIRC the idea was that it's not really feasible to shepherd ~400 patches
> (the current count for 2024-07), especially if the person has other
> things to do too, and spreading this over multiple people would make it
> more manageable - perhaps even allowing more people to participate.
>
> If we wanted to try this, would that require some improvements in the CF
> app, e.g. to track which CF manager is responsible for each entry?
>

Maybe can we just coordinate here? If Corey does not mind, I'd happily help with 2-3 sections. I particularly like "Replication and recovery" and "Server features", but would be glad to take any.

Best regards, Andrey Borodin.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Jacob Champion 2024-07-03 17:02:01 Re: [PoC] Federated Authn/z with OAUTHBEARER
Previous Message Daniel Gustafsson 2024-07-03 16:20:21 Re: Add support to TLS 1.3 cipher suites and curves lists