Re: Should Webinars be training events? - Mailing list pgsql-www

From Joshua D. Drake
Subject Re: Should Webinars be training events?
Date
Msg-id 1254345061.13235.222.camel@jd-desktop.iso-8859-1.charter.com
Whole thread Raw
In response to Should Webinars be training events?  (Josh Berkus <josh@agliodbs.com>)
List pgsql-www
On Wed, 2009-09-30 at 14:08 -0700, Josh Berkus wrote:
> All,
> 
> We're getting quite a few submissions in /events for webinars for
> various PostgreSQL-associated companies and topics.  I'm just not sure,
> as a moderator, whether:
> 
> a) company webinars should be bounced as too corporate, or
> b) should be regular events, or
> c) should be training events.
> 
> For the kind of event I'm talking about, see this description, which is
> typical:
> 
> ==============
> Event: Webinar: Achieving database high availability in 15 minutes with
> Tungsten
> Training event: No
> Location: City: Web-based, State: , Country: United States
> Summary:
> 
> Database downtime is one of the most common reasons for application
> failures. Unfortunately, not every product billed as an HA solution
> solves the whole problem. Tungsten clusters are packed with features
> that address database downtime efficiently and are easy to deploy. In 15
> minutes, in fact.
> ==============
> 
> I'm really honestly not sure what to do with these kinds of events.
> Seems to me we want to list them, but where?

That isn't training. I have no problem with E-Training being a training
event but ... 15 minutes is a marketing slide.

Joshua D. Drake

> 
> -- 
> Josh Berkus
> PostgreSQL Experts Inc.
> www.pgexperts.com
> 
-- 
PostgreSQL.org Major Contributor
Command Prompt, Inc: http://www.commandprompt.com/ - 503.667.4564
Consulting, Training, Support, Custom Development, Engineering
If the world pushes look it in the eye and GRR. Then push back harder. - Salamander



pgsql-www by date:

Previous
From: "David E. Wheeler"
Date:
Subject: Re: Should Webinars be training events?
Next
From: webmaster@postgresql.org
Date:
Subject: PostgreSQL moderation report: 2009-10-1