| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | Matemática A3K <matematica(dot)a3k(at)gmail(dot)com> |
| Cc: | Daniel Gustafsson <daniel(at)yesql(dot)se>, Xavier Fischer <xavier_fischer(at)hotmail(dot)fr>, "pgsql-docs(at)lists(dot)postgresql(dot)org" <pgsql-docs(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Introductory docs-hacking task: Example markup |
| Date: | 2026-11-17 05:20:25 |
| Message-ID: | CAKFQuwbrCB8TKWYdvFXojO9TW3zMXkLkaY2dzsF-MPVjwOVGVQ@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs |
On Mon, Nov 16, 2026 at 8:00 PM Matemática A3K <matematica(dot)a3k(at)gmail(dot)com>
wrote:
> Defining such mechanism should be the priority.
>
I agree that the lack of these guidelines adds a decent amount of friction.
But the project itself has basically zero priorities and this one item
isn't going to make such a list come into existence.
To a large extent what the docs do today is the guideline, if you want
evidence to back a position that is where it will be found.
A decent number of such potential guidelines have been mentioned in the
past, but getting them actually committed right now hasn't been attempted
by anyone, for whatever their personal reasons. Sticking an agent on the
mailing list archives looking for such - my participation in a thread
should narrow the surface area quite a bit though I don't know how big the
false negative set would be - would be a fruitful way to start such an
endeavor. Its on my own todo list but down quite a ways in priority.
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Karen Jex | 2026-11-17 08:49:52 | Re: Good beginner doc-hacking task: clear-text vs. cleartext vs. clear text vs. plaintext etc.. |
| Previous Message | Vinay Manikanda | 2026-11-17 03:44:57 | Re: Introductory docs-hacking task: Example markup |