public inbox for [email protected]  

help / color / mirror / Atom feed

From: Jonathan S. Katz <[email protected]>
To: Daniel Gustafsson <[email protected]>
To: Magnus Hagander <[email protected]>
Cc: Euler Taveira <[email protected]>
Cc: PostgreSQL WWW <[email protected]>
Cc: [email protected] <[email protected]>
Subject: Re: BUG #15706: Support Services page out of date
Date: Sat, 27 Apr 2019 21:37:53 -0400
Message-ID: <[email protected]> (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]>
	<CABUevExGH5gEuPFJDsdqtS8y238KDMb7N_9r5Db=d6pOeCdtNA@mail.gmail.com>
	<nnaVBg86IghiaxiYkCAU9XA9VklOeBuv05GyUGUJloHu0QwGsDCNIzVh8kauw_XTRx6hpJ3IR6SIOWPIc80QBbTQr9Y0VEof0b-I-f9JE58=@yesql.se>
	<[email protected]>

On 4/26/19 11:48 PM, Jonathan S. Katz wrote:
> On 3/25/19 5:33 AM, Daniel Gustafsson wrote:
>> On Sunday, March 24, 2019 6:50 PM, Magnus Hagander <[email protected]>
>> wrote:
>>> On Thu, Mar 21, 2019 at 1:20 AM Jonathan S. Katz <[email protected]
>>> <mailto:[email protected]>> wrote:
>>>
>>>     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.
>>
>> I think it makes sense to remove after a set timeout, if the user hasn't
>> verified in 3 months (or some
>> other sufficiently long period) then the odds that the entry is out of
>> date seems quite high.
>>
>>> Oh, and +1 for doing the same for products. 

OK, so I did the scrub for products.

> The scrub took me about 2 hours and change.

Fortunately, products are a bit more straightforward and did not take as
long as services, though it was still at least an hour. So whatever
system we put in place for services, I suggest the same for products

There were 210 products listed at the beginning of the scrub.

- 170 remain
- 40 were removed as they did not exist + no obvious replacement / went
to things I wish I could unsee.

I would say this was more stale than I thought too, but given that there
has not been a product scrub as long as I can remember, it's not as bad
as the staleness of the services.

Regardless, let's work on getting that system into place to help manage
it so scrubs are less gargantuan tasks.

Thanks,

Jonathan



Attachments:

  [application/pgp-signature] signature.asc (833B, 2-signature.asc)
  download

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], [email protected]
  Subject: Re: BUG #15706: Support Services page out of date
  In-Reply-To: <[email protected]>

* 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