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.89) (envelope-from ) id 1gcTIH-00015D-N2 for pgsql-docs@arkaria.postgresql.org; Thu, 27 Dec 2018 10:53:37 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1gcTIG-0007HN-2y for pgsql-docs@arkaria.postgresql.org; Thu, 27 Dec 2018 10:53:36 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1gcTIF-0007HE-PL for pgsql-docs@lists.postgresql.org; Thu, 27 Dec 2018 10:53:35 +0000 Received: from mail-lf1-x142.google.com ([2a00:1450:4864:20::142]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1gcTIB-0007kg-Pu for pgsql-docs@lists.postgresql.org; Thu, 27 Dec 2018 10:53:34 +0000 Received: by mail-lf1-x142.google.com with SMTP id c16so12441563lfj.8 for ; Thu, 27 Dec 2018 02:53:31 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hagander-net.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=nTma91EyfZdRduow7lX38BeqR7mWfDYgKTiXY1VB/sY=; b=fCDCs33dAPCYiea/5eWDgxXNMoazfH5P10eMh1BpXOAlJhYfTKp2ZaBK76JI8EOanJ UCl8PHn4fY1ijorbThVsAupOBwgz/vn3KBeHul4clmJC8jhCYKoLrhAO5okzZnk8Hbz5 2xKIe/x7iv1oo2tisPk1zldvN5zXPjTTJCBnm8UGvODwKTvWZn/qZXSRxsvRfVsZJQt1 gHEPEYMzWTT+gDqLR1MUdbKHyQtF07A0H1repXL21HPA0+4TpjErJt23BMiwlhYUXq5+ 0cgmB9IMyUrvbJAel940IXO9rZyjRZ0qqTokul7OA0g+AzM8h9JkVGCTYF6gfPFaJ1UH e5kw== 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=nTma91EyfZdRduow7lX38BeqR7mWfDYgKTiXY1VB/sY=; b=ptR77CDjHcG+UfG84FWppBU0mQ7WRT/+KXE4/lKjM7xuFsAkF1B6byJ5Hi24/7I8yD 50irE+OI7WF9bEFo4GLYJyoKjUYQR835MH++T1VERKJSnbCN5job4ANcWvvi+u+wAIA7 HcOFZG2XWI7ZmPraOaEgllzUiZ2FYe1JawdEbNBs8F3QoBW/4qS4rvZl0U6YCJawQFdA IdmbZ8Wwkevs2Hp8oGZQdnZ1L9Emr2fTlOX60BGHu0tWLFLDWBd6OItrX2VGCofzem51 Lo19H2TOIxqUgWCQVPclJUwpJAez15yKL9yD40SpyZug2KGVlhokhZDpp3NxeLU33JzH 27qg== X-Gm-Message-State: AA+aEWa32S1qVu5wpTf1cPeZGsPO7BCJnyNz2RDr5d4STe8+0Y4OmaNT Rwx6dse8JUnr8sJTa7IQItla6CZa4SQhDj79iGH4Tg== X-Google-Smtp-Source: AFSGD/W/X+vluJIboutWxvJH8K7YcVxtt0Q+grYa/sVCiVoUrj3d1OjDH6VhEFAA7NNjIjWsiSB9s++p9RQvSeFhP/A= X-Received: by 2002:ac2:4343:: with SMTP id o3mr12171597lfl.129.1545908009731; Thu, 27 Dec 2018 02:53:29 -0800 (PST) MIME-Version: 1.0 References: <15727.1545403523@sss.pgh.pa.us> <20181221151723.ju6byzk6lukykkwf@alvherre.pgsql> In-Reply-To: <20181221151723.ju6byzk6lukykkwf@alvherre.pgsql> From: Magnus Hagander Date: Thu, 27 Dec 2018 11:53:18 +0100 Message-ID: Subject: Re: tickling the lesser contributor's withering ego To: Alvaro Herrera Cc: Tom Lane , Erik Rijkers , PostgreSQL Developers , Pg Docs , "w^3" , "Jonathan S. Katz" Content-Type: multipart/alternative; boundary="000000000000c69bb8057dfec182" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk --000000000000c69bb8057dfec182 Content-Type: text/plain; charset="UTF-8" On Fri, Dec 21, 2018 at 4:17 PM Alvaro Herrera wrote: > On 2018-Dec-21, Tom Lane wrote: > > > Alvaro Herrera writes: > > > I propose the following patch, which will make those links stable -- > > > then we can add the following links to the contributors page: > > > > https://www.postgresql/org/docs/10/release-10.html#RELEASE-10-ACKNOWLEDGEMENTS > > > > https://www.postgresql/org/docs/11/release-11.html#RELEASE-11-ACKNOWLEDGEMENTS > > > > Seems reasonable, but note the lag time --- unless somebody does > > something out of the ordinary, those pages won't actually have > > such tags till after the February minor releases. > > Good point. That seems acceptable to me. > Good. While it *can* be worked around, it's a PITA and it risks getting overwritten by other things, since the normal docs loads are based off release tarballs. We can make them off a snapshot tarball, but it's a pain :) Oh, and +1 for stable links like that in general. That would be one good step. Not having considered what to do with, but it could also be interesting to teach the loader to read the structured data out of the XML file and store it in one of these weird things called a "database". That could be used for things like matching on the contributors list and add a little per-version badge to which versions they are known to contribute etc. That would require us to be quite consistent in the naming of people, and also not to have duplicates though, but maybe it can be valuable? Actually, do we have a policy for handling duplicates in the docs there? Since we only keep names there and not email or similar? -- Magnus Hagander Me: https://www.hagander.net/ Work: https://www.redpill-linpro.com/ --000000000000c69bb8057dfec182 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


=
On Fri, Dec 21, 2018 at 4:17 PM Alvaro Herrera <alvherre@2ndquadrant.com> wrote= :
On 2018-Dec-21= , Tom Lane wrote:

> Alvaro Herrera <alvherre@2ndquadrant.com> writes:
> > I propose the following patch, which will make those links stable= --
> > then we can add the following links to the contributors page:
> > https://www.= postgresql/org/docs/10/release-10.html#RELEASE-10-ACKNOWLEDGEMENTS
> > https://www.= postgresql/org/docs/11/release-11.html#RELEASE-11-ACKNOWLEDGEMENTS
>
> Seems reasonable, but note the lag time --- unless somebody does
> something out of the ordinary, those pages won't actually have
> such tags till after the February minor releases.

Good point.=C2=A0 That seems acceptable to me.

Good. While it *can* be worked around, it's a PITA and it risks= getting overwritten by other things, since the normal docs loads are based= off release tarballs. We can make them off a snapshot tarball, but it'= s a pain :)

Oh, and=C2=A0+1 for stable links like = that in general. That would be one good step.

Not = having considered what to do with, but it could also be interesting to teac= h the loader to read the structured data out of the XML file and store it i= n one of these weird things called a "database". That could be us= ed for things like matching on the contributors list and add a little per-v= ersion badge to which versions they are known to contribute etc. That would= require us to be quite consistent in the naming of people, and also not to= have duplicates though, but maybe it can be valuable?

=
Actually, do we have a policy for handling duplicates in the docs ther= e? Since we only keep names there and not email or similar?

<= /div>
--
=C2=A0Magnus Hagander
=C2=A0Me: https://www.hagander.net/
=C2=A0Work: https://www.redpill-l= inpro.com/
--000000000000c69bb8057dfec182--