Re: Intention to start an [oauth] "working group"
| От | Melanie Plageman | 
|---|---|
| Тема | Re: Intention to start an [oauth] "working group" | 
| Дата | |
| Msg-id | CAAKRu_avTe-d2g952FVcE3xpkFW5Spe6FQwfHcGEd8b-_bmvXQ@mail.gmail.com обсуждение исходный текст  | 
		
| Ответ на | Intention to start an [oauth] "working group" (Jacob Champion <jacob.champion@enterprisedb.com>) | 
| Список | pgsql-hackers | 
On Thu, Oct 23, 2025 at 1:25 PM Jacob Champion <jacob.champion@enterprisedb.com> wrote: > > I can't really guess how well these will work within our community. So > I'd like to propose an experimental working group covering the new > OAuth code. Sounds like a good experiment to me. > = What does that mean? = > > "Working group" probably carries a bunch of baggage as a term (and > honestly, I wouldn't mind a better suggestion). I want something > lightweight, so here's what I propose to do: > > - I will add "[oauth]" to feature threads I start, so people can filter on it. > - I will add an "[oauth]" tag to the CF app. > - I will attempt to keep a living summary on the wiki for every > [oauth] feature, including ones started by other people, with some > inspiration from my favorite parts of the Python PEPs [2]. All of those ideas make sense. I had suggested to Andres that we add an AIO/DIO CF tag to the CF app because many of the sub-projects he's working on for AIO are not obviously related (e.g. adding a different kind of buffer locking). If people want to get their head around what work needs to be done for the feature, it can be difficult. I haven't followed oauth development enough to know if all related threads and CF entries are more obviously related, but it seems like a good idea for big multi-release projects to bucket their work somehow for ease of consumption of those less in the weeds. - Melanie
В списке pgsql-hackers по дате отправления: