From: | Daniel Gustafsson <daniel(at)yesql(dot)se> |
---|---|
To: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Patch abstracts in the Commitfest app |
Date: | 2021-11-12 12:51:28 |
Message-ID: | 3C53E8AA-B53F-43C2-B3C6-FA71E18A462C@yesql.se |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
While reading through and working with the hundreds of patches in the CF app a
small feature/process request struck me: it would be really helpful if the
patch had a brief abstract outlining what it aims to add or fix (or summary,
description or something else; not sure what to call it). Basically a
two-sentence or so version of the email posting the patch to -hackers.
The "title" field isn't always explanatory enough, and diving into a long
thread to piece together clues can be quite daunting. I'm especially thinking
about new contributors who would like to contribute but who have a hard time
finding something in the CF app (which is a complaint I've heard from multiple
such contributors).
It should be a free-form textfield, and only apply to new submissions to avoid
a need to backfill. The field should, IMHO, be mandatory. The implementation
can be left to discussion on -www iff this list agrees that it would be a good
thing.
Thoughts?
--
Daniel Gustafsson https://vmware.com/
From | Date | Subject | |
---|---|---|---|
Next Message | Julien Rouhaud | 2021-11-12 12:59:57 | Re: Patch abstracts in the Commitfest app |
Previous Message | Daniel Gustafsson | 2021-11-12 12:41:58 | Re: Logical Replication - improve error message while adding tables to the publication in check_publication_add_relation |