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 1h87Gx-0006xl-2K for pgsql-www@arkaria.postgresql.org; Sun, 24 Mar 2019 17:51:03 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1h87Gu-0008Hy-MS for pgsql-www@arkaria.postgresql.org; Sun, 24 Mar 2019 17:51:00 +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 1h87Gu-0008Hr-7f for pgsql-www@lists.postgresql.org; Sun, 24 Mar 2019 17:51:00 +0000 Received: from mail-lf1-x141.google.com ([2a00:1450:4864:20::141]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1h87Gm-0000Mm-Eq for pgsql-www@lists.postgresql.org; Sun, 24 Mar 2019 17:50:58 +0000 Received: by mail-lf1-x141.google.com with SMTP id u2so4420630lfd.4 for ; Sun, 24 Mar 2019 10:50:51 -0700 (PDT) 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=MBRjAOYe3WJOo1sHpNwghuMXVqSS4EQBkpmrGpM+qL8=; b=kbd+jUTnjmLtPqX9VGjLHfZiLISJJdF3Qm6NzmOydlKZK7/PPjqG/Y2N342pMyU89U W7UMRqshXmIZer2e0tE9FxSTv3QGiXJWpO3Vc261FfrJ7DgmIbNKwLy8bEvXQ68Bp+TV OjpbxKqO59hlmvzQjMBoulb99v7ZRE9QeI4bNO7pDTe7JM1VjGwkdiEwWMtsJoIKSAUG dNz/isQpHUlJCcyH6kBm/9P20ZBvyDOOU9QRfVyDkv4wM4eEAQbFp4KuuMSEfgY/ci8L tX9aoREX7wr2zYv/k++N0kB3AjaFzvr7rvPIVaP7WMXlXpRLuZ2fgebmCFZdCG1f0Lq2 lT/w== 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=MBRjAOYe3WJOo1sHpNwghuMXVqSS4EQBkpmrGpM+qL8=; b=KCFkazBuQZq7b1nlyAUP94/i406266QV4AJxCJ3A3UjLi/6KYSxV56DZr9/aoXnocR GIoqNTqJsrlR/qi4WslYvNG415uOL3/wAepRbY58tCEFubOycIflATUW+WikizjEs7qh tiZ1SSspTUGxV68ZIax3Zw7A4al+D1XQeHX1l6yTIozCTYyVlkAHMqQDHs9uk0SDntFh IiieLU0dX3cZWfDjWi3YAv1R3V84D46AryRtQivK+H4T8WOOUyM8bgD4GLXHHBzZpFgi 9onyInOQQa5AnDmmcnKHD9Qxx+2ydO16/khYbigBZH2XlF7MimJk+1vWM/Vnc7Xbv6Oz DJYQ== X-Gm-Message-State: APjAAAVHErfcBuEj41uFeezyTWXClJlG30iNQf86uwuc/nIgEG5Hx/Ha vGyVShbUWNKOZh9cFCszO+mb6E7hcWtSznn0+qZnUQ== X-Google-Smtp-Source: APXvYqzeZ806/D2GYvWb5WPmx+4tLPtvw0xMabBBbaV5sNnXe1rzBS3CbwnpiYfyXz5Pii1SfaiE+N/1NTBRRQaJs3A= X-Received: by 2002:a19:7d84:: with SMTP id y126mr10016139lfc.124.1553449848945; Sun, 24 Mar 2019 10:50:48 -0700 (PDT) MIME-Version: 1.0 References: <15706-8ded5d7a37af6278@postgresql.org> <9ef787c5-62a9-c0a3-6261-5ef4863c78d3@postgresql.org> In-Reply-To: <9ef787c5-62a9-c0a3-6261-5ef4863c78d3@postgresql.org> From: Magnus Hagander Date: Sun, 24 Mar 2019 18:50:37 +0100 Message-ID: Subject: Re: BUG #15706: Support Services page out of date To: "Jonathan S. Katz" Cc: Euler Taveira , PostgreSQL WWW , jtara-github@spamex.com Content-Type: multipart/alternative; boundary="0000000000006c50c90584daba42" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk --0000000000006c50c90584daba42 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Thu, Mar 21, 2019 at 1:20 AM Jonathan S. Katz wrote: > On 3/20/19 7:11 PM, Euler Taveira wrote: > > Em qua, 20 de mar de 2019 =C3=A0s 17:12, Jonathan S. Katz > > escreveu: > >> > >> I did an audit of it a few years back, we are due for another one (and > >> something on my TODO for this year). When I did the audit, it took > >> several weeks to review all of the listings, so without additional hel= p, > >> "every x months" is not reasonable. > >> > > Jonathan, I appreciate your effort. I'm suggesting an automated way to > > check the list (send an URL by email for confirmation). If there is no > > response, stop to show that company. Company can always enable it > > again. Periodic notification can encourage companies to keep their > > info up to date. I'm not volunteering to do the work. > > Some of the pgweb folks have discussed doing that before; it's not a bad > idea, and perhaps would cut down on some of the headaches. > That was in fact the original plan, nobody just got around to building it. There was even a db field for it in the early dev snapshots, but it was removed since it was never quite done. The general idea was to just have a "last confirmed" timestamp field on each entry, and just stop showing any entries that have not been confirmed in days/weeks/months/whatever. We can keep them around some extra time beyond that in case people come back to update them later of course. If we went down that route, I think we would want to borrow from some of > the pgeu codebase, which I believe has reminder infrastructure set up, > and then apply it to this. If we went down this path, it'd be good to > apply it to products in the software catalog as well. > I think we pretty much have all the needed parts already. All that's needed is a "last reminded" field along with the "last onfirmed" one above, and decide on a schedule between those two for sending reminders. Oh, and +1 for doing the same for products. --=20 Magnus Hagander Me: https://www.hagander.net/ Work: https://www.redpill-linpro.com/ --0000000000006c50c90584daba42 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable

On Thu, Mar 21, 2019 at 1:20 AM Jonathan = S. Katz <jkatz@postgresql.org> wrote:
On = 3/20/19 7:11 PM, Euler Taveira wrote:
> Em qua, 20 de mar de 2019 =C3=A0s 17:12, Jonathan S. Katz
> <jkatz@po= stgresql.org> escreveu:
>>
>> I did an audit of it a few years back, we are due for another one = (and
>> something on my TODO for this year). When I did the audit, it took=
>> several weeks to review all of the listings, so without additional= help,
>> "every x months" is not reasonable.
>>
> Jonathan, I appreciate your effort. I'm suggesting an automated wa= y to
> check the list (send an URL by email for confirmation). If there is no=
> response, stop to show that company. Company can always enable it
> again. Periodic notification can encourage companies to keep their
> info up to date. I'm not volunteering to do the work.

Some of the pgweb folks have discussed doing that before; it's not a ba= d
idea, and perhaps would cut down on some of the headaches.
=

That was in fact the original plan, nobody just got aro= und to building it. There was even a db field for it in the early dev snaps= hots, but it was removed since it was never quite done.

The general idea was to just have a "last confirmed" timest= amp field on each entry, and just stop showing any entries that have not be= en confirmed in <n> days/weeks/months/whatever. We can keep them arou= nd some extra time beyond that in case people come back to update them late= r of course.


If we went down that route, I think we would want to borrow from some of the pgeu codebase, which I believe has reminder infrastructure set up,
and then apply it to this. If we went down this path, it'd be good to apply it to products in the software catalog as well.
=
I think we pretty much have all the needed parts already. Al= l that's needed is a "last reminded" field along with the &qu= ot;last onfirmed" one above, and decide on a schedule between those tw= o for sending reminders.

Oh, and=C2=A0+1 for doing= the same for products.=C2=A0

--
=C2=A0Magnus Hagander<= br>=C2=A0Me: https:/= /www.hagander.net/
=C2=A0Work: https://www.redpill-linpro.com/
--0000000000006c50c90584daba42--