From: | "Jonathan S(dot) Katz" <jkatz(at)postgresql(dot)org> |
---|---|
To: | Magnus Hagander <magnus(at)hagander(dot)net> |
Cc: | Daniel Gustafsson <daniel(at)yesql(dot)se>, Euler Taveira <euler(at)timbira(dot)com(dot)br>, PostgreSQL WWW <pgsql-www(at)lists(dot)postgresql(dot)org>, "jtara-github(at)spamex(dot)com" <jtara-github(at)spamex(dot)com> |
Subject: | Re: BUG #15706: Support Services page out of date |
Date: | 2019-04-27 13:31:50 |
Message-ID: | 88dabc4f-ac7d-1c0c-5eaf-58992937c3ac@postgresql.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs pgsql-www |
On 4/27/19 6:41 AM, Magnus Hagander wrote:
>
>
> On Sat, Apr 27, 2019 at 5:48 AM Jonathan S. Katz <jkatz(at)postgresql(dot)org
> <mailto:jkatz(at)postgresql(dot)org>> 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
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2019-04-27 14:47:13 | Re: BUG #15781: subselect on foreign table (postgres_fdw) can crash (segfault) |
Previous Message | Etsuro Fujita | 2019-04-27 13:30:37 | Re: BUG #15781: subselect on foreign table (postgres_fdw) can crash (segfault) |
From | Date | Subject | |
---|---|---|---|
Next Message | Jonathan S. Katz | 2019-04-28 01:37:53 | Re: BUG #15706: Support Services page out of date |
Previous Message | Magnus Hagander | 2019-04-27 10:41:09 | Re: BUG #15706: Support Services page out of date |