Thread: Where's my event?
I recently posted an Event to postgresql.org, but it has not appeared. I've got no way of checking that the posting is actually in a queue somewhere, so its possible that a problem occurred and the posting did not take place. If it is on a queue, how do we check whether someone is actually moderating it? Seems like a general case problem as well as a specific one. Thanks, -- Simon Riggs http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Training & Services
On Thu, Apr 28, 2011 at 10:41 AM, Simon Riggs <simon@2ndquadrant.com> wrote: > I recently posted an Event to postgresql.org, but it has not appeared. > > I've got no way of checking that the posting is actually in a queue > somewhere, so its possible that a problem occurred and the posting did > not take place. > > If it is on a queue, how do we check whether someone is actually moderating it? Ask here. I've approved it now. > Seems like a general case problem as well as a specific one. Yes, it's a problem I complain about regularly. iirc Greg Smith was the last volunteer who was going to ensure everything got dealt with. -- Dave Page Blog: http://pgsnake.blogspot.com Twitter: @pgsnake EnterpriseDB UK: http://www.enterprisedb.com The Enterprise PostgreSQL Company
On Thu, Apr 28, 2011 at 10:49 AM, Dave Page <dpage@pgadmin.org> wrote: > On Thu, Apr 28, 2011 at 10:41 AM, Simon Riggs <simon@2ndquadrant.com> wrote: >> I recently posted an Event to postgresql.org, but it has not appeared. >> >> I've got no way of checking that the posting is actually in a queue >> somewhere, so its possible that a problem occurred and the posting did >> not take place. >> >> If it is on a queue, how do we check whether someone is actually moderating it? > > Ask here. I've approved it now. > >> Seems like a general case problem as well as a specific one. > > Yes, it's a problem I complain about regularly. iirc Greg Smith was > the last volunteer who was going to ensure everything got dealt with. I'm told that the policy was to not approve submissions from the moderator's own company. I like that policy and wish to support it. But it does need at least 2 active participants. Do we have that? Adding manpower is a solvable problem, but only with the right authority. Seems strange to have to fill out a form, then send an email each time. -- Simon Riggs http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Training & Services
On Thu, Apr 28, 2011 at 11:11 AM, Simon Riggs <simon@2ndquadrant.com> wrote: > On Thu, Apr 28, 2011 at 10:49 AM, Dave Page <dpage@pgadmin.org> wrote: >> On Thu, Apr 28, 2011 at 10:41 AM, Simon Riggs <simon@2ndquadrant.com> wrote: >>> I recently posted an Event to postgresql.org, but it has not appeared. >>> >>> I've got no way of checking that the posting is actually in a queue >>> somewhere, so its possible that a problem occurred and the posting did >>> not take place. >>> >>> If it is on a queue, how do we check whether someone is actually moderating it? >> >> Ask here. I've approved it now. >> >>> Seems like a general case problem as well as a specific one. >> >> Yes, it's a problem I complain about regularly. iirc Greg Smith was >> the last volunteer who was going to ensure everything got dealt with. > > I'm told that the policy was to not approve submissions from the > moderator's own company. Yes, but that doesn't mean just ignoring it - it means pinging another moderator. > I like that policy and wish to support it. But it does need at least 2 > active participants. Do we have that? We've not been able to manage that reliably in 10 years, hence my periodic rants on the subject, and the daily nagging email the gets automatically sent. -- Dave Page Blog: http://pgsnake.blogspot.com Twitter: @pgsnake EnterpriseDB UK: http://www.enterprisedb.com The Enterprise PostgreSQL Company
On Thu, Apr 28, 2011 at 11:19 AM, Dave Page <dpage@pgadmin.org> wrote: >>> Yes, it's a problem I complain about regularly. iirc Greg Smith was >>> the last volunteer who was going to ensure everything got dealt with. >> >> I'm told that the policy was to not approve submissions from the >> moderator's own company. > > Yes, but that doesn't mean just ignoring it - it means pinging another > moderator. Be careful what you wish for. :-) -- Simon Riggs http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Training & Services
On Thu, Apr 28, 2011 at 11:24 AM, Simon Riggs <simon@2ndquadrant.com> wrote: > On Thu, Apr 28, 2011 at 11:19 AM, Dave Page <dpage@pgadmin.org> wrote: > >>>> Yes, it's a problem I complain about regularly. iirc Greg Smith was >>>> the last volunteer who was going to ensure everything got dealt with. >>> >>> I'm told that the policy was to not approve submissions from the >>> moderator's own company. >> >> Yes, but that doesn't mean just ignoring it - it means pinging another >> moderator. > > Be careful what you wish for. :-) I'm fine with being pinged - I just don't have the cycles to do the daily check. -- Dave Page Blog: http://pgsnake.blogspot.com Twitter: @pgsnake EnterpriseDB UK: http://www.enterprisedb.com The Enterprise PostgreSQL Company
Dave Page wrote: > Yes, it's a problem I complain about regularly. iirc Greg Smith was > the last volunteer who was going to ensure everything got dealt with. > What Dave is too nice to say is that I slid out of the active moderator set a few months ago, much like previous moderators of yore who made similar claims. Made it almost a year before getting too distracted to keep up every day. (Don't even want to talk about my pgsql-hackers backlog) The only good way to make sure moderation stays timely for one's events is to volunteer someone who helps makes sure the rest of the queue says clean. Then the periodic "hey, can someone else review my request?" finds nothing but that waiting. In short: if you want visibility into the queue and its lack of progress, ask the person you have working on keeping the queue clean. -- Greg Smith 2ndQuadrant US greg@2ndQuadrant.com Baltimore, MD PostgreSQL Training, Services, and 24x7 Support www.2ndQuadrant.us
Simon, > I've got no way of checking that the posting is actually in a queue > somewhere, so its possible that a problem occurred and the posting did > not take place. Assuming we ever move over to Django, I'm hoping that will mean that users will be able to view their own pending and approvedsubmissions. This would solve a lot of issues we have with the current news/events/services stuff. -- Josh Berkus PostgreSQL Experts Inc. http://pgexperts.com San Francisco
On Mon, May 2, 2011 at 17:27, Joshua Berkus <josh@agliodbs.com> wrote: > Simon, > >> I've got no way of checking that the posting is actually in a queue >> somewhere, so its possible that a problem occurred and the posting did >> not take place. > > Assuming we ever move over to Django, I'm hoping that will mean that users will be able to view their own pending and approvedsubmissions. This would solve a lot of issues we have with the current news/events/services stuff. That part is already in the code... -- Magnus Hagander Me: http://www.hagander.net/ Work: http://www.redpill-linpro.com/
On 05/02/2011 11:27 AM, Joshua Berkus wrote: >> I've got no way of checking that the posting is actually in a queue >> somewhere, so its possible that a problem occurred and the posting did >> not take place. >> > Assuming we ever move over to Django, I'm hoping that will mean that users will be able to view their own pending and approvedsubmissions. This would solve a lot of issues we have with the current news/events/services stuff. > I don't think that particular bit will make any real difference though. Right now things submitted sit into one of these categories: 1) Event submission failed 2) Event submitted, then deleted without notifying the submitter 3) Event waiting for moderation 4) Event posted Simon was concerned about whether his event was in (1) or (2) vs. (3). In reality, the odds of it being stuck in (3) are so much higher than the other two that this distinction isn't of much value. It may make people feel a little better to see their event/etc. is still there awaiting moderation, but it won't actually improve anything but that perception. Now, if the "total items waiting in the moderation queue" figure was exposed, that might have been useful--essentially report the total of what's reported in the internal daily report sent to moderators right now. Had he been able to see that number was floating at around 15-ish at that point, not getting a response would have had more sense. Again, doesn't actually help the submitter in terms of improving response time, just makes them feel less singled out. -- Greg Smith 2ndQuadrant US greg@2ndQuadrant.com Baltimore, MD PostgreSQL Training, Services, and 24x7 Support www.2ndQuadrant.us