Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.92) (envelope-from ) id 1jC1bc-0000BC-Du for pgsql-hackers@arkaria.postgresql.org; Wed, 11 Mar 2020 13:41:04 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1jC1ba-0003T9-KK for pgsql-hackers@arkaria.postgresql.org; Wed, 11 Mar 2020 13:41:02 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1jC1ba-0003Sy-92 for pgsql-hackers@lists.postgresql.org; Wed, 11 Mar 2020 13:41:02 +0000 Received: from mail-yw1-xc29.google.com ([2607:f8b0:4864:20::c29]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1jC1bX-0003aY-Vc for pgsql-hackers@postgresql.org; Wed, 11 Mar 2020 13:41:01 +0000 Received: by mail-yw1-xc29.google.com with SMTP id x5so1955018ywb.13 for ; Wed, 11 Mar 2020 06:40:59 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=6WYgo4rkr2nm1F2WK3VtR5zm5yQ5+CJ2HUt828JM2BU=; b=hr7G8JmCGJHJYopoCJb5Lf0Y20dAmW0OxaJ+AVm4hplB9f9vE+dKsowIRj2TAd5/Ps KNJZv0TcPm5dS9XK6Mn6i1NycQ78zWrl/jCukvnKa1W/DaPGiG/VyL9Vl4EnvPL51qHP HhEmBMtHGPi6s9Om8eMosIfICNPPHI2dfrWXabBy2JldBmXwTgZLly2JdSfgpg59gvPI ixISapXmFK3ESu290xnjmeIJSGNNp8Oc+uctdBXD9Qsa/zKlRBGrZ8fx7RMjK8nRBRcR RcYmRYNDjOe1Kqj/zlWnKdDZA9iV8eQqCxQXz/ja1GBXpmnh0FX1QZ9Ho06uxHm0CVU4 L/4A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=6WYgo4rkr2nm1F2WK3VtR5zm5yQ5+CJ2HUt828JM2BU=; b=uimIa5R0FRas9d9QJhDCzC3hNqjVfCvzsqIrX7779gtu/9EZPArF4NF4Ue12J+5d3q 8Msa6hIXk8enBly4ooEzVM+1qkR9g1V1kuQmnJxWt/Rxw7tpUS/fyD3RvPKk76JOGoLl COjcKSoZzrCHbKKdxIF7SBbuhg543ZYAQf6/n0YttQjAyoR+jNPpyS5O6Tw1FLri7wlN giQfrRfKzmcvWWATP/YEPbuv9m2+V9gvTl/Dw9cuM4hWTac4Nw6wJp53QjlpIRfz93rl kzc96awXJLEks9UYOCNTIVlux3pn98zTi/2rrP5gsyvFPp7/w9A/JTUQ7p2eRW6VMGYT hXzQ== X-Gm-Message-State: ANhLgQ3a0qPlYlW3/ks1k0xbk7lzaSx7ELMpI5ZJXTpLGZxjhKO8yh0+ X49c21Il3bUvpqWc5yGQ6LMy0Awdr/g79lji2k4= X-Google-Smtp-Source: ADFU+vuKJ2zurIJnknX6DDG5zMMZlda3MJ9MTcJp5SrUD8aDc9F58ixz3JWq6UsxGl8ipp9e4LRG5dXPjGIuqdMhGgQ= X-Received: by 2002:a25:c805:: with SMTP id y5mr3063808ybf.91.1583934056464; Wed, 11 Mar 2020 06:40:56 -0700 (PDT) MIME-Version: 1.0 References: <20191125075507.GH99720@paquier.xyz> In-Reply-To: From: Roger Harkavy Date: Wed, 11 Mar 2020 09:40:45 -0400 Message-ID: Subject: Re: Add A Glossary To: Corey Huinker Cc: pgsql-hackers@postgresql.org, Fabien COELHO , juergen@purtz.de, Michael Paquier Content-Type: multipart/alternative; boundary="000000000000c8870405a09462ed" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk --000000000000c8870405a09462ed Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hello, everyone, I'm Roger, the tech writer who worked with Corey on the glossary file. I just thought I'd announce that I am also on the list, and I'm looking forward to any questions or comments people may have. Thanks! On Tue, Mar 10, 2020 at 11:37 AM Corey Huinker wrote: > This latest version is an attempt at merging the work of J=C3=BCrgen Purt= z into > what I had posted earlier. There was relatively little overlap in the ter= ms > we had chosen to define. > > Each glossary definition now has a reference id (good idea J=C3=BCrgen), = the > form of which is "glossary-term". So we can link to the glossary from > outside if we so choose. > > I encourage everyone to read the definitions, and suggest fixes to any > inaccuracies or awkward phrasings. Mostly, though, I'm seeking feedback o= n > the structure itself, and hoping to get that committed. > > > On Tue, Feb 11, 2020 at 11:22 PM Corey Huinker > wrote: > >> It seems like this could be a good idea, still the patch has been >>> waiting on his author for more than two weeks now, so I have marked it >>> as returned with feedback. >>> >> >> In light of feedback, I enlisted the help of an actual technical writer >> (Roger Harkavy, CCed) and we eventually found the time to take a second >> pass at this. >> >> Attached is a revised patch. >> >> > --000000000000c8870405a09462ed Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hello, everyone,=20 I'm Roger, the tech writer who worked with Corey on the glossary file. I just thought I'd announce that I am also on the list, and I'm loo= king forward to any questions or comments people may have. Thanks!

On Tu= e, Mar 10, 2020 at 11:37 AM Corey Huinker <corey.huinker@gmail.com> wrote:
This latest version i= s an attempt at merging the work of=C2=A0J=C3=BCrgen Purtz into what I had = posted earlier. There was relatively little overlap in the terms we had cho= sen to define.

Each glossary definition now has a refere= nce id (good idea=C2=A0J=C3=BCrgen), the form of which is "glossary-te= rm". So we can link to the glossary from outside if we so choose.

I encourage everyone to read the definitions, and sugg= est fixes to any inaccuracies or awkward phrasings. Mostly, though, I'm= seeking feedback on the structure itself, and hoping to get that committed= .


On Tue, Feb 11, 2020 at 11:22 PM Corey Huinker <corey.huinker@gm= ail.com> wrote:
It seems like this could be a good idea, still th= e patch has been
waiting on his author for more than two weeks now, so I have marked it
as returned with feedback.

In light of = feedback, I enlisted the help of an actual technical writer (Roger Harkavy,= CCed) and we eventually found the time to take a second pass at this.

Attached is a revised patch.
=C2=A0
--000000000000c8870405a09462ed--