public inbox for [email protected]
help / color / mirror / Atom feedFrom: Magnus Hagander <[email protected]>
To: Jonathan S. Katz <[email protected]>
Cc: Euler Taveira <[email protected]>
Cc: PostgreSQL WWW <[email protected]>
Cc: [email protected]
Subject: Re: BUG #15706: Support Services page out of date
Date: Sun, 24 Mar 2019 18:50:37 +0100
Message-ID: <CABUevExGH5gEuPFJDsdqtS8y238KDMb7N_9r5Db=d6pOeCdtNA@mail.gmail.com> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
<CAHE3wggAmsRALu999i8+n2MHp1mUg9V=XHUV3Qt8zjURv66rNQ@mail.gmail.com>
<[email protected]>
<CAHE3wgiWYdGuS9X=MT5HXKQoe=nCMZ1qqvn9yZ2qGiecbwozQw@mail.gmail.com>
<[email protected]>
On Thu, Mar 21, 2019 at 1:20 AM Jonathan S. Katz <[email protected]>
wrote:
> On 3/20/19 7:11 PM, Euler Taveira wrote:
> > Em qua, 20 de mar de 2019 às 17:12, Jonathan S. Katz
> > <[email protected]> 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 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 <n> 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.
--
Magnus Hagander
Me: https://www.hagander.net/ <http://www.hagander.net/;
Work: https://www.redpill-linpro.com/ <http://www.redpill-linpro.com/;
view thread (16+ messages) latest in thread
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected], [email protected], [email protected], [email protected]
Subject: Re: BUG #15706: Support Services page out of date
In-Reply-To: <CABUevExGH5gEuPFJDsdqtS8y238KDMb7N_9r5Db=d6pOeCdtNA@mail.gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox