public inbox for [email protected]
help / color / mirror / Atom feedFrom: Jonathan S. Katz <[email protected]>
To: Magnus Hagander <[email protected]>
Cc: Daniel Gustafsson <[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 09:31:50 -0400
Message-ID: <[email protected]> (raw)
In-Reply-To: <CABUevEzL8a8TMnsyxiDOgmt9n6ZecRN=A_gqD7fGiQCKfjgOTg@mail.gmail.com>
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]>
<CABUevEzL8a8TMnsyxiDOgmt9n6ZecRN=A_gqD7fGiQCKfjgOTg@mail.gmail.com>
On 4/27/19 6:41 AM, Magnus Hagander wrote:
>
>
> On Sat, Apr 27, 2019 at 5:48 AM Jonathan S. Katz <[email protected]
> <mailto:[email protected]>> wrote:
> This is also a long way of saying that I think we should proceed with
> the solution to help automate this. After going through the painstaking
> process again, I'd recommend it works kind of like this:
>
> - An email goes out once every {6 months, 1 year} to the organizational
> contact that says something like: "Hi, This is an automated check to
> ensure your company is still an active PostgreSQL service provider.
> Please click the URL provided to confirm. <UniqueURL> If you do not
> confirm within 7 days, your listing will be unpublished"
>
>
> 7 days might be a bit on the short side. If someone is unlucky they get
> the notification while on vacation for example, and then they're
> delisted before they can even see it.
Well, that's why I suggested it gets de-listed, so one of us can
manually check and determine if indeed it should be delisted, or it's
the case of out-of-office, or a bad email address, etc.
> - If user clicks URL, it is confirmed and the last_confirmed_date is set
> to CURRENT_DATE
>
> - If user does not click URL, we set the entry to unpublished. This
> would put it into the moderator feed, and one of the pgweb moderators
> can then take further action if need be.
>
>
> That's pretty close to my original thoughts around that, except I'd just
> delete them as step 3 and not bother the queue. I'm fine with
> de-listing it as well, as long as pgweb moderators are happy to handle
> that :) That would also take care of the scenario where the email
> bounces, by simply being able to ignore that fact and leave it up to the
> individual moderator to handle manually.
I would de-list it. It's certainly easier for a moderator to check a few
of said entries vs. the whole slew.
> Anyway, products needs a scrub as well, which I will try to block out
> some time for in the coming days to handle those as well. Those should
> hopefully not take as much time as they are a bit easier to verify.
>
> Cool. Thanks!
NP, feels good to do some spring/fall cleaning :)
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