| From: | Nathan Bossart <nathandbossart(at)gmail(dot)com> |
|---|---|
| To: | Greg Sabino Mullane <htamfids(at)gmail(dot)com> |
| Cc: | Andrew Atkinson <andyatkinson(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)postgresql(dot)org, samay(at)tembo(dot)io |
| Subject: | Re: An improved README experience for PostgreSQL |
| Date: | 2024-02-28 17:10:48 |
| Message-ID: | 20240228171048.GC2435539@nathanxps13 |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Feb 28, 2024 at 09:56:57AM -0500, Greg Sabino Mullane wrote:
> +1 on the general idea. Maybe make that COPYRIGHT link go to an absolute
> URI, like all the other links, in case this file gets copied somewhere?
> Perhaps point it to https://www.postgresql.org/about/licence/
I suspect there will be quite a bit of discussion about what to add to the
README, which is great, but I think we should establish an order of
operations here. We could either add suggested content to the README and
then create an identical Markdown version, or we could create a Markdown
version and add content to both afterwards. The former has my vote since
it seems like it would require less churn. In any case, I think it would
be useful to keep the Markdown effort separate from the content effort
somehow (e.g., separate threads).
--
Nathan Bossart
Amazon Web Services: https://aws.amazon.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2024-02-28 17:17:04 | Re: An improved README experience for PostgreSQL |
| Previous Message | Nathan Bossart | 2024-02-28 17:02:37 | Re: An improved README experience for PostgreSQL |