From: | Magnus Hagander <magnus(at)hagander(dot)net> |
---|---|
To: | Dave Page <dpage(at)postgresql(dot)org> |
Cc: | Chander Ganesan <chander(at)otg-nc(dot)com>, josh(at)agliodbs(dot)com, pgsql-www(at)postgresql(dot)org, Peter Eisentraut <peter_e(at)gmx(dot)net> |
Subject: | Re: Training events policy ... first test case |
Date: | 2007-11-03 17:20:36 |
Message-ID: | 472CADE4.5000807@hagander.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-www |
Dave Page wrote:
>
>> ------- Original Message -------
>> From: Chander Ganesan <chander(at)otg-nc(dot)com>
>> To: josh(at)agliodbs(dot)com
>> Sent: 03/11/07, 16:31:33
>> Subject: Re: [pgsql-www] Training events policy ... first test case
>>
>> Actually, I think that its not unusual for us to see a few enrollments
>> the week before a class... so listing classes that are "next week" is a
>> good idea - i'm sure this is a trend seen by all training companies....
>
> Here's a possibly crazy idea - how about we remove the 3 or 4 listings from /index.html altogether and replace them with a dynamically generated summary saying something like:
>
> "There are 24 training events in 9 countries scheduled over the next 6 months from OTG, EnterpriseDB, Command Prompt, 2nd Quadrant and others. View the complete schedule to find the PostgreSQL training you want."
>
> The numbers are easy to calcuate of course, and we could just grab 3 or 4 company names randomly.
I like it. Takes away the whole problem, really. So +1 from me.
//Magnus
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2007-11-03 18:15:32 | Re: Training events policy ... first test case |
Previous Message | Dave Page | 2007-11-03 17:03:31 | Re: Training events policy ... first test case |