Re: PG list descriptions

> On Aug 9, 2018, at 4:38 PM, Bruce Momjian <bruce@momjian.us> wrote:
>
> On Mon, Jul  2, 2018 at 03:08:17PM -0500, Justin Pryzby wrote:
>> Hi,
>>
>> I'm suggesting updated language for the list descriptions.
>> I couldn't find an address for list admins, so I'm hoping some of them live
>> here (by design or by coincidence).
>>
>> On this page: https://www.postgresql.org/list/
>> I suggest to change from:
>> |    If it is a general usage question, we recommend subscribing to the pgsql-general@postgresql.org mailing list. If it is a more technical question about how PostgreSQL internals work, we recommend subscribing to the pgsql-hackers@postgresql.org mailing list.
>> to:
>> |    If you're a DBA, system administrator, or software developer with a question about or problem using PostgreSQL, we recommend the pgsql-general@postgresql.org mailing list, which is monitored by many experienced PostgreSQL users who may offer advice.  For discussion about development of PostgreSQL itself or questions about its internals, we recommend the pgsql-hackers@postgresql.org mailing list.
>>
>> Here: https://www.postgresql.org/list/pgsql-general/
>> I suggest to change from:
>> |    General discussion area for users. Apart from compile, acceptance test, and bug problems, most new users will probably only be interested in this mailing list (unless they want to contribute to development or documentation). All non-bug related questions regarding PostgreSQL's version of SQL, and all installation related questions that do not involve bugs or failed compiles, should be restricted to this area. Please note that many of the developers monitor this area.
>> to:
>> |    Discussion and questions for users of PostgreSQL, including software developers and database and system administrators.  Topics include advanced technical questions as well as general discussion.  Many of the PostgreSQL developers monitor and contribute here.
>
> Can someone reply to this suggestion?  It looks valid to me.  I don't
> see this text in gitweb so it must be in a database somewhere.

It’s in pgarchives. It’s not accessible via the Django admin. I believe
Magnus would have to handle it.